August 18, 2017
By Electronic Delivery
Honorable Kimberly D. Bose, Secretary
Federal Energy Regulatory Commission
888 First Street, NE
Washington, DC 20426
Re: New York Independent System Operator, Inc.’s Proposed Revisions to Its
Open Access Transmission Tariff Regarding Cost Recovery for Regulated
Transmission Facilities; Docket No. ER17-___-000
Dear Secretary Bose:
Pursuant to Section 205 of the Federal Power Act1 and Part 35 of the Commission’s
Regulations,2 the New York Independent System Operator, Inc. (“NYISO”) respectfully submits
proposed revisions to Section 6.10 (“Rate Schedule 10”) and Attachment Y of its Open Access
Transmission Tariff (“OATT”) to establish a mechanism for the recovery of the costs of any
regulated transmission project that is eligible for cost allocation and recovery in the NYISO’s
Comprehensive System Planning Process (“CSPP”).3
The NYISO’s proposed revisions replace the Reliability Facilities Charge (“RFC”) in
Rate Schedule 10 with a new Regulated Transmission Facilities Charge (“RTFC”) pursuant to
which the NYISO will recover and remit the costs associated with a regulated transmission
project eligible for cost allocation and recovery in any one of the three planning processes in the
CSPP (i.e., reliability, economic, or public policy). In addition, the revisions incorporate into
Rate Schedule 10 several enhancements that the Commission has accepted in more recently filed
rate schedules in the OATT. The revisions also align the cost recovery requirements in Rate
Schedule 10 with those in the CSPP rules located in Attachment Y. Finally, the proposed
revisions clarify the manner in which the NYISO will allocate project preparation costs that
certain Developers are eligible to recover in the NYISO’s Public Policy Transmission Planning
Process (“Public Policy Process”) and specify the location in Attachment Y for any alternative
cost allocation methodology for the Public Policy Process that is approved or accepted by the
Commission.
1 16 U.S.C. § 824d.
2 18 C.F.R. § 35.13 (2016).
3 Capitalized terms not otherwise defined herein shall have the meaning specified in Section
31.1.1 of the OATT and, if not defined therein, in Section 1 of the OATT or Section 2 of the Market
Administration and Control Area Services Tariff.
Honorable Kimberly D. Bose
August 18, 2017
Page 2
The proposed revisions were approved unanimously by NYISO stakeholders in its
Management Committee.
I.
Documents Submitted
The NYISO respectfully submits the following documents with this filing letter:
1.
A clean version of the proposed revisions to the OATT (“Attachment I”); and
2.
A blacklined version of the proposed revisions to the OATT (“Attachment II”).
II.
Background
To comply with Order No. 890,4 the NYISO and the New York Transmission Owners
jointly proposed, and the Commission accepted, Rate Schedule 10, entitled “Rate Mechanism for
the Recovery of the Reliability Facilities Charge.”5 Rate Schedule 10 established the manner in
which the Reliability Facilities Charge (“RFC”), and the Long Island Power Authority (“LIPA”)
Reliability Facilities Charge (“LIPA RFC”) as applicable, would be developed, filed, and
charged to a Load Serving Entity (“LSE”) for the recovery of costs associated with regulated
transmission solutions eligible for cost allocation and recovery under the NYISO’s reliability
planning process. In general, Rate Schedule 10 provided that Transmission Owners or Other
Developers would have rate treatments on file with the Commission, which would be used to
derive and determine the revenue requirement to be used in calculating the RFC.6 The NYISO
would apply the RFC to collect revenues from each LSE based on its Actual Energy
Withdrawals and would disburse such collections to the project’s Developer.7
Subsequent to the Commission’s acceptance of the current Rate Schedule 10, the NYISO
implemented its Congestion Assessment and Resource Integration Study (“CARIS”) process for
economic transmission planning and its Public Policy Process in accordance with Order No. 890
and Order No. 1000. However, the NYISO’s tariffs do not currently include a mechanism
comparable to the RFC for the recovery and remittance of costs associated with regulated
transmission projects eligible for cost allocation and recovery under CARIS or the Public Policy
Process. Attachment Y provides that such costs will be recovered through a rate schedule filed
with and accepted by the Commission, and no such schedule exists as the NYISO has not had a
need for designated rate schedules to provide a cost recovery mechanism for transmission
projects in those processes to date.8 The NYISO, however, is currently in the process of
4 Order No. 890, FERC Stats. & Regs. ¶ 31,241, at n.339 and P 586.
5 See generally, New York Independent System Operator, Inc., Errata Compliance Filing, Docket
No. OA08-13-002 (June 27, 2008); New York Independent System Operator, Inc., 125 FERC ¶ 61,068
(2008).
6 See Section 6.10.2 of the OATT.
7 See Section 6.10.3 of the OATT.
8 See Sections 31.3.2.4.1.1.2 and 31.4.4.1.2 of the OATT.
Honorable Kimberly D. Bose
August 18, 2017
Page 3
evaluating and selecting the more efficient or cost effective solutions to two Public Policy
Transmission Needs in its Public Policy Process. The selected Public Policy Transmission
Projects would be eligible for cost allocation and recovery under the OATT. The NYISO has,
therefore, developed the new RTFC to enhance and expand the applicability of Rate Schedule
10, so that it can be used for all regulated transmission projects that are eligible for cost
allocation and recovery under the CSPP.
Rate Schedule 10 has remained largely unchanged since its acceptance by the
Commission in 2008,9 and the NYISO has not yet used Rate Schedule 10 to recover the costs of
any transmission projects. However, Rate Schedule 10 has served as a model for other rate
schedules under the OATT for the recovery of regulated transmission costs, such as the New
York Transco, LLC Transco Facilities Charge (“Rate Schedule 13”), the New York Power
Authority (“NYPA”) Marcy South Series Compensation Facilities Charge (“Rate Schedule 15”),
the Niagara Mohawk Power Corporation, d/b/a National Grid, Western New York Facilities
Charge (“Rate Schedule 17”), and the Rate Mechanism for the Recovery of the Generator
Deactivation Facilities Charge for a Regulated Transmission Solution in the Generator
Deactivation Process (“Rate Schedule 16”).10 These subsequent rate schedules have included
enhancements to the Rate Schedule 10 model, which the Commission has accepted for filing in
Rate Schedule 13, Rate Schedule 15, and Rate Schedule 17.11 The NYISO’s proposed revisions
to Rate Schedule 10 incorporate these enhancements.
III.
Description of Proposed Tariff Revisions
A.
Revisions to Rate Schedule 10
As detailed below, the NYISO proposes to revise Rate Schedule 10 to expand its scope to
encompass any regulated transmission project that is eligible for cost allocation and recovery
under the CSPP. In addition, the NYISO proposes to incorporate in Rate Schedule 10 the
enhancements previously accepted by the Commission in the similar rate schedules subsequently
filed for inclusion in the OATT (i.e., Rate Schedule 13, Rate Schedule 15, and Rate Schedule
17). These enhancements include: (i) re-ordering and consolidating provisions for clarity and
9 See New York Independent System Operator, Inc., 125 FERC ¶ 61,068 (2008).
10 See New York Power Authority, Filing, Docket No. ER16-835-000 (January 29, 2016); New
York Transco LLC, et al., Filing, Docket No. ER15-592-000 (December 4, 2014); New York Transco
LLC, et al., Offer of Partial Settlement, Docket No. ER15-592-000 (November 5, 2015); Niagara
Mohawk Power Corp. d/b/a National Grid, Western New York Facilities Charge Rate Schedule under
NYISO OATT Filing, Docket No. ER17-1629-001 (May 19, 2017); New York Independent System
Operator, Inc., Compliance Filing, Docket No. ER16-120-003 (September 19, 2016).
11 See, e.g., Section 6.13 of the OATT (Rate Schedule 13); Section 6.15 of the OATT (Rate
Schedule 15); Section 6.17 of the OATT (Rate Schedule 17). These improvements were similarly
proposed in Rate Schedule 16 as part of the NYISO’s proposed Generator Deactivation Process, which
revisions were submitted in September 2016 and currently remain pending before the Commission. See
New York Independent System Operator, Inc., Compliance Filing, Docket No. ER16-120-003 (September
20, 2016).
Honorable Kimberly D. Bose
August 18, 2017
Page 4
reduction of redundancy, (ii) updating the description of the treatment of revenues received from
Incremental Transmission Congestion Contracts (“TCCs”) and any applicable outage charges
relating thereto, and (iii) providing greater detail regarding the application of the charge to
projects developed by Unregulated Transmitting Utilities. Finally, the NYISO has relocated to
Rate Schedule 10 certain cost recovery requirements that were previously located in Attachment
Y of the OATT to consolidate the cost recovery requirements in one location and ensure
consistency within the OATT.
1. Applicability of the Regulated Transmission Facilities Charge
The NYISO proposes to replace the existing RFC with a new RTFC (or a LIPA RTFC or
NYPA RTFC, as applicable)12 that will enable the NYISO to recover from LSEs and remit to
Developers the costs approved or accepted by the Commission that are associated with any
regulated transmission project that is eligible for cost allocation and recovery pursuant to the
CSPP. Specifically, the RTFC will apply to all “Eligible Projects,” which include the
following:13
• Regulated backstop solutions proposed by a Responsible Transmission Owner in the
reliability planning process,
• Alternative regulated transmission solutions that the NYISO has selected as the more
efficient or cost-effective solution to a Reliability Need in the reliability planning
process,
• Regulated transmission Gap Solutions proposed by a Responsible Transmission
Owner,
• Alternative transmission Gap Solutions that have been determined by the appropriate
state regulatory agency(ies) as the preferred solution(s) to a Reliability Need,
• Regulated economic transmission projects that have been approved in CARIS,
• Public Policy Transmission Projects that the NYISO has selected as the more efficient
or cost-effective solution to a Public Policy Transmission Need in the Public Policy
Process,
• Public Policy Transmission Projects proposed by a Developer in the Public Policy
Process in response to a request by the New York State Public Service Commission
(“NYPSC”) or LIPA, and
12 For Eligible Projects proposed and developed by NYPA and LIPA, the proposed revisions
provide for billing and collection of applicable project costs under a separate LIPA RTFC and NYPA
RTFC as set forth in proposed Section 6.10.5 of the OATT.
13 In addition to specifically detailing an exclusive list of Eligible Projects, proposed Section
6.10.1.2 of the OATT lists types of projects that will not be eligible to recover their costs under Rate
Schedule 10 because cost recovery is provided elsewhere in the NYISO’s tariffs or the project does not
otherwise qualify for rate recovery under the OATT.
Honorable Kimberly D. Bose
August 18, 2017
Page 5
• The portion of an Interregional Transmission Project selected by the NYISO in the
CSPP that is allocated to the NYISO region pursuant to Section 31.5.7 of the OATT.
2. Calculation and Recovery of the RTFC
The NYISO will use a separate RTFC for each Eligible Project that will be billed to a
Responsible LSE.14 The establishment of separate RTFCs for each Eligible Project will provide
transparency in the NYISO’s billing and settlement procedures. The NYISO will calculate and
bill the RTFC (or LIPA RTFC or NYPA RTFC, as applicable) to each Responsible LSE across
all applicable Load Zones or Subzones in the New York Control Area (“NYCA”).
The NYISO will calculate the applicable RTFC charges for each Responsible LSE in a
manner largely consistent with the current formula in Rate Schedule 10.15 The NYISO will first
allocate the total charge associated with each Eligible Project to the applicable Load Zones or
Subzones. To do so, the NYISO will use the revenue requirement accepted or approved by the
Commission for the project for the appropriate Billing Period, as adjusted to account for
payments related to any Incremental TCCs awarded to the Eligible Project and any applicable
outage charges relating thereto.16 This amount will be allocated to the applicable Load Zone or
Subzone using the cost allocation methodology for the project prescribed in Section 31.5 of the
OATT or as otherwise accepted or approved by the Commission.17 The NYISO will then
determine the per-megawatt-hour (“MWh”) rate for each applicable Load Zone or Subzone. The
NYISO will calculate the charge for each applicable Responsible LSE in each Load Zone or
Subzone using the MWh rate and the Responsible LSE’s Actual Energy Withdrawals for the
relevant Billing Period. Lastly, the NYISO will calculate the total charge for each Responsible
LSE by summing all of the zonal or subzonal charges for the Responsible LSE for the relevant
Billing Period.
The proposed revisions to the RTFC calculation requirements in Section 6.10.3 of the
OATT incorporate the enhancements already accepted by the Commission in Rate Schedule 13,
14 The “Responsible LSEs” are those Transmission Owners, competitive LSEs, municipal
systems, and any other LSE serving Load in the Load Zones or Subzones that have been allocated costs of
the eligible transmission project pursuant to the applicable cost allocation methodology under Attachment
Y to the OATT.
15 Compare Rate Schedule 10 of the OATT with Proposed Rate Schedule 10 of the OATT; see
also New York Independent System Operator, Inc., Errata Compliance Filing, Docket No. OA08-13-002,
at p 12 (June 27, 2008).
16 See Proposed Section 6.10.3.5 of the OATT.
17 The Commission-approved cost allocation methodologies are set forth in Attachment Y of the
OATT. See, e.g., Section 31.5.3 of the OATT (reliability planning process cost allocation methodology);
Section 31.5.4 of the OATT (CARIS cost allocation methodology); Section 31.5.5 of the OATT (Public
Policy Process cost allocation methodology); Section 31.5.7 of the OATT (Interregional Transmission
Project cost allocation methodology).
Honorable Kimberly D. Bose
August 18, 2017
Page 6
Rate Schedule 15, and Rate Schedule 1718 and as proposed by the NYISO in its new Rate
Schedule 16.19 Specifically, the revisions clarify the treatment of revenues for Incremental
TCCs associated with an Eligible Project and any applicable outage charges relating thereto.
Proposed Section 6.10.3.3 of the OATT requires a Developer of an Eligible Project to
request Incremental TCCs in accordance with Attachment M to the OATT. To the extent that
Incremental TCCs are awarded as a result of the implementation of an Eligible Project, the
Developer will be required to offer such Incremental TCCs in all rounds of the six month Sub-
Auction of each Centralized TCC Auction conducted by the NYISO.20 The NYISO will
disburse any revenues resulting from auction sales to the Developer. To the extent that
Incremental TCCs are not sold in the Centralized TCC Auctions conducted by the NYISO, the
NYISO will provide congestion payments to the Developer for any unsold Incremental TCCs in
accordance with Section 20.2.3 of Attachment N to the OATT. The NYISO will adjust the
otherwise applicable revenue requirement for the Eligible Project to account for these settlements
related to Incremental TCCs.21
The proposed revisions also account for certain outage charges specific to Incremental
TCCs for Eligible Projects in calculating the RTFC rate. Any applicable outage charge related to
Incremental TCCs awarded for the Eligible Project shall be determined and assessed to the
Developer pursuant to Section 19.2.4 of Attachment M to the OATT.22 The NYISO will adjust
the otherwise applicable revenue requirement for the Eligible Project to account for any
applicable outage charges assessed to the Developer for any hour in the Day-Ahead Market
during which the Eligible Project is modeled as wholly or partially out of service.
3. Determining the Revenue Requirement for Calculation of the RTFC
The annual revenue requirement for an Eligible Project, used in calculating the RTFC
rate, will be determined in accordance with proposed Sections 6.10.4 and 6.10.5 of the OATT.
The proposed revisions clarify and consolidate in Rate Schedule 10: (i) the description of the
costs, rate of return, and incentives, as applicable, that may be included in the revenue
requirement; (ii) the period of cost recovery; and (iii) the manner in which the revenue
requirement will be filed with the Commission.23 As revised, Rate Schedule 10 will ensure
consistent treatment of the revenue requirement for Transmission Owners and Other Developers,
while respecting the differences in the revenue requirement for a project developed by an
Unregulated Transmitting Utility.
18 Sections 6.13, 6.15, 6.17 of the OATT.
19 See New York Independent System Operator, Inc., Compliance Filing, Docket No. ER16-120-
003, at Attachment I (September 19, 2016).
20 See Proposed Section 6.10.3.3 of the OATT.
21 See Proposed Section 6.10.3.5 of the OATT.
22 See id.
23 See Proposed Sections 6.10.2, 6.10.4, and 6.10.5 of the OATT.
Honorable Kimberly D. Bose
August 18, 2017
Page 7
For all Eligible Projects, the revenue requirement may include all reasonably incurred
costs related to the preparation of proposals for, and the development, financing, construction,
operation, and maintenance of, an Eligible Project, including those explicit costs set forth in
Attachment Y of the OATT and a reasonable rate of return on investment.24 With the exception
of an Eligible Project developed by LIPA, a reasonable rate of return may also include any
incentives for the construction of transmission projects approved by the Commission under
Section 205 or Section 219 of the Federal Power Act and associated implementing regulations.25
a. Transmission Owner or Other Developer
Revised Section 6.10.4 of the OATT provides that a revenue requirement for a project
developed by a Transmission Owner or Other Developer may be based on either a formula rate
on file with the Commission or pursuant to a Section 205 filing with the Commission.26 The
Transmission Owner or Other Developer (or, at its request, the NYISO)27 shall make either a
Section 205 filing or an informational filing under a previously approved formula rate proposing
a revenue requirement for each Eligible Project. The revenue requirement must be consistent
with the Eligible Project as it was proposed to and evaluated by the NYISO pursuant to
Attachment Y.28 The revenue requirement and the period of recovery will be determined by the
Commission, and cost recovery will begin at the time the project enters service, is halted, or as
otherwise determined by the Commission, including for the recovery of construction work in
progress (“CWIP”) or other permissible cost recovery.29
b. Unregulated Transmitting Utilities
Revised Section 6.10.5 covers the revenue requirements for the LIPA RTFC or NYPA
RTFC for Eligible Projects developed by LIPA or NYPA, respectively.30 This section accounts
for the differences related to the recovery of costs by an Unregulated Transmitting Utility and
details the Eligible Project’s revenue requirement to be used in the calculation and recovery of
24 See Proposed Sections 6.10.4.1 and 6.10.5.1 of the OATT.
25 See Proposed Sections 6.10.4.1 and 6.10.5.3 of the OATT.
26 Rate Schedule 10 previously divided the requirements applicable to Transmission Owners and
Other Developers into separate sections. As revised, the consolidated requirements are consistent for both
Transmission Owners and Other Developers as included in proposed Section 6.10.4 of the OATT. The
previous Transmission Owner and Other Developer-specific sections have been deleted.
27 Where the NYISO makes the filing, the Transmission Owner or Other Developer bears the
burden of resolving all concerns about the contents of the filing that might arise in that proceeding. See
Proposed Section 6.10.4.2 of the OATT.
28 See Proposed Section 6.10.4.2 of the OATT.
29 See id.
30 Rate Schedule 10 previously described general rules applicable to Unregulated Transmitting
Utilities with more detailed requirements for LIPA, but did not specify specific revenue requirement rules
applicable to NYPA. As proposed, Rate Schedule 10 includes specific rules for a NYPA RTFC.
Honorable Kimberly D. Bose
August 18, 2017
Page 8
the LIPA RTFC and NYPA RTFC, the period of recovery, the special considerations in filing
and determining the revenue requirement for LIPA and NYPA, and the roles of the NYISO in
the billing and settlement of the LIPA RTFC and NYPA RTFC.
The NYISO proposes to retain the provisions governing an Eligible Project developed by
LIPA but expands upon them to include any regulated transmission project proposed and/or
selected under the CSPP and to incorporate other enhancements. Notably, Rate Schedule 10
retains the distinction between billing and recovering the costs of an Eligible Project undertaken
by LIPA from LIPA customers within the Long Island Transmission District and from
Responsible LSEs in other Transmission Districts. Section 6.10.5.2.1 provides that for costs to
LIPA customers, LIPA will bill and charge each responsible entity within the Long Island
Transmission District using a rate recovery mechanism that it approves and over a period of cost
recovery established by the LIPA Board of Trustees.31
For costs to Responsible LSEs outside of the Long Island Transmission District, LIPA
will inform the NYISO of its costs incurred in undertaking an Eligible Project that are allocable
to such Responsible LSEs.32 These costs shall constitute the revenue requirement that the
NYISO will file, at LIPA’s request, with the Commission. That revenue requirement must be
consistent with LIPA’s project proposed to and evaluated by the NYISO under Attachment Y,
and LIPA shall bear the burden of resolving all concerns about the revenue requirement filing
submitted on its behalf by the NYISO.33 Once accepted or approved by the Commission, the
NYISO will (i) use that revenue requirement to calculate a separate LIPA RTFC over the period
of cost recovery determined by the Commission; (ii) bill Responsible LSEs outside of the Long
Island Transmission District; and (iii) remit the revenues collected to LIPA in accordance with
the NYISO’s billing and settlement procedures.34
The NYISO also proposes to add Section 6.10.5.3 of the OATT to address the recovery
of costs incurred by NYPA in developing an Eligible Project. Specifically, NYPA will inform
the NYISO of any costs incurred for an Eligible Project, which may include a reasonable rate of
return on investment and any incentives for construction of transmission projects available under
Section 205 and Section 219 of the FPA and the Commission’s associated implementing
regulations.35 The incurred costs will constitute the revenue requirement, provided it is
consistent with NYPA’s project as proposed to and evaluated by the NYISO under Attachment
Y.36 The revenue requirement will then be filed as an informational filing under NYPA’s
already existing formula rate approved by the Commission. NYPA will bear the burden for
resolving all concerns raised in the proceeding before the Commission related to such
31 See Proposed Sections 6.10.3.6 and 6.10.5.2 of the OATT.
32 See Proposed Section 6.10.5.2.2 of the OATT.
33 Id.
34 Id.
35 See Sections 6.10.5.1 and 6.10.5.3 of the OATT.
36 See Section 6.10.5.3.1 of the OATT.
Honorable Kimberly D. Bose
August 18, 2017
Page 9
informational filing. Once the filing is accepted or approved or otherwise allowed to go into
effect pursuant to NYPA’s formula rate, the NYISO will (i) calculate a separate NYPA RTFC
for the period of cost recovery determined by the Commission; (ii) bill Responsible LSEs; and
(iii) remit collected revenues to NYPA in accordance with the NYISO’s billing and settlement
procedures.37
4. Consolidation of Cost Recovery Requirements from Attachment Y
Attachment Y to the OATT currently includes certain cost recovery requirements for
regulated transmission projects developed under the CSPP. The NYISO proposes to relocate
certain provisions from Section 31.5.6 to Rate Schedule 10 that address the costs eligible to be
recovered, the period of recovery, the filing of a revenue requirement, and the awarding of
Incremental TCCs on a regulated transmission project under the CSPP.38
B.
Conforming Tariff Revisions to Attachment Y to the OATT
Attachment Y to the OATT currently contains numerous requirements and references
concerning the recovery of costs associated with regulated transmission projects under the CSPP.
The NYISO proposes to align certain provisions of Attachment Y concerning cost allocation and
recovery with the revised Rate Schedule 10 to ensure consistency in the OATT and reduce
unnecessary repetition. The revisions provide the necessary linkages across the planning
processes, cost allocation provisions, and the cost recovery requirements, while consolidating the
core cost recovery requirements in Rate Schedule 10.
Section 31.5.6 of the OATT contains cost recovery requirements for the regulated
solutions under the CSPP. As discussed above, the NYISO proposes to relocate certain cost
recovery requirements from Section 31.5.6 to Rate Schedule 10. To reduce redundancy and
ensure consistency between Rate Schedule 10 and Attachment Y, the NYISO proposes to update
Section 31.5.6 to be consistent with the revised scope of Rate Schedule 10 and eliminate those
provisions that have been relocated to Rate Schedule 10.39
37 See Proposed Sections 6.10.5.1 and 6.10.5.3 of the OATT.
38 See Proposed Section 6.10.
39 See, e.g., Proposed Section 31.5.6.1 (regulated project to address a Reliability Need); Proposed
Section 31.5.6.2 (regulated economic transmission project); Proposed Section 31.5.6.3 (regulated
transmission project to address a Public Policy Transmission Need); Proposed Section 31.5.6.4
(Interregional Transmission Project selected by the NYISO in the CSPP).
Honorable Kimberly D. Bose
August 18, 2017
Page 10
The NYISO also proposes the following conforming revisions to Attachment Y:
Tariff Section
Reason for Proposed Revision
Clarified and ensured consistency with the proposed revisions to Rate
OATT Section
Schedule 10 related to the time period of a regulated transmission project’s
31.2.6.5.2
cost recovery—i.e., when the project enters into service, is halted, or as
otherwise determined by the Commission.
Clarified that the recovery of costs incurred in connection with a regulated
backstop solution that has been halted is subject to the Commission’s
regulations on abandoned plant recovery. The Commission previously
directed the NYISO to amend the cost recovery requirements for halted
OATT Section
projects in its Public Policy Process to expressly reference the
31.2.8.2.1
Commission’s regulations on abandoned plant recovery.40 The proposed
revision in Section 31.2.8.2.1 aligns the cost recovery requirements in the
reliability planning process concerning halted projects with the related
requirements in the Public Policy Process.
Clarified that the recovery of costs incurred in connection with an
alternative regulated transmission project that has been triggered and
OATT Section
subsequently halted is subject to the Commission’s regulations on
31.2.8.2.2
abandoned plant recovery to align this provision with the Commission’s
directive for the Public Policy Process to expressly reference its regulations
on abandoned plant recovery.41
Clarified that the recovery of costs incurred in connection with a regulated
backstop solution or a triggered alternative regulated transmission project
that does not receive the necessary federal, state, or local agency(ies)
OATT Section
authorizations is subject to the Commission’s regulations on abandoned
31.2.8.2.5
plant recovery, to align this provision with the Commission’s directive for
the Public Policy Process to expressly reference its regulations on
abandoned plant recovery.42
Clarified that the recovery of costs incurred in connection with a regulated
backstop solution or a triggered alternative regulated transmission project
that has its necessary federal, state, and local authorization subsequently
OATT Section
withdrawn is subject to the Commission’s regulations on abandoned plant
31.2.8.2.6
recovery, to align this provision with the Commission’s directive for the
Public Policy Process to expressly reference its regulations on abandoned
plant recovery.43
40 New York Independent System Operator, Inc., 155 FERC ¶ 61,037 at P 22 (2016).
41 Id.
42 Id.
43 Id.
Honorable Kimberly D. Bose
August 18, 2017
Page 11
Tariff Section
Reason for Proposed Revision
Incorporated the requirement that a Responsible Transmission Owner shall
be eligible to recover its costs related to developing a Gap Solution proposal
OATT Section
and seeking necessary approvals to align this provision with the cost
31.2.11.4
recovery requirements in Section 31.5.6 of Attachment Y and Rate Schedule
10.
OATT Section
Clarified that an implemented transmission Gap Solution is entitled to cost
31.2.11.6
recovery under Section 31.5.6 of Attachment Y and Rate Schedule 10.
OATT Section
Clarified that the cost recovery mechanism for a regulated transmission
31.3.2.4.1.1.2
project under CARIS is set forth in Rate Schedule 10.
OATT Section
Clarified that the cost recovery mechanism for a regulated transmission
31.4.3.2
project under the Public Policy Process is set forth in Rate Schedule 10.
OATT Section
Clarified that the cost recovery mechanism for a regulated transmission
31.4.4.1.2
project under the Public Policy Process is set forth in Rate Schedule 10.
Clarified and ensure consistency with the proposed revisions to Rate
OATT Section
Schedule 10 related to when the costs of the regulated transmission project
31.4.8.2
are recoverable—i.e., when the project enters into service, is halted, or as
otherwise determined by the Commission.
OATT Section
Clarified that the cost recovery mechanism for a regulated transmission
31.4.12.1
project under the Public Policy Process is set forth in Rate Schedule 10.
OATT Section
Replaced the generic reference to an applicable rate schedule with a
31.5.1.7
reference to Rate Schedule 10.
OATT Section
Incorporated clarifying references to Rate Schedule 10.
31.5.4.4.6
Incorporated references to Rate Schedule 10 and added a clarifying
OATT Section
reference related to cost recovery for the costs of proposing a Public Policy
31.5.5.3
Transmission Project submitted by a Developer at the request for the
NYPSC or LIPA pursuant to Section 31.4.3.2 of the OATT.
Added a cross-reference to Rate Schedule 10 under Article 8 of the pro
OATT Section
forma Development Agreement with regard to cost recovery in the event of
31.7
termination of the Development Agreement.
C.
Proposed Revisions Related to Cost Allocation in the Public Policy
Process
The NYISO also proposes revisions to: (i) clarify the cost allocation methodology for
certain costs incurred by Developers in preparing proposed solutions to Public Policy
Honorable Kimberly D. Bose
August 18, 2017
Page 12
Transmission Needs at the request of the NYPSC or LIPA in the Public Policy Process and (ii) to
reference the location in the OATT where an alternative cost allocation methodology for a
particular Public Policy Transmission Project will be located once accepted or approved by the
Commission.44
As part of the Public Policy Process, Section 31.4.3.2 of the OATT provides that a
Developer that proposes a transmission solution to a Public Policy Transmission Need in
response to a request by the NYPSC or LIPA may recover its “[c]osts incurred . . . in preparing a
proposed transmission solution.”45 Attachment Y, however, does not specify how the NYISO
should allocate these costs for projects that it has not selected as the more efficient or cost-
effective project in its Public Policy Process.
The NYISO proposes to revise Sections 31.4.3.2 and 31.5.5.3 of the OATT to provide
that, unless otherwise determined by the Commission, costs Developers incur in preparing a
proposed transmission solution, which is prepared at the request of the NYPSC or LIPA but not
selected by the NYISO, will be allocated among all LSEs in the NYCA using the load ratio share
methodology contained in Section 31.5.5.4.3 of the OATT.46 Allocating these project
preparation costs across all LSEs in the NYCA, using the load ratio share methodology accepted
by the Commission, is just and reasonable because all ratepayers throughout the State of New
York benefit from having a robust transmission project solicitation and selection process to
satisfy transmission needs driven by Public Policy Requirements.47
The NYISO also proposes to revise Section 31.5.5.4 of the OATT to provide a cross-
reference to the alternative cost allocation methodologies that are accepted or approved by the
Commission for a particular Public Policy Transmission Project, which methodologies will be
located in Appendix E (Section 31.8) of Attachment Y.48 Currently, Attachment Y does not
specify a specific place in the OATT where such alternative cost allocation methodologies for
44 See Proposed Sections 31.4.3.2 and 31.5.5.4 of the OATT
45 This requirement does not apply to a Developer whose project is ultimately selected by the
NYISO as the more efficient or cost-effective transmission solution because that Developer will recover
its project costs that are accepted or approved by the Commission through the cost allocation
methodology applicable to that Public Policy Transmission Need, as set forth in Section 31.5.5.4 of the
OATT.
46 See Proposed Section 31.4.3.2 of the OATT.
47 Section 31.5.5.4.3 establishes a load ratio share methodology to allocate the costs of projects
selected in the NYISO’s Public Policy Process. The Commission has accepted this methodology as a just
and reasonable default methodology, which methodology the NYISO will apply to projects selected in the
Public Policy Process if no alternative methodology is proposed or determined to be just and reasonable
by the Commission.
48 See Proposed Section 31.5.5.4 of the OATT.
Honorable Kimberly D. Bose
August 18, 2017
Page 13
Public Policy Transmission Projects will be located. This clean-up revision sets aside a specific
location and, therefore, will increase the ease of locating such methodologies in Attachment Y.49
IV.
Effective Date
The NYISO respectfully requests that the Commission make the tariff revisions proposed
in this filing effective on the day following the end of the statutory sixty-day notice period—i.e.,
October 18, 2017.
V.
Stakeholder Approval
The NYISO presented on the proposed revisions to Rate Schedule 10 and Attachment Y
at meetings of its stakeholder Electric System Planning Working Group on March 23, 2017 and
April 19, 2017. The proposed revisions were unanimously approved by the NYISO Business
Issue Committee and Operating Committee on May 17, 2017 and May 18, 2017, respectively.
Thereafter, the NYISO Management Committee unanimously approved the proposed revisions
on May 31, 2017. The NYISO Board of Directors approved the filing of these proposed
revisions on June 19, 2017.
VI.
Communications and Correspondence
All communications and service in this proceeding should be directed to:
Robert E. Fernandez, General Counsel
*Ted Murphy
Raymond Stalter, Director, Regulatory Affairs
Hunton & Williams LLP
* Carl F. Patka, Assistant General Counsel
2200 Pennsylvania Ave, NW
* Brian R. Hodgdon, Attorney
Washington, DC 20037
10 Krey Boulevard
Tel: (202) 955-1500
Rensselaer, NY 12144
tmurphy@hunton.com
Tel: (518) 356-6000
rfernandez@nyiso.com
rstatler@nyiso.com
*Michael J. Messonnier50
cpatka@nyiso.com
Hunton & Williams LLP
bhodgdon@nyiso.com
Riverfront Plaza, East Tower
951 East Byrd Street
Richmond, VA 23219
Tel: (804) 788-8712
mmessonnier@hunton.com
*Persons designated for receipt of service.
49 See, e.g., Sections 31.5.5.4.1 through 31.5.5.4.2.5 of the OATT.
50 Waiver of the Commission’s regulations (18 C.F.R. § 385.203(b)(3) (2014)) is requested to the
extent necessary to permit service on counsel for the NYISO in Rensselaer, NY, Richmond, VA, and
Washington, DC.
Honorable Kimberly D. Bose
August 18, 2017
Page 14
VII.
Service
The NYISO will send an electronic link to this filing to the official representative of each
of its customers, to each participant on its stakeholder committees, to the New York State Public
Service Commission, and to the New Jersey Board of Public Utilities. In addition, the complete
filing will be posted on the NYISO’s website at www.nyiso.com.
VIII.
Conclusion
For the reasons stated above, the New York Independent System Operator, Inc.
respectfully requests that the Commission accept for filing the proposed revisions to the OATT
that are attached hereto with an effective date of October 18, 2017.
Respectfully submitted,
/s/ Carl F. Patka
Carl F. Patka, Assistant General Counsel
Brian R. Hodgdon, Attorney
New York Independent System Operator, Inc.
10 Krey Blvd.
Rensselaer, New York 12144
Tel: (518) 356-6000
cpatka@nyiso.com
Michael J. Messonnier Jr.
Hunton & Williams LLP
951 East Byrd Street
Richmond, Virginia 23219
mmessonnier@hunton.com
cc:
Michael Bardee
Anna Cochrane
Jette Gebhart
Kurt Longo
David Morenoff
Daniel Nowak
Larry Parkinson
J. Arnold Quinn
Douglas Roe
Kathleen Schnorf
Gary Will
6.10
Schedule 10 - Rate Mechanism for the Recovery of the Regulated Transmission
Facilities Charge (“RTFC”)
6.10.1
Applicability.
6.10.1.1 Eligible Projects
This Schedule establishes the Regulated Transmission Facilities Charge (“RTFC”) for the
recovery of the costs of a regulated transmission project that is eligible for cost recovery in
accordance with the Comprehensive System Planning Process requirements set forth in
Attachment Y of the ISO OATT.1 A Transmission Owner, Unregulated Transmitting Utility,2 or
Other Developer may recover through the RTFC the costs that it is eligible to recover pursuant to
Attachment Y of the ISO OATT related to: (i) a regulated backstop transmission solution
proposed by a Responsible Transmission Owner pursuant to Section 31.2.4.3.1 of Attachment Y
of the ISO OATT and the ISO/TO Reliability Agreement or an Operating Agreement; (ii) an
alternative regulated transmission solution that the ISO has selected pursuant to Section
31.2.6.5.2 of Attachment Y of the ISO OATT as the more efficient or cost-effective solution to a
Reliability Need; (iii) a regulated transmission Gap Solution proposed by a Responsible
Transmission Owner pursuant to Section 31.2.11.4 of Attachment Y of the ISO OATT; (iv) an
alternative regulated transmission Gap Solution that has been determined by the appropriate state
regulatory agency(ies) as the preferred solution(s) to a Reliability Need pursuant to Section
31.2.11.5 of Attachment Y of the ISO OATT; (v) a regulated economic transmission project that
has been approved pursuant to Section 31.5.4.6 of Attachment Y of the ISO OATT; (vi) a Public
Policy Transmission Project that the ISO has selected pursuant to Section 31.4.8.2 of Attachment
1 Capitalized terms used in this Schedule that are not defined in this Schedule shall have the meaning set
forth in Section 31.1.1 of Attachment Y of the ISO OATT and, if not therein, in Section 1 of the OATT.
2 An “Unregulated Transmitting Utility” is a Transmission Owner, such as LIPA and NYPA, that,
pursuant to Section 201(f) of the Federal Power Act, is not subject to the Commission’s jurisdiction under
Sections 205 and 206(a) of the Federal Power Act.
Y of the ISO OATT as the more efficient or cost-effective solution to a Public Policy
Transmission Need; (vii) a Public Policy Transmission Project proposed by a Developer in
response to a request by the NYPSC or Long Island Power Authority in accordance with Section
31.4.3.2 of Attachment Y of the ISO OATT; or (viii) the portion of an Interregional
Transmission Project selected by the ISO in the CSPP that is allocated to the NYISO region
pursuant to Section 31.5.7 of Attachment Y of the ISO OATT. For purposes of this Schedule,
such a transmission project is referred to as an “Eligible Project.” The costs incurred for an
Eligible Project by LIPA or NYPA will be billed and collected under a separate LIPA RTFC or
NYPA RTFC, as applicable, as described in Section 6.10.5.
6.10.1.2 Projects Not Eligible for Cost Recovery Through the RTFC
This Schedule does not apply to projects that are not eligible pursuant to Attachment Y of
the ISO OATT for cost allocation and recovery under the ISO OATT, including, but not limited
to: (i) projects undertaken by Transmission Owners through the Local Transmission Owner
Planning Processes pursuant to Section 31.1.3 and Section 31.2.1 of Attachment Y of the ISO
OATT; (ii) market-based solutions to transmission needs identified in the CSPP; (iii) any non-
transmission components of an Eligible Project (e.g., generation, energy efficiency, or demand
response resources); (iv) transmission Generator Deactivation Solutions selected in the Generator
Deactivation Process pursuant to Attachment FF of the ISO OATT and eligible for cost recovery
through Schedule 16 (Section 6.16) of the ISO OATT; (v) transmission facilities eligible for cost
recovery through another rate schedule of the ISO OATT; and (vi) facilities for which costs are
recovered through the Transmission Service Charge (“TSC”) or the NYPA Transmission
Adjustment Charge (“NTAC”) determined in accordance with Attachment H of the ISO OATT..
6.10.2
Revenue Requirement for RTFC
The RTFC (including a LIPA RTFC or NYPA RTFC, as applicable) shall be calculated
in accordance with the formula set forth in Section 6.10.3 using the revenue requirement of the
Transmission Owner, Unregulated Transmitting Utility, or Other Developer, as applicable,
necessary to recover the costs of an Eligible Project. The revenue requirement to be used in the
calculation and recovery of the RTFC for a Transmission Owner or Other Developer, other than
an Unregulated Transmitting Utility, is described in Section 6.10.4. The development of a
revenue requirement and recovery of costs for an Eligible Project by an Unregulated
Transmitting Utility through a NYPA RTFC or a LIPA RTFC, as applicable, is described in
Section 6.10.5.
If an Eligible Project involves the construction of a facility identified as a Highway
System Deliverability Upgrade in a completed Class Year Interconnection Facilities Study, the
Project Cost Allocation for which has been accepted and Security posted by at least one Class
Year Developer, the project cost and resulting revenue requirement will be reduced to the extent
permitted by Section 25.7.12.3.3 of Attachment S of the ISO OATT.
6.10.3
Calculation and Recovery of RTFC and Payment of Recovered Revenue
6.10.3.1
The ISO will calculate and bill an RTFC (or a LIPA RTFC or NYPA
RTFC, as applicable) separately for each Eligible Project in accordance with this
Section 6.10.3. The ISO shall collect the RTFC from LSEs. The LSEs, including
Transmission Owners, competitive LSEs, municipal systems, and any other
LSEs, serving Load in the Load Zones and/or Subzones to which the costs of the
Eligible Project have been allocated (each a “Responsible LSE”) shall pay the
RTFC. The cost of each Eligible Project shall be allocated as follows: (i) the
costs of an Eligible Project that is eligible for cost allocation and recovery through
the reliability planning process shall be allocated in accordance with Section
31.5.3 of Attachment Y of the ISO OATT; (ii) the costs of an Eligible Project that
is eligible for cost allocation and recovery through the CARIS process shall be
allocated in accordance with Section 31.5.4 of Attachment Y of the ISO OATT;
(iii) the costs of an Eligible Project that is eligible for cost allocation and recovery
through the Public Policy Transmission Planning Process shall be allocated in
accordance with Section 31.5.5 of Attachment Y of the ISO OATT; and (iv) the
costs of an Eligible Project that is eligible for cost allocation and recovery as an
Interregional Transmission Project shall be allocated in accordance with Section
31.5.7 of Attachment Y of the ISO OATT.
6.10.3.2
The revenue requirement established by the Transmission Owner or Other
Developer pursuant to Section 6.10.4 and an Unregulated Transmitting Utility
pursuant to Section 6.10.5 will be the basis for the applicable RTFC Rate
($/MWh) that shall be charged by the ISO to each Responsible LSE based on its
Actual Energy Withdrawals as set forth in Section 6.10.3.5.
6.10.3.3
The Developer shall request Incremental TCCs with respect to the Eligible
Project in accordance with the requirements of Section 19.2.4 of Attachment M of
the ISO OATT and receive any Incremental TCCs to the extent awarded by the
ISO pursuant to such request. As it relates solely to the Eligible Project, the
Developer shall not be a “Transmission Owner” for purposes of Section 20.2.5 or
Section 20.3.7 of Attachment N of the ISO OATT and accordingly shall not
receive an allocation of Net Congestion Rents under Section 20.2.5 of Attachment
N of the ISO OATT or Net Auction Revenues under Section 20.3.7 of Attachment
N of the ISO OATT.
The Developer shall in relation to any Eligible Project exercise its right to
obtain and maintain in effect all Incremental TCCs, including temporary
Incremental TCCs, to which it has rights under Section 19.2.4 of Attachment M of
the ISO OATT and shall take the actions required to do so in accordance with the
procedures specified therein. Notwithstanding Sections 19.2.4.7 and 19.2.4.8 of
Attachment M of the ISO OATT, Incremental TCCs created and awarded to the
Developer as a result of implementation of an Eligible Project shall not be eligible
for sale in Secondary Markets. Incremental TCCs that may be created and
awarded to the Developer as a result of the implementation of an Eligible Project,
shall be offered by the Developer in all rounds of the six month Sub-Auction of
each Centralized TCC Auction conducted by the ISO. The ISO shall disburse the
associated auction revenues to the Developer. The total amount of the auction
revenues disbursed to the Developer pursuant to this Section 6.10.3.3 shall be
used in the calculation of the RTFC Rate, as set forth in Section 6.10.3.5.
Incremental TCCs associated with an Eligible Project shall continue to be offered
for the duration of the Incremental TCCs, established pursuant to the terms of
Attachment M of the ISO OATT.
The revenue offset discussed in this Section 6.10.3.3 shall commence
upon the first payment of revenues related to Incremental TCCs associated with
the implementation of an Eligible Project on or after the date the RTFC is
implemented. The RTFC and the revenue offset related to Incremental TCCs
associated with the implementation of an Eligible Project shall not require and
shall not be dependent upon a reopening or review of: (i) the Developer’s revenue
requirements for the RTFC of another Eligible Project pursuant to this Section
6.10 of the ISO OATT, (ii) the Developer’s revenue requirement for charges set
forth in another rate schedule of the ISO OATT, or (iii) the Transmission Owners’
revenue requirements for the TSCs or NTAC set forth in Attachment H of the ISO
OATT. 6.10.3.3.1 With respect to the Eligible Project only, the Developer
shall receive the outage charges described herein and shall not be charged O/R-t-S
Congestion Rent Shortfall Charges, U/D Congestion Rent Shortfall Charges, O/R-
t-S Auction Revenue Shortfall Charges or U/D Auction Revenue Shortfall
Charges or be paid O/R-t-S Congestion Rent Surplus Payments, U/D Congestion
Rent Surplus Payments, O/R-t-S Auction Revenue Surplus Payments or U/D
Auction Revenue Surplus Payments under Section 20.2.4 and Section 20.3.6 of
Attachment N of the ISO OATT. Outage charges related to any Incremental
TCCs awarded by the ISO for an Eligible Project shall be assessed to the
Developer, and payable by the Developer to the ISO, pursuant to Section 19.2.4
of Attachment M of the ISO OATT for an Expander not subject to Section 20.2.5
of Attachment N of the ISO OATT for any hour in the Day-Ahead Market during
which an Expansion, associated with an Eligible Project, is modeled to be wholly
or partially out of service.
6.10.3.4
The billing units for the RTFC Rate for the Billing Period shall be based
on the Actual Energy Withdrawals available for the current Billing Period for
those Load Zones and/or Subzones allocated the costs of the project in the manner
described in Section 6.10.3.1.
6.10.3.5 Cost Recovery Methodology
The ISO shall calculate the RTFC for each Eligible Project for each Responsible LSE as
follows:
Step 1: Calculate the $ assigned to each Load Zone or Subzone (as applicable)
RTFCp,z,B = �AnnualRRp,B − IncrementalTransmissionRightsRevenuep,B + OutageCostAdjustmentp,B�
× �ZonalCostAllocationz,p�
Step 2: Calculate a per-MWh Rate for each Load Zone or Subzone (as applicable)
RTFCRatep,z,B = RTFCp,z,B/MWhz,B
Step 3: Calculate charge for each Billing Period for each Responsible LSE in each
Load Zone or Subzone (as applicable)
ChargeB,l,z,p = RTFCRatep,z,B ∗ MWhl,z,B
Step 4: Calculate charge for each Billing Period for each Responsible LSE across all
Load Zones or Subzones (as applicable)
ChargeB,l,p = ��ChargeB,l,z,p�
z∈Z
Where,
l = the relevant Responsible LSE;
p = an individual Eligible Project;
z = an individual Load Zone or Subzone, as applicable;
Z = set of ISO Load Zones or Subzones, as applicable;
B = the relevant Billing Period;
MWhz,B = Actual Energy Withdrawals in Load Zone or Subzone, as applicable, z aggregated
across all hours in Billing Period B;
MWhl,z,B = Actual Energy Withdrawals for Responsible LSE l in Load Zone or Subzone, as
applicable, z aggregated across all hours in Billing Period B;
AnnualRRp,B = the pro rata share of the annual revenue requirement for each Eligible Project p
as discussed in Section 6.10.2 above, allocated for Billing Period B;
IncrementalTransmissionRightsRevenuep,B = the auction revenue derived from the sale of
Incremental TCCs plus Incremental TCC payments received by the Developer pursuant to
Section 20.2.3 of Attachment N of the ISO OATT for each Eligible Project p, as discussed in
Section 6.10.3.3 above, allocated for Billing Period B. The revenues from the sale of
Incremental TCCs in the ISO’s six month Sub-Auctions of each Centralized TCC Auction shall
be allocated uniformly across all hours of the Billing Period;
OutageCostAdjustmentp,B = the Outage charges determined pursuant to Section 6.10.3.3.1 above
for any hour in the Day-Ahead Market during which the Eligible Project p is modeled to be
wholly or partially out of service aggregated across all hours in Billing Period B; and
ZonalCostAllocationz,p = the proportion of the cost of Eligible Project p allocated to Load Zone
or Subzone, as applicable, z, in the manner described in Section 6.10.3.1 above.
6.10.3.6
The NYISO will collect the appropriate RTFC revenues each Billing
Period and remit those revenues to the appropriate Transmission Owner,
Unregulated Transmitting Utility, or Other Developer in accordance with the
NYISO’s billing and settlement procedures; provided, however, that LIPA will be
responsible for billing and collecting the costs of an Eligible Project undertaken
by LIPA that are allocated to customers within the Long Island Transmission
District in accordance with Section 6.10.5.2.1.
6.10.4
Recovery of Costs Incurred by Transmission Owner or Other Developer
6.10.4.1
The RTFC shall be used as the cost recovery mechanism for the recovery
of the costs of an Eligible Project undertaken by a Transmission Owner or Other
Developer, other than an Unregulated Transmitting Utility, which project is
authorized by the Commission to recover costs under this rate mechanism;
provided, however, nothing in this cost recovery mechanism shall be deemed to
create any additional rights for a Transmission Owner or Other Developer to
proceed with a regulated transmission project that it does not otherwise have at
law. The costs that may be included in the revenue requirement for calculating
the RTFC pursuant to Section 6.10.3 include all reasonably incurred costs, as
determined by the Commission, related to the preparation of proposals for, and
the development, financing, construction, operation, and maintenance of, an
Eligible Project, including those costs explicitly permitted for recovery pursuant
to Attachment Y of the ISO OATT. These costs include, but are not limited to, a
reasonable return on investment and any incentives for the construction of
transmission projects approved under Section 205 or Section 219 of the Federal
Power Act and the Commission’s regulations implementing those sections.
6.10.4.2
The period for cost recovery will be determined by the Commission and
will begin if and when the Eligible Project enters into service, is halted, or as
otherwise determined by the Commission, including for the recovery of CWIP or
other permissible cost recovery. The Transmission Owner/Other Developer, or, at
its request, the ISO, shall either make a Section 205 filing with the Commission or
make an informational filing under a formula rate to provide for the
Commission’s review and approval or acceptance of the project cost and resulting
revenue requirement to be recovered through the RTFC. The filing may include
all reasonably incurred costs specified in Section 6.10.4.1 of this Schedule that are
related to the Transmission Owner’s or the Other Developer’s undertaking an
Eligible Project. The filing must be consistent with the Transmission Owner’s or
the Other Developer’s project proposal made to and evaluated by the ISO
pursuant to Attachment Y. The Transmission Owner or Other Developer shall
bear the burden of resolving all concerns about the contents of the filing that
might be raised in such proceeding. The ISO will begin to calculate and bill the
RTFC in accordance with the period for cost recovery determined by the
Commission after the Commission has accepted or approved the filing or
otherwise allowed the filing to go into effect pursuant to a formula rate.
6.10.5
Recovery of Costs by an Unregulated Transmitting Utility.
6.10.5.1
The costs that may be included in the revenue requirement for an Eligible
Project undertaken by an Unregulated Transmitting Utility include all reasonably
incurred costs related to the preparation of proposals for, and the development,
financing, construction, operation, and maintenance of, an Eligible Project,
including those costs explicitly permitted for recovery pursuant to Attachment Y
of the ISO OATT, as well as a reasonable return on investment. Except as
otherwise provided in Section 6.10.5.2.1, for any recovery of a revenue
requirement by an Unregulated Transmitting Utility under the RTFC, the period
of cost recovery will be determined by the Commission and will begin if and
when the Eligible Project enters into service, is halted, or as otherwise determined
by the Commission, including for the recovery of CWIP or other permissible cost
recovery. Except as otherwise provided in Section 6.10.5.2.1, the ISO will begin
to calculate and bill the RTFC for an Unregulated Transmitting Utility pursuant to
Section 6.10.3 in accordance with the period for cost recovery determined by the
Commission after the Commission has accepted or approved the filing of its
revenue requirement or otherwise allowed the filing to go into effect pursuant to a
formula rate.
6.10.5.2 Cost Recovery for LIPA
Any costs incurred for an Eligible Project undertaken by LIPA, as an Unregulated
Transmitting Utility, that are eligible for recovery under Section 6.10.5.1 under a LIPA RTFC
shall be recovered over the period established by Long Island Power Authority’s Board of
Trustees as follows:
6.10.5.2.1
For costs to LIPA customers: Cost will be recovered pursuant to a rate
recovery mechanism approved by the Long Island Power Authority’s Board of
Trustees pursuant to Article 5, Title 1-A of the New York Public Authorities Law,
Sections 1020-f(u) and 1020-s. Upon approval of the rate recovery mechanism,
LIPA shall provide to the ISO, for purposes of inclusion within the ISO OATT
and filing with the Commission on an informational basis only, a description of
the rate recovery mechanism, the costs of the Eligible Project, and the rate that
LIPA will charge and collect from responsible entities within the Long Island
Transmission District in accordance with the ISO cost allocation methodology
pursuant to Section 31.5 of Attachment Y of the ISO OATT.
6.10.5.2.2
For Costs to Other Transmission Districts, As Applicable: Where the ISO
determines that there are Responsible LSEs serving Load outside of the Long
Island Transmission District that should be allocated a portion of the costs of the
Eligible Project undertaken by LIPA, LIPA shall coordinate with and inform the
ISO of the amount of such costs. Such costs will be an allocable amount of the
cost base recovered through the recovery mechanism described in Section
6.10.5.2.1 in accordance with the formula set forth in Section 6.10.3.5. Such
costs of the Eligible Project allocable to Responsible LSEs serving Load outside
of the Long Island Transmission District shall constitute the “revenue
requirement.” The ISO shall file the revenue requirement with the Commission if
requested to do so by LIPA, for Commission review under the same
“comparability” standard as is applied to review of changes in LIPA’s TSC under
Attachment H of the ISO OATT. The filing must be consistent with LIPA’s
project proposal made to and evaluated by the ISO pursuant to Attachment Y.
LIPA shall intervene in support of such filing at the Commission and shall bear
the burden of resolving all concerns about the contents of the filing that might be
raised in such proceeding. Upon the Commission’s acceptance for filing of
LIPA’s revenue requirement and using the procedures described in Sections
6.10.3.1 through 6.10.3.5 of this Schedule, the ISO shall calculate a separate
LIPA RTFC based on the revenue requirement and shall bill for LIPA the LIPA
RTFC as a separate line item to the Responsible LSEs serving Load in
Transmission Districts located outside of the Long Island Transmission District.
The ISO shall remit the revenues collected to LIPA in accordance with the ISO’s
billing and settlement procedures.
6.10.5.3 Cost Recovery for NYPA
Any costs incurred for an Eligible Project undertaken by NYPA, as an Unregulated
Transmitting Utility, that are eligible for recovery under Section 6.10.5.1 shall be recovered
under a NYPA RTFC as described herein. A reasonable return on investment for an Eligible
Project undertaken by NYPA may include any incentives for construction of transmission
projects available under Section 205 or Section 219 of the Federal Power Act and the
Commission’s regulations implementing those sections, as determined by the Commission.
6.10.5.3.1
NYPA shall coordinate with and inform the ISO of the amount of the costs
it incurred in undertaking an Eligible Project. Such costs shall constitute the
revenue requirement. Either the ISO shall make a Section 205 filing with the
Commission on behalf of NYPA or NYPA shall make an informational filing
under a formula rate with the Commission, of the revenue requirement. The filing
must be consistent with NYPA’s project proposal made to and evaluated by the
ISO pursuant to Attachment Y. NYPA shall intervene in support of such filing at
the Commission and shall bear the burden of resolving all concerns about the
contents of the filing that might be raised in such proceeding, including being
solely responsible for making any arguments or reservations regarding its status
as a non-Commission-jurisdictional utility and the appropriate standard for
Commission review of its revenue requirement. After the Commission has
accepted or approved the filing or otherwise allowed the filing to go into effect
pursuant to a formula rate, the ISO shall calculate in accordance with Sections
6.10.3.1 through 6.10.3.5 of this Schedule a separate NYPA RTFC based on the
revenue requirement and bill for NYPA the NYPA RTFC to the Responsible
LSEs. The ISO shall remit the revenues collected to NYPA in accordance with
the ISO’s billing and settlement procedures.
6.10.5.4
Savings Clause. The inclusion in the ISO OATT or in a filing with the
Commission pursuant to Section 6.10.5 of the revenue requirement for recovery
of costs incurred by an Unregulated Transmitting Utility, including LIPA or
NYPA, related to an Eligible Project undertaken pursuant to Attachment Y of the
ISO OATT, as provided for in this Section 6.10.5, or the inclusion of such
revenue requirement in the LIPA RTFC or NYPA RTFC, shall not be deemed to
modify the treatment of such rates as non-jurisdictional pursuant to Section 201(f)
of the FPA.
31.2
Reliability Planning Process
31.2.1
Local Transmission Owner Planning Process
31.2.1.1 Scope
31.2.1.1.1 Criteria, Assumptions and Data
Each Transmission Owner will post on its website the planning criteria and assumptions
currently used in its LTPP as well as a list of any applicable software and/or analytical tools
currently used in the LTPP. Customers, Market Participants and other interested parties may
review and comment on the planning criteria and assumptions used by each Transmission
Owner, as well as other data and models used by each Transmission Owner in its LTPP. The
Transmission Owners will take into consideration any comments received. Any planning criteria
or assumptions for a Transmission Owner’s BPTFs will meet or exceed any applicable NERC,
NPCC or NYSRC criteria. The LTPP shall include a description of the needs addressed by the
LTPP as well as the assumptions, applicable planning criteria and methodology utilized and the
Public Policy Requirements considered. A link to each Transmission Owner’s website will be
posted on the ISO website.
31.2.1.1.2 Consideration of Transmission Needs Driven by Public Policy
Requirements
31.2.1.1.2.1 Procedures for the Identification of Transmission Needs Driven by
Public Policy Requirements in Local Transmission Plans and for the
Consideration of Transmission Solutions
In developing its LTP, each Transmission Owner shall consider whether there is a
transmission need on its system that is being driven by a Public Policy Requirement. The LTP
will identify any transmission project included in the LTP as a solution to a transmission need
being driven by a Public Policy Requirement. In evaluating potential transmission solutions, the
Transmission Owner will give consideration to the objectives of the Public Policy
Requirement(s) driving the need for transmission.
31.2.1.1.2.2 Determination of Local Transmission Needs Driven by Public Policy
Requirements
As part of its LTP process pursuant to Section 31.2.1.2 below, each Transmission Owner
will consider whether there is a transmission need on its local system that is being driven by a
Public Policy Requirement for which a local transmission solution should be evaluated,
including needs proposed by market participants and other interested parties. A market
participant or other interested party proposing a transmission need on a Transmission Owner’s
local system driven by a Public Policy Requirement shall submit its proposal to the ISO and the
relevant Transmission Owner, and will identify the specific Public Policy Requirement that is
driving the proposed transmission need and an explanation of why a local transmission upgrade
is necessary to implement the Public Policy Requirement. Any proposed local system
transmission need will be posted on the ISO website. The ISO will transmit proposed
transmission needs on a Transmission Owner’s local system driven by Public Policy
Requirements to the NYDPS, with a request that the NYDPS review the proposals and provide
the relevant Transmission Owner with input to assist the Transmission Owner in its
determination. The Transmission Owner, after considering the input provided by the NYDPS
and any information provided by a market participant or other party, will determine whether
there are transmission needs driven by Public Policy Requirements for which local transmission
solutions should be evaluated. The Transmission Owner will post on its website a list of the
transmission needs driven by Public Policy Requirements for which local transmission solutions
should be evaluated, with an explanation of why the Transmission Owner identified those
transmission needs and declined to identify other proposed transmission needs.
31.2.1.1.2.3 Evaluation of Proposed Local Transmission Solutions
In evaluating potential transmission solutions, if any, the Transmission Owner will give
consideration to the objectives of the Public Policy Requirement driving the need for a local
transmission solution. The Transmission Owner will evaluate solutions to identified
transmission needs, including transmission solutions proposed by market participants and other
parties for inclusion in its LTP. The Transmission Owner, in consultation with the NYDPS, will
evaluate proposed transmission solutions on its local system to determine the more efficient or
cost-effective transmission solutions. The Transmission Owner will consider the relative costs
and benefits of proposed transmission solutions and their impact on the Transmission Owner’s
transmission system and its customers. Any local transmission solution identified by the
Transmission Owner through the LTP process will be reviewed with stakeholders as part of each
Transmission Owner’s regular LTP process and will be included in the Transmission Owner’s
subsequent LTP. In conducting its evaluation the Transmission Owner will use criteria that are
relevant to the Public Policy Requirement driving the transmission need, which may include its
published local planning criteria and assumptions.
31.2.1.2 Process Timeline
31.2.1.2.1
Each Transmission Owner, in accordance with a schedule set forth in the
ISO Procedures, will post its current LTP on its website for review and comment
by interested parties sufficiently in advance of the time for submission to the ISO
for input to its RNA so as to allow adequate time for stakeholder review and
comment. Each LTP will include:
identification of the planning horizon covered by the LTP,
data and models used,
reliability needs, needs driven by Public Policy Requirements, and other needs
addressed,
potential solutions under consideration, and,
a description of the transmission facilities covered by the plan.
31.2.1.2.2
To the extent the current LTP utilizes data or inputs, related to the ISO’s
planning process, not already reported by the ISO in Form 715 and referenced on
its website, any such data will be provided to the ISO at the time each
Transmission Owner posts criteria and planning assumptions in accordance with
Section 31.2.1.1 and will be posted by the ISO on its website subject to any
confidentiality or Critical Energy Infrastructure Information restrictions or
requirements.
31.2.1.2.3
Each planning cycle, the ISO shall hold one or more stakeholder meetings
of the ESPWG and TPAS at which each Transmission Owner’s current LTP will
be discussed. Such meetings will be held either at the Transmission Owner’s
Transmission District, or at an ISO location. The ISO shall post notice of the
meeting and shall disclose the agenda and any other material distributed prior to
the meeting.
31.2.1.2.4
Interested parties may submit written comments to a Transmission Owner
with respect to its current LTP within thirty days after the meeting. Each
Transmission Owner shall list on its website, as part of its LTP, the person and/or
location to which comments should be sent by interested parties. All comments
will be posted on the ISO website. Each Transmission Owner will consider
comments received in developing any modifications to its LTP. Any such
modification will be explained in its current LTP posted on its website pursuant to
Section 31.2.1.2.2 above and discussed at the next meeting held pursuant to
Section 31.2.1.2.3 above.
31.2.1.2.5
Each planning cycle, each Transmission Owner will submit the finalized
portions of its current LTP to the ISO as contemplated in Section 31.2.2.4.2 below
for timely inclusion in the RNA.
31.2.1.3 ISO Evaluation of Transmission Owner Local Transmission Plans in
Relation to Regional and Local Transmission Needs
The ISO will review the Transmission Owner LTPs as they relate to the BPTFs as set
forth in Section 31.2.2.4.2. The ISO will also evaluate whether a regional transmission solution
- including, but not limited to, regional transmission solutions proposed by Developers pursuant
to this Attachment Y - could satisfy an identified regional transmission need on the BPTFs that
impacts more than one Transmission District more efficiently or more cost effectively than a
local transmission solution identified in a Transmission Owner’s LTP in accordance with Section
31.2.6.4.2 for the satisfaction of a regional Reliability Need, Section 31.3.1.3.6 for the reduction
of congestion identified in CARIS, or Section 31.4.7.2 for the satisfaction of a Public Policy
Transmission Need. The ISO will report the results of its evaluation solely for informational
purposes in the relevant ISO planning report prepared under this Attachment Y, and the
Transmission Owners shall not be required to revise their LTPs based on the results of the ISO’s
evaluation.
31.2.1.4 LTP Dispute Resolution Process
31.2.1.4.1 Disputes Related to the LTPP; Objective; Notice
Disputes related to the LTPP are subject to the DRP. The objective of the DRP is to
assist parties having disputes in communicating effectively and resolving disputes as
expeditiously as possible. Within fifteen (15) calendar days of the presentation by a
Transmission Owner of its LTP to the ESPWG and TPAS, a party with a dispute shall notify in
writing the Affected TO, the ISO, the ESPWG and TPAS of its intention to utilize the DRP. The
notice shall identify the specific issue in dispute and describe in sufficient detail the nature of the
dispute.
31.2.1.4.2 Review by the ESPWG/TPAS
The issue raised by a party with a dispute shall be reviewed and discussed at a joint
meeting of the ESPWG and the TPAS in an effort to resolve the dispute. The party with a
dispute and the Affected TO shall have an opportunity to present information concerning the
issue in dispute to the ESPWG and the TPAS.
31.2.1.4.3 Information Discussions
To the extent the ESPWG and the TPAS are unable to resolve the dispute, the dispute
will be subject to good faith informal discussions between the party with a dispute and the
Affected TO. Each of those parties will designate a senior representative authorized to enter into
informal discussions and to resolve the dispute. The parties to the dispute shall make a good
faith effort to resolve the dispute through informal discussions as promptly as practicable.
31.2.1.4.4 Alternative Dispute Resolution
In the event that the parties to the dispute are unable to resolve the dispute through
informal discussions within sixty (60) days, or such other period as the parties may agree upon,
the parties may, by mutual agreement, submit the dispute to mediation or any other form of
alternative dispute resolution. The parties shall attempt in good faith to resolve the dispute in
accordance with a mutually agreed upon schedule but in no event may the schedule extend
beyond ninety (90) days from the date on which the parties agreed to submit the dispute to
alternative dispute resolution.
31.2.1.4.5 Notice of Results of Dispute Resolution
The Affected TO shall notify the ISO and ESPWG and TPAS of the results of the DRP
and update its LTP to the extent necessary. The ISO shall use in its planning process the LTP
provided by the Affected TO.
31.2.1.4.6 Rights Under the Federal Power Act
Nothing in the DRP shall affect the rights of any party to file a complaint with the
Commission under relevant provisions of the FPA.
31.2.1.4.7 Confidentiality
All information disclosed in the course of the DRP shall be subject to the same
protections accorded to confidential information and CEII by the ISO under its confidentiality
and CEII policies.
31.2.2
Reliability Needs Assessment
31.2.2.1 General
The ISO shall prepare and publish the RNA as described below. The RNA will identify
Reliability Needs. The ISO shall also designate in the RNA the Responsible Transmission
Owner with respect to each Reliability Need.
31.2.2.2 Interested Party Participation in the Development of the RNA
The ISO shall develop the RNA in consultation with Market Participants and all other
interested parties. TPAS will have responsibility consistent with ISO Procedures for review of
the ISO’s reliability analyses. ESPWG will have responsibility consistent with ISO Procedures
for providing commercial input and assumptions to be used in the development of reliability
assessment scenarios provided under Section 31.2.2.5, and in the reporting and analysis of
historic congestion costs. Coordination and communication will be established and maintained
between these two groups and ISO staff to allow Market Participants and other interested parties
to participate in a meaningful way during each stage of the CSPP. The ISO staff shall report any
majority and minority views of these collaborative governance work groups when it submits the
RNA to the Operating Committee for a vote, as provided below.
31.2.2.3 Preparation of the Reliability Needs Assessment
31.2.2.3.1
The ISO shall evaluate bulk power system needs in the RNA over the
Study Period.
31.2.2.3.2
The starting point for the development of the RNA Base Case will be the
system as defined for the FERC Form No. 715 Base Case. The ISO shall develop
this system representation to be used for its evaluations of the Study Period by
primarily using: (1) the most recent NYISO Load and Capacity Data Report
published by the ISO on its web site; (2) the most recent versions of ISO
reliability analyses and assessments provided for or published by NERC, NPCC,
NYSRC, and neighboring Control Areas; (3) information reported by neighboring
Control Areas such as power flow data, forecasted load, significant new or
modified generation and transmission facilities, and anticipated system conditions
that the ISO determines may impact the BPTFs; and (4) data submitted pursuant
to paragraph 31.2.2.4 below; provided, however, the ISO shall not include in the
RNA Base Case an RMR Generator or an interim non-RMR Generator
Deactivation Solution selected by the ISO pursuant to Attachment FF of the ISO
OATT; provided, further, the ISO will include in the RNA Base Case a
permanent non-RMR Generator Deactivation Solution selected by the ISO
pursuant to Attachment FF of the ISO OATT if it meets the base case inclusion
requirements in the ISO Procedures. The details of the development of the RNA
Base Case are contained in the ISO Procedures. The RNA Base Case shall also
include Interregional Transmission Projects that have been approved by the
NYPSC transmission siting process and meet the base case inclusion requirements
in the ISO Procedures.
31.2.2.3.3
The ISO shall assess the RNA Base Case to determine whether the BPTFs
meet all Reliability Criteria for both resource and transmission adequacy in each
year, and report the results of its evaluation in the RNA. Transmission analyses
will include thermal, voltage, short circuit, and stability studies. Then, if any
Reliability Criteria are not met in any year, the ISO shall perform additional
analyses to determine whether additional resources and/or transmission capacity
expansion are needed to meet those requirements, and to determine the Target
Year of need for those additional resources and/or transmission. A short circuit
assessment will be performed for the tenth year of the Study Period. The study
will not seek to identify specific additional facilities. Reliability Needs will be
defined in terms of total deficiencies relative to Reliability Criteria and not
necessarily in terms of specific facilities.
31.2.2.4 Planning Participant Data Input
31.2.2.4.1
At the ISO’s request, Market Participants, Developers, and other parties
shall provide, in accordance with the schedule set forth in the ISO Procedures, the
data necessary for the development of the RNA. This data will include but not be
limited to (1) existing and planned additions to the New York State Transmission
System (to be provided by Transmission Owners and municipal electric utilities);
(2) proposals for merchant transmission facilities (to be provided by merchant
Developers); (3) generation additions and retirements (to be provided by
generator owners and Developers); (4) demand response programs (to be provided
by demand response providers); and (5) any long-term firm transmission requests
made to the ISO.
31.2.2.4.2
The Transmission Owners shall submit their current LTPs referenced in
Section 31.1.3 and Section 31.2.1 to the ISO. The Transmission Owners and the
ISO will coordinate with each other in reviewing the LTPs. The ISO will review
the Transmission Owners’ LTPs, as they relate to BPTFs, to determine whether
they will meet reliability needs identified in the LTPs, recommend an alternate
means to resolve the local needs from a regional perspective pursuant to Section
31.2.6.4, and indicate if it is not in agreement with a Transmission Owner’s
proposed additions. The ISO shall report its determinations under this section in
the RNA and in the CRP.
31.2.2.4.3
All data received from Market Participants, Developers, and other parties
shall be considered in the development of the system representation for the Study
Period in accordance with the ISO Procedures.
31.2.2.5 Reliability Scenario Development
The ISO, in consultation with the ESPWG and TPAS, shall develop reliability scenarios
addressing the Study Period. Variables for consideration in the development of these reliability
scenarios include but are not limited to: load forecast uncertainty, fuel prices and availability,
new resources, retirements, transmission network topology, and limitations imposed by proposed
environmental or other legislation.
31.2.2.6 Evaluation of Reliability Scenarios
The ISO will conduct additional reliability analyses for the reliability scenarios
developed pursuant to paragraph 31.2.2.5. These evaluations will test the robustness of the needs
assessment studies conducted under paragraphs 31.2.2.3. This evaluation will only identify
conditions under which Reliability Criteria may not be met. It will not identify or propose
additional Reliability Needs. In addition, the ISO will perform appropriate sensitivity studies to
determine whether Reliability Needs previously identified can be mitigated through alternate
system configurations or operational modes. The Reliability Needs may increase in some
reliability scenarios and may decrease, or even be eliminated, in others. The ISO shall report the
results of these evaluations in the RNA.
31.2.2.7 Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of the
reliability transmission projects on such ISO/RTO Regions using the respective planning criteria
of such ISO/RTO Regions. The ISO shall report the results in the CRP. The ISO shall not bear
the costs of required upgrades in another region.
31.2.2.8 Reliability Needs Assessment Report Preparation
Once all the analyses described above have been completed, ISO staff will prepare a draft
of the RNA including discussion of its assumptions, Reliability Criteria, and results of the
analyses and, if necessary, designate the Responsible Transmission Owner. One or more
compensatory MW/ Load adjustment scenarios will be developed by the ISO as a guide to the
development of proposed solutions to meet the identified Reliability Need.
31.2.3
RNA Review Process
31.2.3.1 Collaborative Governance Process
The draft RNA shall be submitted to both TPAS and the ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft RNA. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Market Participants and
other interested parties may submit at any time optional suggestions for changes to ISO rules or
procedures which could result in the identification of additional resources or market alternatives
suitable for meeting Reliability Needs. Following completion of the TPAS and ESPWG review,
the draft RNA reflecting the revisions resulting from the TPAS and ESPWG review, shall be
forwarded to the Operating Committee for discussion and action. The ISO shall notify the
Business Issues Committee of the date of the Operating Committee meeting at which the draft
RNA is to be presented. Following the Operating Committee vote, the draft RNA will be
transmitted to the Management Committee for discussion and action.
31.2.3.2 Board Action
Following the Management Committee vote, the draft RNA, with working group,
Operating Committee, and Management Committee input, will be forwarded to the ISO Board
for review and action. Concurrently, the draft RNA will be provided to the Market Monitoring
Unit for its review and consideration of whether market rules changes are necessary to address
an identified failure, if any, in one of the ISO’s competitive markets. The Board may approve
the RNA as submitted, or propose modifications on its own motion. If any changes are proposed
by the Board, the revised RNA shall be returned to the Management Committee for comment.
The Board shall not make a final determination on a revised RNA until it has reviewed the
Management Committee comments. Upon approval by the Board, the ISO shall issue the final
RNA to the marketplace by posting it on its web site.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of this Attachment are also addressed in Section 30.4.6.8.2 of the Market Monitoring
Plan, Attachment O to the ISO Services Tariff.
31.2.3.3 Needs Assessment Disputes
Notwithstanding any provision to the contrary in this Attachment, the ISO OATT, or the
NYISO Services Tariff, in the event that a Market Participant raises a dispute solely within the
NYPSC’s jurisdiction relating to the final conclusions or recommendations of the RNA, a
Market Participant may refer such dispute to the NYPSC for resolution. The NYPSC’s final
determination shall be binding, subject only to judicial review in the courts of the State of New
York pursuant to Article 78 of the NYCPLR.
31.2.3.4 Public Information Sessions
In order to provide ample exposure for the marketplace to understand the identified
Reliability Needs, the ISO will provide various opportunities for Market Participants and other
potentially interested parties to discuss the final RNA. Such opportunities may include
presentations at various ISO Market Participant committees, focused discussions with various
industry sectors, and/or presentations in public venues.
31.2.4
Development of Solutions to Reliability Needs
31.2.4.1 Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.2.4.1 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.2.4.1.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.2.4.1.1.1 to demonstrate its capability to satisfy the applicable qualification criteria,
and (ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with
signatory authority, in a form acceptable to the ISO, certifying that the Affiliate will participate
in the Developer’s project in the manner described by the Developer and will abide by the
requirements set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures related and
applicable to the Affiliate’s participation.
31.2.4.1.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate and maintain a transmission project to meet identified Reliability
Needs. The ISO shall consider the qualifications of each Developer in an evenhanded and non-
discriminatory manner, treating Transmission Owners and Other Developers alike.
31.2.4.1.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a transmission project as a solution to an identified Reliability Need based on the
following criteria:
31.2.4.1.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.2.4.1.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.2.4.1.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement, or equivalent information;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch, or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to solve a Reliability Need.
31.2.4.1.1.1.4 A detailed plan describing how the Developer - in the absence of previous
experience financing, developing, constructing, operating, or maintaining
transmission facilities - will finance, develop, construct, operate, and maintain a
transmission facility, including the financial, technical, and engineering
qualifications and experience and capabilities of any third parties with which it
will contract for these purposes.
31.2.4.1.1.2 Developer Qualification Determination
Any Developer seeking to become qualified may submit the required information, or
update any previously submitted information, at any time. The ISO shall treat on a confidential
basis in accordance with the requirements of its Code of Conduct in Attachment F of the ISO
OATT any non-public financial qualification information that is submitted to the ISO by the
Developer under Section 31.2.4.1.1.1.3 and is designated by the Developer as “Confidential
Information.” The ISO shall within 15 days of a Developer’s submittal, notify the Developer if
the information is incomplete. If the submittal is deemed incomplete, the Developer shall submit
the additional information within 30 days of the ISO’s request. The ISO shall notify the
Developer of its qualification status within 30 days of receiving all necessary information. A
Developer shall retain its qualification status for a three-year period following the notification
date; provided, however, that the ISO may revoke this status if it determines that there has been a
material change in the Developer’s qualifications and the Developer no longer meets the
qualification requirements. A Developer that has been qualified shall inform the ISO within
thirty days of any material change to the information it provided regarding its qualifications and
shall submit to the ISO each year its most recent audited annual financial statement when
available. At the conclusion of the three-year period or following the ISO’s revocation of a
Developer’s qualification status, the Developer may re-apply for a qualification status under this
section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated transmission project as a solution to an identified Reliability Need and
shall be eligible to use the cost allocation and cost recovery mechanism for regulated
transmission projects set forth in Section 31.5 of this Attachment Y and Rate Schedule 10,
Section 6.10, of the ISO OATT for any approved project.
31.2.4.2 Interregional Transmission Projects
Interregional Transmission Projects may be proposed under Section 31.2.5.1 of this
Attachment Y as regulated backstop solutions, alternative regulated solutions, or market-based
solutions, in response to a request by the ISO for solutions to a Reliability Need under the
relevant provisions of Section 31.2.4. Interregional Transmission Projects proposed as regulated
backstop solutions, alternative regulated solutions or market-based solutions shall be: (i)
evaluated by the ISO in accordance with the applicable requirements of the reliability planning
process of this Attachment Y, and (ii) jointly evaluated by the ISO and the relevant adjacent
transmission planning region(s) in accordance with Section 7.3 of the Interregional Planning
Protocol.
31.2.4.3 Regulated Backstop Solutions
31.2.4.3.1
When a Reliability Need is identified in any RNA issued under this tariff,
the ISO shall request and the Responsible Transmission Owner shall provide to
the ISO, as set forth in Section 31.2.5 below, a proposal for a regulated solution or
combination of solutions that shall serve as a backstop to meet the Reliability
Need if requested by the ISO due to the lack of sufficient viable market-based
solutions to meet such Reliability Needs identified for the Study Period. The
Responsible Transmission Owner shall be eligible to recover its costs for
developing its proposal and seeking necessary approvals under Rate Schedule 10
of the ISO OATT. Regulated backstop solutions may include generation,
transmission, or demand side resources. Such proposals may include reasonable
alternatives that would effectively address the Reliability Need; provided
however, the Responsible Transmission Owner’s obligation to propose and
implement regulated backstop solutions under this tariff is limited to regulated
transmission solutions. Prior to providing its response to the RNA, each
Responsible Transmission Owner will present for discussion at the ESPWG and
TPAS any updates in its LTP that impact a Reliability Need identified in the
RNA. The ISO will present at the ESPWG and TPAS any updates to its
determination under Section 31.2.2.4.2 with respect to the Transmission Owners’
LTPs. Should more than one regulated backstop solution be proposed by a
Responsible Transmission Owner to address a Reliability Need, it will be the
responsibility of that Responsible Transmission Owner to determine which of the
regulated backstop solutions will proceed following a finding by the ISO under
Section 31.2.8 of this Attachment Y. The determination by the Responsible
Transmission Owner will be made prior to the approval of the CRP which
precedes the Trigger Date for the regulated backstop solution with the longest
lead time. Contemporaneous with the request to the Responsible Transmission
Owner, the ISO shall solicit market-based and alternative regulated responses as
set forth in Sections 31.2.4.5 and 31.2.4.7, which shall not be a formal RFP
process.
31.2.4.4 Qualifications for Regulated Backstop Solutions
31.2.4.4.1
The submission of a regulated backstop solution to a Reliability Need for
purposes of the ISO’s evaluation under Section 31.2.5 of the viability and
sufficiency of the proposed solution and the determination of the Trigger Date for
the proposed solution shall include, at a minimum, the following details: (1)
contact information; (2) the lead time necessary to complete the project,
including, if available, the construction windows in which the Responsible
Transmission Owner can perform construction and what, if any, outages may be
required during these periods; (3) a description of the project, including type, size,
and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable
technology, (5) a major milestone schedule; (6) the schedule for obtaining any
permits and other certifications, if available; (7) status of ISO interconnection
studies and interconnection agreement, if available; and (8) status of equipment
availability and procurement, if available.
31.2.4.4.2 The submission of a regulated backstop solution to a Reliability Need for
purposes of the ISO’s evaluation of the proposed solution for possible selection as
the more efficient or cost effective solution to the Reliability Need shall include,
at a minimum, the following details: (1) updates to the information required
under Section 31.2.4.4.1; (2) the schedule for obtaining required permits and other
certifications; (3) a demonstration of Site Control or a schedule for obtaining such
control; (4) the status of any contracts (other than an interconnection agreement)
that are under negotiation or in place, including any contracts with third-party
contractors; (5) status of ISO interconnection studies and interconnection
agreement; (6) status of equipment availability and procurement; (7) evidence of
financing or ability to finance the project; (8) capital cost estimates for the
project; (9) a description of permitting or other risks facing the project at the stage
of project development, including evidence of the reasonableness of project cost
estimates, all based on the information available at the time of the submission;
and (10) any other information requested by the ISO.
A Responsible Transmission Owner shall submit the following
information to indicate the status of any contracts: (i) copies of all final contracts
the ISO determines are relevant to its consideration, or (ii) where one or more
contracts are pending, a timeline on the status of discussions and negotiations
with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The
ISO shall treat on a confidential basis in accordance with the requirements of its
Code of Conduct in Attachment F of the ISO OATT any contract that is submitted
to the ISO and is designated by the Responsible Transmission Owner as
“Confidential Information.”
A Responsible Transmission Owner shall submit the following
information to indicate the status of any required permits: (i) copies of all final
permits received that the ISO determines are relevant to its consideration, or (ii)
where one or more permits are pending, the completed permit application(s) with
information on what additional actions must be taken to meet the permit
requirements and a timeline providing the expected timing for finalization and
receipt of the final permit(s). The final permits shall be submitted to the ISO
when available.
A Responsible Transmission Owner shall submit the following
information, as appropriate, to indicate evidence of financing by it or any Affiliate
upon which it is relying for financing: (i) evidence of self-financing or project
financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such
financing is pending, the status of the application for any relevant financing,
including a timeline providing the status of discussions and negotiations of
relevant documents and when the negotiations are expected to be completed. The
final contracts or approved rates shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission expansion
study of a proposed regulated backstop solution that is performed under Sections
3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO OATT, the
Responsible Transmission Owner of the proposed project shall notify the ISO that
the study has been completed and, at the ISO’s request, shall submit to the ISO
any study report and related materials prepared in connection with the study.
31.2.4.4.3
If the regulated backstop solution does not meet the Reliability Needs , the
ISO will provide sufficient information to the Responsible Transmission Owner to
determine how the regulated backstop should be modified to meet the identified
Reliability Needs. The Responsible Transmission Owner will make necessary
changes to its proposed regulated backstop solution to address reliability
deficiencies identified by the ISO, and submit a revised proposal to the ISO for
review and approval.
31.2.4.5 Market-Based Responses
At the same time that a proposal for a regulated backstop solution is requested from the
Responsible Transmission Owner under Section 31.2.4.3, the ISO shall also request market-
based responses from the market place. Subject to the execution of appropriately drawn
confidentiality agreements and the Commission’s standards of conduct, the ISO and the
appropriate Transmission Owner or Transmission Owners shall provide any party who wishes to
develop such a response access to the data that is necessary to develop its response. Such data
shall only be used for the purposes of preparing a market-based response to a Reliability Need
under this section. Such responses will be open on a comparable basis to all resources, including
generation, demand response providers, and merchant transmission Developers.
31.2.4.6 Qualifications for a Valid Market-Based Response
The submission of a proposed market-based solution must include, at a minimum:
(1) contact information; (2) the lead time necessary to complete the project, including, if
available, the construction windows in which the Developer can perform construction and what,
if any, outages may be required during these periods; (3) a description of the project, including
type, size, and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable technology;
(5) a major milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining Site Control; (8)
the status of any contracts (other than an interconnection agreement) that are under negotiation or
in place; (9) the status of ISO interconnection studies and interconnection agreement; (10) the
status of equipment availability and procurement; (11) evidence of financing or ability to finance
the project; and (12) any other information requested by the ISO.
A Developer shall submit the following information to indicate the status of any
contracts: (i) copies of all final contracts the ISO determines are relevant to its consideration, or
(ii) where one or more contracts are pending, a timeline on the status of discussions and
negotiations with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The ISO shall treat
on a confidential basis in accordance with the requirements of its Code of Conduct in
Attachment F of the ISO OATT any contract that is submitted to the ISO and is designated by
the Developer as “Confidential Information.”
A Developer shall submit the following information to indicate the status of any required
permits: (i) copies of all final permits received that the ISO determines are relevant to its
consideration, or (ii) where one or more permits are pending, the completed permit application(s)
with information on what additional actions must be taken to meet the permit requirements and a
timeline providing the expected timing for finalization and receipt of the final permit(s). The
final permits shall be submitted to the ISO when available.
A Developer shall submit the following information, as appropriate, to indicate evidence
of financing by it or any Affiliate upon which it is relying for financing: (i) copies of all loan
commitment letter(s) and signed financing contract(s), or (ii) where such financing is pending,
the status of the application for any relevant financing, including a timeline providing the status
of discussions and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission expansion study of a
proposed market-based solution that is performed under Sections 3.7 or 4.5 of the ISO OATT or
Attachments P or X of the ISO OATT, the Developer of the proposed project shall notify the ISO
that the study has been completed and, at the ISO’s request, shall submit to the ISO any study
report and related materials prepared in connection with the study.
Failure to provide any data requested by the ISO within the timeframe set forth in Section
31.2.5.1 of this Attachment Y will result in the rejection of the proposed market-based solution
from further consideration during that planning cycle.
31.2.4.7 Alternative Regulated Responses
31.2.4.7.1
The ISO will request alternative regulated responses to Reliability Needs
at the same time that it requests market-based responses and regulated backstop
solutions. Such proposals may include reasonable alternatives that would
effectively address the identified Reliability Need.
31.2.4.7.2
In response to the ISO’s request, Other Developers may develop
alternative regulated proposals for generation, demand side alternatives, and/or
other solutions to address a Reliability Need and submit such proposals to the
ISO. Transmission Owners, at their option, may submit additional proposals for
regulated solutions to the ISO. Transmission Owners and Other Developers may
submit such proposals to the NYDPS for review at any time. Subject to the
execution of appropriately drawn confidentiality agreements and the
Commission’s standards of conduct, the ISO and the appropriate Transmission
Owner(s) shall provide Other Developers access to the data that is needed to
develop their proposals. Such data shall be used only for purposes of preparing
an alternative regulated proposal in response to a Reliability Need.
31.2.4.8 Qualifications for Alternative Regulated Solutions
31.2.4.8.1
The submission of an alternative regulated solution to a Reliability Need
for purposes of the ISO’s evaluation under Section 31.2.5 of the viability and
sufficiency of the proposed solution and the determination of the Trigger Date for
the proposed solution shall include, at a minimum, the following details: (1)
contact information; (2) the lead time necessary to complete the project,
including, if available, the construction windows in which the Other Developer or
Transmission Owner can perform construction and what, if any, outages may be
required during these periods; (3) a description of the project, including type, size,
and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable
technology; (5) a major milestone schedule; (6) the schedule for obtaining any
permits and other certifications, if available; (7) status of ISO interconnection
studies and interconnection agreement, if available; and (8) status of equipment
availability and procurement, if available.
31.2.4.8.2
The submission of a proposed alternative regulated solution to a
Reliability Need for purposes of the ISO’s evaluation of the proposed solution for
possible selection as the more efficient or cost effective solution for the
Reliability Need must include, at a minimum: (1) updates to the information
required under Section 31.2.4.8.1;
(2) a demonstration of Site Control or a
schedule for obtaining Site Control; (3) the status of any contracts (other than an
Interconnection Agreement) that are under negotiation or in place, including any
contracts with third-party contractors; (4) the status of any interconnection studies
and interconnection agreement; (5) the schedule for obtaining any required
permits and other certifications; (6) the status of equipment availability and
procurement; (7) evidence of financing or ability to finance the project; (8) capital
cost estimates for the project; (9) a description of permitting or other risks facing
the project at the stage of project development, including evidence of the
reasonableness of project cost estimates, all based on the information available at
the time of the submission; and (10) any other information requested by the ISO.
An Other Developer or Transmission Owner shall submit the following
information to indicate the status of any contracts: (i) copies of all final contracts
the ISO determines are relevant to its consideration, or (ii) where one or more
contracts are pending, a timeline on the status of discussions and negotiations
with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The
ISO shall treat on a confidential basis in accordance with the requirements of its
Code of Conduct in Attachment F of the ISO OATT any contract that is submitted
to the ISO and is designated by the Other Developer or Transmission Owner as
“Confidential Information.”
An Other Developer or Transmission Owner shall submit the following
information to indicate the status of any required permits: (i) copies of all final
permits received that the ISO determines are relevant to its consideration, or (ii)
where one or more permits are pending, the completed permit application(s) with
information on what additional actions must be taken to meet the permit
requirements and a timeline providing the expected timing for finalization and
receipt of the final permit(s). The final permits shall be submitted to the ISO
when available.
An Other Developer or Transmission Owner shall submit the following
information, as appropriate, to indicate evidence of financing by it or any Affiliate
upon which it is relying for financing: (i) evidence of self-financing or project
financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such
financing is pending, the status of the application for any relevant financing,
including a timeline providing the status of discussions and negotiations of
relevant documents and when the negotiations are expected to be completed. The
final contracts or approved rates shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission
expansion study of a proposed alternative regulated solution that is performed
under Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO
OATT, the Other Developer or Transmission Owner of the proposed project shall
notify the ISO that the study has been completed and, at the ISO’s request, shall
submit to the ISO any study report and related materials prepared in connection
with the study.
31.2.4.8.3
Failure to provide any data requested by the ISO within the timeframe
provided in Sections 31.2.5.1 and 31.2.6.1 of this Attachment Y will result in the
rejection of the proposed alternative regulated solution from further consideration
during that planning cycle. A proponent of a proposed alternative regulated
solution must notify the ISO immediately of any material change in status of a
proposed alternative regulated solution. For purposes of this provision, a material
change includes, but is not limited to, a change in the financial viability of the
developer, a change in the siting status of the project, or a change in a major
element of the project’s development. If the ISO, at any time, learns of a material
change in the status of a proposed alternative regulated solution, it may, at that
time, make a determination as to the continued viability of the proposed
alternative regulated solution.
31.2.4.9 Additional Solutions
Should the ISO determine that it has not received adequate regulated backstop or market-
based solutions to satisfy the Reliability Need, the ISO may, in its discretion, solicit additional
regulated backstop or market-based solutions. Other Developers or Transmission Owners may
submit additional alternative regulated solutions for the ISO’s consideration at that time.
31.2.5
ISO Evaluation of Viability, Sufficiency, and Trigger Date of Proposed
Solutions to Reliability Needs
31.2.5.1 Timing for Submittal of Project Information and Developer Qualification
Information and Opportunity to Provide Additional Information
Within 60 days after a request for solutions to a Reliability Need is made by the ISO after
completion of the RNA, which time period may be extended by the ISO pursuant to Section
31.1.8.7, all Developers proposing solutions to an identified Reliability Need shall submit to the
ISO for purposes of its evaluation the project information, as applicable, for: (i) a proposed
regulated backstop solution under Section 31.2.4.4.1, (ii) a proposed market-based solution under
Section 31.2.4.6, or (iii) a proposed alternative regulated solution under Section 31.2.4.8.1 of this
Attachment Y. In response to a solicitation for a solution to a Reliability Need identified after
the 2014-2015 planning cycle, the Developer of a proposed transmission solution must also
demonstrate to the ISO, simultaneous with its submission of project information, that it has
submitted a valid Transmission Interconnection Application or Interconnection Request, as
applicable.
Any Developer that the ISO has determined under Section 31.2.4.1.1.2 or as set forth in
this Section 31.2.5.1 below to be qualified to propose to develop a project as a transmission
solution to an identified Reliability Need may submit the required project information; provided,
however, that: (i) the Developer shall provide a non-refundable application fee of $10,000 and
(ii) based on the actual identified need, the ISO may request that the qualified Developer provide
additional Developer qualification information. Any Developer that has not been determined by
the ISO to be qualified, but that wants to propose to develop a project, must submit to the ISO
the information required for Developer qualification under Section 31.2.4.1.1 within 30 days
after a request for solutions is made by the ISO. The ISO shall within 30 days of a Developer’s
submittal of its Developer qualification information, notify the Developer if this information is
incomplete. The Developer shall submit additional Developer qualification information or
project information required by the ISO within 15 days of the ISO’s request. A Developer that
fails to submit the additional Developer qualification information or the required project
information will not be eligible for its project to be considered in that planning cycle.
31.2.5.2 Comparable Evaluation of All Proposed Solutions
The ISO shall evaluate: (i) any proposed market-based solution submitted by a Developer
pursuant to Section 31.2.4.5, (ii) any proposed regulated backstop solution submitted by a
Responsible Transmission Owner pursuant to Section 31.2.4.3, and (iii) any proposed alternative
regulated solution submitted by a Transmission Owner or Other Developer pursuant to Section
31.2.4.7. The ISO will evaluate whether each proposed solution is viable and is sufficient to
satisfy the identified Reliability Need by the need date pursuant to Sections 31.2.5.3 and
31.2.5.4. The proposed solutions may include multiple components and resource types. When
evaluating proposed solutions to Reliability Needs from any Developer, all resource types -
generation, transmission, demand response, or a combination of these resource types - shall be
considered on a comparable basis as potential solutions to the Reliability Needs identified. All
solutions will be evaluated in the same general time frame.
31.2.5.3 Evaluation of Viability of Proposed Solution
The ISO will determine the viability of a solution - transmission, generation, demand
response, or a combination of these resource types - proposed to satisfy a Reliability Need. For
purposes of its analysis, the ISO will evaluate whether: (i) the Developer has provided the
required Developer qualification data pursuant to Section 31.2.4.1 and the required project
information data under Sections 31.2.4.4.1, 31.2.4.6, or 31.2.4.8.1; (ii) the proposed solution is
technically practicable; (iii) the Developer has indicated possession of, or an approach for
acquiring, any necessary rights-of-way, property, and facilities that will make the proposal
reasonably feasible in the required timeframe; and (iv) the proposed solution can be completed in
the required timeframe. If the ISO determines that the proposed solution is not viable and, for
regulated solutions, the Developer does not address any identified deficiency pursuant to Section
31.2.5.6, the ISO shall reject the proposed solution from further consideration during that
planning cycle.
31.2.5.4 Evaluation of Sufficiency of Proposed Solution
The ISO will perform a comparable analysis of each proposed solution - transmission,
generation, demand response, or a combination of these resource types - through the Study
Period to identify whether it satisfies the Reliability Need(s). The ISO will evaluate each
solution to determine whether the solution proposed by the Developer fully eliminates the
Reliability Need(s). If the ISO determines that a proposed regulated solution is not sufficient and
the Developer does not address any identified deficiency pursuant to Section 31.2.5.6, the ISO
shall reject the proposed regulated solution from further consideration during that planning cycle.
31.2.5.5 Establishment of Trigger Date of Proposed Regulated Solutions
Upon receipt of all Developers’ proposed regulated solutions pursuant to Section
31.2.5.1, the ISO will notify all Developers if any Developer has proposed a lead time for the
implementation of its regulated solution that could result in a Trigger Date for the regulated
solution within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG, provided that the ISO will not disclose the identity of
such Developer or the details of its project at that time. The ISO will independently analyze the
lead time proposed by each Developer for the implementation of its regulated solution. The ISO
will use the Developer’s estimate and the ISO’s analysis to establish the ISO’s Trigger Date for
each regulated solution. The ISO will also establish benchmark lead times for proposed market-
based solutions.
31.2.5.6 Resolution of Deficiencies
Following initial review of the proposals, as described above, ISO staff will identify any
reliability deficiencies in each of the proposed solutions. The Responsible Transmission Owner,
Transmission Owner or Other Developer will discuss any identified deficiencies with the ISO
staff. Other Developers and Transmission Owners that propose alternative regulated solutions
shall have the option to remedy their proposals to address any deficiency within 30 days of
notification by the ISO. With respect to regulated backstop solutions proposed by a Responsible
Transmission Owner pursuant to Section 31.2.4.3, the Responsible Transmission Owner shall
make necessary changes to its proposed backstop solution to address any reliability deficiencies
identified by the ISO, and submit a revised proposal to the ISO for review within 30 days. The
ISO shall review all such revised proposals to determine whether the identified deficiencies have
been resolved.
31.2.5.7 ISO Report of Evaluation Results
The ISO shall present its Viability and Sufficiency Assessment to stakeholders, interested
parties, and the NYDPS for comment and will indicate at that time whether any of the proposed
regulated solutions found to be viable and sufficient under this Section 31.2.5 will have a Trigger
Date within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG.
The ISO shall report in the CRP the results of its evaluation under this Section 31.2.5: (i)
whether each proposed regulated backstop solution, alternative regulated solution, and market-
based solution is viable and is sufficient to satisfy the identified Reliability Need by the need
date, and (ii) the Trigger Dates for the proposed regulated solutions.
31.2.6
ISO Evaluation and Selection of Proposed Regulated Transmission
Solutions
31.2.6.1 Submission of Project Information for Selection of Proposed Regulated
Transmission Solution
If the ISO determines that the Trigger Date of any Developer’s proposed regulated
solution that was found to be viable and sufficient under Section 31.2.5 will occur within thirty-
six months of the date of the ISO’s presentation of the Viability and Sufficiency Assessment to
the ESPWG, the ISO will request that all Developers of regulated transmission solutions that the
ISO determined were viable and sufficient submit to the ISO their project information, as
applicable, for: (i) a proposed regulated backstop transmission solution under Section 31.2.4.4.2,
or (ii) a proposed alternative regulated transmission solution under Section 31.2.4.8.2. If the ISO
determines that none of the Developers’ proposed regulated solutions that were found to be
viable and sufficient under Section 31.2.5 have a Trigger Date that will occur within the thirty-
six month period, the ISO will not request further project information, perform the evaluation, or
make a selection of a more efficient or cost effective regulated solution under this Section 31.2.6
for that planning cycle.
The ISO will make its request, if necessary, for project information under this Section
31.2.6.1 sufficiently in advance of the earliest Trigger Date of the viable and sufficient regulated
solutions to enable the ISO to evaluate and select the more efficient or cost effective
transmission solution. Upon the ISO’s request for project information, the Developers shall
submit such information for their regulated transmission solution within thirty (30) days, which
time period may be extended by the ISO pursuant to Section 31.1.8.7. The Developer must
include with its project information a demonstration that it has an executed System Impact Study
Agreement or System Reliability Impact Study Agreement, as applicable. A Developer shall
submit additional project information required by the ISO within 15 days of the ISO’s request.
A Developer that fails to submit the required project information will not be eligible for its
project to be considered in that planning cycle.
31.2.6.2 Study Deposit for Proposed Regulated Transmission Solutions
A Developer that proposes a regulated backstop transmission solution or an alternative
regulated transmission solution to satisfy the identified Reliability Need shall submit to the ISO,
at the same time that it provides the project information required pursuant to Section 31.2.6.1, a
study deposit of $100,000, which shall be applied to study costs and subject to refund as
described in this Section 31.2.6.2.
The ISO shall charge, and a Developer proposing a regulated backstop transmission
solution or an alternative regulated transmission solution shall pay, the actual costs of the ISO’s
evaluation of the Developer’s proposed transmission solution for purposes of the ISO’s selection
of the more efficient or cost effective transmission solution to satisfy a Reliability Need for cost
allocation purposes, including costs associated with the ISO’s use of subcontractors. The ISO
will track its staff and administrative costs, including any costs associated with using
subcontractors, that it incurs in performing the evaluation of a Developer’s proposed
transmission solution under this Section 31.2.6 and any supplemental evaluation or re-evaluation
of the proposed transmission solution. If the ISO or its subcontractors perform study work for
multiple proposed transmission solutions on a combined basis, the ISO will allocate the costs of
the combined study work equally among the applicable Developers. The ISO shall invoice the
Developer monthly for study costs incurred by the ISO in evaluating the Developer’s proposed
transmission solution as described above. Such invoice shall include a description and an
accounting of the study costs incurred by the ISO and estimated subcontractor costs. The
Developer shall pay the invoiced amount within thirty (30) calendar days of the ISO’s issuance
of the monthly invoice. The ISO shall continue to hold the full amount of the study deposit until
settlement of the final monthly invoice; provided, however, if a Developer: (i) does not pay its
monthly invoice within the timeframe described above, or (ii) does not pay a disputed amount
into an independent escrow account as described below, the ISO may draw upon the study
deposit to recover the owed amount. If the ISO must draw on the study deposit, the ISO shall
provide notice to the Developer, and the Developer shall within thirty (30) calendar days of such
notice make payments to the ISO to restore the full study deposit amount. If the Developer fails
to make such payments, the ISO may halt its evaluation of the Developer’s proposed
transmission solution and may disqualify the Developer’s proposed transmission solution from
further consideration. After the conclusion of the ISO’s evaluation of the Developer’s proposed
transmission solution or if the Developer: (i) withdraws its proposed transmission solution or (ii)
fails to pay an invoiced amount and the ISO halts its evaluation of the proposed transmission
solution, the ISO shall issue a final invoice and refund to the Developer any portion of the
Developer’s study deposit submitted to the ISO under this Section 31.2.6.2 that exceeds
outstanding amounts that the ISO has incurred in evaluating that Developer’s proposed
transmission solution, including interest on the refunded amount calculated in accordance with
Section 35.19a(a)(2) of FERC’s regulations. The ISO shall refund the remaining portion within
sixty (60) days of the ISO’s receipt of all final invoices from its subcontractors and involved
Transmission Owners.
In the event of a Developer’s dispute over invoiced amounts, the Developer shall: (i)
timely pay any undisputed amounts to the ISO, and (ii) pay into an independent escrow account
the portion of the invoice in dispute, pending resolution of such dispute. If the Developer fails to
meet these two requirements, then the ISO shall not be obligated to perform or continue to
perform its evaluation of the Developer’s proposed transmission solution. Disputes arising under
this section shall be addressed through the Dispute Resolution Procedures set forth in Section
2.16 of the ISO OATT and Section 11 of the ISO Services Tariff. Within thirty (30) Calendar
Days after resolution of the dispute, the Developer will pay the ISO any amounts due with
interest calculated in accordance with Section 35.19a(a)(2) of FERC’s regulations.
31.2.6.3 Evaluation of System Impact of Proposed Regulated Transmission
Solution
A proposed regulated transmission solution that will have a significant adverse impact on
the reliability of the New York State Transmission System shall not be eligible for selection by
the ISO under Section 31.2.6.5. The ISO shall evaluate the system impacts for the entire Study
Period of a proposed regulated transmission solution that the ISO has determined under Section
31.2.5 is viable and sufficient. As part of this evaluation, the ISO shall give due consideration to
the results of any completed System Impact Study or System Reliability Impact Study, as
applicable. The ISO shall perform power flow and short circuit studies for the proposed
regulated transmission solutions and additional studies, as appropriate. If the ISO identifies a
significant adverse impact based on these studies, the ISO shall request that the Developer make
an adjustment to its proposed regulated transmission solution to address this impact and remain
eligible for selection. The Developer shall submit the adjustment within 30 days of the ISO’s
notification.
If the Developer modifies its proposed regulated transmission solution, the ISO shall
confirm that the adjusted solution still satisfies the viability and sufficiency requirements set
forth in Section 31.2.5. If the ISO determines that the proposed regulated transmission solution
does not satisfy the viability and sufficiency requirements or continues to have a significantly
adverse impact on the reliability of the New York State Transmission System, the ISO shall
remove the proposed solution from further consideration during that planning cycle.
31.2.6.4 Evaluation of Regional Transmission Solutions to Address Local and
Regional Reliability Needs More Efficiently or More Cost Effectively
Than Local Transmission Solutions
The ISO will review the LTPs as they relate to BPTFs. The results of the ISO’s analysis
will be reported in the CRP.
31.2.6.4.1 Evaluation of Regional Transmission Solutions to Address Local
Reliability Needs Identified in Local Transmission Plans More Efficiently
or More Cost Effectively than Local Transmission Solutions
The ISO, using engineering judgment, will determine whether proposed regional
transmission solutions on the BPTFs may more efficiently or cost effectively satisfy reliability
needs identified in the LTPs. If the ISO identifies that a regional transmission solution on the
BPTFs has the potential to more efficiently or cost effectively satisfy the reliability need
identified in the LTPs, it will perform a sensitivity analysis to determine whether the proposed
regional transmission solution on the BPTFs would satisfy the reliability needs identified in the
LTPs. If the ISO determines that the proposed regional transmission solutions on the BPTFs
would satisfy the reliability need, the ISO will evaluate the proposed regional transmission
solution using the metrics set forth in Section 31.2.6.5.1 to determine whether it may be a more
efficient or cost effective solution on the BPTFs to satisfy the reliability needs identified in the
LTPs than the local solutions proposed in the LTPs.
31.2.6.4.2 Evaluation of Regional Transmission Solutions to Address Regional
Reliability Needs More Efficiently or More Cost Effectively than Local
Transmission Solutions
As referenced in Section 31.2.1.3, the ISO, using engineering judgment, will determine
whether a regional transmission solution might more efficiently or more cost effectively satisfy
an identified regional Reliability Need on the BPTFs that impacts more than one Transmission
District than any local transmission solutions identified by the Transmission Owners in their
LTPs in the event the LTPs specify such transmission solutions are included to address local
reliability needs.
31.2.6.5 ISO Selection of More Efficient or Cost Effective Transmission Solution
for Cost Allocation Purposes
A proposed regulated transmission solution - including a regulated backstop transmission
solution submitted by a Responsible Transmission Owner pursuant to Section 31.2.4.3 and an
alternative regulated transmission solution submitted by a Transmission Owner or Other
Developer pursuant to Section 31.2.4.7 - that the ISO has determined satisfies the viability and
sufficiency requirements in Section 31.2.5 and the system impact requirements in Section
31.2.6.3 shall be eligible under this Section 31.2.6.5 for selection in the CRP for the purpose of
cost allocation and recovery under the ISO Tariffs. The ISO shall evaluate any eligible proposed
regulated transmission solutions for the planning cycle using the metrics set forth in Section
31.2.6.5.1 below. For purposes of this evaluation, the ISO will review the information submitted
by the Developer and determine whether it is reasonable and how such information should be
used for purposes of the ISO evaluating each metric. In its review, the ISO will give due
consideration to the status of, and any available results of, any applicable interconnection or
transmission expansion studies concerning the proposed regulated transmission solution
performed in accordance with Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the
ISO OATT. The ISO may engage an independent consultant to review the reasonableness and
comprehensiveness of the information submitted by the Developer and may rely on the
independent consultant’s analysis in evaluating each metric. The ISO shall select in the CRP for
cost allocation purposes the more efficient or cost effective transmission solution to satisfy a
Reliability Need in the manner set forth in Section 31.2.6.5.2 below.
31.2.6.5.1 Metrics for Evaluating More Efficient or Cost Effective Regulated
Transmission Solution to Satisfy Reliability Need
In determining which of the eligible proposed regulated transmission solutions is the
more efficient or cost effective solution to satisfy the Reliability Need, the ISO will consider, and
will consult with the NYDPS regarding, the following metrics set forth in this Section 31.2.6.5.1
and rank each proposed solution based on the quality of its satisfaction of these metrics:
31.2.6.5.1.1 The capital cost estimates for the proposed regulated transmission
solutions, including the accuracy of the proposed estimates. For this evaluation,
the Developer shall provide the ISO with credible capital cost estimates for its
proposed solution, with itemized supporting work sheets that identify all material
and labor cost assumptions, and related drawings to the extent applicable and
available. The work sheets should include an estimated quantification of cost
variance, providing an assumed plus/minus range around the capital cost estimate.
The estimate shall include all components that are needed to meet the
Reliability Need throughout the Study Period. To the extent information is
available, the Developer should itemize: material and labor cost by equipment,
engineering and design work, permitting, site acquisition, procurement and
construction work, and commissioning needed for the proposed solution, all in
accordance with Good Utility Practice. For each of these cost categories, the
Developer should specify the nature and estimated cost of all major project
components and estimate the cost of the work to be done at each substation and/or
on each feeder to physically and electrically connect each facility to the existing
system. The work sheets should itemize to the extent applicable and available all
equipment for: (i) the proposed project; (ii) interconnection facilities (including
Attachment Facilities and Direct Assignment Facilities); and (iii) Network
Upgrade Facilities, System Upgrade Facilities, System Deliverability Upgrades,
Network Upgrades, and Distribution Upgrades.
31.2.6.5.1.2 The cost per MW ratio of the proposed regulated transmission solutions.
For this evaluation, the ISO will first determine the present worth, in dollars, of
the total capital cost of the proposed solution in current year dollars. The ISO will
then determine the MW value of the solution by summing the Reliability Need, in
MW, with the additional improvement, in MW, that the proposed solution offers
beyond serving the Reliability Need. The ISO will then determine the cost per
MW ratio by dividing the present worth of the total capital cost by the MW value.
31.2.6.5.1.3 The expandability of the proposed regulated transmission solution. The
ISO will consider the impact of the proposed solution on future construction. The
ISO will also consider the extent to which any subsequent expansion will continue
to use this proposed solution within the context of system expansion.
31.2.6.5.1.4 The operability of the proposed regulated transmission solution. The ISO
will consider how the proposed solution may affect additional flexibility in
operating the system, such as dispatch of generation, access to operating reserves,
access to ancillary services, or ability to remove transmission for maintenance.
The ISO will also consider how the proposed solution may affect the cost of
operating the system, such as how it may affect the need for operating generation
out of merit for reliability needs, reducing the need to cycle generation, or
providing more balance in the system to respond to system conditions that are
more severe than design conditions.
31.2.6.5.1.5 The performance of the proposed regulated transmission solution. The
ISO will consider how the proposed project may affect the utilization of the
system (e.g. interface flows, percent loading of facilities).
31.2.6.5.1.6 The extent to which the Developer of a proposed regulated transmission
solution has the property rights, or ability to obtain the property rights, required to
implement the solution. The ISO will consider whether the Developer: (i) already
possesses the rights of way necessary to implement the solution; (ii) has
completed a transmission routing study, which (a) identifies a specific routing
plan with alternatives, (b) includes a schedule indicating the timing for obtaining
siting and permitting, and (c) provides specific attention to sensitive areas (e.g.,
wetlands, river crossings, protected areas, and schools); or (iii) has specified a
plan or approach for determining routing and acquiring property rights.
31.2.6.5.1.7 The potential issues associated with delay in constructing the proposed
regulated transmission solution consistent with the major milestone schedule and
the schedule for obtaining any permits and other certifications as required to
timely meet the need.
31.2.6.5.2 ISO Selection of More Efficient or Cost Effective Regulated Transmission
Solution to Satisfy Reliability Need
The ISO shall select under this Section 31.2.6.5.2 the proposed regulated transmission
solution, if any, that is the more efficient or cost effective transmission solution proposed in the
planning cycle to satisfy the identified Reliability Need. The ISO shall report the selected
regulated transmission solution in the CRP. The selected regulated transmission solution
reported in the CRP shall be eligible to be triggered by the ISO to satisfy the identified
Reliability Need pursuant to Section 31.2.8 at any point within thirty-six months of the date of
the ISO’s presentation of the Viability and Sufficiency Assessment to the ESPWG. An Other
Developer or Transmission Owner of an alternative regulated transmission project shall not be
eligible for cost allocation and cost recovery under the ISO OATT for its project unless its
project is selected pursuant to this Section 31.2.6.5.2. Once such project is selected, the Other
Developer or Transmission Owner shall be eligible for cost allocation and cost recovery under
the ISO OATT for its project. Within thirty (30) days of the ISO’s selection of an alternative
regulated transmission solution, the Other Developer or Transmission Owner shall submit to the
ISO for the ISO’s approval a proposed schedule and scope of work that describe the preparation
work, if any, that the Developer must perform prior to the Trigger Date of the project, including
a good faith estimate of the costs of such work. Costs will be recovered when the project enters
into service, is halted, or as otherwise determined by the Commission in accordance with the cost
recovery requirements set forth in Section 31.5.6 of this Attachment Y and Rate Schedule 10 of
the ISO OATT. Actual project cost recovery, including any issues related to cost recovery and
project cost overruns, will be submitted to and decided by the Commission.
31.2.7
Comprehensive Reliability Plan
Following the ISO’s evaluation of the proposed market-based and regulated solutions to
Reliability Need(s), the ISO will prepare a draft CRP that sets forth the ISO’s findings regarding
the viability and sufficiency of solutions, the trigger dates of regulated solutions, and any
recommendations that implementation of regulated solutions (which may be a Gap Solution) is
necessary to ensure system reliability. The draft CRP will reflect any input from the NYDPS. If
the CRP cannot be completed in the two-year planning cycle, the ISO will notify stakeholders
and provide an estimated completion date and an explanation of the reasons the additional time is
required.
The ISO will include in the draft CRP the list of Developers that qualify pursuant to
Section 31.2.4.1 and will identify the proposed solutions that it has determined under Section
31.2.5 are viable and sufficient to satisfy the identified Reliability Need(s) by the need date. The
ISO will identify in the CRP the regulated backstop solution that the ISO has determined will
meet the Reliability Need by the need date and the Responsible Transmission Owner. If the ISO
determines at the time of the issuance of the CRP that sufficient market-based solutions will not
be available in time to meet a Reliability Need, and finds that it is necessary to take action to
ensure reliability, it will state in the CRP that the development of regulated solutions (regulated
backstop or alternative regulated solution) is necessary. The draft CRP will also include the
results of the ISO’s analysis of the LTPs consistent with Section 31.2.6.4.
The draft CRP shall indicate whether the ISO has determined that the Trigger Date to any
proposed regulated solution will occur within thirty-six months of the date of ISO’s presentation
of the Viability and Sufficiency Assessment to the ESPWG. If the Trigger Date of any proposed
regulated solution will occur within the thirty-six month period and the ISO makes a selection of
the more efficient or cost effective transmission solution under Section 31.2.6.5.2, the draft CRP
shall include the regulated transmission solution selected for cost allocation purposes pursuant to
Section 31.2.6.5.2 as the more efficient or cost effective transmission solution to satisfy the
Reliability Need(s) and shall indicate whether that transmission solution should be triggered.
The draft CRP shall also indicate the date by which a solution must be in-service to satisfy the
Reliability Need.
If: (i) none of the proposed regulated solutions has a Trigger Date within the thirty-six
month period, or (ii) the Trigger Date of any proposed regulated solution will occur within the
thirty-six month period but the ISO determines in its discretion that it is not necessary at that
time to select a more efficient or cost effective transmission solution under Section 31.2.6.5.2
prior to the completion of the CRP, the draft CRP will not select a regulated transmission
solution. If: (i) the Trigger Date of any proposed regulated solution will occur within the thirty-
six month period, and (ii) the ISO selects a more efficient or cost effective solution subsequent to
the completion of the CRP but prior to the completion of that thirty-six month period, the ISO
shall issue an updated CRP report pursuant to Section 31.2.7.3 that indicates the regulated
transmission solution selected for cost allocation purposes pursuant to Section 31.2.6.5.2 as the
more efficient or cost effective transmission solution to satisfy the Reliability Need(s) whether
that transmission solution should be triggered, and the date by which a solution must be in-
service to satisfy the Reliability Need.
The draft CRP shall include a comparison of a proposed regional solution to an identified
Reliability Need to an Interregional Transmission Project identified and evaluated under the
“Analysis and Consideration of Interregional Transmission Projects” section of the Interregional
Planning Protocol, if any. An Interregional Transmission Project proposed in the ISO’s
reliability planning process may be selected as a market based response, regulated backstop
solution, or an alternative regulated solution under the provisions of the ISO’s reliability
planning process.
31.2.7.1 Collaborative Governance Process
The ISO staff shall submit the draft CRP to the TPAS and ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft CRP. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Following completion
of the TPAS and ESPWG review, the draft CRP reflecting the revisions resulting from the TPAS
and ESPWG review shall be forwarded to the Operating Committee for a discussion and action.
The ISO shall notify the Business Issues Committee of the date of the Operating Committee
meeting at which the draft CRP is to be presented. Following the Operating Committee vote, the
draft CRP will be transmitted to the Management Committee for a discussion and action.
31.2.7.2 Board Review, Consideration, and Approval of CRP
Following the Management Committee vote, the draft CRP, with working group,
Operating Committee, and Management Committee input, will be forwarded to the ISO Board
for review and action. Concurrently, the draft CRP will also be provided to the Market
Monitoring Unit for its review and consideration of whether market rule changes are necessary to
address an identified failure, if any, in one of the ISO’s competitive markets. The Board may
approve the draft CRP as submitted or propose modifications on its own motion, including the
recommendations regarding the selection of transmission projects for cost allocation and cost
recovery under the ISO Tariffs if such selection will occur during that planning cycle. If any
changes are proposed by the Board, the revised CRP shall be returned to the Management
Committee for comment. The Board shall not make a final determination on the draft CRP until
it has reviewed the Management Committee comments. Upon final approval by the Board, the
ISO shall issue the CRP to the marketplace by posting the CRP on its website. The ISO will
provide the CRP to the appropriate regulatory agency(ies) for consideration and appropriate
action.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.3 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.2.7.3 Updated CRP Report
If, pursuant to Section 31.2.7, the ISO identifies a proposed regulated transmission
solution as the more efficient or cost effective transmission solution following the completion of
the CRP, the ISO will prepare a draft updated CRP report that indicates the regulated
transmission solution recommended for selection for cost allocation purposes pursuant to Section
31.2.6.5.2 as the more efficient or cost effective transmission solution to satisfy the Reliability
Need(s), whether that transmission solution should be triggered at that time, and the date by
which a solution must be in-service to satisfy the Reliability Need. The draft updated CRP
report shall be reviewed in accordance with the stakeholder process set forth in Section 31.2.7.1
and will be then forwarded to the ISO Board for its review and action pursuant to Section
31.2.7.2.
31.2.7.4 Reliability Disputes
Notwithstanding any provision to the contrary in this Attachment, the ISO OATT, or the
ISO Services Tariff, in the event that a Market Participant or other interested party raises a
dispute solely within the NYPSC’s jurisdiction concerning ISO’s final determination in the CRP
that a proposed solution will or will not meet a Reliability Need, a Market Participant or other
interested party seeking further review shall refer such dispute to the NYPSC for resolution, as
provided for in the ISO Procedures. The NYPSC’s final determination of such disputes shall be
binding, subject only to judicial review in the courts of the State of New York pursuant to Article
78 of the New York Civil Practice Law and Rules.
31.2.7.5 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers that have undertaken a
commitment to the ISO to build a project (which may be a regulated backstop solution, market-
based response, alternative regulated response or gap solution) that is necessary to ensure system
reliability, as identified in the CRP and approved by the appropriate governmental agency(ies)
and/or authority(ies).
31.2.8
Determination of Necessity
31.2.8.1 Determination of Necessity of a Regulated Solution
31.2.8.1.1
The ISO shall review proposals for market-based solutions pursuant to
Sections 31.2.5, 31.2.8.3, and 31.2.13.1 of this Attachment Y. The ISO will not
trigger a regulated solution if, based on this review, it determines prior to or at the
Trigger Date for a regulated solution that sufficient market-based solutions are
timely progressing to meet the Reliability Need by the need date. If the ISO
decides not to trigger a regulated backstop solution or selected alternative
regulated transmission solution, the Responsible Transmission Owner, Other
Developer, or Transmission Owner will be eligible to recover its costs incurred up
to that point in the same manner it may recover the costs of a halted project in
accordance with Section 31.2.8.2.1 for the Responsible Transmission Owner and
Section 31.2.8.2.2 for the Other Developer or Transmission Owner.
31.2.8.1.2
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date, (ii) the
regulated backstop solution proposed by the Responsible Transmission Owner is
the only proposed viable and sufficient regulated solution or is selected by the
ISO as the more efficient or cost effective transmission solution to meet the
identified Reliability Need, and (iii) the Trigger Date for the regulated backstop
solution has or will occur within thirty-six months of the date of the ISO’s
presentation of the Viability and Sufficiency Assessment to the ESPWG, the ISO
will trigger the regulated backstop solution at its Trigger Date. The ISO will
inform the Responsible Transmission Owner that it should submit the regulated
backstop solution to the appropriate governmental agency(ies) and/or
authority(ies) to begin the necessary approval process to site, construct, and
operate the solution. In response to the ISO’s request, the Responsible
Transmission Owner shall make such a submission to the appropriate
governmental agency(ies) and/or authority(ies).
31.2.8.1.3
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date; (ii) the ISO
selects an alternative regulated transmission solution as the more efficient or cost-
effective transmission solution to meet the identified Reliability Need; (iii) the
Trigger Date for the regulated backstop solution is later than the Trigger Date for
the selected alternative regulated transmission solution; and (iv) the Trigger Date
for the selected alternative regulated transmission solution has or will occur
within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG, the ISO shall trigger the selected
alternative regulated transmission solution at its Trigger Date. The ISO will
inform the Other Developer or Transmission Owner that it should submit the
selected alternative regulated transmission solution to the appropriate
governmental agency(ies) and/or authority(ies) to begin the necessary approval
process to site, construct, and operate the solution. In response to the ISO’s
request, the Other Developer or Transmission Owner shall make such a
submission to the appropriate governmental agency(ies) and/or authority(ies).
Prior to the Trigger Date for the regulated backstop solution, the ISO will review
the status of the development by the Other Developer or Transmission Owner of
the selected alternative regulated transmission solution, including, but not limited
to, reviewing: (i) whether the Developer has executed a Development Agreement
or requested that it be filed unexecuted with the Commission pursuant to Section
31.2.8.1.6; (ii) whether the Developer is timely progressing against the
milestones set forth in the Development Agreement; and (iii) the status of the
Developer’s obtaining required permits or authorizations, including whether the
Developer has received its Article VII certification or other applicable siting
permits or authorizations under New York State law. If, based on its review, the
ISO determines prior to or at the Trigger Date for the regulated backstop solution
that it is necessary for the Responsible Transmission Owner to proceed with a
regulated backstop solution in parallel with the selected alternative regulated
transmission solution to ensure the identified Reliability Need is satisfied by the
need date, the ISO will trigger the regulated backstop solution and report to
stakeholders the reasons for its determination. The Responsible Transmission
Owner shall proceed with due diligence to develop its regulated backstop solution
in accordance with Good Utility Practice and to submit its proposed solution to
the appropriate governmental agency(ies) and/or authority(ies), unless or until
notified by the ISO that it has determined that the regulated backstop solution is
no longer needed as described in Section 31.2.8.2.1 below. If, based on its
review, the ISO decides not to trigger the regulated backstop solution, the ISO
will notify the Responsible Transmission Owner that its regulated backstop
solution is no longer needed and will not be triggered. In such case, the
Responsible Transmission Owner shall be eligible to recover its costs incurred up
to that point in the same manner as it may recover the costs of a halted project in
accordance with Section 31.2.8.2.1.
31.2.8.1.4
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date; (ii) the ISO
selects an alternative regulated transmission solution as the more efficient or cost-
effective transmission solution to meet the identified Reliability Need; (iii) the
Trigger Date for the regulated backstop solution is earlier than the Trigger Date
for the selected alternative regulated transmission solution; and (iv) the Trigger
Date for the regulated backstop solution has or will occur within thirty-six months
of the date of the ISO’s presentation of the Viability and Sufficiency Assessment
to the ESPWG, the ISO shall trigger both the selected alternative regulated
transmission solution and the regulated backstop solution at the Trigger Date for
the regulated backstop solution. The ISO will inform the Responsible
Transmission Owner that proposed the regulated backstop solution and the Other
Developer or Transmission Owner that proposed the selected alternative regulated
transmission solution that they should submit the proposed solutions to the
appropriate governmental agency(ies) and/or authority(ies) to begin the necessary
approval process to site, construct, and operate the solution. In response to the
ISO’s request, the Responsible Transmission Owner, Other Developer or
Transmission Owner shall make such a submission to the appropriate
governmental agency(ies) and/or authority(ies).
31.2.8.1.5
The ISO may make its determination regarding the triggering of a
regulated solution pursuant to Sections 31.2.8.1.1 through 31.2.8.1.4 in the CRP
or at any time before the approval of the next CRP.
31.2.8.1.6
A Responsible Transmission Owner, Other Developer, or Transmission
Owner must enter into a Development Agreement with the ISO if: (i) the ISO has
selected the regulated transmission solution proposed by the Developer as the
more efficient or cost-effective transmission solution to the Reliability Need, (ii)
the ISO has triggered the regulated backstop transmission solution pursuant to
Sections 31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4, or (iii) the Responsible Transmission
Owner has agreed to complete a selected alternative regulated transmission
solution pursuant to Section 31.2.10.1.3. The ISO shall tender the Responsible
Transmission Owner, Other Developer, or Transmission Owner a draft
Development Agreement with draft appendices as soon as reasonably practicable
considering the project’s Trigger Date following, as applicable: (i) the ISO’s
selection of the proposed solution, (ii) the ISO’s triggering of a regulated
backstop transmission solution pursuant to Sections 31.2.8.1.2, 31.2.8.1.3, or
31.2.8.1.4, or (iii) the Responsible Transmission Owner’s agreement to complete
an alternative regulated transmission solution pursuant to Section 31.2.10.1.3.
The draft will be completed by the ISO to the extent practicable for review and
completion by the Developer. The draft Development Agreement shall be in the
form of the ISO’s Commission-approved Development Agreement, which is in
Appendix C in Section 31.7 of this Attachment Y. The ISO and the Developer
shall finalize the Development Agreement and appendices and negotiate
concerning any disputed provisions. For purposes of finalizing the Development
Agreement, the ISO and Developer shall develop the description and dates for the
milestones necessary to develop and construct the selected project by the required
in-service date identified in the CRP report or updated CRP report, as applicable,
including the milestones for obtaining all necessary authorizations. Any
milestone that requires action by a Connecting Transmission Owner or Affected
System Operator identified pursuant to Attachment P of the ISO OATT to
complete must be included as an Advisory Milestone, as that term is defined in
the Development Agreement. Unless otherwise agreed by the ISO and the
Developer, the Developer must execute the Development Agreement within three
(3) months of the ISO’s tendering of the draft Development Agreement; provided,
however, if, during the negotiation period, the ISO or the Developer determines
that negotiations are at an impasse, the ISO may file the Development Agreement
in unexecuted form with the Commission on its own or following the Developer’s
request in writing that the agreement be filed unexecuted. If the Development
Agreement resulting from the negotiation between the ISO and the Developer
does not conform with the Commission-approved standard form in Appendix C in
Section 31.7 of this Attachment Y, the ISO shall file the agreement with the
Commission for its acceptance within thirty (30) Business Days after the
execution of the Development Agreement by both parties. If the Developer
requests that the Development Agreement be filed unexecuted, the ISO shall file
the agreement at the Commission within thirty (30) Business Days of receipt of
the request from the Developer. The ISO will draft to the extent practicable the
portions of the Development Agreement and appendices that are in dispute and
will provide an explanation to the Commission of any matters as to which the
parties disagree. The Developer will provide in a separate filing any comments
that it has on the unexecuted agreement, including any alternative positions it may
have with respect to the disputed provisions.
31.2.8.1.7
Upon the ISO’s and Developer’s execution of the Development
Agreement or the ISO’s filing of an unexecuted Development Agreement with the
Commission pursuant to Section 31.2.8.1.6, the ISO and Developer shall perform
their respective obligations in accordance with the terms of the Development
Agreement that are not in dispute, subject to modifications by the Commission.
The Connecting Transmission Owner(s) and Affected System Operator(s) that are
identified in Attachment P of the ISO OATT in connection with the selected
alternative regulated transmission solution shall act in good faith in timely
performing their obligations that are required for the Developer to satisfy its
obligations under the Development Agreement.
31.2.8.1.8
Other Developers and Transmission Owners proposing alternative
regulated solutions that the ISO has determined will resolve the identified
Reliability Need may submit these proposals to the appropriate governmental
agency(ies) and/or authority(ies) for review. The ISO does not determine the
solution that will be permitted by the appropriate governmental agency(ies) and/or
authority(ies) with jurisdiction over siting or whether the regulated backstop
solution or an alternative regulated solution will be constructed to address the
identified Reliability Need. If the appropriate governmental agency(ies) and/or
authority(ies) makes a final determination that an alternative regulated solution
should be permitted and constructed to satisfy a Reliability Need and that the
regulated backstop solution should not proceed, implementation of the alternative
regulated solution will be the responsibility of the Transmission Owner or Other
Developer that proposed the alternative regulated solution, and the Responsible
Transmission Owner will not be responsible for addressing the Reliability Need
through the implementation of its regulated backstop solution. Should a regulated
solution not be implemented, the ISO may request a Gap Solution pursuant to
Section 31.2.11 of this Attachment Y.
31.2.8.2 Halting and Related Cost Recovery Requirements
31.2.8.2.1
If the ISO has triggered a regulated backstop solution under Sections
31.2.8.1.2, 31.2.8.1.3, 31.2.8.1.4, or 31.2.8.1.5, the ISO will immediately notify
the Responsible Transmission Owner, post such notice on its website, and will
state in the next CRP if it determines that the regulated backstop solution is no
longer needed and should be halted because either: (i) the ISO has determined that
there are sufficient market-based solutions to ensure that the identified Reliability
Need is met by the need date, or (ii) the ISO: (A) has triggered an alternative
regulated transmission solution that the ISO selected in the CRP as the more
efficient or cost effective transmission solution and (B) has determined that it is
no longer necessary for the Responsible Transmission Owner to proceed with a
regulated backstop solution in parallel with the selected alternative regulated
transmission solution to ensure the identified Reliability Need is satisfied by the
need date. In making its determination under Section 31.2.8.2.1(ii), the ISO will
review the status of the development by the Other Developer or Transmission
Owner of the selected alternative regulated transmission solution, including, but
not limited to, reviewing: (i) whether the Developer has executed a Development
Agreement or requested that it be filed unexecuted with the Commission pursuant
to Section 31.2.8.1.6; (ii) whether the Developer is timely progressing against the
milestones set forth in the Development Agreement; and (iii) the status of the
Developer’s obtaining required permits or authorizations, including whether the
Developer has received its Article VII certification or other applicable siting
permits or authorizations under New York State law.
If a regulated backstop solution is halted by the ISO, all of the costs
incurred and commitments made by the Responsible Transmission Owner up to
that point, including reasonable and necessary expenses incurred to implement an
orderly termination of the project, to the extent permitted by the Commission in
accordance with its regulations on abandoned plant recovery, will be recoverable
by the Responsible Transmission Owner under the cost recovery mechanism in
Rate Schedule 10 of this tariff regardless of the nature of the solution.
31.2.8.2.2
If the ISO has triggered an alternative regulated transmission project under
Sections 31.2.8.1.3 or 31.2.8.1.4 that the ISO has selected as the more efficient or
cost effective solution, the ISO will immediately notify the Other Developer or
Transmission Owner, post such notice on its website, and will state in the next
CRP if it determines that the regulated transmission solution is no longer needed
and should be halted because the ISO has determined that there are sufficient
market-based solutions to ensure that the identified Reliability Need is met by the
need date.
If a selected alternative regulated transmission solution is halted by the
ISO, all of the costs incurred and commitments made by the Other Developer or
Transmission Owner up to that point, including reasonable and necessary
expenses incurred to implement an orderly termination of the project, to the extent
permitted by the Commission in accordance with its regulations on abandoned
plant recovery, will be recoverable by the Other Developer or Transmission
Owner under the cost recovery mechanism in Rate Schedule 10 of this tariff.
31.2.8.2.3
Once the Responsible Transmission Owner receives state regulatory
approval of the regulated backstop solution, or, if state regulatory approval is not
required, once the Responsible Transmission Owner receives necessary regulatory
approval, the entry of a market-based solution or an alternative regulated
transmission solution will not result in the halting by the ISO of the regulated
backstop solution pursuant to Section 31.2.8.2.1. Similarly, once the Other
Developer or Transmission Owner receives its state regulatory approval or any
other necessary regulatory approval of its triggered alternative regulated
transmission solution, the entry of a market-based solution will not result in the
halting by the ISO of the regulated transmission solution pursuant to Section
31.2.8.2.2.
31.2.8.2.4
The ISO is not required to review market-based solutions to determine
whether they will meet the identified Reliability Need by the need date after the
triggered alternative regulated transmission solution or regulated backstop
solution has received federal and state regulatory approval, unless a federal or
state regulatory agency requests the ISO to conduct such a review. The ISO will
report the results of its review to the federal or state regulatory agency, with
copies to the Responsible Transmission Owner, Other Developer, or Transmission
Owner.
31.2.8.2.5
If the appropriate federal, state or local agency(ies) does not approve a
necessary authorization for the triggered regulated backstop solution or alternative
regulated transmission solution, all of the necessary and reasonable costs incurred
and commitments made up to the final federal, state or local regulatory decision,
including reasonable and necessary expenses incurred to implement an orderly
termination of the project, to the extent permitted by the Commission in
accordance with its regulations on abandoned plant recovery, will be recoverable
by the Responsible Transmission Owner, Other Developer, or Transmission
Owner under the ISO cost recovery mechanism in Rate Schedule 10 of the ISO
OATT regardless of the nature of the solution.
31.2.8.2.6
If a necessary federal, state or local authorization for a triggered
alternative regulated transmission solution or regulated backstop solution is
withdrawn, all expenditures and commitments made up to that point including
reasonable and necessary expenses incurred to implement an orderly termination
of the project, to the extent permitted by the Commission in accordance with its
regulations on abandoned plant recovery, will be recoverable under the ISO cost
recovery mechanism in Rate Schedule 10 of the ISO OATT by the Responsible
Transmission Owner, Other Developer, or Transmission Owner regardless of the
nature of the solution.
31.2.8.2.7
If a material modification to the regulated backstop solution or the
alternative regulated transmission solution is proposed by any federal, state or
local agency, the Responsible Transmission Owner, Other Developer, or
Transmission Owner will request the ISO to conduct a supplemental reliability
review. If the ISO identifies any reliability deficiency in the modified solution,
the ISO will so advise the Responsible Transmission Owner, Other Developer, or
Transmission Owner and the appropriate federal, state or local regulatory
agency(ies).
31.2.8.3 Criteria for Cutoff Date of Market-Based Solution
31.2.8.3.1
The ISO will apply the criteria in this Section 31.2.8.3 for determining the
cutoff date for a determination that a market-based solution will not be available
to meet a Reliability Need by the need date.
31.2.8.3.2
In the first instance, the ISO shall employ its procedures for monitoring
the viability of a market-based solution to determine when it may no longer be
viable. Under the conditions where a market-based solution is proceeding after
the Trigger Date for the relevant regulated solution, it becomes even more critical
for the ISO to conduct a continued analysis of the viability of such market-based
solutions.
31.2.8.3.3
The Developer of such a market-based solution shall submit updated
information to the ISO twice during each reliability planning process cycle, first
during the input phase of the RNA, and again during the solutions phase during
the period allowed for the solicitation for market-based and regulated solutions.
If no solutions are requested in a particular year, then the second update will be
provided during the ISO’s analysis of whether existing solutions continue to meet
identified Reliability Needs. The updated information of the project status shall
include: status of final permits, status of major equipment, current status of
construction schedule, estimated in-service date, any potential impediments to
completion by the Target Year, and any other information requested by the ISO.
31.2.8.3.4
The Developer shall immediately report to the ISO when it has any
indication of a material change in the project status or that the project in-service
date may slip beyond the Target Year. A material change shall include, but not be
limited to, a change in the financial viability of the Developer, a change in siting
status, or a change in a major element of the project development.
31.2.8.3.5
Based upon the above information, the ISO will perform an independent
review of the development status of the market-based solution to determine
whether it remains viable to meet the identified Reliability Need by the need date.
If the ISO, at any time, learns of a material change in the project status of a
market-based solution, it may, at that time, make a determination as to the
continued viability of such project.
31.2.8.3.6
The ISO, prior to making a determination about the viability of a specific
proposed solution, will communicate its intended determination to the project
Developer along with the basis for its intended determination. The ISO shall
provide the Developer a reasonable period (not more than 2 weeks) to respond to
the ISO’s intended determination, including an opportunity to provide additional
information to the ISO to support the continued viability of the proposed solution.
31.2.8.3.7
If the ISO determines that a market-based solution that is needed to meet
an identified Reliability Need is no longer viable, it will request that a regulated
solution proceed or seek other measures including, but not limited to, a Gap
Solution, to ensure the reliability of the system.
31.2.8.3.8
If the ISO determines that the market-based solution is still viable, but that
its in-service date is likely to slip beyond the Target Year, the ISO may, if needed,
request the Responsible Transmission Owner to prepare a Gap Solution in
accordance with the provisions of Section 31.2.11 of this Attachment Y.
31.2.9
Process for Consideration of Regulated Backstop Solution and Alternative
Regulated Solutions
Upon a determination by the ISO under Section 31.2.8 that a regulated solution should
proceed, the Responsible Transmission Owner, Other Developer, or Transmission Owner will
make a presentation to the ESPWG that will provide a description of the regulated solution. The
presentation will include a non-binding preliminary cost estimate of that regulated solution;
provided, however, that the Responsible Transmission Owner, Other Developer or Transmission
Owner shall be entitled to full recovery of all reasonably incurred costs as described in Rate
Schedule 10 of the ISO OATT. The ISO and stakeholders through this process will have the
opportunity to review and discuss the scope of the projects and their associated non-binding
preliminary cost estimates prior to implementation.
31.2.10 Process for Addressing Inability of Responsible Transmission Owner,
Other Developer, or Transmission Owner to Complete Triggered
Regulated Solution
31.2.10.1
The ISO may take the actions described in Sections 31.2.10.1.1 through
31.2.10.1.4 as soon as practicable if: (i) a Responsible Transmission Owner, Other
Developer or Transmission Owner of a regulated transmission solution is required
to enter into a Development Agreement pursuant to Section 31.2.8.1.6, and (ii)
one of the following events occur: (A) the Responsible Transmission Owner,
Other Developer or Transmission Owner responsible for the regulated
transmission solution does not execute the Development Agreement, or does not
request that it be filed unexecuted with the Commission, within the timeframes set
forth in Section 31.2.8.1.6, or (B) the ISO determines that an effective
Development Agreement may be terminated or terminates the Development
Agreement under the terms of the agreement prior to the completion of the term
of the agreement.
31.2.10.1.1
If the Development Agreement has been filed with and accepted by the
Commission and is terminated under the terms of the agreement, the ISO shall,
upon terminating the Development Agreement, file a notice of termination with
the Commission.
31.2.10.1.2
The ISO may revoke its selection of the regulated transmission solution
and the eligibility of the Developer to recover its costs pursuant to the ISO’s
regional cost allocation mechanism; provided, however, the Developer may
recover its costs to the extent provided in Sections 31.2.8.1.1, 31.2.8.2.1,
31.2.8.2.2, 31.2.8.2.5, and 31.2.8.2.6 or as otherwise determined by the
Commission; provided, further, that if the Developer is the Responsible
Transmission Owner, it may also recover costs to the extent permitted under the
ISO/TO Reliability Agreement.
31.2.10.1.3
The ISO may take one or more of the following actions to address the
Reliability Need based on the particular circumstances: (i) address the Reliability
Need in the CRP for the next planning cycle; (ii) direct the Developer to continue
with the development of its regulated transmission solution for completion
beyond the in-service date required to address the Reliability Need; (iii) direct the
Responsible Transmission Owner to proceed with its regulated backstop solution
if it has not yet been halted by the ISO pursuant to Section 31.2.8.2.1; (iv) request
that the Responsible Transmission Owner complete the selected alternative
regulated transmission solution; (v) commence the Gap Solution process under
Section 31.2.11; (vi) adopt new ISO or Transmission Owner operating
procedures; and/or (vii) take any other action the ISO reasonably considers is
appropriate to address the Reliability Need. If a Responsible Transmission Owner
agrees to complete the selected alternative regulated transmission solution, it shall
enter into a Development Agreement with the ISO in accordance with Sections
31.2.8.1.6 and 31.2.8.1.7.
31.2.10.1.4
If the Responsible Transmission Owner agrees to complete the selected
alternative regulated transmission solution, the Responsible Transmission Owner
and the Other Developer or Transmission Owner that proposed the selected
alternative regulated transmission solution shall work cooperatively with each
other to implement the transition, including negotiating in good faith with each
other to transfer the project; provided, however, that the transfer is subject to: (i)
any required approvals by the appropriate governmental agency(ies) and/or
authority(ies), (ii) any requirements or restrictions on the transfer of Developer’s
rights-of-way under federal or state law, regulation, or contract (including
mortgage trust indentures or debt instruments), and (iii), if the Developer is a New
York public authority, any requirements or restrictions on the transfer under the
New York Public Authorities Law; provided, further, that the Responsible
Transmission Owner and the Developer will address any disputes regarding the
transfer of the project in accordance with the dispute resolution provisions in
Article 11 of the ISO Services Tariff.
31.2.10.2 If: (i) the Responsible Transmission Owner’s non-transmission or partial
transmission regulated backstop solution has been triggered by the ISO under
Sections 31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4, and the regulated backstop solution
has not been halted by the ISO under Section 31.2.8.2.1, and (ii) the ISO
determines that the Responsible Transmission Owner: (A) has not submitted its
proposed regulated backstop solution for necessary regulatory action within a
reasonable period of time, (B) is unable to or fails to obtain the approvals or
property rights necessary to construct the project, or (C) is otherwise not taking
the actions necessary to construct the project to satisfy the Reliability Need by the
need date, the ISO shall: (i) submit a report to the Commission for its
consideration and determination of whether action is appropriate under federal
law, and (ii) take such action as it reasonably considers is appropriate to ensure
that the Reliability Need is satisfied by the need date.
31.2.11 Gap Solutions
31.2.11.1
If the ISO determines that neither market-based proposals nor regulated
proposals can satisfy the Reliability Needs by the need date, the ISO will set forth
its determination that a Gap Solution is necessary in the CRP. The ISO will also
request the Responsible Transmission Owner to seek a Gap Solution. Gap
Solutions may include generation, transmission, or demand side resources.
31.2.11.2
If there is an imminent threat to the reliability of the New York State
Power System, the ISO Board, after consultation with the NYDPS, may request
the appropriate Transmission Owner or Transmission Owners to propose a Gap
Solution outside of the normal planning cycle.
31.2.11.3
Notwithstanding Sections 31.2.11.1 and 31.2.11.2, if a Market Participant
notifies the ISO of its intent for its Generator to be Retired or to enter into a
Mothball Outage pursuant to Section 38.3.1 of Attachment FF of the ISO OATT
or if a Market Participant’s Generator enters into an ICAP Ineligible Forced
Outage pursuant to Section 5.18.2.1 of the ISO Services Tariff, the ISO will
evaluate whether a Generator Deactivation Reliability Need or an immediate
reliability need will result from the Generator’s deactivation and will address any
resulting Generator Deactivation Reliability Need or immediate reliability need in
accordance with the Generator Deactivation Process set forth in Attachment FF of
the ISO OATT.
31.2.11.4
Upon the ISO’s determination of the need for a Gap Solution, pursuant to
Sections 31.2.11.1 or 31.2.11.2 above, the Responsible Transmission Owner will
propose such a solution as soon as reasonably possible, for consideration by the
ISO and NYDPS. The Responsible Transmission Owner shall be eligible to
recover its costs for developing its Gap Solution proposal and seeking necessary
approvals pursuant to the cost recovery requirements in Section 31.5.6 of this
Attachment Y and Rate Schedule 10 of the ISO OATT.
31.2.11.5
Any party may submit an alternative Gap Solution proposal to the ISO and
the NYDPS for their consideration. The ISO shall evaluate all Gap Solution
proposals to determine whether they will meet the Reliability Need or imminent
threat. The ISO will also evaluate, as an alternative Gap Solution proposal, any
Generator in a Mothball Outage or an ICAP Ineligible Forced Outage to
determine whether its return to service would meet the Reliability Need or
imminent threat; provided, however, that the Mothball Outage began on or after
May 1, 2015 and the ICAP Ineligible Forced Outage followed a Forced Outage
that began after May 1, 2015. The ISO will report the results of its evaluation to
the party making the proposal, or to the Generator when evaluating its return to
service, as well as to the NYDPS and/ or other appropriate governmental
agency(ies) and/or authority(ies) for consideration in their review of the
proposals. The appropriate governmental agency(ies) and/or authority(ies) with
jurisdiction over the implementation or siting of Gap Solutions will determine
whether the Gap Solution or an alternative Gap Solution will be implemented to
address the identified Reliability Need. When the return to service of a Generator
in a Mothball Outage or an ICAP Ineligible Forced Outage has been selected as
either the Gap Solution or to resolve a reliability issue arising on a non-New York
State Bulk Power Transmission Facility during its outage, the compensation and
return to service procedures set forth in Section 5.18.4 of the Services Tariff shall
apply.
31.2.11.6
A Responsible Transmission Owner, Other Developer, or Transmission
Owner may recover its costs with respect to a transmission Gap Solution that is
implemented pursuant to Section 31.2.11.5 in accordance with the cost recovery
requirements in Section 31.5.6 of this Attachment Y and Rate Schedule 10 of the
ISO OATT.
31.2.11.7
Gap Solution proposals submitted under Sections 31.2.11.4 and 31.2.11.5
shall be designed to be temporary solutions and to strive to be compatible with
permanent market-based proposals.
31.2.11.8
A permanent regulated solution, if appropriate, may proceed in parallel
with a Gap Solution.
31.2.12 Confidentiality of Solutions
31.2.12.1
The term “Confidential Information” shall include all types of solutions to
Reliability Needs that are submitted to the ISO as a response to Reliability Needs
identified in any RNA issued by the ISO as part of the reliability planning process
if the Developer of that solution designates such reliability solutions as
“Confidential Information.” Notwithstanding the requirements in this Section
31.2.12 or the Developer’s designation of project information as “Confidential
Information,” the ISO may publicly disclose information regarding the proposed
facility that the ISO is required to disclose under its interconnection or
transmission expansion processes pursuant to Sections 3.7 or 4.5 of the ISO
OATT or Attachments X or P of the ISO OATT.
31.2.12.2
For regulated backstop solutions and plans submitted by the Responsible
Transmission Owner in response to the findings of the RNA, the ISO shall
maintain the confidentiality of same until the ISO and the Responsible
Transmission Owner have agreed that the Responsible Transmission Owner has
submitted viable and sufficient regulated backstop solutions and plans to meet the
Reliability Needs identified in an RNA and the Responsible Transmission Owner
consents to the ISO’s inclusion of the proposed solution in the CRP. Thereafter,
the ISO shall disclose the regulated backstop solutions and plans to the Market
Participants; however, any preliminary cost estimates that may have been
provided to the ISO shall not be disclosed.
31.2.12.3
For an alternative regulated response, the ISO shall determine, after
consulting with the Developer thereof, whether the response would meet a
Reliability Need identified in an RNA, whether the response is viable and
sufficient to meet all or part of the Reliability Need, and the Developer consents
to the ISO’s inclusion of the proposed solution in the CRP. Thereafter, the ISO
shall disclose the alternative regulated response to the Market Participants and
other interested parties; however, any preliminary cost estimates that may have
been provided to the ISO shall not be disclosed.
31.2.12.4
For a market-based response, the ISO shall maintain the confidentiality of
same during the reliability planning process and in the CRP, except for the
following information which may be disclosed by the ISO: (i) the type of
resource proposed (e.g., generation, transmission, demand side); (ii) the size of
the resource expressed in megawatts of equivalent load that would be served by
that resource; (iii) the subzone in which the resource would interconnect or
otherwise be located; and (iv) the proposed in-service date of the resource.
31.2.12.5
In the event that the Developer of a market-based response has made a
public announcement of its project or has submitted a proposal for
interconnection with the ISO, the ISO shall disclose the identity of the market-
based Developer and the specific project during the reliability planning process
and in the CRP.
31.2.13 Monitoring of Reliability Project Status
31.2.13.1
The ISO will monitor and report on the status of market-based solutions to
ensure their continued viability to meet Reliability Needs by the need date in the
CRP. The ISO shall assess the continued viability of such projects using the
following criteria:
31.2.13.1.1
Between three and five years before the Trigger Date for a regulated
solution, the ISO will use a screening analysis to verify the feasibility of the
proposed market-based solution (this analysis will not require final permit
approvals or final contract documents).
31.2.13.1.2
Between one and two years before the Trigger Date for a regulated
solution, the ISO will perform a more extensive review of the proposed market-
based solution, including such elements as: status of the required interconnection
studies, contract negotiations, permit applications, financing, and Site Control.
31.2.13.1.3
Less than one year before the Trigger Date of a regulated solution, the ISO
will perform a detailed review of the market-based solution’s status and schedule,
including the status of: (1) final permits; (2) required interconnection studies; (3)
the status of an interconnection agreement; (4) financing; (5) equipment; and (6)
the implementation of construction schedules.
31.2.13.1.4
If the ISO, following its analysis, determines that a proposed market-based
solution is no longer viable to meet the Reliability Need, the proposed market-
based solution will be removed from the list of potential market-based solutions.
31.2.13.2
The ISO will monitor and report on the status of regulated solutions to
ensure their continued viability to meet Reliability Needs by the need date in the
CRP. The ISO will undertake this monitoring and reporting in accordance with
this Attachment Y, ISO Procedures, and the terms of the Development Agreement
(if applicable) until the project has been completed and is in-service or has been
halted in accordance with this Attachment Y or the terms of the Development
Agreement (if applicable). Prior to the Trigger Date for the regulated solution,
the ISO shall assess the continued viability of regulated solutions using the
following criteria:
31.2.13.2.1
Between three and five years before the Trigger Date for the regulated
solution, the ISO will use a screening analysis to verify the feasibility of the
regulated solution.
31.2.13.2.2
Between one and two years before the Trigger Date for the regulated
solution, the ISO will perform a more extensive review of the proposed regulated
solution, including such elements as: the status of the required interconnection
studies, contract negotiations, permit applications, financing, and Site Control.
31.2.13.2.3
Less than one year before the Trigger Date for the regulated solution, the
ISO will perform a detailed review of the regulated solution’s status, including the
status of: (1) final permits; (2) required interconnection studies; (3) the status of
an interconnection agreement; (4) financing; (5) equipment; and (6) the
implementation of construction schedules.
31.2.13.2.4
Prior to making a determination about the viability of a regulated solution,
the ISO will communicate its intended determination to the project sponsor along
with the basis for its intended determination, and will provide the sponsor a
reasonable period (not more than two weeks) to respond to the ISO’s intended
determination, including an opportunity to provide additional information to the
ISO to support the continued viability of the proposed regulated solution. If the
ISO, following its analysis, determines that a proposed regulated solution is no
longer viable to meet the Reliability Need, the proposed regulated solution will be
removed from the list of potential regulated solutions.
31.3
Economic Planning Process
31.3.1
Congestion Assessment and Resource Integration Study for Economic
Planning
31.3.1.1 General
The ISO shall prepare and publish the CARIS as described below. Each CARIS shall (1)
develop a ten-year projection of congestion and shall identify, rank, and group the most
congested elements on the New York bulk power system based on historic and projected
congestion; and (2) include three studies, selected pursuant to Section 31.3.1.2.2, of the potential
impacts of generic solutions to mitigate the identified congestion.
The CARIS process shall determine whether to approve an Interregional Transmission
Project, identified and evaluated under the “Analysis and Consideration of Interregional
Transmission Projects” section of the Interregional Planning Protocol, if any, and proposed in the
NYISO’s economic planning process, as an economic transmission project in lieu of a proposed
regional economic transmission project for regulated cost allocation and recovery under the ISO
Tariff.
The CARIS will align with the reliability planning process.
31.3.1.2 Interested Party Participation in the Development of the CARIS
31.3.1.2.1
The ISO shall develop the CARIS in consultation with Market Participants
and all other interested parties. The TPAS will have responsibilities consistent
with ISO Procedures for review of the ISO’s technical analyses. ESPWG will
have responsibilities consistent with ISO Procedures for providing commercial
input and assumptions to be used in the development of the congestion assessment
and the congestion assessment scenarios provided for under Section 31.3.1.5, and
in the reporting and analysis of congestion costs. Coordination and
communication will be established and maintained between these two groups and
ISO staff to allow Market Participants and other interested parties to participate in
a meaningful way during each stage of the economic planning process. The ISO
staff shall report any majority and minority views of these collaborative
governance work groups when it submits the CARIS to the Business Issues
Committee for a vote, as provided below.
31.3.1.2.2
The ISO, in conjunction with ESPWG, will develop criteria for the
selection and grouping of the three congestion and resource integration studies
that comprise each CARIS, as well as for setting the associated timelines for
completion of the selected studies. Study selection criteria may include
congestion estimates, and shall include a process to prioritize the three studies that
comprise each CARIS. Criteria shall also include a process to set the cut off date
for inputs into and completion of each CARIS study cycle.
31.3.1.2.3
The ISO, in conjunction with ESPWG, will develop a process by which
interested parties can request and fund other congestion and resource integration
studies, in addition to those included in each CARIS. These individual congestion
and resource integration studies are in addition to those studies that a customer
can request related to firm point-to-point transmission service pursuant to Section
3.7 of the ISO OATT, studies that a customer can request related to Network
Integration Transmission Service pursuant to Section 4.5 of the ISO OATT,
studies related to interconnection requests under Attachment X or Attachment Z
of the ISO OATT, or studies related to Transmission Interconnection Applications
under Attachment P.
31.3.1.2.4
The ISO shall post all requests for congestion and resource integration
studies on its website.
31.3.1.3 Preparation of the CARIS
31.3.1.3.1
The Study Period for the CARIS shall be the same ten-year Study Period
covered by the most recently approved CRP.
31.3.1.3.2
The CARIS will assume a reliable system throughout the Study Period,
based first upon the solutions identified in the most recently completed viability
and sufficiency analysis performed pursuant to 31.2.5.7, as part of the CRP
process, and reported to stakeholders and the NYDPS for comment. The baseline
system for the CARIS shall first incorporate sufficient viable market-based
solutions to meet the identified Reliability Needs as well as any regulated
backstop solutions triggered by an ISO request pursuant to Section 31.2.8 of this
Attachment Y. The ISO, in conjunction with the ESPWG, will develop
methodologies to scale back market-based solutions to the minimum needed to
meet the identified Reliability Needs, if more have been proposed than are
necessary to meet the identified Reliability Needs. Regulated backstop solutions
that have been proposed but not triggered pursuant to Section 31.2.8 shall also be
used if there are insufficient market-based solutions for the ten-year Study Period.
Multiple market-based solutions, as well as regulated solutions to Reliability
Needs, may be included in the scenario assessments described in Section 31.3.1.5.
31.3.1.3.3
In conducting the CARIS, the ISO shall combine the component studies
selected and assess system congestion and resource integration over the Study
Period, measuring congestion by the metrics discussed in Appendix A to this
Attachment Y. The ISO, in conjunction with the ESPWG, will develop the
specific production costing model to be used in the CARIS. All resource types
shall be considered on a comparable basis as potential solutions to the congestion
identified: generation, transmission, demand response, and energy efficiency.
The CARIS may include consideration of the economic impacts of advancing a
regulated back stop solution contained in the CRP.
31.3.1.3.4
In conducting the CARIS, the ISO shall conduct benefit/cost analysis of
each potential solution to the congestion identified, applying benefit/cost metrics
that are described in this Section 31.3.1.3. The principal benefit metric for the
CARIS analysis will be expressed as the present value of the NYCA-wide
production cost reduction that would result from each potential solution. The
present value of the NYCA-wide production cost reduction will be determined in
accordance with the following formula:
Present Value in year 1 = Sum of the Present Values from each of the 10 years of the
Study Period.
The discount rate to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners.
31.3.1.3.5
Additional benefit metrics shall include estimates of reductions in losses,
LBMP load costs, generator payments, ICAP costs, Ancillary Services costs,
emission costs, and TCC payments. The ISO will work with the ESPWG to
determine the most useful metrics for each CARIS cycle, given overall ISO
resource requirements. The additional metrics will estimate the benefits of the
potential generic solutions in mitigating the congestion identified for information
purposes only. All the quantities, except ICAP, will be the result of the forward
looking production cost simulation. The additional benefit metrics will be
determined by measuring the difference between the CARIS base case system
value and a system value when the potential generic solution is added. All four
resource types will be considered as potential generic solutions to the congestion
identified, such as generation, transmission, and/or demand response. The value
of the additional metrics will be expressed in present value by using the following
formula:
Present Value in year 1 = Sum of the Present Values from each of the 10 years of the
Study Period.
The discount rate to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners. The
definitions of the LBMP load cost metric, generator payments metric, reduction in
losses metric, Ancillary Services costs metric, and TCC payment metric are set
forth below.
31.3.1.3.5.1 LBMP load costs measure the change in total load payments and
unhedged load payments. Total load payments will include the LBMP payments
(energy, congestion and losses) paid by electricity demand (forecasted load,
exports, and wheeling). Exports will be consistent with the input assumptions for
each neighboring control area. Unhedged load payments will represent total load
payments minus the TCC payments.
31.3.1.3.5.2 Reductions in losses measure the change in marginal losses payments.
Losses payments will be based upon the loss component of the zonal LBMP load
payments.
31.3.1.3.5.3 Generator payments measure the change in generation payments.
Generation payments will include the LBMP payments (energy, congestion,
losses), and Ancillary Services payments made to electricity suppliers. Ancillary
Services costs will include payments for Regulation Services and Operating
Reserves, including 10 Minute Synchronous, 10 Minute Non-synchronous and 30
Minute Non-synchronous. Generator payments will be the sum of the LBMP
payments and Ancillary Services payments to generators and imports. Imports
will be consistent with the input assumptions for each neighboring Control Area.
31.3.1.3.5.4 The TCC payment metric set forth below will be used for purposes of the
study phase of the CARIS process, and will not be used for regulated economic
transmission project cost allocation under Section 31.5.4.4 of this Attachment Y.
The TCC payment metric will measure the change in total congestion rents
collected in the day-ahead market. These congestion rents shall be calculated as
the product of the Congestion Component of the Day-Ahead LBMP in each Load
Zone or Proxy Generator Bus and the withdrawals scheduled in each hour at that
Load Zone or Proxy Generator Bus, minus the product of the Congestion
Component of the Day-Ahead LBMP at each Generator Bus or Proxy Generator
Bus and the injections scheduled in each hour at that Generator bus or Proxy
Generator Bus, summed over all locations and hours.
31.3.1.3.5.5 The emission metric will measure the change in CO2, NOx, and SO2,
emissions in tons on a zonal basis as well as the change in emission cost by
emission type. Emission costs will be reflected in the development of the
production cost curve.
31.3.1.3.5.6 The calculation of the ICAP cost metric will be determined as set forth
below. The ICAP cost metric will be highly dependent on the rules and
procedures guiding the calculation of the IRM, LCR, and the ICAP Demand
Curves, both for the next capability period and future capability periods. In each
CARIS cycle, the ISO will review, with the ESPWG and, as appropriate, other
ISO committees, the results of the ICAP cost metric.
31.3.1.3.5.6.1 The ICAP metric, in the form of a megawatt impact, will be computed for
both generic and actual economic project proposals based on a methodology that:
(1) determines the base system LOLE for the applicable horizon year; (2) adds the
proposed project; and (3) calculates the LOLE for the system with the addition of
the proposed project. If the system LOLE is lower than that of the base system,
the ISO will reduce generation in all NYCA zones proportionally (i.e., based on
proportion of zonal capacity to total NYCA capacity) until the base system LOLE
is achieved. That amount of reduced generation is the NYCA megawatt impact.
31.3.1.3.5.6.2 The ISO will calculate both of the following ICAP cost metrics described
in subsections (1) and (2) below by first determining the megawatt impact
described above in Section 31.3.1.3.5.6.1 and then:
(1)
For Rest of State, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in Rest of State under the assumption that the proposed generic
project is not in place, with that forecast based on the latest available ICAP
Demand Curve for the NYCA and the amount of Installed Capacity available in
the NYCA, as shown in the NYISO Load and Capacity Data Report developed for
that year; and (ii) multiplying that forecasted cost per megawatt-year for Rest of
State in that year by the sum of the megawatt impact for all Load Zones contained
within Rest of State, as calculated in accordance with subsection (A) of this
Section 31.3.1.3.5.4.
For each Locality, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in that Locality under the assumption that the proposed generic
project is not in place, with that forecast based on the latest available ICAP
Demand Curve for that Locality and the amount of Installed Capacity available in
that Locality as shown in the relevant NYISO Load and Capacity Data Report
developed for that year, and (ii) multiplying that forecasted cost per megawatt-
year for that Locality in each year by the sum of the megawatt impact for all Load
Zones contained within that Locality, as calculated in accordance with subsection
(A) of this Section 31.3.1.3.5.4.
This ICAP cost metric will then be presented for each applicable planning year as
a stream of present value benefits for each Locality and for Rest of State. The
applicable planning years start with the proposed commercial operation date of
the proposed generic project and end ten years after the proposed commercial
operation date of the proposed generic project.
(2)
For Rest of State, the ISO will measure the cost impact of a proposed economic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in Rest of State under the assumption that the proposed generic
project is in place, with that forecast based on the latest available ICAP Demand
Curve for the NYCA and the amount of Installed Capacity available in the
NYCA; (ii) subtracting that forecasted cost per megawatt-year from the forecasted
cost per megawatt-year of Installed Capacity in Rest of State calculated in
subsection (1) under the assumption that the proposed generic project is not in
place; and (iii) multiplying that difference by fifty percent (50%) of the assumed
amount of Installed Capacity available in Rest of State as calculated from the
relevant NYISO Load and Capacity Data Report developed for the CARIS
process.
For each Locality, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in that Locality under the assumption that the proposed generic
project is in place, with that forecast based on the latest available ICAP Demand
Curve for that Locality and the amount of Installed Capacity available in that
Locality as shown in the relevant NYISO Load and Capacity Data Report
developed for that year; (ii) subtracting the greater of that forecasted cost per
megawatt-year with the proposed generic project in place or the forecasted Rest of
State Installed Capacity cost per megawatt-year with the proposed generic project
in place from the forecasted cost of Installed Capacity in that Locality calculated
in subsection (1) under the assumption that the proposed generic project is not in
place; and (iii) multiplying that difference by fifty percent (50%) of assumed
amount of Installed Capacity available in that Locality, as taken from the relevant
Load and Capacity tables developed for the CARIS process.
This ICAP cost metric will then be represented for each applicable planning year
as a stream of present value benefits for each Locality and for Rest of State. The
applicable planning years start with the proposed commercial operation date of
the proposed generic project and end with the earlier of: (i) the year when the
system, with the proposed generic project in place, reaches an LOLE of 0.1, or (ii)
ten years after the proposed commercial operation date of the proposed generic
project.
(3)
The forecast of Installed Capacity costs per megawatt-year are developed by: first,
escalating the Net Cost of New Entry (“CONE”) for the NYCA or a Locality from
the most recently completed ICAP Demand Curves for each year of the planning
period; second, determining the future proxy Locational Minimum Installed
Capacity Requirement or Minimum Installed Capacity Requirement for the
NYCA as the actual amount of Installed Capacity in the Locality or the NYCA for
the year that NYCA reaches 0.1 LOLE; third, reducing the cost per megawatt-
year in each year from the escalated Net CONE to reflect the excess Installed
Capacity from the NYISO Load and Capacity Data Report above the future proxy
Minimum Installed Capacity Requirement with the adjustment calculated from
the excess and the slope of the ICAP Demand Curve.
The forecasts of Installed Capacity costs for Localities or Rest of State performed
in subsections (1) and (2) above shall, in addition to the assumptions listed above,
be based upon: (i) the forecasted Net CONE for the Locality (the NYCA in the
case of the Rest of State forecast); (ii) the amount of Installed Capacity required
to meet the future proxy Locational Minimum Installed Capacity Requirement
(the Minimum Installed Capacity Requirement for the NYCA in the case of the
Rest of State forecast); (iii) the slope of the relevant ICAP Demand Curve, and
(iv) the smallest quantity where the cost of Installed Capacity on that ICAP
Demand Curve reaches zero.
31.3.1.3.6
As referenced in Section 31.2.1.3, the ISO, using engineering judgment,
will determine whether a regional alternative transmission solution might more
efficiently or more cost effectively address congestion on the BPTFs identified in
the CARIS that impacts more than one Transmission District than any local
transmission solutions identified by the Transmission Owners in their LTPs in the
event the LTPs specify that such transmission solutions are included to address
congestion for economic reasons.
31.3.1.4 Planning Participant Data Input
At the ISO’s request, Market Participants, Developers, and other parties shall provide, in
accordance with the schedule set forth in the ISO Procedures, the data necessary for the
development of the CARIS. This input will include but not be limited to existing and planned
additions and modifications to the New York State Transmission System (to be provided by
Transmission Owners and municipal electric utilities); proposals for merchant transmission
facilities (to be provided by merchant Developers); generation additions and retirements (to be
provided by generator owners and Developers); demand response programs (to be provided by
demand response providers); and any long-term firm transmission requests made to the ISO.
The relevant Transmission Owners will assist the ISO in developing the potential solution cost
estimates to be used by the ISO to conduct benefit/cost analysis of each of the potential
solutions.
31.3.1.5 Congestion and Resource Integration Scenario Development
The ISO, in consultation with the ESPWG, shall develop congestion and resource
integration scenarios addressing the Study Period. Variables for consideration in the
development of these congestion and resource integration scenarios include but are not limited
to: load forecast uncertainty, fuel price uncertainty, new resources, retirements, emission data,
the cost of allowances and potential requirements imposed by proposed environmental and
energy efficiency mandates, as well as overall ISO resource requirements. The ISO shall report
the results of these scenario analyses in the CARIS.
31.3.1.6 Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of an
economic transmission project on such neighboring ISO/RTO Regions using the respective
planning criteria of such ISO/RTO Regions. The ISO shall report the results in the CARIS. The
ISO shall not bear the costs of required upgrades in another region.
31.3.1.7 CARIS Report Preparation
Once all the analyses described above have been completed, ISO staff will prepare a draft
of the CARIS including a discussion of its assumptions, inputs, methodology, and the results of
its analyses.
31.3.2
CARIS Review Process and Actual Project Proposals
31.3.2.1 Collaborative Governance Process
The draft CARIS shall be submitted to both TPAS and the ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft CARIS. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Following completion
of that review, the draft CARIS reflecting the revisions resulting from the TPAS and ESPWG
review shall be forwarded to the Business Issues Committee and the Management Committee for
discussion and action.
31.3.2.2 Board Action
Following the Management Committee vote, the draft CARIS, with Business Issues
Committee and Management Committee input, will be forwarded to the ISO Board for review
and action. Concurrently, the draft CARIS will be provided to the Market Monitoring Unit for
its review and consideration. The Board may approve the CARIS as submitted, or propose
modifications on its own motion. If any changes are proposed by the Board, the revised CARIS
shall be returned to the Management Committee for comment. The Board shall not make a final
determination on a revised CARIS until it has reviewed the Management Committee comments.
Upon approval by the Board, the ISO shall issue the CARIS to the marketplace by posting it on
its website.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.4 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.3.2.3 Public Information Sessions
In order to provide ample exposure for the market place to understand the content of the
CARIS, the ISO will provide various opportunities for Market Participants and other potentially
interested parties to discuss final CARIS. Such opportunities may include presentations at
various ISO Market Participant committees, focused discussions with various industry sectors,
and /or presentations in public venues.
31.3.2.4 Actual Project Proposals
As discussed in Section 31.3.1 of this Attachment Y, the CARIS analyzes system
congestion over the Study Period and, for informational purposes, provides benefit/cost analysis
and other analysis of potential generic solutions to the congestion identified. If, in response to
the CARIS, a Developer proposes an actual project, including an Interregional Transmission
Project, to address specific congestion identified in the CARIS, then the ISO will: (i) process that
project proposal in accordance with the relevant provisions of Sections 31.5.1, 31.5.4 and 31.5.6
of this Attachment Y, and (ii) for Interregional Transmission Projects, jointly evaluate the project
proposal with the relevant adjacent transmission planning region(s) in accordance with Section
7.3 of the Interregional Planning Protocol.
31.3.2.4.1 Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.3.2.4.1 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.3.2.4.1.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.3.2.4.1.1.1 to demonstrate its capability to satisfy the applicable qualification criteria,
and (ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with
signatory authority, in a form acceptable to the ISO, certifying that the Affiliate will participate
in the Developer’s project in the manner described by the Developer and will abide by the
requirements set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures related and
applicable to the Affiliate’s participation.
31.3.2.4.1.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate and maintain a transmission project proposed to address specific
congestion identified in the CARIS. The ISO shall consider the qualifications of each Developer
in an even-handed and non-discriminatory manner, treating Transmission Owners and Other
Developers alike.
31.3.2.4.1.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a transmission project as a solution to address specific congestion identified in the
CARIS based on the following criteria:
31.3.2.4.1.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.3.2.4.1.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.3.2.4.1.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement or equivalent information;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to address specific congestion identified in the CARIS.
31.3.2.4.1.1.1.4 A detailed plan describing how the Developer - in the absence of
previous experience financing, developing, constructing, operating, or
maintaining transmission facilities - will finance, develop, construct, operate, and
maintain a transmission facility, including the financial, technical, and
engineering qualifications and experience and capabilities of any third parties
with which it will contract for these purposes.
31.3.2.4.1.1.2 Developer Qualification Determination
Any Developer seeking to become qualified may submit the required information, or
update any previously submitted information, at any time. The ISO shall treat on a confidential
basis in accordance with the requirements of its Code of Conduct in Attachment F of the ISO
OATT any non-public financial qualification information that is submitted to the ISO by the
Developer under Section 31.3.2.4.1.1.1.3 and is designated by the Developer as “Confidential
Information.” The ISO shall within 15 days of a Developer’s submittal, notify the Developer if
the information is incomplete. If the submittal is deemed incomplete, the Developer shall submit
the additional information within 30 days of the ISO’s request. The ISO shall notify the
Developer of its qualification status within 30 days of receiving all necessary information. A
Developer shall retain its qualification status for a three-year period following the notification
date; provided, however, that the ISO may revoke this status if it determines that there has been a
material change in the Developer’s qualifications and the Developer no longer meets the
qualification requirements. A Developer that has been qualified shall inform the ISO within
thirty days of any material change to the information it provided regarding its qualifications and
shall submit to the ISO each year its most recent audited annual financial statement when
available. At the conclusion of the three-year period or following the ISO’s revocation of a
Developer’s qualification status, the Developer may re-apply for a qualification status under this
section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated transmission project as a solution to address specific congestion identified
in the CARIS and shall be eligible to use the cost allocation and cost recovery mechanism for
regulated transmission projects set forth in Section 31.5 of this Attachment Y and Rate Schedule
10 of the ISO OATT for any approved project.
31.3.2.4.1.2 Information Requirements for Projects
The ISO shall consider the criteria in Section 31.3.2.4.2 when determining whether a
proposed project is eligible to be offered as a regulated economic transmission project.
31.3.2.4.1.3 Timing for Submittal of Project Information and Entity Qualification
Information and Opportunity to Provide Additional Information
The required project information may be submitted at any time, but the proposed
regulated economic transmission project will be evaluated against the most recently available
CARIS Phase II database. Any Developer that the ISO has determined under Section
31.3.2.4.1.1.2 to be qualified to propose to develop a transmission project to address specific
congestion identified in the CARIS may submit the required project information; provided,
however, that based on the specific congestion identified that requires a solution, the ISO may
request that the qualified Developer provide additional Developer information. Any Developer
that the ISO has not determined to be qualified, but that wants to propose to develop a project,
must submit to the ISO the information required for Developer qualification under Section
31.3.2.4.1.1. The ISO shall within 30 days of a Developer’s submittal of its Developer
qualification information, notify the Developer if this information is incomplete. The Developer
shall submit additional Developer or project information required by the ISO within 15 days of
the ISO’s request. A Developer that fails to submit the additional Developer qualification
information or the required project information will not be eligible for its project to be
considered in that planning cycle.
31.3.2.4.2 Project Information Requirements
Any Developer seeking to offer a regulated economic transmission project as a solution
to address specific congestion identified in the CARIS must provide, at a minimum, the
following details:
(1) contact information; (2) the lead time necessary to complete the project
including, if available, the construction windows in which the Developer can perform
construction and what, if any, outages may be required during these periods; (3) a description of
the project, including type, size, and geographic and electrical location, as well as planning and
engineering specifications as appropriate; (4) evidence of a commercially viable technology; (5)
a major milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining such control; (8)
status of any contracts (other than an interconnection agreement) that are under negotiation or in
place, including any contracts with third-party contractors; (9) status of ISO interconnection
studies and interconnection agreement; (10) status of equipment availability and procurement;
(11) evidence of financing or ability to finance the project; (12) detailed capital cost estimates for
each segment of the project; (13) a description of permitting or other risks facing the project at
the stage of project development, including evidence of the reasonableness of project cost
estimates, all based on the information available at the time of the submission; and (14) any other
information requested by the ISO.
A Developer shall submit the following information to indicate the status of any
contracts: (i) copies of all final contracts the ISO determines are relevant to its consideration, or
(ii) where one or more contracts are pending, a timeline on the status of discussions and
negotiations with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The ISO shall treat
on a confidential basis in accordance with the requirements of its Code of Conduct in
Attachment F of the ISO OATT any contract that is submitted to the ISO and is designated by
the Developer as “Confidential Information.”
A Developer shall submit the following information to indicate the status of any required
permits: (i) copies of all final permits received that the ISO determines are relevant to its
consideration, or (ii) where one or more permits are pending, the completed permit application(s)
with information on what additional actions must be taken to meet the permit requirements and a
timeline providing the expected timing for finalization and receipt of the final permit(s). The
final permits shall be submitted to the ISO when available.
A Developer shall submit the following information, as appropriate, to indicate evidence
of financing by it or any Affiliate upon which it is relying for financing: (i) evidence of self-
financing or project financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such financing is pending,
the status of the application for any relevant financing, including a timeline providing the status
of discussions and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts or approved rates shall be submitted to the ISO when
available.
Upon the completion of any interconnection study or transmission expansion study of a
proposed regulated economic transmission project that is performed under Sections 3.7 or 4.5 of
the ISO OATT or Attachments P or X of the ISO OATT, the Developer of the proposed project
shall notify the ISO that the study has been completed and, at the ISO’s request, shall submit to
the ISO any study report and related materials prepared in connection with the study.
Failure to provide any data requested by the ISO within the timeframe provided in
Section 31.3.2.4.1.3 of this Attachment Y will result in the rejection of the proposed solution
from further consideration during that planning cycle.
31.3.2.5 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers who have undertaken a
commitment to build a project that has been approved by project beneficiaries, in accordance
with Section 31.5.4.6 of this Attachment Y.
31.4
Public Policy Transmission Planning Process
31.4.1
General
The Public Policy Transmission Planning Process shall consist of three steps: (1)
identification of Public Policy Transmission Needs; (2) requests for proposed Public Policy
Transmission Projects and Other Public Policy Projects to address those Public Policy
Transmission Needs and the evaluation of those projects; and (3) selection of the more efficient
or cost-effective Public Policy Transmission Project, if any, to satisfy each Public Policy
Transmission Need to be eligible for cost allocation under the ISO OATT. Sections 31.4.2.1
through 31.4.2.3 provide for the identification of transmission needs driven by Public Policy
Requirements and warranting evaluation by the ISO. The ISO shall request and evaluate
proposed Public Policy Transmission Projects and Other Public Policy Projects to address such
needs. The ISO shall select the more efficient or cost-effective Public Policy Transmission
Project, if any, to satisfy each need. The Public Policy Transmission Planning Process will be
conducted on a two-year cycle, unless requested by the NYPSC to be conducted out of that
cycle. If the Public Policy Transmission Planning Process cannot be completed in the two-year
cycle, the ISO will notify stakeholders and provide an estimated completion date and an
explanation of the reasons the additional time is required. The NYPSC’s issuance of a written
statement pursuant to Section 31.4.2.1 below will occur after the draft RNA study results are
posted.
31.4.2
Identification and Posting of Proposed Transmission Needs Driven by
Public Policy Requirements
At the start of each cycle for the Public Policy Transmission Planning Process, the ISO
will provide a 60-day period, which time period may be extended by the ISO pursuant to Section
31.1.8.7, to allow any stakeholders or interested parties to submit to the ISO, or for the ISO on its
own initiative to identify, any proposed transmission need(s) that it believes are being driven by
Public Policy Requirement(s) and for which transmission solutions should be requested and
evaluated. Each submittal will identify the Public Policy Requirement(s) that the party believes
is driving the need for transmission, propose criteria for the evaluation of transmission solutions
to that need, and describe how the construction of transmission will fulfill the Public Policy
Requirement(s).
For submittals to identify transmission needs pursuant to Section 31.4.2.1, the ISO will
post all submittals on its website after the end of the needs solicitation period, and will submit to
the NYPSC all submittals proposed by stakeholders, other interested parties, and any additional
transmission needs and criteria identified by the ISO. For submittals to identify transmission
needs that require a physical modification to transmission facilities in the Long Island
Transmission District pursuant to Section 31.4.2.3, the ISO will post all submittals on its website
after the end of the needs solicitation period, and will provide to the NYPSC and the Long Island
Power Authority all submittals proposed by stakeholders, other interested parties, and any
additional transmission needs and criteria identified by the ISO.
31.4.2.1 Identification and Determination of Transmission Needs Driven by
Public Policy Requirements
The NYPSC will review all proposed transmission need(s) and, with input from the ISO
and interested parties, identify the transmission needs, if any, for which specific transmission
solutions should be requested and evaluated. The NYPSC will maintain procedures to govern
the process by which it will review proposed transmission need(s), which procedures shall:
ensure that such process is open and transparent, provide the ISO and interested parties a
meaningful opportunity to participate in such process, provide input regarding the NYPSC’s
considerations, and result in the development of a written determination as required by law,
inclusive of the input provided by the ISO and interested parties. In addition, the NYPSC may,
on its own, identify a transmission need driven by a Public Policy Requirement. Any such
transmission need identified by the NYPSC on its own shall be described by the NYPSC in
accordance with the requirements for stakeholder submittals set forth in Section 31.4.2, and shall
be identified and posted to the ISO’s website prior to NYPSC’s issuance of the required written
statement discussed below in this Section 31.4.2.1 so as to provide the ISO and interested parties
an opportunity to provide input to the NYPSC relating thereto.
The ISO shall assist the NYPSC in its analyses as requested. The NYPSC may also
request that the ISO, pursuant to Section 3.8.1 of the ISO OATT, conduct an evaluation of
alternative options to address the transmission needs.
The NYPSC shall issue a written statement that identifies the relevant Public Policy
Requirements driving transmission needs and explains why it has identified the Public Policy
Transmission Needs for which transmission solutions will be requested by the ISO. The
statement shall also explain why transmission solutions to other suggested transmission needs
should not be requested. The NYPSC’s statement may also provide: (i) additional criteria for the
evaluation of transmission solutions and non-transmission projects, (ii) the required timeframe, if
any, for completion of the proposed solution, and (iii) the type of analyses that it will request
from the ISO.
If the NYPSC does not identify any transmission needs driven by Public Policy
Requirements, it will provide confirmation of that conclusion to the ISO, and the ISO shall not
request solutions. The ISO shall post the NYPSC’s statement on the ISO’s website.
31.4.2.2 Disputes of NYPSC Determinations
In the event that a dispute is raised solely within the NYPSC’s jurisdiction relating to any
NYPSC decision to either accept or deny a proposed transmission need as one for which
transmission solutions should be requested, the dispute shall be addressed through judicial
review in the courts of the State of New York pursuant to Article 78 of the New York Civil
Practice Law and Rules.
31.4.2.3 Identification and Determination of Transmission Needs Within the Long
Island Transmission District Driven by Public Policy Requirements
The Long Island Power Authority, pursuant to its jurisdiction under Title 1-A of Article 5
(§1020 et seq.) of the Public Authorities Law of the State of New York, shall identify and
determine whether a Public Policy Requirement drives the need for a physical modification to
transmission facilities in the Long Island Transmission District. The identification and
determination of such transmission needs shall be consistent with Section 31.4.2.1, as further
supplemented by this Section 31.4.2.3. The Long Island Power Authority shall have no authority
to identify a transmission need outside of the Long Island Transmission District.
Based on the information provided by the ISO pursuant to Section 31.4.2, the Long
Island Power Authority shall review whether a proposed Public Policy Requirement drives the
need for a physical modification to transmission facilities in the Long Island Transmission
District. In addition, the following requirements shall apply to the Long Island Power Authority:
(i)
The Long Island Power Authority shall consult with the NYDPS on the
identification of transmission needs driven by a Public Policy Requirement solely
within the Long Island Transmission District;
(ii)
Upon completion of its review, the Long Island Power Authority shall issue a
written statement explaining whether a Public Policy Requirement does or does
not drive the need for a physical modification to transmission facilities solely
within the Long Island Transmission District, and describing the consultation
undertaken with the NYDPS;
(iii)
In conjunction with the issuance of its written statement, the Long Island Power
Authority shall transmit to the NYPSC and request that it review and determine
whether a transmission need solely within the Long Island Transmission District
identified by the Long Island Power Authority as being driven by a Public Policy
Requirement should be considered a Public Policy Transmission Need for
purposes of the evaluation of solutions by the ISO and the potential eligibility of
transmission solutions for selection and regional cost allocation under the ISO
OATT. Any transmission need within the Long Island Transmission District that
has been identified by the Long Island Power Authority, but which the NYPSC
has not determined to be a Public Policy Transmission Need that would be
evaluated by the ISO, shall be addressed under the Long Island Power Authority’s
Local Transmission Plan.
(iv)
The determination of whether there is a transmission need solely within the Long
Island Transmission District is the sole responsibility of the Long Island Power
Authority;
(v)
The NYDPS and Long Island Power Authority shall consult and coordinate on
procedures to be adopted by the NYPSC and Long Island Power Authority to
ensure that their respective determinations under this Section 31.4.2.3, including
any NYPSC determination that there is a Public Policy Transmission Need within
the Long Island Transmission District for which solutions should be evaluated by
the ISO, are completed, publicly posted and transmitted to the ISO at the same
time as the NYPSC makes its final determinations pursuant to Section 31.4.2.1;
and
(vi)
In the event that a dispute is raised solely within the Long Island Power
Authority’s jurisdiction relating to a decision by the Long Island Power Authority
to either accept or deny a proposed transmission need solely within the Long
Island Transmission District, the dispute shall be addressed through judicial
review in the courts of the State of New York pursuant to Article 78 of the New
York Civil Practice Law and Rules.
31.4.3
Request for Proposed Solutions
The ISO will request proposed Public Policy Transmission Projects, including
Interregional Transmission Projects, to satisfy each Public Policy Transmission Need identified
pursuant to Sections 31.4.2.1 through 31.4.2.3. An Interregional Transmission Project shall be:
(i) evaluated in accordance with the applicable requirements of the Public Policy Transmission
Planning Process of this Attachment Y, and (ii) jointly evaluated by the ISO and the relevant
adjacent transmission planning region(s) in accordance with Section 7.3 of the Interregional
Planning Protocol. The ISO shall also accept specific proposed Other Public Policy Projects to
satisfy a Public Policy Transmission Need identified pursuant to Sections 31.4.2.1 through
31.4.2.3.
31.4.3.1 Timing of ISO Request for Proposed Solutions
Following posting of a determination pursuant to Sections 31.4.2.1 through 31.4.2.3, the
ISO will provide a 60-day period, which time period may be extended by the ISO pursuant to
Section 31.1.8.7, for Developers to propose specific solutions, whether Public Policy
Transmission Project(s) or Other Public Policy Project(s), to satisfy each identified Public Policy
Transmission Need in accordance with the requirements set forth in Section 31.4.4.3. Any
proposed transmission needs that are under appeal pursuant to Section 31.4.2.2 or Section
31.4.2.3(vi) may be addressed with proposed solutions, if required, except where the NYPSC
order has been stayed pending the resolution of that appeal.
31.4.3.2 NYPSC and LIPA Requests for Solutions
To ensure that there will be a response to a Public Policy Transmission Need, the NYPSC
may request the appropriate Transmission Owner(s) or Other Developer, as identified by the
NYPSC, to propose a Public Policy Transmission Project. With respect to a transmission need
identified by the Long Island Power Authority and determined to be a Public Policy
Transmission Need by the NYPSC pursuant to Section 31.4.2.3, the Long Island Power
Authority’s Board of Trustees may request that an appropriate Transmission Owner(s) or Other
Developer propose a Public Policy Transmission Project or Other Public Policy Project. A
request for the provision of a Public Policy Transmission Project or Other Public Policy Project
by either the NYPSC or the Long Island Power Authority’s Board of Trustees, pursuant to this
section, is supplementary to, and not to the exclusion of, the submission of proposed projects
pursuant to Section 31.4.3.1. Costs incurred by a Transmission Owner or Other Developer in
preparing a proposed transmission solution in response to a request under this Section 31.4.3.2
will be recoverable under Section 31.5.6 and Rate Schedule 10 of the ISO OATT. The ISO shall
allocate these costs among Load Serving Entities in accordance with Section 31.5.5.4.3, except
as otherwise determined by the Commission.
31.4.4
Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.4.4 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.4.4.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.4.4.1.1 to demonstrate its capability to satisfy the applicable qualification criteria and
(ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with signatory
authority, in a form acceptable to the ISO, certifying that the Affiliate will participate in the
Developer’s project in the manner described by the Developer and will abide by the requirements
set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures, related and applicable to the
Affiliate’s participation.
31.4.4.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate, and maintain a Public Policy Transmission Project. The ISO shall
consider the qualification of each Developer in an evenhanded and non-discriminatory manner,
treating Transmission Owners and Other Developers alike.
31.4.4.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a Public Policy Transmission Project based on the following criteria:
31.4.4.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.4.4.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.4.4.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement or equivalent information, if available;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to solve a Public Policy Transmission Need.
31.4.4.1.1.4 A detailed plan describing how the Developer - in the absence of previous
experience financing, developing, constructing, operating, or maintaining
transmission facilities - will finance, develop, construct, operate, and maintain a
transmission facility, including the financial, technical, and engineering
qualifications and experience and capabilities of any third parties with which it
will contract for these purposes.
31.4.4.1.2 Developer Qualification Determination
Any Developer seeking to be qualified may submit the required information, or update
any previously submitted information, at any time. The ISO shall treat on a confidential basis in
accordance with the requirements of its Code of Conduct in Attachment F of the ISO OATT any
non-public financial qualification information that is submitted to the ISO by the Developer
under Section 31.4.4.1.1.3 and is designated by the Developer as “Confidential Information.”
The ISO shall within 15 days of a Developer’s submittal, notify the Developer if the information
is incomplete. If the submittal is deemed incomplete, the Developer shall submit the additional
information within 30 days of the ISO’s request. The ISO shall notify the Developer of its
qualification status within 30 days of receiving all necessary information. A Developer shall
retain its qualification status for a three-year period following the notification date; provided,
however, that the ISO may revoke this status if it determines that there has been a material
change in the Developer’s qualifications and the Developer no longer meets the qualification
requirements. A Developer that has been qualified shall inform the ISO within thirty days of any
material change to the information it provided regarding its qualifications and shall submit to the
ISO each year its most recent audited annual financial statement when available. At the
conclusion of the three-year period or following the ISO’s revocation of a Developer’s
qualification status, the Developer may re-apply for a qualification status under this section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated Public Policy Transmission Project and shall be eligible to use the cost
allocation and cost recovery mechanism for regulated Public Policy Transmission Projects set
forth in Section 31.5 of this Attachment Y and the Rate Schedule 10 of the ISO OATT for any
approved project.
31.4.4.3 Timing for Submittal of Project Information and Developer Qualification
Information and Opportunity to Provide Additional Information
31.4.4.3.1
All Developers of Public Policy Transmission Projects or Other Public
Policy Projects proposed to satisfy a Public Policy Transmission Need shall
submit to the ISO within 60 days of the ISO’s request for solutions to a Public
Policy Transmission Need, which time period may be extended by the ISO
pursuant to Section 31.1.8.7, the project information required under Section
31.4.5. In response to a solicitation for a solution to a Public Policy Transmission
Need identified after the 2014-2015 planning cycle, the Developer of a Public
Policy Transmission Project must also demonstrate to the ISO, simultaneous with
its submission of project information, that it has submitted a valid Transmission
Interconnection Application or Interconnection Request as applicable. If: (i) the
ISO determines that a Developer’s submission of its project information is
incomplete, or (ii) the ISO determines at any time in the planning process that
additional project information is required, the ISO shall request that the Developer
provide additional project information within the timeframe set forth in Section
31.4.4.3.4. A Developer’s failure to provide the data requested by the ISO within
the timeframes provided in Sections 31.4.4.3.1 and 31.4.4.3.4 of this Attachment
Y will result in the rejection of the Developer’s proposed Public Policy
Transmission Project or Other Public Policy Project from further consideration
during that planning cycle.
31.4.4.3.2
Any Developer that the ISO has determined under Section 31.4.4.1.2 of
this Attachment Y to be qualified to propose to develop a transmission project as
a transmission solution to a Public Policy Transmission Need may submit the
required project information for its proposed Public Policy Transmission Project;
provided, however, that based on the actual identified need that requires
resolution, the ISO may request that the qualified Developer provide additional
Developer qualification information within the timeframe set forth in Section
31.4.4.3.4.
31.4.4.3.3
Any Developer that has not been determined by the ISO to be qualified,
but that wants to propose to develop a Public Policy Transmission Project, must
submit to the ISO the information required for Developer qualification under
Section 31.4.4.1 within 30 days after a request for solutions is made by the ISO.
The ISO shall within 30 days of a Developer’s submittal of its Developer
qualification information, notify the Developer if this information is incomplete
and request that the Developer provide additional Developer qualification
information within the timeframe set forth in Section 31.4.4.3.4. The ISO shall
notify a Developer that has submitted the requested Developer qualification
information whether it is qualified to propose to develop a Public Policy
Transmission Project to be considered in that planning cycle.
31.4.4.3.4
The Developer shall submit additional Developer qualification
information or project information required by the ISO within 15 days of the
ISO’s request.
31.4.4.3.5
If a Developer fails to timely submit the additional Developer qualification
information requested by the ISO, the Developer will not be eligible for its
proposed Public Policy Transmission Project to be considered in that planning
cycle.
31.4.4.4. Application Fee and Study Deposit for Proposed Regulated Public Policy
Transmission Project
Within sixty (60) days of the ISO’s request for solutions to a Public Policy Transmission
Need, which time period may be extended by the ISO pursuant to Section 31.1.8.7, all
Developers that propose Public Policy Transmission Projects shall, at the same time that they
provide project information pursuant to Section 31.4.4.3.1, (i) execute a study agreement with
the ISO in the form set forth in Section 31.12 (Appendix I) of this Attachment Y for purposes of
the ISO’s evaluation of the proposed Public Policy Transmission Project under Sections 31.4.7,
31.4.8, 31.4.9, and 31.4.10, and (ii) submit to the ISO: (A) a non-refundable application fee of
$10,000, and (B) a study deposit of $100,000, which shall be applied to study costs and subject
to refund as described in this Section 31.4.4.4.
The ISO shall charge, and a Developer proposing a regulated Public Policy Transmission
Project shall pay, the actual costs of the ISO’s evaluation of the Developer’s proposed Public
Policy Transmission Project for purposes of the ISO’s selection of the more efficient or cost
effective Public Policy Transmission Project to satisfy a Public Policy Transmission Need for
cost allocation purposes, including costs associated with the ISO’s use of subcontractors. The
ISO will track its staff and administrative costs, including any costs associated with using
subcontractors, that it incurs in performing the evaluation of a Developer’s proposed Public
Policy Transmission Project under Sections 31.4.7, 31.4.8, 31.4.9, and 31.4.10 and any
supplemental evaluation or re-evaluation of the proposed Public Policy Transmission Project. If
the ISO or its subcontractors perform study work for multiple proposed Public Policy
Transmission Projects on a combined basis, the ISO will allocate the costs of the combined study
work equally among the applicable Developers.
The ISO shall invoice the Developer monthly for study costs incurred by the ISO in
evaluating the Developer’s proposed Public Policy Transmission Projects as described above.
Such invoice shall include a description and an accounting of the study costs incurred by the ISO
and estimated subcontractor costs. The Developer shall pay the invoiced amount within thirty
(30) calendar days of the ISO’s issuance of the monthly invoice. The ISO shall continue to hold
the full amount of the study deposit until settlement of the final monthly invoice; provided,
however, if a Developer: (i) does not pay its monthly invoice within the timeframe described
above, or (ii) does not pay a disputed amount into an independent escrow account as described
below, the ISO may draw upon the study deposit to recover the owed amount. If the ISO must
draw on the study deposit, the ISO shall provide notice to the Developer, and the Developer shall
within thirty (30) calendar days of such notice make payments to the ISO to restore the full study
deposit amount. If the Developer fails to make such payments, the ISO may halt its evaluation
of the Developer’s proposed Public Policy Transmission Project and may disqualify the
Developer’s proposed Public Policy Transmission Project from further consideration. After the
conclusion of the ISO’s evaluation of the Developer’s proposed Public Policy Transmission
Project or if the Developer: (i) withdraws its proposed Public Policy Transmission Project or (ii)
fails to pay an invoiced amount and the ISO halts its evaluation of the proposed Public Policy
Transmission Project, the ISO shall issue a final invoice and refund to the Developer any portion
of the Developer’s study deposit submitted to the ISO under this Section 31.4.4.4 that exceeds
outstanding amounts that the ISO has incurred in evaluating that Developer’s proposed Public
Policy Transmission Project, including interest on the refunded amount calculated in accordance
with Section 35.19a(a)(2) of FERC’s regulations. The ISO shall refund the remaining portion
within sixty (60) days of the ISO’s receipt of all final invoices from its subcontractors and
involved Transmission Owners.
In the event of a Developer’s dispute over invoiced amounts, the Developer shall: (i)
timely pay any undisputed amounts to the ISO, and (ii) pay into an independent escrow account
the portion of the invoice in dispute, pending resolution of such dispute. If the Developer fails to
meet these two requirements, then the ISO shall not be obligated to perform or continue to
perform its evaluation of the Developer’s proposed Public Policy Transmission Project.
Disputes arising under this section shall be addressed through the Dispute Resolution Procedures
set forth in Section 2.16 of the ISO OATT and Section 11 of the ISO Services Tariff. Within
thirty (30) Calendar Days after resolution of the dispute, the Developer will pay the ISO any
amounts due with interest calculated in accordance with Section 35.19a(a)(2) of FERC’s
regulations.
31.4.5
Project Information Requirements
31.4.5.1 Requirements for Public Policy Transmission Projects
31.4.5.1.1
A Developer proposing a Public Policy Transmission Project to satisfy a
Public Policy Transmission Need must provide, at a minimum, the following
details:
(1) contact information; (2) the lead time necessary to complete the
project, including, if available, the construction windows in which the Developer
can perform construction and what, if any, outages may be required during these
periods; (3) a description of the project, including type, size, and geographic and
electrical location, as well as planning and engineering specifications as
appropriate; (4) evidence of a commercially viable technology; (5) a major
milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining such
control; (8) status of any contracts (other than an interconnection agreement) that
are under negotiations or in place, including any contracts with third-party
contractors; (9) status of ISO interconnection studies and interconnection
agreement; (10) status of equipment availability and procurement; (11) evidence
of financing or ability to finance the project; (12) capital cost estimates for the
project; (13) a description of permitting or other risks facing the project at the
stage of project development, including evidence of the reasonableness of project
cost estimates all based on the information available at the time of the submission;
and (14) any other information requested by the ISO.
31.4.5.1.2
A Developer shall submit the following information to indicate the status
of any contracts: (i) copies of all final contracts the ISO determines are relevant to
its consideration, or (ii) where one or more contracts are pending, a timeline on
the status of discussions and negotiations with the relevant documents and when
the negotiations are expected to be completed. The final contracts shall be
submitted to the ISO when available. The ISO shall treat on a confidential basis
in accordance with the requirements of its Code of Conduct in Attachment F of
the ISO OATT any contract that is submitted to the ISO and is designated by the
Developer as “Confidential Information.”
31.4.5.1.3
A Developer shall submit the following information to indicate the status
of any required permits: (i) copies of all final permits received that the ISO
determines are relevant to its consideration, or (ii) where one or more permits are
pending, the completed permit application(s) with information on what additional
actions must be taken to meet the permit requirements and a timeline providing
the expected timing for finalization and receipt of the final permit(s). The final
permits shall be submitted to the ISO when available.
31.4.5.1.4
A Developer shall submit the following information, as appropriate, to
indicate evidence of financing by it or any Affiliate upon which it is relying for
financing: (i) evidence of self-financing or project financing through approved
rates or the ability to do so, (ii) copies of all loan commitment letter(s) and signed
financing contract(s), or (iii) where such financing is pending, the status of the
application for any relevant financing, including a timeline providing the status of
discussions and negotiations of relevant documents and when the negotiations are
expected to be completed. The final contracts or approved rates shall be
submitted to the ISO when available.
31.4.5.1.5
Upon the completion of any interconnection study or transmission
expansion study of a proposed Public Policy Transmission Project that is
performed under Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of
the ISO OATT, the Developer of the proposed project shall notify the ISO that the
study has been completed and, at the ISO’s request, shall submit to the ISO any
study report and related materials prepared in connection with the study.
31.4.5.2 Requirements for Other Public Policy Projects
31.4.5.2.1
A Developer proposing an Other Public Policy Project to satisfy a Public
Policy Transmission Need must provide, at a minimum: (1) contact information;
(2) the lead time necessary to complete the project, including, if available, the
construction windows in which the Developer can perform construction and what,
if any, outages may be required during these periods; (3) a description of the
project, including type, size, and geographic and electrical location, as well as
planning and engineering specifications and drawings as appropriate; (4) evidence
of a commercially viable technology; (5) a major milestone schedule; (6) a
schedule for obtaining any required permits and other certifications; (7) a
demonstration of Site Control or a schedule for obtaining Site Control, as
applicable; (8) the status of any contracts (other than an interconnection
agreement) that are under negotiation or in place; (9) the status of ISO
interconnection studies and interconnection agreement, as applicable; (10) the
status of equipment availability and procurement, as applicable; (11) evidence of
financing or ability to finance the project; and (12) any other information
requested by the ISO.
31.4.5.2.2
A Developer shall submit the following information to indicate the status
of any contracts: (i) copies of all final contracts the ISO determines are relevant
to its consideration, or (ii) where one or more contracts are pending, a timeline on
the status of discussions and negotiations with the relevant documents and when
the negotiations are expected to be completed. The final contracts shall be
submitted to the ISO when available. The ISO shall treat on a confidential basis
in accordance with the requirements of its Code of Conduct in Attachment F of
the ISO OATT any contract that is submitted to the ISO and is designated by the
Developer as “Confidential Information.”
31.4.5.2.3
A Developer shall submit the following information to indicate the status
of any required permits: (i) copies of all final permits received that the ISO
determines are relevant to its consideration, or (ii) where one or more permits are
pending, the completed permit application(s) with information on what additional
actions must be taken to meet the permit requirements and a timeline providing
the expected timing for finalization and receipt of the final permit(s). The final
permits shall be submitted to the ISO when available.
31.4.5.2.4
A Developer shall submit the following information, as appropriate, to
indicate evidence of financing by it or any Affiliate upon which it is relying for
financing: (i) copies of all loan commitment letter(s) and signed financing
contract(s), or (ii) where such financing is pending, the status of the application
for any relevant financing, including a timeline providing the status of discussions
and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts shall be submitted to the ISO when available.
31.4.5.2.5
Upon the completion of any interconnection study or transmission
expansion study of a proposed Other Public Policy Project that is performed under
Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO OATT,
the Developer of the proposed project shall notify the ISO that the study has been
completed and, at the ISO’s request, shall submit to the ISO any study report and
related materials prepared in connection with the study.
31.4.6
ISO Evaluation of Proposed Solutions to Public Policy Transmission
Needs
31.4.6.1 Evaluation Time Period
The ISO will study proposed Public Policy Transmission Projects and Other Public
Policy Projects using: (i) the most recent base case from the reliability planning process, (ii)
updates in accordance with ISO Procedures, and (iii) compensatory MWs as needed to resolve
the Reliability Needs over the ten-year Study Period. The ISO will extend the most recent
reliability and economic planning models for modeling solutions for Public Policy Transmission
Needs by up to an additional twenty years following the Study Period, as appropriate based upon
the Public Policy Requirement and the identified Public Policy Transmission Need.
31.4.6.2 Comparable Evaluation of All Proposed Solutions
The ISO shall evaluate any proposed Public Policy Transmission Project or Other Public
Policy Project submitted by a Developer to a Public Policy Transmission Need. The ISO will
evaluate whether each proposed solution is viable pursuant to Section 31.4.6.3 below and is
sufficient to satisfy the Public Policy Transmission Need pursuant to Section 31.4.6.4. The
proposed solution may include multiple components and resource types. When evaluating
proposed solutions to a Public Policy Transmission Need from any Developer, the ISO shall
consider all resource types - including generation, transmission, demand response, or a
combination of these resource types - on a comparable basis as potential solutions. All solutions
will be evaluated in the same general time frame.
31.4.6.3 Evaluation of Viability of Proposed Solution
The ISO will determine the viability of a Public Policy Transmission Project or Other
Public Policy Project - whether transmission, generation, demand response, or a combination of
these resource types - proposed to satisfy a Public Policy Transmission Need. For purposes of
its analysis, the ISO will consider: (i) the Developer qualification data provided pursuant to
Section 31.4.4 and the project information data provided under Section 31.4.5; (ii) whether the
proposed solution is technically practicable; (iii) the Developer’s possession of, or approach for
acquiring, any necessary rights-of-way, property, and facilities that will make the proposal
reasonably feasible in the required timeframe; and (iv) whether the proposed solution can be
completed in the required timeframe, if any. If the ISO determines that the proposed solution is
not viable, the ISO shall reject the proposed solution from further consideration during that
planning cycle.
31.4.6.4 Evaluation of Sufficiency of Proposed Solution
The ISO will perform a comparable analysis of each proposed Public Policy
Transmission Project or Other Public Policy Project - whether transmission, generation, demand
response, or a combination of these resource types - to confirm that the proposed solution
satisfies the Public Policy Transmission Need. The ISO will evaluate each solution to measure
the degree to which the proposed solution independently satisfies the Public Policy Transmission
Need, including the evaluation criteria provided by the NYPSC. If the ISO determines that the
proposed solution is not sufficient, the ISO shall reject the proposed solution from further
consideration during that planning cycle.
31.4.6.5 Viability and Sufficiency Assessment
The ISO will present its Viability and Sufficiency Assessment to stakeholders, interested
parties, and the NYPSC for comment. The ISO shall report in the Public Policy Transmission
Planning Report the results of its evaluation under this Section 31.4.6 of whether each proposed
Public Policy Transmission Project or Other Public Policy Project is viable and is sufficient to
satisfy the identified Public Policy Transmission Need.
31.4.6.6 Developer’s Determination to Proceed
Within 15 Calendar Days following the NYPSC’s issuance of an order in accordance
with Section 31.4.6.7 indicating that the ISO should proceed with its evaluation of transmission
solutions to a Public Policy Transmission Need, which time period may be extended by the ISO
pursuant to Section 31.1.8.7, all Developers of proposed Public Policy Transmission Projects that
the ISO has determined satisfy the viability and sufficiency requirements in this Section 31.4.6
shall notify the ISO whether they intend for their projects to proceed to be evaluated by the ISO
for purposes of the ISO’s selection of the more efficient or cost effective Public Policy
Transmission Project to satisfy an identified Public Policy Transmission Need. To proceed, a
Developer must include with its notification to the ISO under this Section 31.4.6.6: (i) its consent
to the ISO’s disclosure of the details of its proposed Public Policy Transmission Project in the
Public Policy Transmission Planning Report, except for the information that shall remain
confidential in accordance with Section 31.4.15, and (ii) a demonstration that it has an executed
System Impact Study Agreement or System Reliability Impact Study Agreement, as applicable.
If a Developer: (i) notifies the ISO that it does not intend for its proposed Public Policy
Transmission Project to proceed to be evaluated for purposes of the ISO’s selection, or (ii) does
not provide the required notification to the ISO under this Section 31.4.6.6, the ISO will remove
the project from further consideration during that planning cycle.
31.4.6.7 NYPSC Determination on Whether to Proceed with Evaluation of
Transmission Solutions to a Public Policy Transmission Need
31.4.6.7.1
Following the ISO’s presentation of the Viability and Sufficiency
Assessment, the NYPSC will review the Viability and Sufficiency Assessment and will issue an
order, subject to and in accordance with the State Administrative Procedure Act, explaining
whether the ISO should continue to evaluate transmission solutions to a Public Policy
Transmission Need or whether non-transmission solutions should be pursued. If the NYPSC
concludes that non-transmission solutions should be pursued outside of the Public Policy
Transmission Planning Process, the NYPSC will indicate in its order that either: (i) there is no
longer a transmission need driven by a Public Policy Requirement that requires the ISO’s
evaluation of potential transmission solutions, or (ii) the transmission need should be modified.
31.4.6.7.2
If the NYPSC concludes that there is no longer a transmission need driven
by a Public Policy Requirement in its order as set forth in Section 31.4.6.7.1, the ISO will not
perform an evaluation, or make a selection of, a more efficient or cost-effective transmission
solution under Sections 31.4.7 through 31.4.11 for the Public Policy Transmission Need initially
identified by the NYPSC for that planning cycle pursuant to Section 31.4.2.1.
31.4.6.7.3
If the NYPSC modifies the transmission need driven by a Public Policy
Requirement in its order as set forth in Section 31.4.6.7.1, the ISO will re-start its Public Policy
Transmission Planning Process as an out-of-cycle process to evaluate Public Policy
Transmission Projects to address the modified Public Policy Transmission Need. This out-of-
cycle process will begin with the ISO’s solicitation for Public Policy Transmission Projects to
address the modified Public Policy Transmission Need in accordance with Sections 31.4.3 and
31.4.4.3. The ISO shall evaluate the viability and sufficiency of the proposed Public Policy
Transmission Projects in accordance with Sections 31.4.6.3 and 31.4.6.4. Within 30 Calendar
Days following the ISO’s presentation of the Viability and Sufficiency Assessment for the out-
of-cycle process, which time period may be extended by the ISO pursuant to Section 31.1.8.7, all
Developers of proposed Public Policy Transmission Projects that the ISO has determined satisfy
the viability and sufficiency requirements in this Section 31.4.6 shall notify the ISO whether they
intend for their projects to proceed to be evaluated for purposes of selection in accordance with
the requirements in Section 31.4.6.6. The ISO will then proceed to evaluate the viable and
sufficient Public Policy Transmission Projects that have elected to proceed in accordance with
Sections 31.4.7 through 31.4.11 for purposes of selecting the more efficient or cost-effective
transmission solution to the modified Public Policy Transmission Need. The requirements in
Section 31.4.6.7.1 that the NYPSC review the Viability and Sufficiency Assessment and issue an
order concerning the Public Policy Transmission Need do not apply in this out-of-cycle process.
31.4.7
Evaluation of Regional Public Policy Transmission Projects to Address
Local and Regional Needs Driven by Public Policy Requirements More
Efficiently or More Cost Effectively Than Local Transmission Solutions
The ISO will review the LTPs as they relate to the BPTFs. The ISO will include the
results of its analysis in its Public Policy Transmission Planning Report, as approved by the ISO
Board.
31.4.7.1 Evaluation of Regional Public Policy Transmission Projects to Address
Local Needs Driven By Public Policy Requirements Identified in Local
Transmission Plans More Efficiently or More Cost Effectively than Local
Transmission Solutions
The ISO, using engineering judgment, will determine whether any proposed regional
Public Policy Transmission Project on the BPTFs more efficiently or cost-effectively satisfies
any needs driven by a Public Policy Requirement identified in the LTPs. If the ISO identifies
that a regional Public Policy Transmission Project has the potential to more efficiently or cost
effectively satisfy the needs driven by a Public Policy Requirement identified in the LTPs, it will
perform a sensitivity analysis to determine whether the proposed regional Public Policy
Transmission Project on the BPTFs would satisfy the needs driven by a Public Policy
Requirement identified in the LTPs. If the ISO determines that the proposed regional Public
Policy Transmission Project would satisfy the need, the ISO will evaluate the proposed regional
Public Policy Transmission Project using the metrics set forth in Section 31.4.8.1 below to
determine whether it may be a more efficient or cost effective solution on the BPTFs to the needs
driven by a Public Policy Requirement identified in the LTPs than the local solutions proposed in
the LTPs.
31.4.7.2 Evaluation of Regional Public Policy Transmission Project to Address
Regional Pubic Policy Transmission Needs More Efficiently or More Cost
Effectively than Local Transmission Solutions
As referenced in Section 31.2.1.3, the ISO, using engineering judgment, will determine
whether a regional Public Policy Transmission Project might more efficiently or more cost
effectively satisfy an identified regional Public Policy Transmission Need on the BPTFs that
impacts more than one Transmission District than any local transmission solutions identified by
the Transmission Owners in their LTPs in the event the LTPs specify that such transmission
solutions are included to address local transmission needs driven by Public Policy Requirements.
31.4.8
ISO Selection of More Efficient or Cost Effective Public Policy
Transmission Project to Satisfy a Public Policy Transmission Need
A proposed regulated Public Policy Transmission Project submitted by a Developer that
the ISO has determined has provided the required notification to proceed under Section 31.4.6.6
shall be eligible under this Section 31.4.8 for selection in the Public Policy Transmission
Planning Report for the purpose of cost allocation under the ISO Tariffs. The ISO shall evaluate
any proposed regulated Public Policy Transmission Projects that are eligible for selection in the
planning cycle of the Public Policy Transmission Planning Process using the metrics set forth in
Section 31.4.8.1 below. For purposes of this evaluation, the ISO will review the information
submitted by the Developer and determine whether it is reasonable and how such information
should be used for purposes of the ISO evaluating each metric. In its review, the ISO will give
due consideration to the status of, and any available results of, any applicable interconnection or
transmission expansion studies concerning the proposed Public Policy Transmission Project
performed in accordance with Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the
ISO OATT. The ISO may engage an independent consultant to review the reasonableness and
comprehensiveness of the information submitted by the Developer and may rely on the
independent consultant’s analysis in evaluating each metric. The ISO shall select in the Public
Policy Transmission Planning Report for cost allocation purposes the more efficient or cost
effective transmission solution to satisfy a Public Policy Transmission Need in the manner set
forth in Section 31.4.8.2 below.
31.4.8.1 Metrics for Evaluating More Efficient or Cost Effective Regulated Public
Policy Transmission Project to Satisfy Public Policy Transmission Need
In determining which of the eligible proposed regulated Public Policy Transmission
Projects is the more efficient or cost effective solution to satisfy a Public Policy Transmission
Need, the ISO will consider, and will consult with the NYDPS regarding, the metrics set forth
below in this Section 31.4.8.1 and rank each proposed project based on the quality of its
satisfaction of these metrics:
31.4.8.1.1
The capital cost estimates for the proposed regulated Public Policy
Transmission Project, including the accuracy of the proposed estimates. For this
evaluation, the Developer shall provide the ISO with credible capital cost
estimates for its proposed project, with itemized supporting work sheets that
identify all material and labor cost assumptions, and related drawings to the extent
applicable and available. The work sheets should include an estimated
quantification of cost variance, providing an assumed plus/minus range around
the capital cost estimate.
The estimate shall include all components that are needed to meet the
Public Policy Transmission Need. To the extent information is available, the
Developer should itemize: material and labor cost by equipment, engineering and
design work, permitting, site acquisition, procurement and construction work, and
commissioning needed for the proposed project, all in accordance with Good
Utility Practice. For each of these cost categories, the Developer should specify
the nature and estimated cost of all major project components and estimate the
cost of the work to be done at each substation and/or on each feeder to physically
and electrically connect each facility to the existing system. The work sheets
should itemize to the extent applicable and available all equipment for: (i) the
proposed project, (ii) interconnection facilities (including Attachment Facilities
and Direct Assignment Facilities), and (iii) Network Upgrade Facilities, System
Upgrade Facilities, System Deliverability Upgrades, Network Upgrades, and
Distribution Upgrades.
31.4.8.1.2
The cost per MW ratio of the proposed regulated Public Policy
Transmission Project. For this evaluation, the ISO will first determine the present
worth, in dollars, of the total capital cost of the proposed project in current year
dollars. The ISO will then determine the cost per MW ratio by dividing the
capital cost by the MW value of increased transfer capability.
31.4.8.1.3
The expandability of the proposed regulated Public Policy Transmission
Project. The ISO will consider the impact of the proposed project on future
construction. The ISO will also consider the extent to which any subsequent
expansion will continue to use this proposed project within the context of system
expansion.
31.4.8.1.4
The operability of the proposed regulated Public Policy Transmission
Project. The ISO will consider how the proposed project may affect additional
flexibility in operating the system, such as dispatch of generation, access to
operating reserves, access to ancillary services, or ability to remove transmission
for maintenance. The ISO will also consider how the proposed project may affect
the cost of operating the system, such as how it may affect the need for operating
generation out of merit for reliability needs, reducing the need to cycle generation,
or providing more balance in the system to respond to system conditions that are
more severe than design conditions.
31.4.8.1.5
The performance of the proposed regulated Public Policy Transmission
Project. The ISO will consider how the proposed project may affect the
utilization of the system (e.g. interface flows, percent loading of facilities).
31.4.8.1.6
The extent to which the Developer of a proposed regulated Public Policy
Transmission Project has the property rights, or ability to obtain the property
rights, required to implement the project. The ISO will consider whether the
Developer: (i) already possesses the rights of way necessary to implement the
project; (ii) has completed a transmission routing study, which (a) identifies a
specific routing plan with alternatives, (b) includes a schedule indicating the
timing for obtaining siting and permitting, and (c) provides specific attention to
sensitive areas (e.g., wetlands, river crossings, protected areas, and schools); or
(iii) has specified a plan or approach for determining routing and acquiring
property rights.
31.4.8.1.7
The potential issues associated with delay in constructing the proposed
regulated Public Policy Transmission Project consistent with the major milestone
schedule and the schedule for obtaining any permits and other certifications as
required to timely meet the need.
31.4.8.1.8
The ISO shall apply any criteria specified by the Public Policy
Requirement or provided by the NYPSC and perform the analyses requested by
the NYPSC, to the extent compliance with such criteria and analyses are feasible.
31.4.8.1.9
The ISO, in consultation with stakeholders, shall, as appropriate, consider
other metrics in the context of the Public Policy Requirement, such as: change in
production costs; LBMP; losses; emissions; ICAP; TCC; congestion; impact on
transfer limits; and deliverability.
31.4.8.2 ISO Selection of More Efficient or Cost Effective Regulated Public Policy
Transmission Project to Satisfy a Public Policy Transmission Need
The ISO shall identify under this Section 31.4.8 the proposed regulated Public Policy
Transmission Project, if any, that is the more efficient or cost effective transmission solution
proposed in the planning cycle for the Public Policy Transmission Planning Process to satisfy a
Public Policy Transmission Need. The ISO shall include the more efficient or cost effective
transmission solution in the Public Policy Transmission Planning Report. The Developer of a
regulated Public Policy Transmission Project shall be eligible to recover costs for the project
only if the project is selected by the ISO, except as otherwise provided in Section 31.4.3.2 or as
otherwise determined by the Commission. Costs will be recovered when the project enters into
service, is halted, or as otherwise determined by the Commission in accordance with the cost
recovery requirements set forth in Section 31.5.6 of this Attachment Y and Rate Schedule 10 of
the ISO OATT. Actual project cost recovery, including any issues related to cost recovery and
project cost overruns, will be submitted to and decided by the Commission.
Any selection of a Public Policy Transmission Project by the ISO under Section 31.4.8,
including but not limited to the selection of a project that involves the physical modification of
facilities within the Long Island Transmission District, shall not affect the obligation and
responsibility of the Developer to apply for, and receive, all necessary authorizations or permits
required by federal or state law for such project.
31.4.9
Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of a
transmission solution driven by Public Policy Requirements on neighboring ISO/RTO Regions
using the respective planning criteria of such ISO/RTO Regions. The ISO shall report the results
in its Public Policy Transmission Planning Report. The ISO shall not bear the costs of required
upgrades in another region.
31.4.10 Evaluation of Impact of Proposed Public Policy Transmission Project on
ISO Wholesale Electricity Markets
The ISO shall evaluate using the metrics set forth in Section 31.4.8.1.9 the impacts on the
ISO-administered wholesale electricity markets of a proposed Public Policy Transmission
Project that the ISO has determined under Section 31.4.6 is viable and sufficient. The ISO shall
include the results of its analysis in the Public Policy Transmission Planning Report.
31.4.11 Public Policy Transmission Planning Report
Following the ISO’s evaluation of the proposed solutions to Public Policy Transmission
Need(s), the ISO will prepare a draft Public Policy Transmission Planning Report that sets forth
the ISO’s assumptions, inputs, methodologies and the results of its analyses. The draft Public
Policy Transmission Planning Report will reflect any input from the NYDPS.
Except as otherwise provided in the confidentiality requirements in Section 31.4.15, the
ISO will include in the draft Public Policy Transmission Planning Report: (i) the list of
Developers and their proposed Public Policy Transmission Projects and Other Public Policy
Projects that qualify pursuant to Sections 31.4.4 and 31.4.5; (ii) the proposed Public Policy
Transmission Projects and Other Public Policy Projects that the ISO has determined under
Section 31.4.6 are viable and sufficient to satisfy the identified Public Policy Transmission
Need(s); and (iii) the regulated Public Policy Transmission Project, if any, that the ISO staff
recommends for selection for cost allocation purposes pursuant to Section 31.4.8 as the more
efficient or cost effective transmission solution to satisfy each identified Public Policy
Transmission Need. The draft Public Policy Transmission Planning Report will also include the
results of the ISO’s analysis of the LTPs consistent with Section 31.4.7.
The draft Public Policy Transmission Planning Report shall also indicate the date by
which the Public Policy Transmission Project must be in-service to address the Public Policy
Transmission Need. The in-service date shall be: (i) the date prescribed by the NYPSC in its
order identifying the Public Policy Transmission Need as described in Section 31.4.2.1 or in a
subsequent order, or (ii) if the NYPSC has not prescribed a date, the date proposed by the
Developer and reviewed and accepted by the ISO, which date may be either: (A) the in-service
date included in the Developer’s project proposal, or (B) such other date accepted by the ISO as
reasonable in light of the Public Policy Transmission Need.
The draft Public Policy Transmission Planning Report shall include a comparison of a
proposed Public Policy Transmission Project to an Interregional Transmission Project proposed
in the Public Policy Transmission Planning Process, if any, identified and evaluated under the
“Analysis and Consideration of Interregional Transmission Projects” section of the Interregional
Planning Protocol. An Interregional Transmission Project proposed in the ISO’s Public Policy
Transmission Planning Process may be selected as a regulated Public Policy Transmission
Project under the provisions of this process.
31.4.11.1 Collaborative Governance Process
The draft Public Policy Transmission Planning Report shall be submitted to both TPAS
and the ESPWG for review and comment. Concurrently, the draft report will be provided to the
Market Monitoring Unit for its review and consideration. The Market Monitoring Unit’s
evaluation will be provided to the Management Committee prior to the Management
Committee’s advisory vote. The ISO shall make available to any interested party sufficient
information to replicate the results of the draft Public Policy Transmission Planning Report. The
information made available will be electronically masked and made available pursuant to a
process that the ISO reasonably determines is necessary to prevent the disclosure of any
Confidential Information or Critical Energy Infrastructure Information contained in the
information made available. Following completion of that review, the draft report reflecting the
revisions resulting from the TPAS and ESPWG review shall be forwarded to the Business Issues
Committee and the Management Committee for discussion and an advisory vote.
31.4.11.2 Board Review, Consideration, and Approval of Public Policy
Transmission Planning Report
Following the Management Committee vote, the draft Public Policy Transmission
Planning Report, with Business Issues Committee and Management Committee input, will be
forwarded to the ISO Board for review and action. Concurrently, the Market Monitoring Unit’s
evaluation will be provided to the Board. The Board may approve the Public Policy
Transmission Planning Report as submitted or propose modifications on its own motion,
including a determination not to select a Public Policy Transmission Project to satisfy a Public
Policy Transmission Need. If any changes are proposed by the Board, the revised report shall be
returned to the Management Committee for comment. The Board shall not make a final
determination on a revised report until it has reviewed the Management Committee comments,
including comments regarding the Market Monitoring Unit’s evaluation. Upon approval by the
Board, the ISO shall issue the report to the marketplace by posting it on its website. If the ISO
Board determines not to select a Public Policy Transmission Project under this Section 31.4.11.2,
the Board shall state the reasons for its determination.
The responsibilities of the Market Monitoring Unit that are addressed in the above
Section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.5 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.4.12 Developer’s Responsibilities Following Selection of Its Public Policy
Transmission Project
31.4.12.1 Developer’s Responsibility to Obtain Necessary Approvals and
Authorizations
Upon its selection of a Public Policy Transmission Project, the ISO will inform the
Developer that it should submit the selected Public Policy Transmission Project to the
appropriate governmental agency(ies) and/or authority(ies) to begin the necessary approval
process to the site, construct, and operate the project. In response to the ISO’s request, the
Developer shall make such a submission to the appropriate governmental agency(ies) and/or
authority(ies) to the extent such authorization has not already been requested or obtained.
If the appropriate federal, state or local agency(ies) either rejects a necessary
authorization, or approves and later withdraws authorization, for the selected Public Policy
Transmission Project, the Developer may recover all of the necessary and reasonable costs
incurred and commitments made up to the final federal, state or local regulatory decision,
including reasonable and necessary expenses incurred to implement an orderly termination of the
project, to the extent permitted by the Commission in accordance with its regulations on
abandoned plant recovery. The ISO shall allocate these costs among Load Serving Entities in
accordance with Section 31.5.5.4.3, except as otherwise determined by the Commission. The
ISO shall recover such costs in accordance with Section 31.5.6 of this Attachment Y and Rate
Schedule 10 of the ISO OATT.
31.4.12.2 Development Agreement
As soon as reasonably practicable following the ISO’s selection of the proposed project,
the ISO shall tender to the Developer that proposed the selected Public Policy Transmission
Project a draft Development Agreement with draft appendices completed by the ISO to the
extent practicable for review and completion by the Developer. The draft Development
Agreement shall be in the form of the ISO’s Commission-approved Development Agreement,
which is in Appendix D in Section 31.7 of this Attachment Y. The ISO and the Developer, as
applicable, shall finalize the Development Agreement and appendices and negotiate concerning
any disputed provisions. For purposes of finalizing the Development Agreement, the ISO and
Developer shall develop the description and dates for the milestones necessary to develop and
construct the selected project by the required in-service date identified in the Public Policy
Transmission Planning Report, including the milestones for obtaining all necessary
authorizations. Any milestone that requires action by a Connecting Transmission Owner or
Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete
must be included as an Advisory Milestone, as that term is defined in the Development
Agreement.
Unless otherwise agreed by the ISO and the Developer, the Developer must execute the
Development Agreement within three (3) months of the ISO’s tendering of the draft
Development Agreement; provided, however, if, during the negotiation period, the ISO or the
Developer determines that negotiations are at an impasse, the ISO may file the Development
Agreement in unexecuted form with the Commission on its own or following the Developer’s
request in writing that the agreement be filed unexecuted. If the Development Agreement
resulting from the negotiation between the ISO and the Developer does not conform with the
Commission-approved standard form in Appendix D in Section 31.7 of this Attachment Y, the
ISO shall file the agreement with the Commission for its acceptance within thirty (30) Business
Days after the execution of the Development Agreement by both parties. If the Developer
requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement
at the Commission within thirty (30) Business Days of receipt of the request from the Developer.
The ISO will draft to the extent practicable the portions of the Development Agreement and
appendices that are in dispute and will provide an explanation to the Commission of any matters
as to which the parties disagree. The Developer will provide in a separate filing any comments
that it has on the unexecuted agreement, including any alternative positions it may have with
respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the
Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the
Commission, the ISO and the Developer shall perform their respective obligations in accordance
with the terms of the Development Agreement that are not in dispute, subject to modification by
the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that
are identified in Attachment P of the ISO OATT in connection with the selected Public Policy
Transmission Project shall act in good faith in timely performing their obligations that are
required for the Developer to satisfy its obligations under the Development Agreement.
31.4.12.3 Process for Addressing Inability of Developer to Complete Selected
Public Policy Transmission Project
31.4.12.3.1
The ISO may take the actions described in Sections 31.4.12.3.1.1 through
31.4.12.3.1.3 as soon as practicable if one of the following events occur: (i) the
Developer that proposed the selected Public Policy Transmission Project and is
required to execute the Development Agreement pursuant to Section 31.4.12.2
does not execute the Development Agreement, or does not request that it be filed
unexecuted with the Commission, within the timeframes set forth in Section
31.4.12.2, or (ii) the ISO determines that an effective Development Agreement
may be terminated or terminates the Development Agreement under the terms of
the agreement prior to the completion of the term of the agreement.
31.4.12.3.1.1 If the Development Agreement has been filed with and accepted by the
Commission and is terminated under the terms of the agreement, the ISO shall,
upon terminating the Development Agreement file a notice of termination with
the Commission.
31.4.12.3.1.2 The ISO may take one or more of the following actions to address a Public
Policy Transmission Need based on the particular circumstances: (i) address the
Public Policy Transmission Need in the subsequent planning cycle or, if requested
by the NYPSC pursuant to Section 31.4.1, in an out-of-cycle process; (ii) direct
the Developer to continue with the development of its Public Policy Transmission
Project for completion beyond the in-service date required to address the Public
Policy Transmission Need; or (iii) solicit bids from qualified Developers to
complete the selected Public Policy Transmission Project in accordance with
Section 31.4.12.3.1.3.
31.4.12.3.1.3 If the ISO determines in accordance with Section 31.4.12.3.1.2 that an
alternative Developer should be identified to complete a selected Public Policy
Transmission Project, the ISO shall solicit bids from Developers to finance and
complete the development and construction of the project to bring it into service.
Any Developer that is qualified at the time of the ISO’s solicitation to propose a
Public Policy Transmission Project may submit a proposal to complete the Public
Policy Transmission Project. The ISO will specify in its solicitation for bids by
Developers those categories of project information described in Section 31.4.5.1.1
that the Developer must submit and will identify the metrics in Section 31.4.8 that
the ISO will use to select among the bidding Developers. The ISO will determine
the appropriate project information and metrics based on the current status of
development of the Public Policy Transmission Project. The ISO will make any
selection of an alternative Developer using the selection metrics identified in its
solicitation for bids and consistent with the selection processes set forth in
Sections 31.4.8 and 31.4.11, including issuing an updated Public Policy
Transmission Planning Report. The ISO shall charge, and a Developer bidding
for the Public Policy Transmission Project, shall pay the actual costs of the ISO’s
evaluation of its bid for purposes of selecting a Developer to complete the project
consistent with Section 31.4.4.4. Each bidding Developer will reimburse the ISO
for its actual study costs consistent with the requirements in Section 31.4.4.4. The
selected alternative Developer must enter into a Development Agreement with the
ISO in accordance with the requirements in Section 31.4.12.2. The selected
alternative Developer will be eligible for cost allocation under the ISO OATT for
its development and construction of the Public Policy Transmission Project. The
selected alternative Developer and the Developer that initially proposed the
selected Public Policy Transmission Project shall work cooperatively with each
other to implement the transition, including negotiating in good faith with each
other to transfer the project; provided, however, that the transfer is subject to: (i)
any required approvals by the appropriate governmental agency(ies) and/or
authority(ies), (ii) any requirements or restrictions on the transfer of Developer’s
rights-of-way under federal or state law, regulation, or contract (including
mortgage trust indentures or debt instruments), and (iii) if the Developer is a New
York public authority, any requirements or restrictions on the transfer under the
New York Public Authorities Law; provided, further, that the selected alternative
Developer and the initial Developer will address any disputes regarding the
transfer of the project in accordance with the dispute resolution provisions in
Article 11 of the ISO Services Tariff.
31.4.12.4 Execution of ISO/TO Agreement or Comparable Agreement
The Developer of a selected Public Policy Transmission Project shall execute the ISO/TO
Agreement or an Operating Agreement in accordance with Section 31.1.7 of this Attachment Y
prior to energizing the Public Policy Transmission Project.
31.4.13 ISO Monitoring of Selected Public Policy Transmission Projects
The ISO shall monitor Public Policy Transmission Projects selected by the ISO as the
more efficient or cost effective transmission solutions to Public Policy Transmission Needs to
confirm that they continue to develop consistent with the conditions, actions, or schedules for the
projects.
31.4.14 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers who have accepted the terms
and conditions of an Article VII certificate under the New York Public Service Law, or any
successor statute, or any other applicable permits to build a Public Policy Transmission Project
in response to a need driven by a Public Policy Requirement.
31.4.15 Confidentiality of Solutions
31.4.15.1
The term “Confidential Information” shall include all proposed solutions
to Public Policy Transmission Needs that are submitted to the ISO in response to
a request for solutions under Section 31.4.3 of this Attachment Y if the Developer
of that solution designates the solution as “Confidential Information”; provided,
however, that “Confidential Information” shall not include: (i) the identity of the
Developer, (ii) the proposed facility type, (iii) the proposed facility size, (iv) the
proposed location of the facility, (v) the proposed in-service date for the facility,
and (vi) information regarding the proposed facility that the ISO is required to
disclose under its interconnection or transmission expansion processes pursuant to
Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the ISO OATT.
31.4.15.2
The ISO shall maintain the confidentiality of the Developer’s proposed
solution and plans designated as “Confidential Information” until the ISO
determines that the Developer’s proposed solution and plans are viable and
sufficient to meet the Public Policy Transmission Need and the Developer
provides its consent to the ISO’s inclusion of the proposed solution in the Public
Policy Transmission Planning Report under Section 31.4.6.6. Thereafter, the ISO
shall disclose the proposed solution and plans to Market Participants and other
interested parties; provided, however, any preliminary cost estimates that may
have been provided to the ISO, any non-public financial qualification information
provided under Section 31.4.4.1.2, and any contract provided under Sections
31.4.5.1.2 or 31.4.5.2.2 that is designated as “Confidential Information” shall not
be disclosed.
31.5
Cost Allocation and Cost Recovery
31.5.1
The Scope of Attachment Y Cost Allocation
31.5.1.1 Regulated Responses
The cost allocation principles and methodologies in this Attachment Y cover only
regulated transmission solutions to Reliability Needs, regulated transmission responses to
congestion identified in the CARIS, and regulated Public Policy Transmission Projects whether
proposed by a Responsible Transmission Owner or a Transmission Owner or Other Developer.
The cost allocation principles and methodology for: (i) regulated transmission solutions to
Reliability Needs are contained in Sections 31.5.3.1 and 31.5.3.2 of this Attachment Y, (ii)
regulated transmission responses to congestion identified in the CARIS are contained in Sections
31.5.4.1 and 31.5.4.2 of this Attachment Y, and (iii) regulated Public Policy Transmission
Projects are contained in Sections 31.5.5 and 31.5.6 of this Attachment Y.
31.5.1.2 Market-Based Responses
The cost allocation principles and methodologies in this Attachment Y do not apply to
market-based solutions to Reliability Needs, to market-based responses to congestion identified
in the CARIS, or to Other Public Policy Projects. The cost of a market-based project shall be the
responsibility of the developer of that project.
31.5.1.3 Interconnection Cost Allocation
The cost allocation principles and methodologies in this Attachment Y do not apply to the
interconnection costs of generation and merchant transmission projects. Interconnection costs
are determined and allocated in accordance with Attachment P, Attachment S, Attachment X and
Attachment Z of the ISO OATT. Cost related to the deliverability of a resource will be
addressed under the ISO’s deliverability procedures in Attachment S of the ISO OATT.
31.5.1.4 Individual Transmission Service Requests
The cost allocation principles and methodologies in this Attachment Y do not apply to the
cost of transmission expansion projects undertaken in connection with an individual request for
Transmission Service. The cost of such a project is determined and allocated in accordance with
Section 3.7 or Section 4.5 of the ISO OATT.
31.5.1.5 LTP Facilities
The cost allocation principles and methodologies in this Attachment Y do not apply to the
cost of transmission projects included in LTPs or LTP updates. Each Transmission Owner will
recover the cost of such transmission projects in accordance with its then existing rate recovery
mechanisms.
31.5.1.6 Regulated Non-Transmission Projects
Costs related to regulated non-transmission projects will be recovered by Responsible
Transmission Owners, Transmission Owners and Other Developers in accordance with the
provisions of New York Public Service Law, New York Public Authorities Law, or other
applicable state law. Nothing in this section shall affect the Commission’s jurisdiction over the
sale and transmission of electric energy subject to the jurisdiction of the Commission.
31.5.1.7 Eligibility for Cost Allocation and Cost Recovery
Any entity, whether a Responsible Transmission Owner, Other Developer, or
Transmission Owner, shall be eligible for cost allocation and cost recovery as set forth in Section
31.5 of this Attachment Y and Rate Schedule 10 of the ISO OATT for any transmission project
proposed to satisfy an identified Reliability Need, regulated economic transmission project, or
Public Policy Transmission Project that is determined by the ISO to be eligible under Sections
31.2, 31.3, or 31.4, as applicable. Interregional Transmission Projects identified in accordance
with the Interregional Planning Protocol, and that have been accepted in each region’s planning
process, shall be eligible for interregional cost allocation and cost recovery, as set forth in
Section 31.5 of this Attachment Y and Rate Schedule 10 of the ISO OATT. The ISO’s share of
the cost of an Interregional Transmission Project selected pursuant to this Attachment Y to meet
a Reliability Need, congestion identified in the CARIS, or a Public Policy Transmission Need
shall be eligible for cost allocation consistent with the cost allocation methodology applicable to
the type of regional transmission project that would be replaced through the construction of such
Interregional Transmission Project.
31.5.2
Cost Allocation Principles Required Under Order No. 1000
31.5.2.1
In compliance with Commission Order No. 1000, the ISO shall implement
the specific cost allocation methodology in Section 31.5.3.2, 31.5.4.4, and
31.5.5.4 in accordance with the following Regional Cost Allocation Principles
(“Order No. 1000 Regional Cost Allocation Principles”):
Regional Cost Allocation Principle 1: The ISO shall allocate the cost of
transmission facilities to those within the transmission planning region that
benefit from those facilities in a manner that is at least roughly commensurate
with estimated benefits. In determining the beneficiaries of transmission
facilities, the ISO’s CSPP will consider benefits including, but not limited to, the
extent to which transmission facilities, individually or in the aggregate provide for
maintaining reliability and sharing reserves, production cost savings and
congestion relief, and/or meeting Public Policy Requirements.
Regional Cost Allocation Principle 2: The ISO shall not involuntarily allocate
any of the costs of transmission facilities to those that receive no benefit from
transmission facilities.
Regional Cost Allocation Principle 3: In the event that the ISO adopts a benefit
to cost threshold in its CSPP to determine which transmission facilities have
sufficient net benefits to be selected in a regional transmission plan for the
purpose of cost allocation, such benefit to cost threshold will not be so high that
transmission facilities with significant positive net benefits are excluded from cost
allocation. If the ISO chooses to adopt such a threshold in its CSPP it will not
include a ratio of benefits to costs that exceeds 1.25 unless the ISO justifies and
the Commission approves a higher ratio.
Regional Cost Allocation Principle 4: The ISO’s allocation method for the cost
of a transmission facility selected pursuant to the process in the CSPP shall
allocate costs solely within the ISO’s transmission planning region unless another
entity outside the region or another transmission planning region voluntarily
agrees to assume a portion of those costs. Costs for an Interregional Transmission
Project must be assigned only to regions in which the facility is physically
located. Costs cannot be assigned involuntarily to another region. The ISO shall
not bear the costs of required upgrades in another region.
Regional Cost Allocation Principle 5: The ISO’s cost allocation method and
data requirements for determining benefits and identifying beneficiaries for a
transmission facility shall be transparent with adequate documentation to allow a
stakeholder to determine how they were applied to a proposed transmission
facility, as consistent with confidentiality requirements set forth in this
Attachment Y and the ISO Code of Conduct in Attachment F of the OATT.
Regional Cost Allocation Principle 6: The ISO’s CSPP provides a different cost
allocation method for different types of transmission facilities in the regional
transmission plan and each cost allocation method is set out clearly and explained
in detail in this Section 31.5.
31.5.2.2
In compliance with Commission Order No. 1000, the ISO shall implement
the specific cost allocation methodology in Section 31.5.7 of this Attachment Y in
accordance with the following Interregional Cost Allocation Principles:
Interregional Cost Allocation Principle 1: The ISO shall allocate the cost of
new Interregional Transmission Projects to each region in which an Interregional
Transmission Project is located in a manner that is at least roughly commensurate
with estimated benefits of the Interregional Transmission Project in each of the
regions. In determining the beneficiaries of Interregional Transmission Projects,
the ISO will consider benefits including, but not limited to, those associated with
maintaining reliability and sharing reserves, production cost savings and
congestion relief, and meeting Public Policy Requirements.
Interregional Cost Allocation Principle 2: The ISO shall not involuntarily
allocate any of the costs of an Interregional Transmission Project to a region that
receives no benefit from an Interregional Transmission Project that is located in
that region, either at present or in a likely future scenario.
Interregional Cost Allocation Principle 3: In the event that the ISO adopts a
benefit-cost threshold ratio to determine whether an Interregional Transmission
Project has sufficient net benefits to qualify for interregional cost allocation, this
ratio shall not be so large as to exclude an Interregional Transmission Project with
significant positive net benefits from cost allocation. If the ISO chooses to adopt
such a threshold, they will not include a ratio of benefits to costs that exceeds 1.25
unless the Parties justify and the Commission approves a higher ratio.
Interregional Cost Allocation Principle 4: The ISO’s allocation of costs for an
Interregional Transmission Project shall be assigned only to regions in which the
Interregional Transmission Project is located. The ISO shall not assign costs
involuntarily to a region in which that Interregional Transmission Project is not
located. The ISO shall, however, identify consequences for other regions, such as
upgrades that may be required in a third region. The ISO’s interregional cost
allocation methodology includes provisions for allocating the costs of upgrades
among the beneficiaries in the region in which the Interregional Transmission
Project is located to the transmission providers in such region that agree to bear
the costs associated with such upgrades.
Interregional Cost Allocation Principle 5: The ISO’s cost allocation
methodology and data requirements for determining benefits and identifying
beneficiaries for an Interregional Transmission Project shall be transparent with
adequate documentation to allow a stakeholder to determine how they were
applied to a proposed Interregional Transmission Project, as consistent with the
confidentiality requirements set forth in this Attachment Y and the ISO Code of
Conduct in Attachment F of the OATT.
Interregional Cost Allocation Principle 6: Though Order No. 1000 allows the
ISO to provide a different cost allocation methodology for different types of
interregional transmission facilities, such as facilities needed for reliability,
congestion relief, or to achieve Public Policy Requirements, the ISO has chosen to
adopt one interregional cost allocation methodology for all Interregional
Transmission Planning Projects. The interregional cost allocation methodology is
set out clearly and explained in detail in Section 31.5.7 of this Attachment Y. The
share of the cost related to any Interregional Transmission Project assigned to the
ISO shall be allocated as described in Section 31.5.7.1.
31.5.3
Regulated Responses to Reliability Needs
31.5.3.1 Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.3.2 of this
Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as set
forth in Section 31.5.2.1. This methodology shall apply to cost allocation for a regulated
transmission solution to an identified Reliability Need, including the ISO’s share of the costs of
an Interregional Transmission Project proposed as a regulated transmission solution to an
identified Reliability Need allocated in accordance with Section 31.5.7 of this Attachment Y.
The specific cost allocation methodology in Section 31.5.3.2 incorporates the following
elements:
31.5.3.1.1
The focus of the cost allocation methodology shall be on solutions to
Reliability Needs.
31.5.3.1.2
Potential impacts unrelated to addressing the Reliability Needs shall not be
considered for the purpose of cost allocation for regulated solutions.
31.5.3.1.3
Primary beneficiaries shall initially be those Load Zones or Subzones
identified as contributing to the reliability violation.
31.5.3.1.4
The cost allocation among primary beneficiaries shall be based upon their
relative contribution to the need for the regulated solution.
31.5.3.1.5
The ISO will examine the development of specific cost allocation rules
based on the nature of the reliability violation (e.g., thermal overload, voltage,
stability, resource adequacy and short circuit).
31.5.3.1.6
Cost allocation shall recognize the terms of prior agreements among the
Transmission Owners, if applicable.
31.5.3.1.7
Consideration should be given to the use of a materiality threshold for cost
allocation purposes.
31.5.3.1.8
The methodology shall provide for ease of implementation and
administration to minimize debate and delays to the extent possible.
31.5.3.1.9
Consideration should be given to the “free rider” issue as appropriate.
The methodology shall be fair and equitable.
31.5.3.1.10
The methodology shall provide cost recovery certainty to investors to the
extent possible.
31.5.3.1.11
The methodology shall apply, to the extent possible, to Gap Solutions.
31.5.3.1.12
Cost allocation is independent of the actual triggered project(s), except
when allocating cost responsibilities associated with meeting a Locational
Minimum Installed Capacity Requirement (“LCR”), and is based on a separate
process that results in NYCA meeting its LOLE requirement.
31.5.3.1.13
Cost allocation for a solution that meets the needs of a Target Year
assumes that backstop solutions of prior years have been implemented.
31.5.3.1.14
Cost allocation will consider the most recent values for LCRs. LCRs must
be met for the Target Year.
31.5.3.2 Cost Allocation Methodology
The cost allocation mechanism under this Section 31.5.3.2 sets forth the basis for
allocating costs associated with a Responsible Transmission Owner’s regulated backstop solution
or an Other Developer’s or Transmission Owner’s alternative regulated transmission solution
selected by the ISO as the more efficient or cost-effective transmission solution to an identified
Reliability Need.
The formula is not applicable to that portion of a project beyond the size of the solution
needed to provide the more efficient or cost effective solution appropriate to the Reliability Need
identified in the RNA. Nor is the formula applicable to that portion of the cost of a regulated
transmission reliability project that is, pursuant to Section 25.7.12 of Attachment S to the ISO
OATT, paid for with funds previously committed by or collected from Developers for the
installation of System Deliverability Upgrades required for the interconnection of generation or
merchant transmission projects.
This Section 31.5.3.2 establishes the allocation of the costs related to resolving
Reliability Needs resulting from resource adequacy, BPTF thermal transmission security, BPTF
voltage security, dynamic stability, and short circuit issues. Costs will be allocated in
accordance with the following hierarchy: (i) resource adequacy pursuant to Section 31.5.3.2.1,
(ii) BPTF thermal transmission security pursuant to Section 31.5.3.2.2, (iii) BPTF voltage
security pursuant to Section 31.5.3.2.3, (iv) dynamic stability pursuant to Section 31.5.3.2.4, and
(v) short circuit pursuant to Section 31.5.3.2.5.
31.5.3.2.1 Resource Adequacy Reliability Solution Cost Allocation Formula
For purposes of solutions eligible for cost allocation under this Section 31.5.3.2, this
section sets forth the cost allocation methodology applicable to that portion of the costs of the
solution attributable to resolving resource adequacy. The same cost allocation formula is applied
regardless of the project or sets of projects being triggered; however, the nature of the solution
set may lead to some terms equaling zero, thereby dropping out of the equation. To ensure that
appropriate allocation to the LCR and non-LCR zones occurs, the zonal allocation percentages
are developed through a series of steps that first identify responsibility for LCR deficiencies,
followed by responsibility for remaining need. The following formula shall apply to the
allocation of the costs of the solution attributable to resource adequacy:
+
*
+
*
*100%
Where i is for each applicable zone, n represent the total zones in NYCA, m represents
the zones isolated by the binding interfaces, IRM is the statewide reserve margin, and where
LCR is defined as the locational capacity requirement in terms of percentage and is equal to zero
for those zones without an LCR requirement, LCRdefi is the applicable zonal LCR deficiency,
SolnSTWdef is the STWdef for each applicable project, SolnCIdef is the CIdef for each
applicable project, and Soln_Size represents the total compensatory MW addressed by each
applicable project for all reliability cost allocation steps in this Section 31.5.3.2.
Three step cost allocation methodology for regulated reliability solutions:
31.5.3.2.1.1 Step 1 - LCR Deficiency
31.5.3.2.1.1.1 Any deficiencies in meeting the LCRs for the Target Year will be referred
to as the LCRdef. If the reliability criterion is met once the LCR deficiencies
have been addressed, that is LOLE 0.1 for the Target Year is achieved, then the
only costs allocated will be those related to the LCRdef MW. Cost responsibility
for the LCRdef MW will be borne by each deficient locational zone(s), to the
extent each is individually deficient.
For a single solution that addresses only an LCR deficiency in the applicable LCR zone,
the equation would reduce to:
Where i is for each applicable LCR zone, LCRdefi represents the applicable zonal LCR
deficiency, and Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.1.1.2 Prior to the LOLE calculation, voltage constrained interfaces will be
recalculated to determine the resulting transfer limits when the LCRdef MW are
added.
31.5.3.2.1.2 Step 2 - Statewide Resource Deficiency. If the reliability criterion is not
met after the LCRdef has been addressed, that is an LOLE > 0.1, then a NYCA
Free Flow Test will be conducted to determine if NYCA has sufficient resources
to meet an LOLE of 0.1.
31.5.3.2.1.2.1 If NYCA is found to be resource limited, the ISO, using the transfer limits
and resources determined in Step 1, will determine the optimal distribution of
additional resources to achieve a reduction in the NYCA LOLE to 0.1.
31.5.3.2.1.2.2 Cost allocation for compensatory MW added for cost allocation purposes
to achieve an LOLE of 0.1, defined as a Statewide MW deficiency (STWdef), will
be prorated to all NYCA zones, based on the NYCA coincident peak load. The
allocation to locational zones will take into account their locational requirements.
For a single solution that addresses only a statewide deficiency, the equation
would reduce to:
*
*100%
Where i is for each applicable zone, n is for the total zones in NYCA, IRM is the
statewide reserve margin, and LCR is defined as the locational capacity
requirement in terms of percentage and is equal to zero for those zones without an
LCR requirement, Soln STWdef is the STWdef for the applicable project, and
Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.1.3 Step 3 - Constrained Interface Deficiency. If the NYCA is not resource
limited as determined by the NYCA Free Flow Test, then the ISO will examine
constrained transmission interfaces, using the Binding Interface Test.
31.5.3.2.1.3.1 The ISO will provide output results of the reliability simulation program
utilized for the RNA that indicate the hours that each interface is at limit in each
flow direction, as well as the hours that coincide with a loss of load event. These
values will be used as an initial indicator to determine the binding interfaces that
are impacting LOLE within the NYCA.
31.5.3.2.1.3.2 The ISO will review the output of the reliability simulation program
utilized for the RNA along with other applicable information that may be
available to make the determination of the binding interfaces.
31.5.3.2.1.3.3 Bounded Regions are assigned cost responsibility for the compensatory
MW, defined as CIdef, needed to reach an LOLE of 0.1.
31.5.3.2.1.3.4 If one or more Bounded Regions are isolated as a result of binding
interfaces identified through the Binding Interface Test, the ISO will determine
the optimal distribution of compensatory MW to achieve a NYCA LOLE of 0.1.
Compensatory MW will be added until the required NYCA LOLE is achieved.
31.5.3.2.1.3.5 The Bounded Regions will be identified by the ISO’s Binding Interface
Test, which identifies the bounded interface limits that can be relieved and have
the greatest impact on NYCA LOLE. The Bounded Region that will have the
greatest benefit to NYCA LOLE will be the area to be first allocated costs in this
step. The ISO will determine if after the first addition of compensating MWs the
Bounded Region with the greatest impact on LOLE has changed. During this
iterative process, the Binding Interface Test will look across the state to identify
the appropriate Bounded Region. Specifically, the Binding Interface Test will be
applied starting from the interface that has the greatest benefit to LOLE (the
greatest LOLE reduction per interface compensatory MW addition), and then
extended to subsequent interfaces until a NYCA LOLE of 0.1 is achieved.
31.5.3.2.1.3.6 The CIdef MW are allocated to the applicable Bounded Region isolated as
a result of the constrained interface limits, based on their NYCA coincident peaks.
Allocation to locational zones will take into account their locational requirements.
For a single solution that addresses only a binding interface deficiency, the
equation would reduce to:
*
*100%
Where i is for each applicable zone, m is for the zones isolated by the binding
interfaces, IRM is the statewide reserve margin, and where LCR is defined as the
locational capacity requirement in terms of percentage and is equal to zero for
those zones without an LCR requirement, SolnCIdef is the CIdef for the
applicable project and Soln_Size represents the total compensatory MW
addressed by the applicable project.
31.5.3.2.2 BPTF Thermal Transmission Security Cost Allocation Formula
For purposes of solutions eligible for cost allocation under this Section 31.5.3.2, this
section sets forth the cost allocation methodology applicable to that portion of the costs of the
solution attributable to resolving BPTF thermal transmission security issues. If, after
consideration of the compensatory MW identified in the resource adequacy reliability solution
cost allocation in accordance with Section 31.5.3.2.1, there remains a BPTF thermal transmission
security issue, the ISO will allocate the costs of the portion of the solution attributable to
resolving the BPTF thermal transmission security issue(s) to the Subzones that contribute to the
BPTF thermal transmission security issue(s) in the following manner.
31.5.3.2.2.1 Calculation of Nodal Distribution Factors. The ISO will calculate the
nodal distribution factor for each load bus modeled in the power flow case
utilizing the output of the reliability simulation program that identified the
Reliability Need, including the NYCA generation dispatch and NYCA coincident
peak Load. The nodal distribution factor represents the percentage of the Load
that flows across the facility subject to the Reliability Need. The sign (positive or
negative) of the nodal distribution factor represents the direction of flow.
31.5.3.2.2.2 Calculation of Nodal Flow. The ISO will calculate the nodal megawatt
flow, defined as Nodal Flow, for each load bus modeled in the power flow case
by multiplying the amount of Load in megawatts for the bus, defined as Nodal
Load, by the nodal distribution factor for the bus. Nodal Flow represents the
number of megawatts that flow across the facility subject to the Reliability Need
due to the Load.
31.5.3.2.2.3 Calculation of Contributing Load and Contributing Flow. The Nodal
Load for a load bus with a positive nodal distribution factor is a contributing
Load, defined as CLoad, and the Nodal Flow for that Load is contributing flow,
defined as CFlow. To identify contributing Loads that have a material impact on
the Reliability Need, the ISO will calculate a contributing materiality threshold,
defined as CMT, as follows:
Where m is for the total number of Subzones and n is for the total number of load
buses in a given Subzone.
31.5.3.2.2.4 Calculation of Helping Load and Helping Flow. The Nodal Load for a
load bus with a negative or zero nodal distribution factor is a helping Load,
defined as HLoad, and the Nodal Flow for that Load is helping flow, defined as
HFlow. To identify helping Loads that have a material impact on the Reliability
Need, the ISO will calculate a helping materiality threshold, defined as HMT, as
follows:
Where m is for the total number of Subzones and n is for the total number of load
buses in a given Subzone.
31.5.3.2.2.5 Calculation of Net Material Flow for Each Subzone. The ISO will
identify material Nodal Flow for each Subzone and calculate the net material flow
for each Subzone. For each load bus, the Nodal Flow will be identified as
material flow, defined as MFlow, if the nodal distribution factor is (i) greater than
or equal to CMT, or (ii) less than or equal to HMT. The net material flow for
each Subzone, defined as SZ_NetFlow, is calculated as follows:
Where j is for each Subzone and n is for the total number of load buses in a given
Subzone.
31.5.3.2.2.6 Identification of Allocated Flow for Each Subzone. The ISO will identify
the allocated flow for each Subzone and verify that sufficient contributing flow is
being allocated costs. For each Subzone, if the SZ_NetFlow is greater than zero,
that Subzone has a net material contribution to the Reliability Need and the
SZ_NetFlow is identified as allocated flow, defined as SZ_AllocFlow. If the
SZ_NetFlow is less than or equal to zero, that Subzone does not have a net
material contribution to the Reliability Need and the SZ_AllocFlow is zero for
that Subzone. If the total SZ_AllocFlow for all Subzones is less than 60% of the
total CFlow for all Subzones, then the CMT will be reduced and SZ_NetFlow
recalculated until the total SZ_AllocFlow for all Subzones is at least 60% of the
total CFlow for all Subzones.
31.5.3.2.2.7 Cost Allocation for a Single BPTF Thermal Transmission Security Issue.
For a single solution that addresses only a BPTF thermal transmission security
issue, the equation for cost allocation would reduce to:
Where j is for each Subzone; m is for the total number of Subzones;
SZ_AllocFlow is the allocated flow for each Subzone; SolnBTSdef is the number
of compensatory MW for the BPTF thermal transmission security issue for the
applicable project; and Soln_Size represents the total compensatory MW
addressed by the applicable project.
31.5.3.2.2.8 Cost Allocation for Multiple BPTF Thermal Transmission Security Issues.
If a single solution addresses multiple BPTF thermal transmission security issues,
the ISO will calculate weighting factors based on the ratio of the present value of
the estimated costs for individual solutions to each BPTF thermal transmission
security issue. The present values of the estimated costs for the individual
solutions shall be based on a common base date that will be the beginning of the
calendar month in which the cost allocation analysis is performed (the “Base
Date”). The ISO will apply the weighting factors to the cost allocation calculated
for each Subzone for each individual BPTF thermal transmission security issue.
The following example illustrates the cost allocation for such a solution:
A cost allocation analysis for the selected solution is to be performed during a
given month establishing the beginning of that month as the Base Date.
The ISO has identified two BPTF thermal transmission security issues, Overload
X and Overload Y, and the ISO has selected a single solution (Project Z) to
address both BPTF thermal transmission security issues.
The cost of a solution to address only Overload X (Project X) is Cost(X),
provided in a given year’s dollars. The number of years from the Base Date to the
year associated with the cost estimate of Project (X) is N(X).
The cost of a solution to address only Overload Y (Project Y) is Cost(Y),
provided in a given year’s dollars. The number of years from the Base Date to the
year associated with the cost estimate of Project Y is N(Y).
The discount rate, D, to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners.
Based on the foregoing assumptions, the following formulas will be used:
Present Value of Cost (X) = PV Cost (X) = Cost (X) / (1+D)N(X)
Present Value of Cost (Y) = PV Cost (Y) = Cost (Y) / (1+D)N(Y)
Overload X weighting factor = PV Cost (X)/[PV Cost (X) + PV Cost (Y)]
Overload Y weighting factor = PV Cost (Y)/[PV Cost (X) + PV Cost (Y)]
Applying those formulas, if:
Cost (X) = $100 Million and N(X) = 6.25 years
Cost (Y) = $25 Million and N(Y) = 4.75 years
D = 7.5% per year
Then:
PV Cost (X) = 100/(1+0.075) 6.25 = 63.635 Million
PV Cost (Y) = 25/(1+0.075)4.75
= 17.732 Million
Overload X weighting factor = 63.635 / (63.635 + 17.732) = 78.21%
Overload Y weighting factor = 17.732 / (63.635 + 17.732) = 21.79%
Applying those weighing factors, if:
Subzone A cost allocation for Overload X is 15%
Subzone A cost allocation for Overload Y is 70%
Then:
Subzone A cost allocation % for Project Z =
(15% * 78.21%) + (70% * 21.79%) = 26.99%
31.5.3.2.2.9 Exclusion of Subzone(s) Based on De Minimis Impact. If a Subzone is
assigned a BPTF thermal transmission security cost allocation less than a de
minimis dollar threshold of the total project costs, that Subzone will not be
allocated costs; provided however, that the total de minimis Subzones may not
exceed 10% of the total BPTF thermal transmission security cost allocation. The
de minimis threshold is initially $10,000. If the total allocation percentage of all
de minimis Subzones is greater than 10%, then the de minimis threshold will be
reduced until the total allocation percentage of all de minimis Subzones is less
than or equal to 10%.
31.5.3.2.3 BPTF Voltage Security Cost Allocation
If, after consideration of the compensatory MW identified in the resource adequacy cost
allocation in accordance with Section 31.5.3.2.1 and BPTF thermal transmission security cost
allocation in accordance with Section 31.5.3.2.2, there remains a BPTF voltage security issue,
the ISO will allocate the costs of the portion of the solution attributable to resolving the BPTF
voltage security issue(s) to the Subzones that contribute to the BPTF voltage security issue(s).
The cost responsibility for the portion (MW or MVAr) of the solution attributable to resolving
the BPTF voltage security issue(s), defined as SolnBVSdef, will be allocated on a Load-ratio
share to each Subzone to which each bus with a voltage issue is connected, as follows:
Where j is for each Subzone; m is for the total number of Subzones that are subject to
BPTF voltage cost allocation; Coincident Peak is for the total peak Load for each Subzone;
SolnBVSdef is for the portion of the solution necessary to resolve the BPTF voltage security
issue(s); and Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.4 Dynamic Stability Cost Allocation
If, after consideration of the compensatory MW identified in the resource adequacy cost
allocation in accordance with Section 31.5.3.2.1, BPTF thermal transmission security cost
allocation in accordance with Section 31.5.3.2.2, and BPTF voltage security cost allocation in
accordance with Section 31.5.3.2.3, there remains a dynamic stability issue, the ISO will allocate
the costs of the portion of the solution attributable to resolving the dynamic stability issue(s) to
all Subzones in the NYCA on a Load-ratio share basis, as follows:
Where j is for each Subzone; m is for the total number of Subzones; Coincident Peak is
for the total peak Load for each Subzone; DynamicMW is for the megawatt portion of the
solution necessary to resolve the dynamic stability issue(s) for the applicable project; and
Soln_Size represents the total compensatory MW addressed by the applicable project.
31.5.3.2.5 Short Circuit Issues
If, after the completion of the prior reliability cost allocation steps, there remains a short
circuit issue, the short circuit issue will be deemed a local issue and related costs will not be
allocated under this process.
31.5.4
Regulated Economic Projects
31.5.4.1 The Scope of Section 31.5.4
As discussed in Section 31.5.1 of this Attachment Y, the cost allocation principles and
methodologies of this Section 31.5.4 apply only to regulated economic transmission projects
(“RETPs”) proposed in response to congestion identified in the CARIS.
This Section 31.5.4 does not apply to generation or demand side management projects,
nor does it apply to any market-based projects. This Section 31.5.4 does not apply to regulated
backstop solutions triggered by the ISO pursuant to the CSPP, provided, however, the cost
allocation principles and methodologies in this Section 31.5.4 will apply to regulated backstop
solutions when the implementation of the regulated backstop solution is accelerated solely to
reduce congestion in earlier years of the Study Period. The ISO will work with the ESPWG to
develop procedures to deal with the acceleration of regulated backstop solutions for economic
reasons.
Nothing in this Attachment Y mandates the implementation of any project in response to
the congestion identified in the CARIS.
31.5.4.2 Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.4.4 of
this Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as
set forth in Section 31.5.2.1. The specific cost allocation methodology in Section 31.5.4.4
incorporates the following elements:
31.5.4.2.1
The focus of the cost allocation methodology shall be on responses to
specific conditions identified in the CARIS.
31.5.4.2.2
Potential impacts unrelated to addressing the identified congestion shall
not be considered for the purpose of cost allocation for RETPs.
31.5.4.2.3
Projects analyzed hereunder as proposed RETPs may proceed on a market
basis with willing buyers and sellers at any time.
31.5.4.2.4
Cost allocation shall be based upon a beneficiaries pay approach. Cost
allocation under the ISO tariff for a RETP shall be applicable only when a super
majority of the beneficiaries of the project, as defined in Section 31.5.4.6 of this
Attachment Y, vote to support the project.
31.5.4.2.5
Beneficiaries of a RETP shall be those entities economically benefiting
from the proposed project. The cost allocation among beneficiaries shall be based
upon their relative economic benefit.
31.5.4.2.6
Consideration shall be given to the proposed project’s payback period.
31.5.4.2.7
The cost allocation methodology shall address the possibility of cost
overruns.
31.5.4.2.8
Consideration shall be given to the use of a materiality threshold for cost
allocation purposes.
31.5.4.2.9
The methodology shall provide for ease of implementation and
administration to minimize debate and delays to the extent possible.
31.5.4.2.10
Consideration should be given to the “free rider” issue as appropriate. The
methodology shall be fair and equitable.
31.5.4.2.11
The methodology shall provide cost recovery certainty to investors to the
extent possible.
31.5.4.2.12
Benefits determination shall consider various perspectives, based upon the
agreed-upon metrics for analyzing congestion.
31.5.4.2.13
Benefits determination shall account for future uncertainties as appropriate
(e.g., load forecasts, fuel prices, environmental regulations).
31.5.4.2.14
Benefits determination shall consider non-quantifiable benefits as
appropriate (e.g., system operation, environmental effects, renewable integration).
31.5.4.3 Project Eligibility for Cost Allocation
The methodologies in this Section 31.5.4.3 will be used to determine the eligibility of a
proposed RETP to have its cost allocated and recovered pursuant to the provisions of this
Attachment Y.
31.5.4.3.1
The ISO will evaluate the benefits against the costs (as provided by the
Developer) of each proposed RETP over a ten-year period commencing with the
proposed commercial operation date for the project. The Developer of each
project will pay the cost incurred by the ISO to conduct the ten-year benefit/cost
analysis of its project. The ISO, in conjunction with the ESPWG, will develop
methodologies for extending the most recently completed CARIS database as
necessary to evaluate the benefits and costs of each proposed RETP.
31.5.4.3.2
The benefit metric for eligibility under the ISO’s benefit/cost analysis will
be expressed as the present value of the annual NYCA-wide production cost
savings that would result from the implementation of the proposed project,
measured for the first ten years from the proposed commercial operation date for
the project.
31.5.4.3.3
The cost for the ISO’s benefit/cost analysis will be supplied by the
Developer of the project, and the cost metric for eligibility will be expressed as
the present value of the first ten years of annual total revenue requirements for the
project, reasonably allocated over the first ten years from the proposed
commercial operation date for the project.
31.5.4.3.4
For informational purposes only, the ISO will also calculate the present
value of the annual total revenue requirement for the project over a 30 year period
commencing with the proposed commercial operation date of the project.
31.5.4.3.5
To be eligible for cost allocation and recovery under this Attachment Y,
the benefit of the proposed project must exceed its cost measured over the first ten
years from the proposed commercial operation date for the project, and the
requirements of section 31.5.4.2 must be met. The total capital cost of the project
must exceed $25 million. In addition, a super-majority of the beneficiaries must
vote in favor of the project, as specified in Section 31.5.4.6 of this Attachment Y.
31.5.4.3.6
In addition to calculating the benefit metric as defined in Section
31.5.4.3.2, the ISO will calculate additional metrics to estimate the potential
benefits of the proposed project, for information purposes only, in accordance
with Section 31.3.1.3.5, for the applicable metric. These additional metrics shall
include those that measure reductions in LBMP load costs, changes to generator
payments, ICAP costs, Ancillary Service costs, emissions costs, and losses. TCC
revenues will be determined in accordance with Section 31.5.4.4.2.3. The ISO
will provide information on these additional metrics to the maximum extent
practicable considering its overall resource commitments.
31.5.4.3.7
In addition to the benefit/cost analysis performed by the ISO under this
Section 31.5.4.3, the ISO will work with the ESPWG to consider the development
and implementation of scenario analyses, for information only, that shed
additional light on the benefit/cost analysis of a proposed project. These
additional scenario analyses may cover fuel and load forecast uncertainty,
emissions data and the cost of allowances, pending environmental or other
regulations, and alternate resource and energy efficiency scenarios. Consideration
of these additional scenarios will take into account the resource commitments of
the ISO.
31.5.4.4 Cost Allocation for Eligible Projects
As noted in Section 31.5.4.2 of this Attachment Y, the cost of a RETP will be allocated to
those entities that would economically benefit from implementation of the proposed project. This
methodology shall apply to cost allocation for a RETP, including the ISO’s share of the costs of
an Interregional Transmission Project proposed as a RETP allocated in accordance with Section
31.5.7 of this Attachment Y.
31.5.4.4.1
The ISO will identify the beneficiaries of the proposed project over a ten-
year time period commencing with the proposed commercial operation date for
the project. The ISO, in conjunction with the ESPWG, will develop
methodologies for extending the most recently completed CARIS database as
necessary for this purpose.
31.5.4.4.2
The ISO will identify beneficiaries of a proposed project as follows:
31.5.4.4.2.1 The ISO will measure the present value of the annual zonal LBMP load
savings for all Load Zones which would have a load savings, net of reductions in
TCC revenues, and net of reductions from bilateral contracts (based on available
information provided by Load Serving Entities to the ISO as set forth in
subsection 31.5.4.4.2.5 below) as a result of the implementation of the proposed
project. For purposes of this calculation, the present value of the load savings will
be equal to the sum of the present value of the Load Zone’s load savings for each
year over the ten-year period commencing with the project’s commercial
operation date. The load savings for a Load Zone will be equal to the difference
between the zonal LBMP load cost without the project and the LBMP load cost
with the project, net of reductions in TCC revenues and net of reductions from
bilateral contracts.
31.5.4.4.2.2 The beneficiaries will be those Load Zones that experience net benefits
measured over the first ten years from the proposed commercial operation date for
the project. If the sum of the zonal benefits for those Load Zones with load
savings is greater than the revenue requirements for the project (both load savings
and revenue requirements measured in present value over the first ten years from
the commercial operation date of the project), the ISO will proceed with the
development of the zonal cost allocation information to inform the beneficiary
voting process.
31.5.4.4.2.3 Reductions in TCC revenues will reflect the forecasted impact of the
project on TCC auction revenues and day-ahead residual congestion rents
allocated to load in each zone, not including the congestion rents that accrue to
any Incremental TCCs that may be made feasible as a result of this project. This
impact will include forecasts of: (1) the total impact of that project on the
Transmission Service Charge offset applicable to loads in each zone (which may
vary for loads in a given zone that are in different Transmission Districts); (2) the
total impact of that project on the NYPA Transmission Adjustment Charge offset
applicable to loads in that zone; and (3) the total impact of that project on
payments made to LSEs serving load in that zone that hold Grandfathered Rights
or Grandfathered TCCs, to the extent that these have not been taken into account
in the calculation of item (1) above. These forecasts shall be performed using the
procedure described in Appendix B to this Attachment Y.
31.5.4.4.2.4 Estimated TCC revenues from any Incremental TCCs created by a
proposed RETP over the ten-year period commencing with the project’s
commercial operation date will be added to the Net Load Savings used for the
cost allocation and beneficiary determination.
31.5.4.4.2.5 The ISO will solicit bilateral contract information from all Load Serving
Entities, which will provide the ISO with bilateral energy contract data for
modeling contracts that do not receive benefits, in whole or in part, from LBMP
reductions, and for which the time period covered by the contract is within the
ten-year period beginning with the commercial operation date of the project.
Bilateral contract payment information that is not provided to the ISO will not be
included in the calculation of the present value of the annual zonal LBMP savings
in section 31.5.4.4.2.1 above.
31.5.4.4.2.5.1 All bilateral contract information submitted to the ISO must identify the
source of the contract information, including citations to any public documents
including but not limited to annual reports or regulatory filings
31.5.4.4.2.5.2 All non-public bilateral contract information will be protected in
accordance with the ISO’s Code of Conduct, as set forth in Section 12.4 of
Attachment F of the ISO OATT, and Section 6 of the ISO Services Tariff.
31.5.4.4.2.5.3 All bilateral contract information and information on LSE-owned
generation submitted to the ISO must include the following information:
(1)
Contract quantities on an annual basis:
(a)
For non-generator specific contracts, the Energy (in MWh) contracted to serve
each Zone for each year.
(b)
For generator specific contracts or LSE-owned generation, the name of the
generator(s) and the MW or percentage output contracted or self-owned for use by
Load in each Zone for each year.
(2)
For all Load Serving Entities serving Load in more than one Load Zone, the
quantity (in MWh or percentage) of bilateral contract Energy to be applied to each
Zone, by year over the term of the contract.
(3)
Start and end dates of the contract.
(4)
Terms in sufficient detail to determine that either pricing is not indexed to LBMP,
or, if pricing is indexed to LBMP, the manner in which prices are connected to
LBMP.
(5)
Identify any changes in the pricing methodology on an annual basis over the term
of the contract.
31.5.4.4.2.5.4 Bilateral contract and LSE-owned generation information will be used to
calculate the adjusted LBMP savings for each Load Zone as follows:
AdjLBMPSy,z, the adjusted LBMP savings for each Load Zone z in each year y, shall be
calculated using the following equation:
Where:
TLy,z is the total annual amount of Energy forecasted to be consumed by Load in year y in
Load Zone z;
By,z is the set of blocks of Energy to serve Load in Load Zone z in year y that are sold
under bilateral contracts for which information has been provided to the ISO that meets the
requirements set forth elsewhere in this Section 31.5.4.4.2.5
BCLb,y,z is the total annual amount of Energy sold into Load Zone z in year y under
bilateral contract block b;
Indb,y,z is the ratio of (1) the increase in the amount paid by the purchaser of Energy,
under bilateral contract block b, as a result of an increase in the LBMP in Load Zone z in year y
to (2) the increase in the amount that a purchaser of that amount of Energy would pay if the
purchaser paid the LBMP for that Load Zone in that year for all of that Energy (this ratio shall be
zero for any bilateral contract block of Energy that is sold at a fixed price or for which the cost of
Energy purchased under that contract otherwise insensitive to the LBMP in Load Zone z in year
y);
SGy,z is the total annual amount of Energy in Load Zone z that is forecasted to be served
by LSE-owned generation in that Zone in year y;
LBMP1y,z is the forecasted annual load-weighted average LBMP for Load Zone z in year
y, calculated under the assumption that the project is not in place; and
LBMP2y,z is the forecasted annual load-weighted average LBMP for Load Zone z in year
y, calculated under the assumption that the project is in place.
31.5.4.4.2.6 NZSz, the Net Zonal Savings for each Load Zone z resulting from a given
project, shall be calculated using the following equation:
Where:
PS is the year in which the project is expected to enter commercial operation;
AdjLBMPSy,z is as calculated in Section 31.5.4.4.2.5;
TCCRevImpacty,z is the forecasted impact of TCC revenues allocated to Load Zone z in
year y, calculated using the procedure described in Appendix B in Section 31.7 of this
Attachment Y; and
DFy is the discount factor applied to cash flows in year y to determine the present value
of that cash flow in year PS.
31.5.4.4.3
Load Zones not benefiting from a proposed RETP will not be allocated
any of the costs of the project under this Attachment Y. There will be no “make
whole” payments to non-beneficiaries.
31.5.4.4.4
Costs of a project will be allocated to beneficiaries as follows:
31.5.4.4.4.1 The ISO will allocate the cost of the RETP based on the zonal share of
total savings to the Load Zones determined pursuant to Section 31.5.4.4.2 to be
beneficiaries of the proposed project. Total savings will be equal to the sum of
load savings for each Load Zone that experiences net benefits pursuant to Section
31.5.4.4.2. A Load Zone’s cost allocation will be equal to the present value of the
following calculation:
31.5.4.4.4.2 Zonal cost allocation calculations for a RETP will be performed prior to
the commencement of the ten-year period that begins with the project’s
commercial operation date, and will not be adjusted during that ten-year period.
31.5.4.4.4.3 Within zones, costs will be allocated to LSEs based on MWhs calculated
for each LSE for each zone using data from the most recent available 12 month
period. Allocations to an LSE will be calculated in accordance with the following
formula:
31.5.4.4.5
Project costs allocated under this Section 31.5.4.4 will be determined as
follows:
31.5.4.4.5.1 The project cost allocated under this Section 31.5.4.4 will be based on the
total project revenue requirement, as supplied by the Developer of the project, for
the first ten years of project operation. The total project revenue requirement will
be determined in accordance with the formula rate on file at the Commission. If
there is no formula rate on file at the Commission, then the Developer shall
provide to the ISO the project-specific parameters to be used to calculate the total
project revenue requirement.
31.5.4.4.5.2 Once the benefit/cost analysis is completed the amortization period and
the other parameters used to determine the costs that will be recovered for the
project should not be changed, unless so ordered by the Commission or a court of
applicable jurisdiction, for cost recovery purposes to maintain the continued
validity of the benefit/cost analysis.
31.5.4.4.5.3 The ISO, in conjunction with the ESPWG, will develop procedures to
allocate the risk of project cost increases that occur after the ISO completes its
benefit/cost analysis under this Attachment Y. These procedures may include
consideration of an additional review and vote prior to the start of construction
and whether the developer should bear all or part of the cost of any overruns.
31.5.4.4.6
The Commission must approve the cost of a proposed RETP for that cost
to be recovered through Rate Schedule 10 of the ISO OATT. The developer’s
filing of its project revenue requirement with the Commission pursuant to Rate
Schedule 10 must be consistent with the project proposal evaluated by the ISO
under this Attachment Y in order to be cost allocated to beneficiaries.
31.5.4.5 Collaborative Governance Process and Board Action
31.5.4.5.1
The ISO shall submit the results of its project benefit/cost analysis and
beneficiary determination to the ESPWG and TPAS, and to the identified
beneficiaries of the proposed RETP for comment. The ISO shall make available
to any interested party sufficient information to replicate the results of the
benefit/cost analysis and beneficiary determination. The information made
available will be electronically masked and made available pursuant to a process
that the ISO reasonably determines is necessary to prevent the disclosure of any
Confidential Information or Critical Energy Infrastructure Information contained
in the information made available. Following completion of the review by the
ESPWG and TPAS of the project benefit/cost analysis, the ISO’s analysis
reflecting any revisions resulting from the TPAS and ESPWG review shall be
forwarded to the Business Issues Committee and Management Committee for
discussion and action.
31.5.4.5.2
Following the Management Committee vote, the ISO’s project benefit/cost
analysis and beneficiary determination will be forwarded, with the input of the
Business Issues Committee and Management Committee, to the ISO Board for
review and action. In addition, the ISO’s determination of the beneficiaries’
voting shares will be forwarded to the ISO Board for review and action. The
Board may approve the analysis and beneficiary determinations as submitted or
propose modifications on its own motion. If any changes to the benefit/cost
analysis or the beneficiary determinations are proposed by the Board, the revised
analysis and beneficiary determinations shall be returned to the Management
Committee for comment. If the Board proposes any changes to the ISO’s voting
share determinations, the Board shall so inform the LSE or LSEs impacted by the
proposed change and shall allow such an LSE or LSEs an opportunity to comment
on the proposed change. The Board shall not make a final determination on the
project benefit/cost analysis and beneficiary determination until it has reviewed
the Management Committee comments. Upon final approval of the Board,
project benefit/cost analysis and beneficiary determinations shall be posted by the
ISO on its website and shall form the basis of the beneficiary voting described in
Section 31.5.4.6 of this Attachment Y.
31.5.4.6 Voting by Project Beneficiaries
31.5.4.6.1
Only LSEs serving Load located in a beneficiary zone determined in
accordance with the procedures in Section 31.5.4.4 of this Attachment Y shall be
eligible to vote on a proposed project. The ISO will, in conjunction with the
ESPWG, develop procedures to determine the specific list of voting entities for
each proposed project. Prior to a vote being conducted, the Developer of the
RETP must have a completed System Impact Study or System Reliability Impact
Study, as applicable.
31.5.4.6.2
The voting share of each LSE shall be weighted in accordance with its
share of the total project benefits, as allocated by Section 31.5.4.4 of this
Attachment Y.
31.5.4.6.3
The costs of a RETP shall be allocated under this Attachment Y if eighty
percent (80%) or more of the actual votes cast on a weighted basis are cast in
favor of implementing the project.
31.5.4.6.4
If the proposed RETP meets the required vote in favor of implementing
the project, and the project is implemented, all beneficiaries, including those
voting “no,” will pay their proportional share of the cost of the project.
31.5.4.6.5
The ISO will tally the results of the vote in accordance with procedures set
forth in the ISO Procedures, and report the results to stakeholders. Beneficiaries
voting against approval of a project must submit to the ISO their rationale for
their vote within 30 days of the date that the vote is taken. Beneficiaries must
provide a detailed explanation of the substantive reasons underlying the decision,
including, where appropriate: (1) which additional benefit metrics, either
identified in the tariff or otherwise, were used; (2) the actual quantification of
such benefit metrics or factors; (3) a quantification and explanation of the net
benefit or net cost of the project to the beneficiary; and (4) data supporting the
metrics and other factors used. Such explanation may also include uncertainties,
and/or alternative scenarios and other qualitative factors considered, including
state public policy goals. The ISO will report this information to the Commission
in an informational filing to be made within 60 days of the vote. The
informational filing will include: (1) a list of the identified beneficiaries; (2) the
results of the benefit/cost analysis; and (3) where a project is not approved,
whether the developer has provided any formal indication to the ISO as to the
future development of the project.
31.5.5
Regulated Transmission Solutions to Public Policy Transmission Needs
31.5.5.1 The Scope of Section 31.5.5
As discussed in Section 31.5.1 of this Attachment Y, the cost allocation principles and
methodologies of this Section 31.5.5 apply only to regulated Public Policy Transmission
Projects. This Section 31.5.5 does not apply to Other Public Policy Projects, including
generation or demand side management projects, or any market-based projects. This Section
31.5.5 does not apply to regulated reliability solutions implemented pursuant to the reliability
planning process, nor does it apply to RETPs proposed in response to congestion identified in the
CARIS.
A regulated solution shall only utilize the cost allocation methodology set forth in Section
31.5.3 where it is: (1) a Responsible Transmission Owner’s regulated backstop solution, (2) an
alternative regulated transmission solution selected by the ISO as the more efficient or cost
effective regulated transmission solution to satisfy a Reliability Need, or (3) seeking cost
recovery where it has been halted or cancelled pursuant to the provisions of Section 31.2.8.2. A
regulated economic transmission solution proposed in response to congestion identified in the
CARIS, and approved pursuant to Section 31.5.4.6, shall only be eligible to utilize the cost
allocation principles and methodologies set forth in Section 31.5.4.
31.5.5.2
Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.5.4 of
this Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as
set forth in Section 31.5.2.1. The specific cost allocation methodology in Section 31.5.5.4
incorporates the following elements:
31.5.5.2.1
The focus of the cost allocation methodology shall be on regulated Public
Policy Transmission Projects.
31.5.5.2.2
Projects analyzed hereunder as Public Policy Transmission Projects may
proceed on a market basis with willing buyers and sellers at any time.
31.5.5.2.3
Cost allocation shall be based on a beneficiaries pay approach.
31.5.5.2.4
Project benefits will be identified in accordance with Section 31.5.5.4.
31.5.5.2.5
Identification of beneficiaries for cost allocation and cost allocation
among those beneficiaries shall be according to the methodology specified in
Section 31.5.5.4.
31.5.5.3 Project Eligibility for Cost Allocation
The Developer of a Public Policy Transmission Project will be eligible for cost allocation
in accordance with the process set forth in Section 31.5.5.4 when its project is selected by the
ISO as the more efficient or cost effective regulated Public Policy Transmission Project;
provided, however, that if the appropriate federal, state, or local agency(ies) rejects the selected
project’s necessary authorizations, or such authorizations are withdrawn, the costs the Developer
is eligible to recover under Section 31.4.12.1 shall be allocated in accordance with Section
31.5.5.4.3, except as otherwise determined by the Commission. The Developer of the selected
regulated transmission solution may recover its costs in accordance with Section 31.5.6 and Rate
Schedule 10 of the ISO OATT. If the Developer proposed its Public Policy Transmission Project
in response to a request by the NYPSC or Long Island Power Authority pursuant to Section
31.4.3.2 and its project was not selected by the ISO, the costs that the Developer is eligible to
recover pursuant to Section 31.4.3.2 shall be allocated in accordance with Section 31.5.5.4.3,
except as otherwise determined by the Commission. The Developer may recover these costs in
accordance with Section 31.5.6 and Rate Schedule 10 of the ISO OATT.
31.5.5.4 Cost Allocation for Eligible Projects
As noted in Section 31.5.5.2 of this Attachment Y, the identification of beneficiaries for
cost allocation and the cost allocation of a selected Public Policy Transmission Project will be
conducted in accordance with the process described in this Section 31.5.5.4. This Section will
also apply to the allocation within New York of the ISO’s share of the costs of an Interregional
Transmission Project proposed as a solution to a Public Policy Transmission Need allocated in
accordance with Section 31.5.7 of this Attachment Y. The establishment of a cost allocation
methodology and rates for a proposed solution that is undertaken by LIPA or NYPA as an
Unregulated Transmitting Utility to a Public Policy Transmission Need as determined in
Sections 31.4.2.1 through 31.4.2.3, as applicable, or an Interregional Transmission Project shall
occur pursuant to Section 31.5.5.4.4 through 31.5.5.4.6, as applicable. Nothing herein shall
deprive a Transmission Owner or Other Developer of any rights it may have under Section 205
of the Federal Power Act to submit filings proposing any other cost allocation methodology to
the Commission or create any Section 205 filing rights for any Transmission Owner, Other
Developer, the ISO, or any other entity. The ISO shall apply the cost allocation methodology
accepted by the Commission. The cost allocation methodology that is accepted or approved by
the Commission for a particular Public Policy Transmission Project in accordance with this
Section 31.5.5.4 will be set forth in Appendix E (Section 31.8) of this Attachment Y.
31.5.5.4.1
If the Public Policy Requirement that results in the identification by the
NYPSC of a Public Policy Transmission Need prescribes the use of a particular
cost allocation and recovery methodology, then the ISO shall file that
methodology with the Commission within 60 days of the issuance by the NYPSC
of its identification of a Public Policy Transmission Need. Nothing herein shall
deprive a Transmission Owner or Other Developer of any rights it may have
under Section 205 of the Federal Power Act to submit filings proposing any other
cost allocation methodology to the Commission or create any Section 205 filing
rights for any Transmission Owner, Other Developer, the ISO, or any other entity.
If the Developer files a different proposed cost allocation methodology under
Section 205 of the Federal Power Act, it shall have the burden of demonstrating
that its proposed methodology is compliant with the Order No. 1000 Regional
Cost Allocation Principles taking into account the methodology specified in the
Public Policy Requirement.
31.5.5.4.2
Subject to the provisions of Section 31.5.5.4.1, the Developer may submit
to the NYPSC for its consideration - no later than 30 days after the ISO’s
selection of the regulated Public Policy Transmission Project - a proposed cost
allocation methodology, which may include a cost allocation based on load ratio
share, adjusted to reflect, as applicable, the Public Policy Requirement or Public
Policy Transmission Need, the party(ies) responsible for complying with the
Public Policy Requirement, and the party(ies) who benefit from the transmission
facility.
31.5.5.4.2.1 The NYPSC shall have 150 days to review the Developer’s proposed cost
allocation methodology and to inform the Developer regarding whether it
supports the methodology.
31.5.5.4.2.2. If the NYPSC supports the proposed cost allocation methodology, the
Developer shall file that cost allocation methodology with the Commission for its
acceptance under Section 205 of the Federal Power Act within 30 days of the
NYPSC informing the Developer of its support. The Developer shall have the
burden of demonstrating that the proposed cost allocation methodology is
compliant with the Order No. 1000 Regional Cost Allocation Principles.
31.5.5.4.2.3 If the NYPSC does not support the proposed cost allocation methodology,
then the Developer shall take reasonable steps to respond to the NYPSC’s
concerns and to develop a mutually agreeable cost allocation methodology over a
period of no more than 60 days after the NYPSC informing the Developer that it
does not support the methodology.
31.5.5.4.2.4 If a mutually acceptable cost allocation methodology is developed during
the timeframe set forth in Section 31.5.5.4.2.3, the Developer shall file it with the
Commission for acceptance under Section 205 of the Federal Power Act no later
than 30 days after the conclusion of the 60 day discussion period with the
NYPSC. The Developer shall have the burden of demonstrating that the proposed
cost allocation methodology is compliant with the Order No. 1000 Regional Cost
Allocation Principles.
31.5.5.4.2.5 If no mutually agreeable cost allocation methodology is developed, the
Developer shall file its preferred cost allocation methodology with the
Commission for acceptance under Section 205 of the Federal Power Act no later
than 30 days after the conclusion of the 60 day discussion period with the
NYPSC. The Developer shall have the burden of demonstrating that its proposed
methodology is compliant with the Order No. 1000 Regional Cost Allocation
Principles in consideration of the position of the NYPSC. The filing shall include
the methodology supported by NYPSC for the Commission’s consideration. If the
Developer elects to use the load ratio share cost allocation methodology
referenced below in Section 31.5.5.4.3, the Developer shall notify the
Commission of its intent to utilize the load ratio share methodology and shall
include in its notice the NYPSC supported methodology for the Commission’s
consideration.
31.5.5.4.3.
Unless the Commission has accepted an alternative cost allocation
methodology pursuant to this Section, the ISO shall allocate the costs of the
Public Policy Transmission Project to all Load Serving Entities in the NYCA
using the default cost allocation methodology, based upon a load ratio share
methodology.
31.5.5.4.4
The NYISO will make any Section 205 filings related to this Section on
behalf of NYPA to the extent requested to do so by NYPA. NYPA shall bear the
burden of demonstrating that such a filing is compliant with the Order No. 1000
Regional Cost Allocation Principles. NYPA shall also be solely responsible for
making any jurisdictional reservations or arguments related to their status as non-
Commission-jurisdictional utilities that are not subject to various provisions of the
Federal Power Act.
31.5.5.4.5
The cost allocation methodology and any rates for cost recovery for a
proposed solution to a Public Policy Transmission Need undertaken by LIPA, as
an Unregulated Transmitting Utility (for purposes of this section a “LIPA
project”), shall be established and recovered as follows:
31.5.5.4.5.1 For costs solely to LIPA customers. The cost allocation methodology and
rates to be established for a LIPA project, for which cost recovery will only occur
from LIPA customers, will be established pursuant to Article 5, Title 1-A of the
New York Public Authorities Law, Sections 1020-f(u) and 1020-s. Prior to the
adoption of any cost allocation mechanism or rates for such a LIPA project, and
pursuant to Section 1020-f(u), the Long Island Power Authority’s Board of
Trustees shall request that the NYDPS provide a recommendation with respect to
the cost allocation methodology and rate that LIPA has proposed and the Board of
Trustees shall consider such recommendation in accordance with the requirements
of Section 1020-f(u). Upon approval of the cost allocation mechanism and/or
rates by the Long Island Power Authority’s Board of Trustees, LIPA shall provide
to the ISO, for purposes of inclusion within the ISO OATT and filing with FERC
on an informational basis only, a description of the cost allocation mechanism and
the rate that LIPA will charge and collect within the Long Island Transmission
District.
31.5.5.4.5.2 For Costs for a LIPA Project That May be Allocated to Other
Transmission Districts. A LIPA project that meets a Public Policy Transmission
Need as determined by the NYPSC pursuant to Section 31.4.2.3(iii) may be
allocated to market participants outside of the Long Island Transmission District.
The cost allocation methodology and rate for such a LIPA project shall be
established in accordance with the following procedures. LIPA’s proposed cost
allocation methodology and/or rate shall be reviewed and approved by the Long
Island Power Authority’s Board of Trustees pursuant to Article 5, Title 1-A of the
New York Public Authorities Law, Sections 1020-f(u) and 1020-s. Prior to the
adoption of any cost allocation mechanism or rates for such project and pursuant
to Section 1020-f(u), the Long Island Power Authority’s Board of Trustees shall
request that the NYDPS provide a recommendation with respect to the cost
allocation methodology and rate that LIPA has proposed and the Board of
Trustees shall consider such recommendation in accordance with the requirements
of Section 1020-f(u). LIPA shall inform the ISO of the cost allocation
methodology and rate that has been approved by the Long Island Power
Authority’s Board of Trustees for filing with the Commission.
Upon approval by the Long Island Power Authority’s Board of Trustees,
LIPA shall submit and request that the ISO file the LIPA cost allocation
methodology for approval with the Commission. Any cost allocation
methodology for a LIPA project that allocates costs to market participants outside
of the Long Island Transmission District shall be reviewed as to whether there is
comparability in the derivation of the cost allocation for market participants such
that LIPA has demonstrated that the proposed cost allocation is compliant with
the Order No. 1000 cost allocation principles, there are benefits provided by the
project to market participants outside of the Long Island Transmission District,
and that the proposed allocation is roughly commensurate to the identified
benefits.
Article 5, Title 1-A of the New York Public Authorities Law, Sections
1020-f(u) and 1020-s, requires that LIPA’s rates be established at the lowest level
consistent with sound fiscal and operating practices of the Long Island Power
Authority and which provide for safe and adequate service. Upon approval of a
LIPA rate by the Long Island Power Authority’s Board of Trustees pursuant to
Section 1020-f(u), LIPA shall submit, and request that the ISO file, the LIPA rate
with the Commission for review under the same comparability standard as applied
to the review of changes in LIPA’s TSC under Attachment H of this tariff.
In the event that the cost allocation methodology or rate approved by the
Long Island Power Authority’s Board of Trustees did not adopt the NYDPS
recommendation, the NYDPS recommendation shall be included in the filing for
the Commission’s consideration.
31.5.5.4.5.3 Support for Filing. LIPA shall intervene in support of the filing(s) made
pursuant to Section 31.5.5.4.5 at the Commission and shall take the responsibility
to demonstrate that: (i) the cost allocation methodology and/or rate approved by
the Long Island Power Authority’s Board of Trustees meets the applicable
standard of comparability, and (ii) the Commission should accept such
methodology or rate for filing. LIPA shall also be responsible for responding to,
and seeking to resolve, concerns about the contents of the filing that might be
raised in such proceeding.
31.5.5.4.5.4 Billing of LIPA Charges Outside of the Long Island Transmission District.
For Transmission Districts other than the Long Island Transmission District, the
ISO shall bill for LIPA, as a separate charge, the costs incurred by LIPA for a
solution to a Public Policy Transmission Need allocated using the cost allocation
methodology and rates established pursuant to Section 31.5.5.4.5.2 and accepted
for filing by the Commission and shall remit the revenues collected to LIPA each
Billing Period in accordance with the ISO’s billing and settlement procedures.
31.5.5.4.6
The inclusion in the ISO OATT or in a filing with the Commission of the
cost allocation and charges for recovery of costs incurred by NYPA or LIPA
related to a solution to a transmission need driven by a Public Policy Requirement
or Interregional Transmission Project as provided for in Sections 31.5.5.4.4 and
31.5.5.4.5 shall not be deemed to modify the treatment of such rates as non-
jurisdictional pursuant to Section 201(f) of the FPA.
31.5.6
Cost Recovery for Regulated Projects
31.5.6.1
Cost Recovery for Regulated Transmission Project to Address a
Reliability Need
31.5.6.1.1
A Responsible Transmission Owner, a Transmission Owner, or an Other
Developer may recover in accordance with Rate Schedule 10 of the ISO OATT
the costs incurred with respect to the implementation of: (i) a regulated backstop
transmission solution proposed by a Responsible Transmission Owner pursuant to
Section 31.2.4.3.1 of this Attachment Y and the ISO/TO Reliability Agreement or
an Operating Agreement; (ii) an alternative regulated transmission solution that
the ISO has selected pursuant to Section 31.2.6.5.2 of this Attachment Y as the
more efficient or cost-effective solution to a Reliability Need; (iii) a regulated
transmission Gap Solution proposed by a Responsible Transmission Owner
pursuant to Section 31.2.11.4 of this Attachment Y; or (iv) an alternative
regulated transmission Gap Solution that has been determined by the appropriate
state regulatory agency(ies) as the preferred solution(s) to a Reliability Need
pursuant to Section 31.2.11.5 of Attachment Y of the ISO OATT. 31.5.6.1.2
If a regulated solution: (i) is eligible for cost recovery as described in Section
31.5.6.1.1 and (ii) is not triggered or is halted pursuant to Sections 31.2.8 or
31.2.10.1.2 of this Attachment Y, the Responsible Transmission Owner,
Transmission Owner or Other Developer of that solution may recover the costs
that it eligible to recover pursuant to Sections 31.2.8 or 31.2.10.1.2 in accordance
with Rate Schedule 10 of the ISO OATT.
31.5.6.1.3
Costs related to non-transmission regulated solutions to Reliability Needs
will be recovered by a Responsible Transmission Owner, Transmission Owner, or
Other Developer in accordance with the provisions of New York Public Service
Law, New York Public Authorities Law, or other applicable state law. A
Responsible Transmission Owner, a Transmission Owner, or Other Developer
may propose and undertake a regulated non-transmission solution, provided that
the appropriate state agency(ies) has established cost recovery procedures
comparable to those provided in this tariff for regulated transmission solutions to
ensure the full and prompt recovery of all reasonably-incurred costs related to
such non-transmission solutions. Nothing in this section shall affect the
Commission’s jurisdiction over the sale and transmission of electric energy
subject to the jurisdiction of the Commission.
31.5.6.2
Cost Recovery for Regulated Economic Transmission Project
A Transmission Owner or an Other Developer may recover in accordance
with Rate Schedule 10 of the ISO OATT the costs incurred with respect to the
implementation a regulated economic transmission project that has been
approved pursuant to Section 31.5.4.6 of this Attachment Y.
31.5.6.3
Cost Recovery for Regulated Transmission Project to Address a Public
Policy Transmission Need
31.5.6.3.1
A Transmission Owner or an Other Developer may recover in accordance
with Rate Schedule 10 of the ISO OATT the costs incurred with respect to the
implementation of: (i) a Public Policy Transmission Project that the ISO has
selected as the more efficient or cost-effective solution to a Public Policy
Transmission Need, or (ii) a Public Policy Transmission Project proposed by a
Developer in response to a request by the NYPSC or Long Island Power
Authority in accordance with Section 31.4.3.2 of Attachment Y of the ISO OATT.
Such cost recovery will also include reasonable costs incurred by the Developer to
provide a more detailed study or cost estimate for such project at the request of
the NYPSC, and to prepare the application required to comply with New York
Public Service Law Article VII, or any successor statute or any other applicable
permits, and to seek other necessary authorizations.
31.5.6.3.2
If a regulated solution that: (i) is eligible for cost recovery as described in
Section 31.5.6.3.1 and (ii) is halted as described in Section 31.4.12.1 of this
Attachment Y, the Transmission Owner or Other Developer of that solution may
recover the costs that it is eligible to recover pursuant to Section 31.4.12.1 in
accordance with Rate Schedule 10 of the ISO OATT.
31.5.6.4
Cost Recovery for Interregional Transmission Project
A Responsible Transmission Owner, a Transmission Owner, or an Other
Developer may recover in accordance with Rate Schedule 10 of the ISO OATT
the costs incurred with respect to the implementation of the portion of an
Interregional Transmission Project selected by the ISO in the CSPP that is
allocated to the NYISO region pursuant to Section 31.5.7 of Attachment Y of the
ISO OATT.
31.5.7
Cost Allocation for Eligible Interregional Transmission Projects
31.5.7.1 Costs of Approved Interregional Transmission Projects
The cost allocation methodology reflected in this Section 31.5.7.1 shall be referred to as
the “Northeastern Interregional Cost Allocation Methodology” (or “NICAM”), and shall not be
modified without the mutual consent of the Section 205 rights holders in each region.
The costs of Interregional Transmission Projects, as defined in the Interregional Planning
Protocol, evaluated under the Interregional Planning Protocol and selected by ISO-NE, PJM and
the ISO in their regional transmission plans for purposes of cost allocation under their respective
tariffs shall, when applicable, be allocated to the ISO-NE region, PJM region and the ISO region
in accordance with the cost allocation principles of FERC Order No. 1000, as follows:
(a)
To be eligible for interregional cost allocation, an Interregional Transmission
Project must be selected in the regional transmission plan for purposes of cost allocation in each
of the transmission planning regions in which the transmission project is proposed to be located,
pursuant to agreements and tariffs on file at FERC for each region. With respect to Interregional
Transmission Projects and other transmission projects involving the ISO and PJM, the cost
allocation of such projects shall be in accordance with the Joint Operating Agreement (“JOA”)
among and between the ISO and PJM. With respect to Interregional Transmission Projects and
other transmission projects involving the ISO and ISO-NE, the cost allocation for such projects
shall be in accordance with this Section 31.5.7 of Attachment Y of the NYISO Open Access
Transmission Tariff and with the respective tariffs of ISO-NE.
(b)
The share of the costs of an Interregional Transmission Project allocated to a
region will be determined by the ratio of the present value of the estimated costs of such region’s
displaced regional transmission project to the total of the present values of the estimated costs of
the displaced regional transmission projects in all regions that have selected the Interregional
Transmission Project in their regional transmission plans.
(i)
The present values of the estimated costs of each region’s displaced regional
transmission project shall be based on a common base date that will be the
beginning of the calendar month of the cost allocation analysis for the subject
Interregional Transmission Project (the “Base Date”).
(ii)
In order to perform the analysis in this Section 31.5.7.1(b), the estimated cost of
the displaced regional transmission projects shall specify the year’s dollars in
which those estimates are provided.
(iii)
The present value analysis for all displaced regional transmission projects shall
use a common discount rate. The regions having displaced projects will mutually
agree, in consultation with their respective transmission owners, and for purposes
of the ISO, its other stakeholders, on the discount rate to be used for the present
value analysis.
(iv)
For the purpose of this allocation, cost estimates shall use comparable cost
estimating procedures. In the Interregional Planning Stakeholder Advisory
Committee review process, the regions having displaced projects will review and
determine, in consultation with their respective transmission owners, and for
purposes of the NYISO, its other stakeholders, that reasonably comparable
estimating procedures have been used prior to applying this cost allocation.
(c)
No cost shall be allocated to a region that has not selected the Interregional
Transmission Project in its regional transmission plan.
(d)
When a portion of an Interregional Transmission Project evaluated under the
Interregional Planning Protocol is included by a region (Region 1) in its regional transmission
plan but there is no regional need or displaced regional transmission project in Region 1, and the
neighboring region (Region 2) has a regional need or displaced regional project for the
Interregional Transmission Project and selects the Interregional Transmission Project in its
regional transmission plan, all of the costs of the Interregional Transmission Project shall be
allocated to Region 2 in accordance with the NICAM and none of the costs shall be allocated to
Region 1. However, Region 1 may voluntarily agree, with the mutual consent of the Section 205
rights holders in the other affected region(s) (including the Long Island Power Authority and the
New York Power Authority in the NYISO region) to use an alternative cost allocation method
filed with and accepted by the Commission.
(e)
The portion of the costs allocated to a region pursuant to the NICAM shall be
further allocated to that region’s transmission customers pursuant to the applicable provisions of
the region’s FERC-filed documents and agreements, for the ISO in accordance with Section
31.5.1.7 of Attachment Y of the ISO OATT.
(f)
The following example illustrates the cost allocation for such an Interregional
Transmission Project:
A cost allocation analysis of the costs of Interregional Transmission Project Z is to be
performed during a given month establishing the beginning of that month as the Base
Date.
Region A has identified a reliability need in its region and has selected a transmission
project (Project X) as the preferred solution in its regional plan. The estimated cost of
Project X is: Cost (X), provided in a given year’s dollars. The number of years from
the Base Date to the year associated with the cost estimate of Project (X) is: N(X).
Region B has identified a reliability need in its region and has selected a transmission
project (Project Y) as the preferred solution in its Regional Plan. The estimated cost
of Project Y is: Cost (Y), provided in a given year’s dollars. The number of years
from the Base Date to the year associated with the cost estimate of Project (Y) is:
N(Y).
Regions A and B, through the interregional planning process have determined that an
Interregional Transmission Project (Project Z) will address the reliability needs in
both regions more efficiently and cost-effectively than the separate regional projects.
The estimated cost of Project Z is: Cost (Z). Regions A and B have each determined
that Interregional Transmission Project Z is the preferred solution to their reliability
needs and have adopted that Interregional Transmission Project in their respective
regional plans in lieu of Projects X and Y respectively. If Regions A and B have
agreed to bear the costs of upgrades in other affected transmission planning regions,
these costs will be considered part of Cost (Z).
The discount rate used for all displaced regional transmission projects is: D
Based on the foregoing assumptions, the following formulas will be used:
Present Value of Cost (X) = PV Cost (X) = Cost (X) / (1+D)N(X)
Present Value of Cost (Y) = PV Cost (Y) = Cost (Y) / (1+D)N(Y)
Cost Allocation to Region A = Cost (Z) x PV Cost (X)/[PV Cost (X) + PV
Cost (Y)]
Cost Allocation to Region B = Cost (Z) x PV Cost (Y)/[PV Cost (X) + PV
Cost (Y)]
Applying those formulas, if:
Cost (X) = $60 Million and N(X) = 8.25 years
Cost (Y) = $40 Million and N(Y) = 4.50 years
Cost (Z) = $80 Million
D = 7.5% per year
Then:
PV Cost (X) = 60/(1+0.075) 8.25 = 33.039 Million
PV Cost (Y) = 40/(1+0.075)4.50
= 28.888 Million
Cost Allocation to Region A = $80 x 33.039/(33.039 + 28.888) = $42,681 Million
Cost Allocation to Region B = $80 x 28.888/(33.039+28.888) = $37.319 Million
31.5.7.2 Other Cost Allocation Arrangements
(a)
Except as provided in Section 31.5.7.2(b), the NICAM is the exclusive means by
which any costs of an Interregional Transmission Project may be allocated between or among
PJM, the ISO, and ISO-NE.
(b)
Nothing in the FERC-filed documents of ISO-NE, the ISO or PJM shall preclude
agreement by entities with cost allocation rights under Section 205 of the Federal Power Act for
their respective regions (including the Long Island Power Authority and the New York Power
Authority in the ISO region) to enter into separate agreements to allocate the cost-of
Interregional Transmission Projects proposed to be located in their regions as an alternative to
the NICAM, or other transmission projects identified pursuant to assessments and studies
conducted pursuant to Section 6 of the Interregional Planning Protocol. Such other cost-
allocation methodologies must be approved in each region pursuant to the Commission-approved
rules in each region, filed with and accepted by the Commission, and shall apply only to the
region's share of the costs of an Interregional Transmission Project or other transmission projects
pursuant to Section 6 of the Interregional Planning Protocol, as applicable.
31.5.7.3 Filing Rights
Nothing in this Section 31.5.7 will convey, expand, limit or otherwise alter any rights of
ISO-NE, the ISO, PJM, each region’s transmission owners, market participants, or other entities
to submit filings under Section 205 of the Federal Power Act regarding interregional cost
allocation or any other matter.
Where applicable, the regions have been authorized by entities that have cost allocation
rights for their respective regions to implement the provisions of this Section 31.5.7.
31.5.7.4. Merchant Transmission and Individual Transmission Owner Projects
Nothing in this Section 31.5.7 shall preclude the development of Interregional
Transmission Projects that are funded solely by merchant transmission developers or by
individual transmission owners.
31.5.7.5 Consequences to Other Regions from Regional or Interregional
Transmission Projects
Except as provided herein in Sections 31.5.7.1 and 31.5.7.2, or where cost responsibility
is expressly assumed by ISO-NE, the ISO or PJM in other documents, agreements or tariffs on
file with FERC, neither the ISO-NE region, the ISO region nor the PJM region shall be
responsible for compensating another region or each other for required upgrades or for any other
consequences in another planning region associated with regional or interregional transmission
facilities, including but not limited to, transmission projects identified pursuant to Section 6 of
the Interregional Planning Protocol and Interregional Transmission Projects identified pursuant
to Section 7 of the Interregional Planning Protocol.
APPENDIX A - REPORTING OF HISTORIC AND PROJECTED CONGESTION
1.0
General
As part of its CSPP, the ISO will prepare summaries and detailed analysis of historic and
projected congestion across the NYS Transmission System. This will include analysis to identify
the significant causes of historic congestion in an effort to help Market Participants and other
interested parties distinguish persistent and addressable congestion from congestion that results
from one time events or transient adjustments in operating procedures that may or may not recur.
This information will assist Market Participants and other stakeholders to make appropriately
informed decisions.
2.0
Definition of Cost of Congestion
The ISO will report the cost of congestion as the change in bid production costs that
results from transmission congestion. The following elements of congestion-related costs also
will be reported: (i) impact on load payments; (ii) impact on generator payments; and
(iii) hedged and unhedged congestion payments.
The determination of the change in bid production costs and the other elements of
congestion will be based upon the difference in costs between the actual constrained system
prices computed in the ISO’s Day-Ahead Market and a simulation of an unconstrained system.
The simulation shall be developed by the use of the PROBE model approved by the ISO
Operating Committee on January 22, 2004 or by such other software as may provide the required
congestion information.
3.0
Analysis
Each RNA will include the ISO’s summaries and detailed analysis of the prior year’s
congestion across the NYS Transmission System. The ISO’s analysis will identify the
significant causes of the historic congestion.
Each study of projected congestion for economic planning will include the results of the
ISO’s analysis conducted in accordance with Section 31.3.1 of this Attachment Y. The ISO’s
analysis will identify the significant causes of the projected congestion.
4.0
Detailed Cause Analysis for Unusual Events
The ISO will perform an analysis to identify unusual events causing significant
congestion levels. Such analysis will include the following elements: (i) identification of major
transmission or generation outages; and (ii) quantification of the market impact of relieving
historic constraints.
Some of the information necessary to this analysis may constitute critical energy
infrastructure information and will need to be handled with appropriate confidentiality
limitations to protect national security interests.
5.0
Summary Reports
The ISO will prepare various reports of historic and projected congestion costs. Historic
congestion reports will be based upon the actual congestion data from the ISO Day-Ahead
Market, and will include summaries, aggregated by month and calendar year, such as: (i) NYCA;
(ii) by zone; (iii) by contingency in rank order; (iv) by constraint in rank order; (v) total dollars;
and (vi) number of hours. Results of projected congestion studies conducted pursuant to Section
31.3.1 of this Attachment Y will include summaries of selected additional metrics and scenarios.
These reports will be based upon the foregoing definitions of congestion.
APPENDIX B - PROCEDURE FOR FORECASTING THE NET REDUCTIONS IN
TCC REVENUES THAT WOULD RESULT FROM A PROPOSED
PROJECT
For the purpose of determining the allocation of costs associated with a proposed project as
described in Section 31.5.4.4 of this Attachment Y, the ISO shall use the procedure described herein
to forecast the net reductions in TCC revenues allocated to Load in each Load Zone as a result of a
proposed project.
Definitions
The following definitions will apply to this appendix:
Pre-CARIS Centralized TCC Auction: The last Centralized TCC Auction that had been completed
as of the date the input assumptions were determined for the CARIS in which the Project was
identified as a candidate for development under the provisions of this Attachment Y.
Project: The proposed transmission project for which the evaluation of the net benefits forecasted
for Load in each Load Zone, as described in Section 31.5.4.4.2 of this Attachment Y, is being
performed.
TCC Revenue Factor: A factor that is intended to reflect the expected ratio of (1) revenue realized in
the TCC auction from the sale of a TCC to (2) the Congestion Rents that a purchaser of that TCC
would expect to realize. The value to be used for the TCC Revenue Factor shall be stated in the ISO
Procedures.
Steps 1 Through 6 of the Procedure
For each Project, the ISO will perform Steps 1 through 6 of this procedure twice for each of the ten
(10) years following the proposed commercial operation date of the Project: once under the
assumption that the Project is in place in each of those years, and once under the assumption that the
Project is not in place in each of those years.
Forecasting the Value of Grandfathered TCCs and TCC Auction Revenue
Step 1. The ISO shall forecast Congestion Rents collected on the New York electricity system in
each year, which shall be equal to:
(a) the product of:
(i) the forecasted Congestion Component of the Day-Ahead LBMP for each hour at
each Load Zone or Proxy Generator Bus and
(ii) forecasted withdrawals scheduled in that hour in that Load Zone or Proxy
Generator Bus,
summed over all locations and over all hours in that year, minus:
(b) the product of:
(i) the forecasted Congestion Component of the Day-Ahead LBMP for each hour at
each Generator bus or Proxy Generator Bus and
(ii) forecasted injections scheduled in that hour at that Generator bus or Proxy
Generator Bus,
summed over all locations and over all hours in that year.
Step 2. The ISO shall forecast:
(a) payments in each year associated with any Incremental TCCs that the ISO projects would
be awarded in conjunction with that Project (which will be zero for the calculation that is
performed under the assumption that the Project is not in place);
(b) payments in each year associated with any Incremental TCCs that the ISO has awarded,
or that the ISO projects it would award, in conjunction with other projects that have entered
commercial operation or are expected to enter commercial operation before the Project enters
commercial operation; and
(c) payments that would be made to holders of Grandfathered Rights and imputed payments
that would be made to the Primary Holders of Grandfathered TCCs that would be in effect in
each year, under the following assumptions:
(i) all Grandfathered Rights and Grandfathered TCCs expire at their stated expiration
dates;
(ii) imputed payments to holders of Grandfathered Rights are equal to the payments
that would be made to the Primary Holder of a TCC with the same Point of Injection
and Point of Withdrawal as that Grandfathered Right; and
(iii) in cases where a Grandfathered TCC is listed in Table 1 of Attachment M of the
ISO OATT, the number of those TCCs held by their Primary Holders shall be set to
the number of such TCCs remaining at the conclusion of the ETCNL reduction
procedure conducted before the Pre-CARIS Centralized TCC Auction.
Step 3. The ISO shall forecast TCC auction revenues for each year by subtracting:
(a) the forecasted payments calculated for that year in Steps 2(a), 2(b) and 2(c) of this
procedure
from:
(b) the forecasted Congestion Rents calculated for that year in Step 1 of this procedure, and
multiplying the difference by the TCC Revenue Factor.
Forecasting the Allocation of TCC Auction Revenues Among the Transmission Owners
Step 4. The ISO shall forecast the following:
(a) payments in each year to the Primary Holders of Original Residual TCCs and
(b) payments in each year to the Primary Holders of TCCs that correspond to the amount of
ETCNL remaining at the conclusion of the ETCNL reduction procedure conducted before the
Pre-CARIS Centralized TCC Auction,
and multiply each by the TCC Revenue Factor to determine the forecasted payments to the Primary
Holders of Original Residual TCCs and the Transmission Owners that have been allocated ETCNL.
Step 5. The ISO shall forecast residual auction revenues for each year by subtracting:
(a) the sum of the forecasted payments for each year to the Primary Holders of Original
Residual TCCs and the Transmission Owners that have been allocated ETCNL, calculated in
Step 4 of this procedure
from:
(b) forecasted TCC auction revenues for that year calculated in Step 3 of this procedure.
Step 6. The ISO shall forecast each Transmission Owner’s share of residual auction revenue for
each year by multiplying:
(a) the forecast of residual auction revenue calculated in Step 5 of this procedure and
(b) the ratio of:
(i) the amount of residual auction revenue allocated to that Transmission Owner in
the Pre-CARIS Centralized TCC Auction to
(ii) the total amount of residual auction revenue allocated in the Pre-CARIS
Centralized TCC Auction.
Steps 7 Through 10 of the Procedure
The ISO will perform Steps 7 through 10 of this procedure once for each of the ten (10) years
following the proposed commercial operation date of the Project, using the results of the preceding
calculations performed both under the assumption that the Project is in place in each of those years,
and under the assumption that the Project is not in place in each of those years.
Forecasting the Impact of the Project on TSC Offsets and the NTAC Offset
Step 7. The ISO shall calculate the forecasted net impact of the Project on the TSC offset for each
megawatt-hour of electricity consumed by Load in each Transmission District (other than the NYPA
Transmission District) in each year by:
(a) summing the following, each forecasted for that Transmission District for that year under
the assumption that the Project is in place:
(i) forecasted Congestion Rents associated with any Incremental TCCs that the ISO
has awarded, or that the ISO projects it would award, as calculated in Step 2(b) of this
procedure, in conjunction with other projects that have entered commercial operation
or are expected to enter commercial operation before the Project enters commercial
operation, if those Congestion Rents would affect the TSC for that Transmission
District;
(ii) forecasted Congestion Rents associated with any Grandfathered TCCs and
forecasted imputed Congestion Rents associated with any Grandfathered Rights held
by the Transmission Owner serving that Transmission District that would be paid to
that Transmission Owner for that year, as calculated in Step 2(c) of this procedure, if
those Congestion Rents would affect the TSC for that Transmission District;
(iii) the payments that are forecasted to be made for that year to the Primary Holders
of Original Residual TCCs and ETCNL that have been allocated to the Transmission
Owner serving that Transmission District, as calculated in Step 4 of this procedure;
and
(iv) that Transmission District’s forecasted share of residual auction revenues for that
year, as calculated in Step 6 of this procedure for the Transmission Owner serving
that Transmission District;
(b) subtracting the sum of items (i) through (iv) above, each forecasted for that Transmission
District for that year under the assumption that the Project is not in place; and
(c) dividing this difference by the amount of Load forecasted to be served in that
Transmission District in that year, stated in terms of megawatt-hours, net of any Load served
by municipally owned utilities that is not subject to the TSC.
Step 8. The ISO shall calculate the forecasted net impact of the Project on the NTAC offset for each
megawatt-hour of electricity consumed by Load in each year by:
(a) summing the following, each forecasted for that year under the assumption that the
Project is in place:
(i) forecasted Congestion Rents associated with any Incremental TCCs that the ISO
has awarded, or that the ISO projects it would award, as calculated in Step 2(b) of this
procedure, in conjunction with other projects that have entered commercial operation
or are expected to enter commercial operation before the Project enters commercial
operation, if those Congestion Rents would affect the NTAC;
(ii) forecasted Congestion Rents associated with any Grandfathered TCCs and
forecasted imputed Congestion Rents associated with any Grandfathered Rights held
by NYPA that would be paid to NYPA for that year, as calculated in Step 2(c) of this
procedure, if those Congestion Rents would affect the NTAC;
(iii) the payments that are forecasted to be made for that year to NYPA in association
with Original Residual TCCs allocated to NYPA, as calculated in Step 4 of this
procedure; and
(iv) NYPA’s forecasted share of residual auction revenues for that year, as calculated
in Step 6 of this procedure;
(b) subtracting the sum of items (i) through (iv) above, each forecasted for that year under the
assumption that the Project is not in place; and
(c) dividing this difference by the amount of Load expected to be served in the NYCA in that
year, stated in terms of megawatt-hours, net of any Load served by municipally owned
utilities that is not subject to the NTAC.
Forecasting the Net Impact of the Project on TCC Revenues Allocated to Load in Each Zone
Step 9. The ISO shall calculate the forecasted net impact of the Project in each year in each Load
Zone on payments made in conjunction with TCCs and Grandfathered Rights that benefit Load but
which do not affect TSCs or the NTAC, which shall be the sum of:
(a) Forecasted Congestion Rents paid or imputed to municipally owned utilities serving Load
in that Load Zone that own Grandfathered Rights or Grandfathered TCCs that were not
included in the calculation of the TSC offset in Step 7(a)(ii) of this procedure or the NTAC
offset in Step 8(a)(ii) of this procedure, which the ISO shall calculate by:
(i) summing forecasted Congestion Rents that any such municipally owned utilities
serving Load in that Load Zone would be paid for that year in association with any
such Grandfathered TCCs and any forecasted imputed Congestion Rents that such a
municipally owned utility would be paid for that year in association with any such
Grandfathered Rights, as calculated in Step 2(c) of this procedure under the
assumption that the Project is in place; and
(ii) subtracting forecasted Congestion Rents that any such municipally owned utilities
would be paid for that year in association with any such Grandfathered TCCs, and
any forecasted imputed Congestion Rents that such a municipally owned utility
would be paid for that year in association with any such Grandfathered Rights, as
calculated in Step 2(c) of this procedure under the assumption that the Project is not
in place.
(b) Forecasted Congestion Rents collected from Incremental TCCs awarded in conjunction
with projects that were previously funded through this procedure, if those Congestion Rents
are used to reduce the amount that Load in that Load Zone must pay to fund such projects,
which the ISO shall calculate by:
(i) summing forecasted Congestion Rents that would be collected for that year in
association with any such Incremental TCCs, as calculated in Step 2(b) of this
procedure under the assumption that the Project is in place; and
(ii) subtracting forecasted Congestion Rents that would be collected for that year in
association with any such Incremental TCCs, as calculated in Step 2(b) of this
procedure under the assumption that the Project is not in place.
Step 10. The ISO shall calculate the forecasted net reductions in TCC revenues allocated to Load in
each Load Zone as a result of a proposed Project by summing the following:
(a) the product of:
(i) the forecasted net impact of the Project on the TSC offset for each megawatt-hour
of electricity consumed by Load, as calculated for each Transmission District (other
than the NYPA Transmission District) in Step 7 of this procedure; and
(ii) the number of megawatt-hours of energy that are forecasted to be consumed by
Load in that year, in the portion of that Transmission District that is in that Load
Zone, for Load that is subject to the TSC;
summed over all Transmission Districts;
(b) the product of:
(i) the forecasted net impact of the Project on the NTAC offset for each megawatt-
hour of electricity consumed by Load, as calculated in Step 8 of this procedure; and
(ii) the number of megawatt-hours of energy that are forecasted to be consumed by
Load in that year in that Load Zone, for Load that is subject to the NTAC; and
(c) the forecasted net impact of the Project on payments and imputed payments made in
conjunction with TCCs and Grandfathered Rights that benefit Load but which do not affect
TSCs or the NTAC, as calculated in Step 9 of this procedure.
Additional Notes Concerning the Procedure
For the purposes of Steps 2(c) and 4(b) of this procedure, the ISO will utilize the currently effective
version of Attachment L of the ISO OATT to identify Existing Transmission Agreements and
Existing Transmission Capacity for Native Load.
Each Transmission Owner, other than NYPA, will inform the ISO of any Grandfathered Rights and
Grandfathered TCCs it holds whose Congestion Rents should be taken into account in Step 7 of this
procedure because those Congestion Rents affect its TSC.
NYPA will inform the ISO of any Grandfathered Rights and Grandfathered TCCs it holds whose
Congestion Rents should be taken into account in Step 8 of this procedure because those Congestion
Rents affect the NTAC.
APPENDIX C - RELIABILITY PLANNING PROCESS DEVELOPMENT
AGREEMENT
TABLE OF CONTENTS
Page
ARTICLE 1.
DEFINITIONS
2
ARTICLE 2.
EFFECTIVE DATE AND TERM
6
2.1.
Effective Date
6
2.2.
Filing
7
2.3.
Term of Agreement
7
ARTICLE 3.
TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
7
3.1.
Application for Required Authorizations and Approvals
7
3.2.
Development and Construction of Transmission Project
7
3.3.
Milestones
8
3.4.
Modifications to Transmission Project
9
3.5.
Billing and Payment
10
3.6.
Project Monitoring
10
3.7.
Right to Inspect
10
3.8.
Exclusive Responsibility of Developer
10
3.9.
Subcontractors
11
3.10.
No Services or Products Under NYISO Tariffs
11
3.11.
Tax Status
11
ARTICLE 4.
COORDINATION WITH THIRD PARTIES
11
4.1.
Interconnection Requirements for Transmission Project
11
4.2.
Interconnection with Affected System
12
4.3.
Coordination of Interregional Transmission Project
12
ARTICLE 5.
OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
12
ARTICLE 6.
INSURANCE
13
ARTICLE 7.
BREACH AND DEFAULT
15
7.1.
Breach
15
7.2.
Default
15
7.3.
Remedies
16
ARTICLE 8.
TERMINATION
16
8.1.
Termination by the NYISO
16
8.2.
Reporting of Inability to Comply with Provisions of Agreement
17
8.3.
Transmission Project Transfer Rights Upon Termination
17
ARTICLE 9.
LIABILITY AND INDEMNIFICATION
18
9.1.
Liability
18
9.2.
Indemnity
18
ARTICLE 10. ASSIGNMENT
18
ARTICLE 11. INFORMATION EXCHANGE AND CONFIDENTIALITY
19
11.1.
Information Access
19
11.2.
Confidentiality
20
ARTICLE 12. REPRESENTATIONS, WARRANTIES AND COVENANTS
20
12.1.
General
20
12.2.
Good Standing
20
12.3.
Authority
21
12.4.
No Conflict
21
12.5.
Consent and Approval
21
12.6.
Compliance with All Applicable Laws and Regulations
21
ARTICLE 13. DISPUTE RESOLUTION
21
ARTICLE 14. SURVIVAL
21
ARTICLE 15. MISCELLANEOUS
22
15.1.
Notices
22
15.2.
Entire Agreement
22
15.3.
Cost Recovery
22
15.4.
Binding Effect
22
15.5.
Force Majeure
23
15.6.
Disclaimer
23
15.7.
No NYISO Liability for Review or Approval of Developer Materials
23
15.8.
Amendment
24
15.9.
No Third Party Beneficiaries
24
15.10.
Waiver
24
15.11.
Rules of Interpretation
24
15.12.
Severability
25
15.13.
Multiple Counterparts
25
15.14.
No Partnership
25
15.15.
Headings
25
15.16.
Governing Law
25
15.17.
Jurisdiction and Venue
25
Appendices
THIS DEVELOPMENT AGREEMENT (“Agreement”) is made and entered into this ___ day
of ______ 20__, by and between _______________, a [corporate description] organized and
existing under the laws of the State/Commonwealth of _________ (“Developer”), and the New
York Independent System Operator, Inc., a not-for-profit corporation organized and existing
under the laws of the State of New York (“NYISO”). Developer or NYISO each may be referred
to as a “Party” or collectively referred to as the “Parties.”
RECITALS
WHEREAS, the NYISO administers the Comprehensive System Planning Process (“CSPP”) in
the New York Control Area pursuant to the terms set forth in Attachment Y of the NYISO’s
Open Access Transmission Tariff (“OATT”), as accepted by the Federal Energy Regulatory
Commission (“FERC”);
WHEREAS, as part of the CSPP, the NYISO administers a reliability planning process pursuant
to which the reliability of the New York State Bulk Power Transmission Facilities is assessed
over a ten-year Study Period; Reliability Need(s) that may arise over this period are identified;
proposed solutions to the identified need(s) are solicited by the NYISO; and the more efficient or
cost-effective transmission solution to satisfy the identified need(s) is selected by the NYISO and
reported in the NYISO’s Comprehensive Reliability Plan report;
[Alternative 1 - To include if the Developer’s regulated transmission solution was selected as
the more efficient or cost effective solution:
WHEREAS, the Developer has proposed a regulated transmission solution to satisfy an
identified Reliability Need (“Transmission Project”);
WHEREAS, the NYISO has selected the Developer’s Transmission Project as the more efficient
or cost-effective transmission solution to satisfy an identified Reliability Need and has directed
the Developer to proceed with the Transmission Project pursuant to Section 31.2.8.1 of
Attachment Y of the OATT;]
[Alternative 2 - To include if the NYISO triggers a Developer’s regulated backstop
transmission solution that has not been selected pursuant to Sections 31.2.8.1.2, 31.2.8.1.3, or
31.2.8.1.4:
WHEREAS, the Developer has proposed a regulated backstop transmission solution to satisfy
an identified Reliability Need (“Transmission Project”);
WHEREAS, the NYISO has triggered the Transmission Project to proceed pursuant to Sections
31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4;]
[Alternative 3 - To include if a Transmission Owner agrees to complete an alternative selected
transmission solution pursuant to Section 31.2.10.1.3:
WHEREAS, the Developer has agreed to step-in to complete a regulated transmission project to
satisfy an identified Reliability Need (“Transmission Project”) pursuant to Section 31.2.10.1.3 of
Attachment Y of the OATT;]
WHEREAS, the Developer has agreed to obtain the required authorizations and approvals from
Governmental Authorities needed for the Transmission Project, to develop and construct the
Transmission Project, and to abide by the related requirements in Attachment Y of the OATT,
the ISO Tariffs, and the ISO Procedures;
WHEREAS, the Developer and the NYISO have agreed to enter into this Agreement pursuant to
Section 31.2.8.1.6 of Attachment Y of the OATT for the purpose of ensuring that the
Transmission Project will be constructed and in service in time to satisfy the Reliability Need
(“Required Project In-Service Date”); and
WHEREAS, the Developer has agreed to construct, and the NYISO has requested that the
Developer proceed with construction of, the Transmission Project to address the identified
Reliability Need by the Required Project In-Service Date.
NOW, THEREFORE, in consideration of and subject to the mutual covenants contained herein,
it is agreed:
ARTICLE 1. DEFINITIONS
Whenever used in this Agreement with initial capitalization, the following terms shall have the
meanings specified in this Article 1. Terms used in this Agreement with initial capitalization that
are not defined in this Article 1 shall have the meanings specified in Section 31.1.1 of
Attachment Y of the OATT or, if not therein, in Article 1 of the OATT.
Advisory Milestones shall mean the milestones set forth in the Development Schedule in
Attachment C to this Agreement that are not Critical Path Milestones.
Affected System Operator shall mean any Affected System Operator(s) identified in connection
with the Transmission Project pursuant to Attachment P of the ISO OATT.
Applicable Laws and Regulations shall mean: (i) all duly promulgated applicable federal, state
and local laws, regulations, rules, ordinances, codes, decrees, judgments, directives, or judicial or
administrative orders, permits and other duly authorized actions of any Governmental Authority,
and (ii) all applicable requirements of the ISO Tariffs, ISO Procedures, and ISO Related
Agreements.
Applicable Reliability Organizations shall mean the NERC, the NPCC, and the NYSRC.
Applicable Reliability Requirements shall mean the requirements, criteria, rules, standards,
and guidelines, as they may be amended and modified and in effect from time to time, of: (i) the
Applicable Reliability Organizations, (ii) the Connecting Transmission Owner(s), (iii) [to insert
the name(s) of any other Transmission Owners or developers whose transmission facilities the
NYISO has determined may be impacted by the Transmission Project], and (iv) any Affected
System Operator; provided, however, that no Party shall waive its right to challenge the
applicability or validity of any requirement, criteria, rule, standard, or guideline as applied to it in
the context of this Agreement.
Breach shall have the meaning set forth in Article 7.1 of this Agreement.
Breaching Party shall mean a Party that is in Breach of this Agreement.
Business Day shall mean Monday through Friday, excluding federal holidays.
Calendar Day shall mean any day including Saturday, Sunday, or a federal holiday.
Change of Control shall mean a change in ownership of more than 50% of the membership or
ownership interests or other voting securities of the Developer to a third party in one or more
related transactions, or any other transaction that has the effect of transferring control of the
Developer to a third party.
Confidential Information shall mean any information that is defined as confidential by Article
11.2.
Connecting Transmission Owner shall be the Connecting Transmission Owner(s) identified in
connection with the Transmission Project pursuant to Attachment P of the ISO OATT.
Critical Path Milestones shall mean the milestones identified as such in the Development
Schedule in Attachment C to this Agreement that must be met for the Transmission Project to be
constructed and operating by the Required Project In-Service Date.
Default shall mean the failure of a Party in Breach of this Agreement to cure such Breach in
accordance with Article 7.2 of this Agreement.
Developer shall have the meaning set forth in the introductory paragraph.
Development Schedule shall mean the schedule of Critical Path Milestones and Advisory
Milestones set forth in Appendix C to this Agreement.
Effective Date shall mean the date upon which this Agreement becomes effective as determined
in Article 2.1 of this Agreement.
FERC shall mean the Federal Energy Regulatory Commission or its successor.
Force Majeure shall mean any act of God, labor disturbance, act of the public enemy, war,
insurrection, riot, fire, storm or flood, explosion, breakage or accident to machinery or
equipment, any order, regulation or restriction imposed by governmental, military or lawfully
established civilian authorities, or any other cause beyond a Party’s control. A Force Majeure
event does not include acts of negligence or intentional wrongdoing by the Party claiming Force
Majeure.
Good Utility Practice shall mean any of the practices, methods and acts engaged in or approved
by a significant portion of the electric industry during the relevant time period, or any of the
practices, methods and acts which, in the exercise of reasonable judgment in light of the facts
known at the time the decision was made, could have been expected to accomplish the desired
result at a reasonable cost consistent with good business practice, reliability, safety and
expedition. Good Utility Practice is not intended to be limited to the optimum practice, method,
or act to the exclusion of all others, but rather to delineate acceptable practices, methods, or acts
generally accepted in the region.
Governmental Authority shall mean any federal, state, local or other governmental regulatory
or administrative agency, public authority, court, commission, department, board, or other
governmental subdivision, legislature, rulemaking board, tribunal, or other governmental
authority having jurisdiction over any of the Parties, their respective facilities, or the respective
services they provide, and exercising or entitled to exercise any administrative, executive, police,
or taxing authority or power; provided, however, that such term does not include the NYISO, the
Developer, the Connecting Transmission Owner(s), the Affected System Operator(s), or any
Affiliate thereof.
In-Service Date shall mean the date upon which the Transmission Project is energized
consistent with the provisions of the Transmission Project Interconnection Agreement and
available to provide Transmission Service under the NYISO Tariffs.
ISO/TO Agreement shall mean the Agreement Between the New York Independent System
Operator and Transmission Owners, as filed with and accepted by the Commission in Cent.
Hudson Gas & Elec. Corp., et al., 88 FERC ¶ 61,138 (1999) in Docket Nos. ER97-1523, et al.,
and as amended or supplemented from time to time, or any successor agreement thereto.
New York State Transmission System shall mean the entire New York State electrical
transmission system, which includes: (i) the Transmission Facilities Under ISO Operational
Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining
transmission facilities within the New York Control Area.
NERC shall mean the North American Electric Reliability Corporation or its successor
organization.
NPCC shall mean the Northeast Power Coordinating Council or its successor organization.
NYISO/TO Reliability Agreement shall mean the Agreement Between the New York
Independent System Operator, Inc., and the New York Transmission Owners on the
Comprehensive Planning Process for Reliability Needs, as filed with and accepted by the
Commission in New York Independent System Operator, Inc., 109 FERC ¶ 61,372 (2004) and
111 FERC ¶ 61,182 (2005) in Docket No. ER04-1144, and as amended or supplemented from
time to time, or any successor agreement thereto.
NYSRC shall mean the New York State Reliability Council or its successor organization.
OATT shall mean the NYISO’s Open Access Transmission Tariff, as filed with the
Commission, and as amended or supplemented from time to time, or any successor tariff thereto.
Party or Parties shall mean the NYISO, the Developer, or both.
Point of Interconnection shall mean the point or points at which the Developer’s Transmission
Project will interconnect to the New York State Transmission System.
Project Description shall mean the description of the Transmission Project set forth in
Appendix A to this Agreement that is consistent with the project proposed and evaluated in the
NYISO’s reliability planning process and, if applicable, selected by the NYISO Board of
Directors as the more efficient or cost-effective transmission solution to the identified Reliability
Need.
Reliability Planning Process Manual shall mean the NYISO’s manual adopted by the NYISO
stakeholder Operating Committee describing the NYISO’s procedures for implementing the
reliability planning process component of the NYISO’s Comprehensive System Planning
Process, as the manual is amended or supplemented from time to time, or any successor manual
thereto.
Required Project In-Service Date shall mean the In-Service Date by which the Transmission
Project must be constructed and operating to satisfy the Reliability Need, as specified in the
Development Schedule set forth in Appendix C to this Agreement.
Services Tariff shall mean the NYISO’s Market Administration and Control Area Services Tariff,
as filed with the Commission, and as amended or supplemented from time to time, or any
successor tariff thereto.
Significant Modification shall mean a Developer’s proposed modification to its Transmission
Project that: (i) could impair the Transmission Project’s ability to meet the identified Reliability
Need, (ii) could delay the In-Service Date of the Transmission Project beyond the Required
Project In-Service Date, or (iii) would constitute a material change to the project information
submitted by the Developer under Attachment Y of the OATT for use by the NYISO in
evaluating the Transmission Project for purposes of selecting the more efficient or cost-effective
transmission solution to meet the identified Reliability Need.
Scope of Work shall mean the description of the work required to implement the Transmission
Project as set forth in Appendix B to this Agreement. The Scope of Work shall be drawn from
the Developer’s submission of the Required Data Submission for Solutions to Reliability Needs,
which is set forth in Attachment C of the NYISO Reliability Planning Manual, as may be
updated as agreed upon by the Parties, and shall include, but not be limited to, a description of:
the acquisition of required rights-of-ways, the work associated with the licensing, design,
financing, environmental and regulatory approvals, engineering, procurement of equipment,
construction, installation, testing, and commissioning of the Transmission Project; the relevant
technical requirements, standards, and guidelines pursuant to which the work will be performed;
the major equipment and facilities to be constructed and/or installed in connection with the
Transmission Project, and the cost estimates for the work associated with the Transmission
Project.
Transmission Owner Technical Standards shall mean the technical requirements and
standards (e.g, equipment or facilities electrical and physical capabilities, design characteristics,
or construction requirements), as those requirements and standards are amended and modified and
in effect from time to time, of: (i) the Connecting Transmission Owner(s), (ii) [to insert the name(s)
of any other Transmission Owners or developers whose transmission facilities the NYISO has
determined may be impacted by the Transmission Project], and (iii) any Affected System
Operator.
Transmission Project shall mean the Developer’s regulated transmission solution that is subject
to this Agreement as described in the Project Description set forth in Appendix A to this
Agreement.
ARTICLE 2. EFFECTIVE DATE AND TERM
2.1.
Effective Date
This Agreement shall become effective on the date it has been executed by all Parties;
provided, however, if the Agreement is filed with FERC as a non-conforming or an unexecuted
agreement pursuant to Section 31.2.8.1.6 of Attachment Y of the OATT, the Agreement shall
become effective on the effective date accepted by FERC.
2.2.
Filing
If the Agreement must be filed with FERC pursuant to Section 31.2.8.1.6 of Attachment
Y of the OATT, the NYISO shall file this Agreement for acceptance with FERC within the
timeframe set forth for the filing in Section 31.2.8.1.6 of Attachment Y of the OATT. The
Developer shall cooperate in good faith with the NYISO with respect to such filing and provide
any information requested by the NYISO to comply with Applicable Laws and Regulations.
Any Confidential Information shall be treated in accordance with Article 11.2 of this Agreement.
2.3.
Term of Agreement
Subject to the termination provisions in Article 8 of this Agreement, this Agreement shall
remain in effect from the Effective Date until: (i) the Developer executes an operating agreement
with the NYISO, and (ii) the Transmission Project: (A) has been completed in accordance with
the terms and conditions of this Agreement, and (B) is in-service; provided, however, that the
terms of this Agreement shall continue in effect to the extent provided in Article 14 of this
Agreement.
ARTICLE 3. TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
3.1.
Application for Required Authorizations and Approvals
The Developer shall timely seek and obtain all authorizations and approvals from
Governmental Authorities required to develop, construct, and operate the Transmission Project
by the Required Project In-Service Date. The required authorizations and approvals shall be
listed in the Scope of Work in Appendix B to this Agreement. The Developer shall seek and
obtain the required authorizations and approvals in accordance with the milestones set forth in
the Development Schedule in Appendix C to this Agreement. The milestones for obtaining the
required authorizations and approvals shall be included in the Development Schedule as Critical
Path Milestones and Advisory Milestones, as designated by the Parties under Article 3.3.1. The
Developer shall notify the NYISO in accordance with the notice requirements in Article 3.3 if it
has reason to believe that it may be unable to timely obtain or is denied an approval or
authorization by a Governmental Authority required for the development, construction, or
operation of the Transmission Project, or if such approval or authorization is withdrawn or
modified.
3.2.
Development and Construction of Transmission Project
The Developer shall design, engineer, procure, install, construct, test and commission the
Transmission Project in accordance with: (i) the terms of this Agreement, including, but not
limited to, the Project Description in Appendix A to this Agreement, the Scope of Work in
Appendix B to this Agreement, and the Development Schedule in Appendix C to this
Agreement; (ii) Applicable Reliability Requirements; (iii) Applicable Laws and Regulations; (iv)
Good Utility Practice; (v) the Transmission Owner Technical Standards, and (vi) any
interconnection agreement(s) entered into by and among the NYISO, Developer, and Connecting
Transmission Owner(s) for the Transmission Project to interconnect to the New York State
Transmission System.
3.3.
Milestones
3.3.1.
The NYISO shall provide the Developer with the Required Project In-Service Date that is
set forth in the Comprehensive Reliability Plan report or the updated Comprehensive
Reliability Plan report, as applicable, in accordance with Sections 31.2.7 and 31.2.7.3 of
Attachment Y of the OATT. Prior to executing and/or filing this Agreement with FERC,
the NYISO and the Developer shall agree to the Critical Path Milestones and Advisory
Milestones set forth in the Development Schedule in Appendix C to this Agreement for
the development, construction, and operation of the Transmission Project by the Required
Project In-Service Date in accordance with Section 31.2.8.1.6 of Attachment Y of the
OATT; provided that any such milestone for the Transmission Project that requires action
by a Connecting Transmission Owner or an Affected System Operator to complete must
be included as an Advisory Milestone.
3.3.2.
The Developer shall meet the Critical Path Milestones in accordance with the
Development Schedule set forth in Appendix C to this Agreement. The Developer’s
inability or failure to meet a Critical Path Milestone specified in the Development
Schedule, as such Critical Path Milestone may be amended with the agreement of the
NYISO under this Article 3.3, shall constitute a Breach of this Agreement under Article
7.1.
3.3.3.
The Developer shall notify the NYISO thirty (30) Calendar Days prior to the date of each
Critical Path Milestone specified in the Development Schedule whether, to the best of its
knowledge, it expects to meet the Critical Path Milestone by the specified date; provided,
however, that notwithstanding this requirement:
(i) the Developer shall notify the NYISO as soon as reasonably practicable, and no later
than fifteen (15) Calendar Days, following the Developer’s discovery of a potential delay
in meeting a Critical Path Milestone, including a delay caused by a Force Majeure event;
and
(ii) the NYISO may request in writing at any time, and Developer shall submit to the
NYISO within five (5) Business Days of the request, a written response indicating
whether the Developer will meet, or has met, a Critical Path Milestone and providing all
required supporting documentation for its response.
3.3.4.
The Developer shall not make a change to a Critical Path Milestone without the prior
written consent of the NYISO. To request a change to a Critical Path Milestone, the
Developer must: (i) inform the NYISO in writing of the proposed change to the Critical
Path Milestone and the reason for the change, including the occurrence of a Force
Majeure event in accordance with Section 15.5, (ii) submit to the NYISO a revised
Development Schedule containing any necessary changes to Critical Path Milestones and
Advisory Milestones that provide for the Transmission Project to be completed and
achieve its In-Service Date no later than the Required Project In-Service Date, and (iii)
submit a notarized officer’s certificate certifying the Developer’s capability to complete
the Transmission Project in accordance with the modified schedule. If the Developer: (i)
must notify the NYISO of a potential delay in meeting a Critical Path Milestone in
accordance with one of the notification requirements in Section 3.3.3 or (ii) is requesting
a change to a Critical Path Milestone to cure a Breach in Section 7.2, the Developer shall
submit any request to change the impacted Critical Path Milestone(s) within the relevant
notification timeframe set forth in Section 3.3.3 or the cure period set forth in Section 7.2,
as applicable. The NYISO will promptly review the Developer’s requested change. The
Developer shall provide the NYISO with all required information to assist the NYISO in
making its determination and shall be responsible for the costs of any study work the
NYISO performs in making its determination. If the Developer demonstrates to the
NYISO’s satisfaction that the delay in meeting a Critical Path Milestone will not delay
the Transmission Project’s In-Service Date beyond the Required Project In-Service Date,
then the NYISO’s consent to extending the Critical Path Milestone date will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s written consent to a
revised Development Schedule proposed by the Developer will satisfy the amendment
requirements in Article 15.8, and the NYISO will not be required to file the revised
Development Schedule with FERC.
3.3.5. Within fifteen (15) Calendar Days of the Developer’s discovery of a potential delay in
meeting an Advisory Milestone, the Developer shall inform the NYISO of the potential
delay and describe the impact of the delay on meeting the Critical Path Milestones. The
Developer may extend an Advisory Milestone date upon informing the NYISO of such
change; provided, however, that if the change to the Advisory Milestone will delay a
Critical Path Milestone, the NYISO’s written consent to make such change is required as
described in Article 3.3.4.
3.4.
Modifications to Transmission Project
The Developer shall not make a Significant Modification to the Transmission Project
without the prior written consent of the NYISO, including, but not limited to, modifications
necessary for the Developer to obtain required approvals or authorizations from Governmental
Authorities. The NYISO’s determination regarding a Significant Modification to the
Transmission Project under this Agreement shall be separate from, and shall not replace, the
NYISO’s review and determination of material modifications to the Transmission Project under
Attachment P of the OATT. The Developer may request that the NYISO review whether a
modification to the Transmission Project would constitute a Significant Modification. The
Developer shall provide the NYISO with all required information to assist the NYISO in making
its determination regarding a Significant Modification and shall be responsible for the costs of
any study work the NYISO must perform in making its determination. If the Developer
demonstrates to the NYISO’s satisfaction that its proposed Significant Modification: (i) does not
impair the Transmission Project’s ability to satisfy the identified Reliability Need, (ii) does not
delay the In-Service Date of the Transmission Project beyond the Required Project In-Service
Date, and (iii) does not change the grounds upon which the NYISO selected the Transmission
Project as the more efficient or cost-effective transmission solution to the identified Reliability
Need (if applicable), the NYISO’s consent to the Significant Modification will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s performance of this review shall
not constitute its consent to delay the completion of any Critical Path Milestone.
3.5.
Billing and Payment
The NYISO shall charge, and the Developer shall pay, the actual costs of: (i) any study
work performed by the NYISO or its subcontractor(s) under Articles 3.3 and 3.4, or (ii) any
assessment of the Transmission Project by the NYISO or its subcontractor(s) under Article 3.7.
The NYISO will invoice Developer on a monthly basis for the expenses incurred by the NYISO
each month, including estimated subcontractor costs, computed on a time and material basis.
The Developer shall pay invoiced amounts to the NYISO within thirty (30) Calendar Days of the
NYISO’s issuance of a monthly invoice. In the event the Developer disputes an amount to be
paid, the Developer shall pay the disputed amount to the NYISO, pending resolution of the
dispute. To the extent the dispute is resolved in the Developer’s favor, the NYISO will net the
disputed amount, including interest calculated from Developer’s date of payment at rates
applicable to refunds under FERC regulations, against any current amounts due from the
Developer and pay the balance to the Developer. This Article 3.5 shall survive the termination,
expiration, or cancellation of this Agreement.
3.6.
Project Monitoring
The Developer shall provide regular status reports to the NYISO in accordance with the
monitoring requirements set forth in the Development Schedule, the Reliability Planning Process
Manual and Attachment Y of the OATT.
3.7.
Right to Inspect
Upon reasonable notice, the NYISO or its subcontractor shall have the right to inspect the
Transmission Project for the purpose of assessing the progress of the development and
construction of the Transmission Project and satisfaction of milestones. The exercise or non-
exercise by the NYISO or its subcontractor of this right shall not be construed as an endorsement
or confirmation of any element or condition of the development or construction of the
Transmission Project, or as a warranty as to the fitness, safety, desirability or reliability of the
same. Any such inspection shall take place during normal business hours, shall not interfere
with the construction of the Transmission Project and shall be subject to such reasonable safety
and procedural requirements as the Developer shall specify.
3.8.
Exclusive Responsibility of Developer
As between the Parties, the Developer shall be solely responsible for all planning, design,
engineering, procurement, construction, installation, management, operations, safety, and
compliance with Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards associated with the Transmission Project, including,
but not limited to, scheduling, meeting Critical Path Milestones and Advisory Milestones, timely
requesting review and consent to any project modifications, and obtaining all necessary permits,
siting, and other regulatory approvals. The NYISO shall have no responsibility and shall have
no liability regarding the management or supervision of the Developer’s development of the
Transmission Project or the compliance of the Developer with Applicable Laws and Regulations,
Applicable Reliability Requirements, and Transmission Owner Technical Standards. The
NYISO shall cooperate with the Developer in good faith in providing information to assist the
Developer in obtaining all approvals and authorizations from Governmental Authorities required
to develop, construct, and operate the Transmission Project by the Required Project In-Service
Date, including, if applicable, information describing the NYISO’s basis for selecting the
Transmission Project as the more efficient or cost-effective transmission solution to satisfy an
identified Reliability Need.
3.9.
Subcontractors
3.9.1. Nothing in this Agreement shall prevent a Party from using the services of any
subcontractor as it deems appropriate to perform its obligations under this Agreement;
provided, however, that each Party shall require, and shall provide in its contracts with its
subcontractors, that its subcontractors comply with all applicable terms and conditions of
this Agreement in providing such services; provided, further, that each Party shall remain
primarily liable to the other Party for the performance of such subcontractor.
3.9.2. The creation of any subcontractor relationship shall not relieve the hiring Party of any of
its obligations under this Agreement. The hiring Party shall be fully responsible to the
other Party for the acts or omissions of any subcontractor the hiring Party hires as if no
subcontract had been made.
3.10. No Services or Products Under NYISO Tariffs
This Agreement does not constitute a request for, nor agreement by the NYISO to provide,
Transmission Service, interconnection service, Energy, Ancillary Services, Installed Capacity,
Transmission Congestion Contracts or any other services or products established under the ISO
Tariffs. If Developer wishes to receive or supply such products or services, the Developer must
make application to do so under the applicable provisions of the ISO Tariffs, ISO Related
Agreements, and ISO Procedures.
3.11. Tax Status
Each Party shall cooperate with the other Party to maintain each Party’s tax status to the
extent the Party’s tax status is impacted by this Agreement. Nothing in this agreement is
intended to affect the tax status of any Party.
ARTICLE 4. COORDINATION WITH THIRD PARTIES
4.1.
Interconnection Requirements for Transmission Project
The Developer shall satisfy all requirements set forth in the Transmission Interconnection
Procedures in Attachment P of the OATT applicable to a “Transmission Project” to interconnect
the Transmission Project to the New York State Transmission System by the Required Project
In-Service Date, including, but not limited to, submitting a Transmission Interconnection
Application; participating in all necessary studies; executing, and/or requesting the NYISO to
file for FERC acceptance, a Transmission Project Interconnection Agreement; and constructing,
or arranging for the construction of, all required Network Upgrade Facilities; provided, however,
if the Developer began the interconnection process in Attachment X of the OATT or the
transmission expansion process in Sections 3.7 or 4.5 of the OATT prior to the effective date of
the Transmission Interconnection Procedures, the Developer shall satisfy the requirements of the
Transmission Interconnection Procedures in accordance with the transition rules in Section
22.3.3 of Attachment P of the OATT.
If the NYISO determines that the proposed interconnection of a “Transmission Project”
under Attachment P could affect the Transmission Project under this Agreement, the Developer
shall participate in the Transmission Interconnection Procedures as an Affected System Operator
in accordance with the requirements set forth in Section 22.4.4 of Attachment P. If the NYISO
determines that the proposed interconnection of a “Large Generating Facility,” “Small
Generating Facility,” or “Merchant Transmission Facility” under Attachments X or Z of the
OATT could affect the Transmission Project, the Developer shall participate in the
interconnection process as an Affected System Operator in accordance with the requirements set
forth in Section 30.3.5 of Attachment X of the OATT. If the NYISO determines that a proposed
transmission expansion under Sections 3.7 and 4.5 of the OATT could affect the Transmission
Project, the Developer shall participate in the transmission expansion process as an affected
Transmission Owner in accordance with the requirements set forth in Sections 3.7 and 4.5 of the
OATT.
4.2.
Interconnection with Affected System
If part of the Transmission Project will affect the facilities of an Affected System as
determined in Attachment P of the OATT, the Developer shall satisfy the requirements of the
Affected System Operator for the interconnection of the Transmission Project.
4.3.
Coordination of Interregional Transmission Project
If the Transmission Project is or seeks to become an Interregional Transmission Project
selected by the NYISO and by the transmission provider in one or more neighboring
transmission planning region(s) to address an identified Reliability Need, the Developer shall
coordinate its development and construction of the Transmission Project in New York with its
responsibilities in the relevant neighboring transmission planning region(s) and must satisfy the
applicable planning requirements of the relevant transmission planning region(s).
ARTICLE 5. OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
If the Developer is a Transmission Owner, the Developer shall comply with the operating
requirements set forth in the ISO/TO Agreement. If the Developer is not a Transmission Owner,
the Developer shall: (i) execute, and/or obtain a FERC accepted, interconnection agreement for
the Transmission Project in accordance with the requirements in Attachment P of the OATT; (ii)
satisfy the applicable requirements set forth in the interconnection agreement and ISO
Procedures for the safe and reliable operation of the Transmission Project consistent with the
Project Description set forth in Appendix A by the In-Service Date, including satisfying all
applicable testing, metering, communication, system protection, switching, start-up, and
synchronization requirements; (iii) enter into required operating protocols as determined by the
NYISO; (iv) register with NERC as a Transmission Owner, be certified as a Transmission
Operator unless otherwise agreed by the Parties, and comply with all NERC Reliability
Standards and Applicable Reliability Requirements applicable to Transmission Owners and
Transmission Operators; and (v) prior to energizing the Transmission Project, execute an
operating agreement with the NYISO.
ARTICLE 6. INSURANCE
The Developer shall, at its own expense, maintain in force throughout the period of this
Agreement, and until released by the NYISO, the following minimum insurance coverages, with
insurers authorized to do business in the state of New York and rated “A- (minus) VII” or better
by A.M. Best & Co. (or if not rated by A.M. Best & Co., a rating entity acceptable to the
NYISO):
6.1
Workers’ Compensation and Employers’ Liability Insurance providing statutory benefits
in accordance with the laws and regulations of New York State under NCCI Coverage
Form No. WC 00 00 00, as amended or supplemented from time to time, or an equivalent
form acceptable to the NYISO; provided, however, if the Transmission Project will be
located in part outside of New York State, Developer shall maintain such Employers’
Liability Insurance coverage with a minimum limit of One Million Dollars ($1,000,000).
6.2
Commercial General Liability Insurance - under ISO Coverage Form No. CG 00 01
(04/13), as amended or supplemented from time to time, or an equivalent form acceptable
to the NYISO - with minimum limits of Two Million Dollars ($2,000,000) per
occurrence/Four Million Dollars ($4,000,000) aggregate combined single limit for
personal injury, bodily injury, including death and property damage.
6.3
Commercial Business Automobile Liability Insurance - under ISO Coverage Form No.
CA 00 01 10 13, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO - for coverage of owned and non-owned and hired vehicles,
trailers or semi-trailers designed for travel on public roads, with a minimum, combined
single limit of One Million Dollars ($1,000,000) per occurrence for bodily injury,
including death, and property damage.
6.4
Umbrella/Excess Liability Insurance over and above the Employers’ Liability,
Commercial General Liability, and Commercial Business Automobile Liability Insurance
coverage, with a minimum combined single limit of Twenty-Five Million Dollars
($25,000,000) per occurrence/Twenty-Five Million Dollars ($25,000,000) aggregate.
6.5
Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility
Practice.
6.6
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies of the Developer shall name
the NYISO and its respective directors, officers, agents, servants and employees
(“NYISO Parties”) as additional insureds. For Commercial General Liability Insurance,
the Developer shall name the NYISO Parties as additional insureds under the following
ISO form numbers, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO: (i) ISO Coverage Form No. CG 20 37 04 13 (“Additional
Insured - Owners, Lessees or Contractors - Completed Operations”) and (ii) (A) ISO
Coverage Form No. CG 20 10 04 13 (“Additional Insured - Owner, Lessees or
Contractors - Scheduled Person or Organization”), or (B) ISO Coverage Form No. CG
20 26 04 13 (“Additional Insured - Designated Person or Organization”). For
Commercial Business Automobile Liability Insurance, the Developer shall name the
NYISO Parties as additional insureds under ISO Coverage Form No. CA 20 48 10 13
(“Designated Insured for Covered Autos Liability Coverage”), as amended or
supplemented from time to time, or an equivalent form acceptable to the NYISO.
6.7
All policies shall contain provisions whereby the insurers waive all rights of subrogation
in accordance with the provisions of this Agreement against the NYISO Parties and
provide thirty (30) Calendar days advance written notice to the NYISO Parties prior to
non-renewal, cancellation or any material change in coverage or condition.
6.8
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies shall contain provisions that
specify that the policies are primary and shall apply to such extent without consideration
for other policies separately carried and shall state that each insured is provided coverage
as though a separate policy had been issued to each, except the insurer’s liability shall not
be increased beyond the amount for which the insurer would have been liable had only
one insured been covered. The Developer shall be responsible for its respective
deductibles or retentions.
6.9
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies, if written on a Claims First
Made Basis in a form acceptable to the NYISO, shall be maintained in full force and
effect for two (2) years after termination of this Agreement, which coverage may be in
the form of an extended reporting period (ERP) or a separate policy, if agreed by the
Developer and the NYISO.
6.10
The requirements contained herein as to the types and limits of all insurance to be
maintained by the Developer are not intended to and shall not in any manner, limit or
qualify the liabilities and obligations assumed by the Developer under this Agreement.
6.11
The Developer shall provide certification of all insurance required in this Agreement,
executed by each insurer or by an authorized representative of each insurer: (A) within
ten (10) days following: (i) execution of this Agreement, or (ii) the NYISO’s date of
filing this Agreement if it is filed unexecuted with FERC, and (B) as soon as practicable
after the end of each fiscal year or at the renewal of the insurance policy and in any event
within thirty (30) days thereafter.
6.12
Notwithstanding the foregoing, the Developer may self-insure to meet the minimum
insurance requirements of Articles 6.2 through 6.10 to the extent it maintains a self-
insurance program; provided that, the Developer’s senior debt is rated at investment
grade, or better, by Standard & Poor’s and that its self-insurance program meets the
minimum insurance requirements of Articles 6.2 through 6.10. For any period of time
that the Developer’s senior debt is unrated by Standard & Poor’s or is rated at less than
investment grade by Standard & Poor’s, the Developer shall comply with the insurance
requirements applicable to it under Articles 6.2 through 6.11. In the event that the
Developer is permitted to self-insure pursuant to this Article 6.12, it shall notify the
NYISO that it meets the requirements to self-insure and that its self-insurance program
meets the minimum insurance requirements in a manner consistent with that specified in
Article 6.11.
6.13
The Developer and the NYISO agree to report to each other in writing as soon as
practical all accidents or occurrences resulting in injuries to any person, including death,
and any property damage arising out of this Agreement.
6.14
Notwithstanding the minimum insurance coverage types and amounts described in this
Article 6, the Developer: (i) shall also maintain any additional insurance coverage types
and amounts required under Applicable Laws and Regulations, including New York State
law, and under Good Utility Practice for the work performed by the Developer and its
subcontractors under this Agreement, and (ii) shall satisfy the requirements set forth in
Articles 6.6 through 6.13 with regard to the additional insurance coverages, including
naming the NYISO Parties as additional insureds under these policies.
ARTICLE 7. BREACH AND DEFAULT
7.1.
Breach
A Breach of this Agreement shall occur when: (i) the Developer notifies the NYISO in
writing that it will not proceed to develop the Transmission Project for reasons other than those
set forth in Articles 8.1(i) through (iv); (ii) the Developer fails to meet a Critical Path Milestone,
as the milestone may be extended with the agreement of the NYISO under Article 3.3.4 of this
Agreement, set forth in the Development Schedule in Appendix C to this Agreement; (iii) the
Developer makes a Significant Modification to the Transmission Project without the prior
written consent of the NYISO; (iv) the Developer fails to pay a monthly invoice within the
timeframe set forth in Article 3.5; (v) the Developer misrepresents a material fact of its
representations and warranties set forth in Article 12; (vi) a Party assigns this Agreement in a
manner inconsistent with the terms of Article 10 of this Agreement; (vii) the Developer fails to
comply with any other material term or condition of this Agreement; (viii) a custodian, receiver,
trustee or liquidator of the Developer, or of all or substantially all of the assets of the Developer,
is appointed in any proceeding brought by the Developer; or (ix) any such custodian, receiver,
trustee, or liquidator is appointed in any proceeding brought against the Developer that is not
discharged within ninety (90) Days after such appointment, or if the Developer consents to or
acquiesces in such appointment. A Breach shall not occur as a result of a Force Majeure event in
accordance with Article 15.5. A Breach shall also not occur as a result of a delay caused by a
Connecting Transmission Owner or an Affected System Operator.
7.2.
Default
Upon a Breach, the non-Breaching Party shall give written notice of the Breach to the
Breaching Party describing in reasonable detail the nature of the Breach and, where known and
applicable, the steps necessary to cure such Breach, including whether and what such steps must
be accomplished to complete the Transmission Project by the Required Project In-Service Date.
The Breaching Party shall have thirty (30) Calendar Days from receipt of the Breach notice to
cure the Breach, or such other period of time as may be agreed upon by the Parties, which
agreement the NYISO will not unreasonably withhold, condition, or delay if it determines a
longer cure period will not threaten the Developer’s ability to complete the Transmission Project
by the Required Project In-Service Date; provided, however, that if the Breach is the result of a
Developer’s inability or failure to meet a Critical Path Milestone, the Developer may only cure
the Breach if either: (i) it meets the Critical Path Milestone within the cure period and
demonstrates to the NYISO’s satisfaction that, notwithstanding its failure to timely meet the
Critical Path Milestone, the Transmission Project will achieve its In-Service Date no later than
the Required Project In-Service Date, or (ii) the Developer requests in writing within the cure
period, and the NYISO consents to, a change to the missed Critical Path Milestone in accordance
with Article 3.3.4. If the Breach is cured within such timeframe, the Breach specified in the
notice shall cease to exist. If the Breaching Party does not cure its Breach within this timeframe
or cannot cure the Breach in a manner that provides for the Transmission Project to be completed
by the Required Project In-Service Date, the non-Breaching Party shall have the right to declare
a Default and terminate this Agreement pursuant to Article 8.1.
7.3.
Remedies
Upon the occurrence of an event of Default, the non-defaulting Party shall be entitled: (i)
to commence an action to require the defaulting Party to remedy such Default and specifically
perform its duties and obligations hereunder in accordance with the terms and conditions hereof;
and (ii) to exercise such other rights and remedies as it may have in equity or at law; provided,
however, the defaulting Party’s liability under this Agreement shall be limited to the extent set
forth in Article 9.1. No remedy conferred by any provision of this Agreement is intended to be
exclusive of any other remedy and each and every remedy shall be cumulative and shall be in
addition to every other remedy given hereunder or now or hereafter existing at law or in equity
or by statute or otherwise. The election of any one or more remedies shall not constitute a
waiver of the right to pursue other available remedies. This Article 7.3 shall survive the
termination, expiration, or cancellation of this Agreement.
ARTICLE 8. TERMINATION
8.1.
Termination by the NYISO
The NYISO may terminate this Agreement by providing written notice of termination to
the Developer in the event that: (i) the Transmission Project is not triggered pursuant to Section
31.2.8.1.1 of Attachment Y of the OATT or is halted pursuant to Sections 31.2.8.2.1 or
31.2.8.2.2, as applicable, of Attachment Y of the OATT; (ii) the Developer notifies the NYISO
that it is unable to or has not received the required approvals or authorizations by Governmental
Authorities required to develop, construct, and operate the Transmission Project by the Required
Project In-Service Date; (iii) the Developer notifies the NYISO that its required approvals or
authorizations by Governmental Authorities have been withdrawn by the Governmental
Authorities; (iv) the Developer cannot complete the Transmission Project by the Required
Project In-Service Date for any reason: (A) including the occurrence of a Force Majeure event
that will prevent the Developer from completing the Transmission Project by the Required
Project In-Service Date, but (B) excluding a delay caused by a Connecting Transmission Owner
or an Affected System Operator; or (v) the NYISO declares a default pursuant to Article 7.2 of
this Agreement.
The NYISO will provide the written notice of termination to the Developer within fifteen
(15) Business Days of its determination under Article 8.1(i), which notice will specify the date of
termination. If the NYISO identifies grounds for termination under Articles 8.1(iv) or (v) or
receives notice from the Developer under Articles 8.1(ii) or (iii), the NYISO may, prior to
providing a written notice of termination, take action in accordance with Section 31.2.10.1.3 of
Attachment Y of the OATT to address the Reliability Need and, notwithstanding the
confidentiality provisions in Article 11.2, may disclose information regarding the Transmission
Project to Governmental Authorities as needed to implement such action. If the NYISO decides
to terminate this Agreement under Article 8.1(ii), (iii), (iv), or (v), it will provide written notice
of termination to the Developer, which notice will specify the date of termination. If the
Agreement was filed and accepted by FERC pursuant to Section 31.2.8.1.6 of Attachment Y of
the OATT, the NYISO will, following its provision of a notice of termination to the Developer,
promptly file with FERC for its acceptance a notice of termination of this Agreement.
In the event of termination under Articles 8.1(i), (ii), or (iii), the Developer may be
eligible for cost recovery under the OATT in the manner set forth in Attachment Y and Schedule
10 of the OATT. In the event of termination under Articles 8.1(iv) or (v), cost recovery may be
permitted as determined by FERC; provided, however, that if the Developer is the Responsible
Transmission Owner, it may also recover costs to the extent permitted under the NYISO/TO
Reliability Agreement. In the event of termination for any reason under this Article 8.1, the
Developer shall use commercially reasonable efforts to mitigate the costs, damages, and charges
arising as a consequence of termination and any transfer or winding up of the Transmission
Project.
8.2.
Reporting of Inability to Comply with Provisions of Agreement
Notwithstanding the notification requirements in Article 3 and this Article 8 of this
Agreement, each Party shall notify the other Party promptly upon the notifying Party becoming
aware of its inability to comply with any provision of this Agreement. The Parties agree to
cooperate with each other and provide necessary information regarding such inability to comply,
including the date, duration, reason for inability to comply, and corrective actions taken or
planned to be taken with respect to such inability to comply.
8.3.
Transmission Project Transfer Rights Upon Termination
If the Transmission Project was proposed as an alternative regulated transmission
solution that was selected by the NYISO as the more efficient or cost-effective transmission
solution to a Reliability Need and the NYISO terminates this Agreement pursuant to Article 8.1,
the NYISO shall have the right, but shall not be required, to request an entity other than the
Developer to complete the Transmission Project. The NYISO may exercise this right by
providing the Developer with written notice within sixty (60) days after the date on which this
Agreement is terminated. If the NYISO exercises its right under this Article 8.3 and Section
31.2.10.1.3 of Attachment Y of the OATT, the Developer shall work cooperatively with the
NYISO’s designee pursuant to the requirements set forth in Section 31.2.10.1.4 of Attachment Y
of the OATT to implement the transition, including entering into good faith negotiations with the
NYISO’s designee to transfer the Transmission Project to the NYISO’s designee. All liabilities
under this Agreement existing prior to such transfer shall remain with the Developer, unless
otherwise agreed upon by the Developer and the NYISO’s designee as part of their good faith
negotiations regarding the transfer. This Article 8.3 shall survive the termination, expiration, or
cancellation of this Agreement.
ARTICLE 9. LIABILITY AND INDEMNIFICATION
9.1.
Liability
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, neither Party shall be liable, whether based on contract, indemnification, warranty,
equity, tort, strict liability, or otherwise, to the Other Party or any Transmission Owner, NYISO
Market Participant, third party or any other person for any damages whatsoever, including,
without limitation, direct, incidental, consequential (including, without limitation, attorneys’ fees
and litigation costs), punitive, special, multiple, exemplary, or indirect damages arising or
resulting from any act or omission under this Agreement, except in the event the Party is found
liable for gross negligence or intentional misconduct in the performance of its obligations under
this Agreement, in which case the Party’s liability for damages shall be limited only to direct
actual damages. This Article 9.1 shall survive the termination, expiration, or cancellation of this
Agreement.
9.2.
Indemnity
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, each Party shall at all times indemnify and save harmless, as applicable, the other
Party, its directors, officers, employees, trustees, and agents or each of them from any and all
damages (including, without limitation, any consequential, incidental, direct, special, indirect,
exemplary or punitive damages and economic costs), losses, claims, including claims and actions
relating to injury to or death of any person or damage to property, liabilities, judgments,
demands, suits, recoveries, costs and expenses, court costs, attorney and expert fees, and all other
obligations by or to third parties, arising out of, or in any way resulting from this Agreement,
provided, however, that the Developer shall not have any indemnification obligation under this
Article 9.2 with respect to any loss to the extent the loss results from the negligence or
intentional misconduct of the NYISO; provided, further, that the NYISO shall not have any
indemnification obligation under this Article 9.2 with respect to any loss to the extent the loss
results from the negligence or intentional misconduct of the Developer. This Article 9.2 shall
survive the termination, expiration, or cancellation of this Agreement.
ARTICLE 10.
ASSIGNMENT
This Agreement may be assigned by a Party only with the prior written consent of the
other Party; provided that:
(i) any Change of Control shall be considered an assignment under this Article 10 and
shall require the other Party’s prior written consent;
(ii) an assignment by the Developer shall be contingent upon the Developer or assignee
demonstrating to the satisfaction of the NYISO prior to the effective date of the
assignment that: (A) the assignee has the technical competence, financial ability, and
materials, equipment, and plans to comply with the requirements of this Agreement and
to construct and place in service the Transmission Project by the Required Project In-
Service Date consistent with the assignor’s cost estimates for the Transmission Project;
and (B) the assignee satisfies the requirements for a qualified developer pursuant to
Section 31.2.4.1.1 of Attachment Y of the OATT; and
(iii) the Developer shall have the right to assign this Agreement, without the consent of
the NYISO, for collateral security purposes to aid in providing financing for the
Transmission Project and shall promptly notify the NYISO of any such assignment;
provided, however, that such assignment shall be subject to the following: (i) prior to or
upon the exercise of the secured creditor’s, trustee’s, or mortgagee’s assignment rights
pursuant to said arrangement, the secured creditor, the trustee, or the mortgagee will
notify the NYISO of the date and particulars of any such exercise of assignment right(s),
and (ii) the secured creditor, trustee, or mortgagee must demonstrate to the satisfaction of
the NYISO that any entity that it proposes to complete the Transmission Project meets
the requirements for the assignee of a Developer described in Article 10(ii).
For all assignments by any Party, the assignee must assume in a writing, to be provided to
the other Party, all rights, duties, and obligations of the assignor arising under this Agreement,
including the insurance requirements in Article 6 of this Agreement. Any assignment under this
Agreement shall not relieve a Party of its obligations, nor shall a Party’s obligations be enlarged,
in whole or in part, by reasons thereof, absent the written consent of the other Party. Where
required, consent to assignment will not be unreasonably withheld, conditioned, or delayed. Any
attempted assignment that violates this Article 10 is void and ineffective, is a Breach of this
Agreement under Article 7.1 and may result in the termination of this Agreement under Articles
8.1 and 7.2.
ARTICLE 11.
INFORMATION EXCHANGE AND CONFIDENTIALITY
11.1. Information Access
Subject to Applicable Laws and Regulations, each Party shall make available to the other
Party information necessary to carry out obligations and responsibilities under this Agreement
and Attachment Y of the OATT. The Parties shall not use such information for purposes other
than to carry out their obligations or enforce their rights under this Agreement or Attachment Y
of the OATT.
11.2.
Confidentiality
11.2.1
Confidential Information shall mean: (i) all detailed price information and vendor
contracts; (ii) any confidential and/or proprietary information provided by one Party to
the other Party that is clearly marked or otherwise designated “Confidential Information”;
and (iii) information designated as Confidential Information by the NYISO Code of
Conduct contained in Attachment F of the OATT; provided, however, that Confidential
Information does not include information: (i) in the public domain or that has been
previously publicly disclosed; (ii) required by an order of a Governmental Authority to be
publicly submitted or divulged (after notice to the other Party); or (iii) necessary to be
divulged in an action to enforce this Agreement.
11.2.2
The NYISO shall treat any Confidential Information it receives in accordance with the
requirements of the NYISO Code of Conduct contained in Attachment F of the OATT. If
the Developer receives Confidential Information, it shall hold such information in
confidence, employing at least the same standard of care to protect the Confidential
Information obtained from the NYISO as it employs to protect its own Confidential
Information. Each Party shall not disclose the other Party’s Confidential Information to
any third party or to the public without the prior written authorization of the Party
providing the information, except: (i) to the extent required for the Parties to perform
their obligations under this Agreement, the ISO Tariffs, ISO Related Agreements, or ISO
Procedures, or (ii) to fulfill legal or regulatory requirements, provided that if the Party
must submit the information to a Governmental Authority in response to a request by the
Governmental Authority on a confidential basis, the Party required to disclose the
information shall request under applicable rules and regulations that the information be
treated as confidential and non-public by the Governmental Authority.
ARTICLE 12.
REPRESENTATIONS, WARRANTIES, AND COVENANTS
12.1. General
The Developer makes the following representations, warranties, and covenants, which are
effective as to the Developer during the full time this Agreement is effective:
12.2. Good Standing
The Developer is duly organized, validly existing and in good standing under the laws of
the state in which it is organized, formed, or incorporated, as applicable. The Developer is
qualified to do business in the state or states in which the Transmission Project is located. The
Developer has the corporate power and authority to own its properties, to carry on its business as
now being conducted and to enter into this Agreement and carry out the transactions
contemplated hereby and to perform and carry out covenants and obligations on its part under
and pursuant to this Agreement.
12.3. Authority
The Developer has the right, power, and authority to enter into this Agreement, to
become a Party hereto, and to perform its obligations hereunder. This Agreement is a legal,
valid, and binding obligation of the Developer, enforceable against the Developer in accordance
with its terms, except as the enforceability thereof may be limited by applicable bankruptcy,
insolvency, reorganization, or other similar laws affecting creditors’ rights generally and by
general equitable principles (regardless of whether enforceability is sought in a proceeding in
equity or at law).
12.4. No Conflict
The execution, delivery and performance of this Agreement does not violate or conflict
with the organizational or formation documents, or bylaws or operating agreement, of the
Developer, or any judgment, license, permit, order, material agreement or instrument applicable
to or binding upon the Developer or any of its assets.
12.5. Consent and Approval
The Developer has sought or obtained, or, in accordance with this Agreement will seek or
obtain, such consent, approval, authorization, order, or acceptance by any Governmental
Authority in connection with the execution, delivery and performance of this Agreement, and it
will provide to any Governmental Authority notice of any actions under this Agreement that are
required by Applicable Laws and Regulations.
12.6. Compliance with All Applicable Laws and Regulations
The Developer will comply with all Applicable Laws and Regulations, including all
approvals, authorizations, orders, and permits issued by any Governmental Authority; all
Applicable Reliability Requirements, and all applicable Transmission Owner Technical
Standards in the performance of its obligations under this Agreement.
ARTICLE 13.
DISPUTE RESOLUTION
If a dispute arises under this Agreement, the Parties shall use the dispute resolution
process described in Article 11 of the NYISO’s Services Tariff, as such process may be amended
from time to time. Notwithstanding the process described in Article 11 of the NYISO’s Services
Tariff, the NYISO may terminate this Agreement in accordance with Article 8 of this
Agreement.
ARTICLE 14.
SURVIVAL
The rights and obligations of the Parties in this Agreement shall survive the termination,
expiration, or cancellation of this Agreement to the extent necessary to provide for the
determination and enforcement of said obligations arising from acts or events that occurred while
this Agreement was in effect. The remedies and rights and obligation upon termination
provisions in Articles 7.3 and 8.3 of this Agreement, the liability and indemnity provisions in
Article 9, and the billing and payment provisions in Article 3.5 of this Agreement shall survive
termination, expiration, or cancellation of this Agreement.
ARTICLE 15.
MISCELLANEOUS
15.1. Notices
Any notice or request made to or by any Party regarding this Agreement shall be made to
the Parties, as indicated below:
NYISO:
[Insert contact information.]
Developer:
[Insert contact information.]
15.2. Entire Agreement
Except as described below in this Section 15.2, this Agreement, including all Appendices
attached hereto, constitutes the entire agreement between the Parties with reference to the subject
matter hereof, and supersedes all prior and contemporaneous understandings of agreements, oral
or written, between the Parties with respect to the subject matter of this Agreement. There are no
other agreements, representations, warranties, or covenants that constitute any part of the
consideration for, or any condition to, either Party’s compliance with its obligation under this
Agreement.
Notwithstanding the foregoing, this Agreement is in addition to, and does not supersede
or limit the Developer’s and NYISO’s rights and responsibilities, under any interconnection
agreement(s) entered into by and among the NYISO, Developer, and Connecting Transmission
Owner(s) for the Transmission Project to interconnect to the New York State Transmission
System, as such interconnection agreements may be amended, supplemented, or modified from
time to time.
15.3. Cost Recovery
The Developer may recover the costs of the Transmission Project in accordance with the
cost recovery requirements in the ISO Tariffs and, if the Developer is the Responsible
Transmission Owner, the ISO Tariffs and the NYISO/TO Reliability Agreement.
15.4. Binding Effect
This Agreement, and the rights and obligations hereof, shall be binding upon and shall
inure to the benefit of the successors and permitted assigns of the Parties hereto.
15.5. Force Majeure
A Party that is unable to carry out an obligation imposed on it by this Agreement due to
Force Majeure shall notify the other Party in writing as soon as reasonably practicable after the
occurrence of the Force Majeure event and no later than the timeframe set forth in Article
3.3.3(i) if the Force Majeure event will result in a potential delay for the Developer to meet a
Critical Path Milestone. If the notifying Party is the Developer, it shall indicate in its notice
whether the occurrence of a Force Majeure event has the potential to delay its meeting one or
more Critical Path Milestones and/or completing the Transmission Project by the Required
Project In-Service Date. If the Force Majeure will delay the Developer’s ability to meet one or
more Critical Path Milestones, the Developer shall request with its notice a change to the
impacted milestones in accordance with the requirements in Section 3.3.4 and must satisfy the
requirements in Section 3.3.4 to change any Critical Path Milestones. A Party shall not be
responsible for any non-performance or considered in Breach or Default under this Agreement,
for any failure to perform any obligation under this Agreement to the extent that such failure is
due to Force Majeure and will not delay the Developer’s ability to complete the Transmission
Project by the Required Project In-Service Date. A Party shall be excused from whatever
performance is affected only for the duration of the Force Majeure and while the Party exercises
reasonable efforts to alleviate such situation. As soon as the nonperforming Party is able to
resume performance of its obligations excused because of the occurrence of Force Majeure, such
Party shall resume performance and give prompt notice thereof to the other Party. In the event
that Developer will not be able to complete the Transmission Project by the Required Project In-
Service Date because of the occurrence of Force Majeure, the NYISO may terminate this
Agreement in accordance with Section 8.1 of this Agreement.
15.6. Disclaimer
Except as provided in this Agreement, the Parties make no other representations,
warranties, covenants, guarantees, agreements or promises regarding the subject matter of this
Agreement.
15.7. No NYISO Liability for Review or Approval of Developer Materials
No review or approval by the NYISO or its subcontractor(s) of any agreement, document,
instrument, drawing, specifications, or design proposed by the Developer nor any inspection
carried out by the NYISO or its subcontractor(s) pursuant to this Agreement shall relieve the
Developer from any liability for any negligence in its preparation of such agreement, document,
instrument, drawing, specification, or design, or its carrying out of such works; or for its failure
to comply with the Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards with respect thereto, nor shall the NYISO be liable to
the Developer or any other person by reason of its or its subcontractor’s review or approval of an
agreement, document, instrument, drawing, specification, or design or such inspection.
15.8. Amendment
The Parties may by mutual agreement amend this Agreement, including the Appendices
to this Agreement, by a written instrument duly executed by both of the Parties. If the
Agreement was filed and accepted by FERC pursuant to Section 31.2.8.1.6 of Attachment Y of
the OATT, the NYISO shall promptly file the amended Agreement for acceptance with FERC.
15.9. No Third Party Beneficiaries
With the exception of the indemnification rights of the NYISO’s directors, officers,
employees, trustees, and agents under Article 9.2, this Agreement is not intended to and does not
create rights, remedies, or benefits of any character whatsoever in favor of any persons,
corporations, associations, or entities other than the Parties, and the obligations herein assumed
are solely for the use and benefit of the Parties, their successors in interest and their permitted
assigns.
15.10. Waiver
The failure of a Party to this Agreement to insist, on any occasion, upon strict
performance of any provision of this Agreement will not be considered a waiver of any
obligation, right, or duty of, or imposed upon, such Party. Any waiver at any time by either
Party of its rights with respect to this Agreement shall not be deemed a continuing waiver or a
waiver with respect to any other failure to comply with any other obligation, right, or duty of this
Agreement. Any waiver of this Agreement shall, if requested, be provided in writing.
15.11. Rules of Interpretation
This Agreement, unless a clear contrary intention appears, shall be construed and
interpreted as follows: (1) the singular number includes the plural number and vice versa; (2)
reference to any person includes such person’s successors and assigns but, in the case of a Party,
only if such successors and assigns are permitted by this Agreement, and reference to a person in
a particular capacity excludes such person in any other capacity or individually; (3) reference to
any agreement (including this Agreement), document, instrument or tariff means such
agreement, document, instrument, or tariff as amended or modified and in effect from time to
time in accordance with the terms thereof and, if applicable, the terms hereof; (4) reference to
any Applicable Laws and Regulations means such Applicable Laws and Regulations as
amended, modified, codified, or reenacted, in whole or in part, and in effect from time to time,
including, if applicable, rules and regulations promulgated thereunder; (5) unless expressly stated
otherwise, reference to any Article, Section or Appendix means such Article of this Agreement,
such Appendix to this Agreement, or such Section of this Agreement, as the case may be; (6)
“hereunder”, “hereof’, “herein”, “hereto” and words of similar import shall be deemed references
to this Agreement as a whole and not to any particular Article or other provision hereof or
thereof; (7) “including” (and with correlative meaning “include”) means including without
limiting the generality of any description preceding such term; and (8) relative to the
determination of any period of time, “from” means “from and including”, “to” means “to but
excluding” and “through” means “through and including”.
15.12. Severability
Each provision of this Agreement shall be considered severable and if, for any reason,
any provision is determined by a court or regulatory authority of competent jurisdiction to be
invalid, void, or unenforceable, the remaining provisions of this Agreement shall continue in full
force and effect and shall in no way be affected, impaired, or invalidated, and such invalid, void,
or unenforceable provision should be replaced with valid and enforceable provision or provisions
that otherwise give effect to the original intent of the invalid, void, or unenforceable provision.
15.13. Multiple Counterparts
This Agreement may be executed in two or more counterparts, each of which is deemed
an original, but all constitute one and the same instrument.
15.14. No Partnership
This Agreement shall not be interpreted or construed to create an association, joint
venture, agency relationship, or partnership among the Parties or to impose any partnership
obligation or partnership liability upon any Party. No Party shall have any right, power, or
authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an
agent or representative of, or otherwise bind, any other Party.
15.15. Headings
The descriptive headings of the various Articles and Sections of this Agreement have
been inserted for convenience of reference only and are of no significance in the interpretation or
construction of this Agreement.
15.16. Governing Law
This Agreement shall be governed, as applicable, by: (i) the Federal Power Act, and (ii)
the substantive law of the State of New York, without regard to any conflicts of laws provisions
thereof (except to the extent applicable, Sections 5-1401 and 5-1402 of the New York General
Obligations Law).
15.17. Jurisdiction and Venue
Any legal action or judicial proceeding regarding a dispute arising out of or relating to
this Agreement or any performance by either Party pursuant thereto that: (i) is within the primary
or exclusive jurisdiction of FERC shall be brought in the first instance at FERC, or (ii) is not
within the primary or exclusive jurisdiction of FERC shall be brought in, and fully and finally
resolved in, either, as applicable, the courts of the State of New York situated in Albany County,
New York or the United States District Court of the Northern District of New York situated in
Albany, New York.
IN WITNESS WHEREFORE, the Parties have executed this Agreement in duplicate originals,
each of which shall constitute an original Agreement between the Parties.
NYISO
By: _______________________
Title:______________________
Date:______________________
[Insert name of Developer]
By:_______________________
Title:______________________
Date:______________________
Appendix A
Project Description
Appendix C
Development Schedule
[To be prepared by Developer consistent with the Developer’s project information submission,
pursuant to Attachment C of the Reliability Planning Process Manual, and subject to acceptance
by the NYISO, as required by Article 3.3 of this Agreement.]
The Developer shall demonstrate to the NYISO that it timely meets the following Critical
Path Milestones and Advisory Milestones and that such milestones remain in good standing.
Critical Path Milestones: [To be developed with consideration of each of the work plan
requirements submitted by the Developer pursuant to Attachment C to the Reliability Planning
Process Manual and presented herein according to the sequence of the critical path. The NYISO
anticipates that the Developer’s critical path schedule will include many of the example
milestones set forth below and that most of the other example milestones will be included as
Advisory Milestones. The composition and sequence of the Critical Path Milestones will differ
depending on the Developer’s Transmission Project and schedule.]
Advisory Milestones: [To include in Development Schedule other milestones (e.g., periodic
project review meetings) that are not determined to be on the critical path, but that will be
monitored by the Developer and reported to NYISO.]
[Example Milestones:
Interconnection studies (e.g. Optional Feasibility Study, System Impact Study, Facilities
Study)
Siting activities (e.g. locating line routing, access roads, and substation site location
options)
Environmental impact studies (relative to siting options)
Engineering (initial)
Permitting and regulatory activities (e.g. Certificate of Environmental Compatibility and
Public Need)
Public outreach plan
Initiation of negotiation of key contracts and financing
Acquisition of all necessary approvals and authorizations of Governmental Authorities,
including identification of all required regulatory approvals
Closing of project financing
Completion of key contracts
Engineering (detailed)
Procurement of major equipment and materials
Environmental management & construction plan (for Article VII certification)
Acquisition of [all or %] required rights of way and property / demonstration of site
control
Surveying and geotechnical assessment (relative to line and station layouts)
Execution, or filing of unexecuted version, of interconnection agreement
Engineering (completed)
Delivery of major electrical equipment
Line and substation site work including milestones for foundations, towers, conductor
stringing, equipment delivery and installation, substation controls and communication,
security, etc.
Construction outage and restoration coordination plan
Completion, verification and testing
Operating and maintenance agreements and instructions
In-Service Date
Required Project In-Service Date]
APPENDIX D - PUBLIC POLICY TRANSMISSION PLANNING PROCESS
DEVELOPMENT AGREEMENT
TABLE OF CONTENTS
Page
ARTICLE 1.
DEFINITIONS
2
ARTICLE 2.
EFFECTIVE DATE AND TERM
6
2.1.
Effective Date
6
2.2.
Filing
6
2.3.
Term of Agreement
6
ARTICLE 3.
TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
6
3.1.
Application for Required Authorizations and Approvals
6
3.2.
Development and Construction of Transmission Project
7
3.3.
Milestones
7
3.4.
Modifications to Required Project In-Service Date
8
3.5.
Modifications to Transmission Project
9
3.6.
Billing and Payment
10
3.7.
Project Monitoring
10
3.8.
Right to Inspect
10
3.9.
Exclusive Responsibility of Developer
10
3.10.
Subcontractors
11
3.11.
No Services or Products Under NYISO Tariffs
11
3.12.
Tax Status
11
ARTICLE 4.
COORDINATION WITH THIRD PARTIES
11
4.1.
Interconnection Requirements for Transmission Project
11
4.2.
Interconnection with Affected System
12
4.3.
Coordination of Interregional Transmission Project
12
ARTICLE 5.
OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
12
ARTICLE 6.
INSURANCE
13
ARTICLE 7.
BREACH AND DEFAULT
15
7.1.
Breach
15
7.2.
Default
15
7.3.
Remedies
16
ARTICLE 8.
TERMINATION
16
8.1.
Termination by the NYISO
16
8.2.
Reporting of Inability to Comply with Provisions of Agreement
17
8.3.
Transmission Project Transfer Rights Upon Termination
17
ARTICLE 9.
LIABILITY AND INDEMNIFICATION
18
9.1.
Liability
18
9.2.
Indemnity
18
ARTICLE 10. ASSIGNMENT
18
ARTICLE 11. INFORMATION EXCHANGE AND CONFIDENTIALITY
19
11.1.
Information Access
19
11.2.
Confidentiality
19
ARTICLE 12. REPRESENTATIONS, WARRANTIES AND COVENANTS
20
12.1.
General
20
12.2.
Good Standing
20
12.3.
Authority
20
12.4.
No Conflict
20
12.5.
Consent and Approval
21
12.6.
Compliance with All Applicable Laws and Regulations
21
ARTICLE 13. DISPUTE RESOLUTION
21
ARTICLE 14. SURVIVAL
21
ARTICLE 15. MISCELLANEOUS
21
15.1.
Notices
21
15.2.
Entire Agreement
22
15.3.
Cost Recovery
22
15.4.
Binding Effect
22
15.5.
Force Majeure
22
15.6.
Disclaimer
23
15.7.
No NYISO Liability for Review or Approval of Developer Materials
23
15.8.
Amendment
23
15.9.
No Third Party Beneficiaries
23
15.10.
Waiver
23
15.11.
Rules of Interpretation
24
15.12.
Severability
24
15.13.
Multiple Counterparts
24
15.14.
No Partnership
24
15.15.
Headings
25
15.16.
Governing Law
25
15.17.
Jurisdiction and Venue
25
Appendices
THIS DEVELOPMENT AGREEMENT (“Agreement”) is made and entered into this ___ day
of ______ 20__, by and between _______________, a [corporate description] organized and
existing under the laws of the State/Commonwealth of _________ (“Developer”), and the New
York Independent System Operator, Inc., a not-for-profit corporation organized and existing
under the laws of the State of New York (“NYISO”). Developer or NYISO each may be referred
to as a “Party” or collectively referred to as the “Parties.”
RECITALS
WHEREAS, the NYISO administers the Comprehensive System Planning Process (“CSPP”) in
the New York Control Area pursuant to the terms set forth in Attachment Y of the NYISO’s
Open Access Transmission Tariff (“OATT”), as accepted by the Federal Energy Regulatory
Commission (“FERC”);
WHEREAS, as part of the CSPP, the NYISO administers a Public Policy Transmission
Planning Process pursuant to which Public Policy Transmission Need(s) are identified; proposed
solutions to the identified need(s) are solicited by the NYISO; and the more efficient or cost-
effective transmission solution to satisfy the identified need(s) is selected by the NYISO and
reported in the NYISO’s Public Policy Transmission Planning Report;
WHEREAS, the Developer has proposed a Public Policy Transmission Project to satisfy an
identified Public Policy Transmission Need (“Transmission Project”);
WHEREAS, the NYISO has selected the Developer’s Transmission Project as the more efficient
or cost-effective transmission solution to satisfy an identified Public Policy Transmission Need
and has directed the Developer to proceed with the Transmission Project;
WHEREAS, the Developer has agreed to obtain the required authorizations and approvals from
Governmental Authorities needed for the Transmission Project, to develop and construct the
Transmission Project, and to abide by the related requirements in Attachment Y of the OATT,
the ISO Tariffs, and the ISO Procedures;
WHEREAS, the Developer and the NYISO have agreed to enter into this Agreement pursuant to
Section 31.4.12.2 of Attachment Y of the OATT for the purpose of ensuring that the
Transmission Project will be constructed and in service in time to satisfy the Public Policy
Transmission Need (“Required Project In-Service Date”); and
WHEREAS, the Developer has agreed to construct, and the NYISO has requested that the
Developer proceed with construction of, the Transmission Project to address the identified Public
Policy Transmission Need by the Required Project In-Service Date.
NOW, THEREFORE, in consideration of and subject to the mutual covenants contained herein,
it is agreed:
ARTICLE 1. DEFINITIONS
Whenever used in this Agreement with initial capitalization, the following terms shall have the
meanings specified in this Article 1. Terms used in this Agreement with initial capitalization that
are not defined in this Article 1 shall have the meanings specified in Section 31.1.1 of
Attachment Y of the OATT or, if not therein, in Article 1 of the OATT.
Advisory Milestones shall mean the milestones set forth in the Development Schedule in
Attachment C to this Agreement that are not Critical Path Milestones.
Affected System Operator shall mean any Affected System Operator(s) identified in connection
with the Transmission Project pursuant to Attachment P of the ISO OATT.
Applicable Laws and Regulations shall mean: (i) all duly promulgated applicable federal, state
and local laws, regulations, rules, ordinances, codes, decrees, judgments, directives, or judicial or
administrative orders, permits and other duly authorized actions of any Governmental Authority,
and (ii) all applicable requirements of the ISO Tariffs, ISO Procedures, and ISO Related
Agreements.
Applicable Reliability Organizations shall mean the NERC, the NPCC, and the NYSRC.
Applicable Reliability Requirements shall mean the requirements, criteria, rules, standards,
and guidelines, as they may be amended and modified and in effect from time to time, of: (i) the
Applicable Reliability Organizations, (ii) the Connecting Transmission Owner(s), (iii) [to insert
the name(s) of any other Transmission Owners or developers whose transmission facilities the
NYISO has determined may be impacted by the Transmission Project], and (iv) any Affected
System Operator; provided, however, that no Party shall waive its right to challenge the
applicability or validity of any requirement, criteria, rule, standard, or guideline as applied to it in
the context of this Agreement.
Breach shall have the meaning set forth in Article 7.1 of this Agreement.
Breaching Party shall mean a Party that is in Breach of this Agreement.
Business Day shall mean Monday through Friday, excluding federal holidays.
Calendar Day shall mean any day including Saturday, Sunday, or a federal holiday.
Change of Control shall mean a change in ownership of more than 50% of the membership or
ownership interests or other voting securities of the Developer to a third party in one or more
related transactions, or any other transaction that has the effect of transferring control of the
Developer to a third party.
Confidential Information shall mean any information that is defined as confidential by Article
11.2.
Connecting Transmission Owner shall be the Connecting Transmission Owner(s) identified in
connection with the Transmission Project pursuant to Attachment P of the ISO OATT.
Critical Path Milestones shall mean the milestones identified as such in the Development
Schedule in Attachment C to this Agreement that must be met for the Transmission Project to be
constructed and operating by the Required Project In-Service Date.
Default shall mean the failure of a Party in Breach of this Agreement to cure such Breach in
accordance with Article 7.2 of this Agreement.
Developer shall have the meaning set forth in the introductory paragraph.
Development Schedule shall mean the schedule of Critical Path Milestones and Advisory
Milestones set forth in Appendix C to this Agreement.
Effective Date shall mean the date upon which this Agreement becomes effective as determined
in Article 2.1 of this Agreement.
FERC shall mean the Federal Energy Regulatory Commission or its successor.
Force Majeure shall mean any act of God, labor disturbance, act of the public enemy, war,
insurrection, riot, fire, storm or flood, explosion, breakage or accident to machinery or
equipment, any order, regulation or restriction imposed by governmental, military or lawfully
established civilian authorities, or any other cause beyond a Party’s control. A Force Majeure
event does not include acts of negligence or intentional wrongdoing by the Party claiming Force
Majeure.
Good Utility Practice shall mean any of the practices, methods and acts engaged in or approved
by a significant portion of the electric industry during the relevant time period, or any of the
practices, methods and acts which, in the exercise of reasonable judgment in light of the facts
known at the time the decision was made, could have been expected to accomplish the desired
result at a reasonable cost consistent with good business practice, reliability, safety and
expedition. Good Utility Practice is not intended to be limited to the optimum practice, method,
or act to the exclusion of all others, but rather to delineate acceptable practices, methods, or acts
generally accepted in the region.
Governmental Authority shall mean any federal, state, local or other governmental regulatory
or administrative agency, public authority, court, commission, department, board, or other
governmental subdivision, legislature, rulemaking board, tribunal, or other governmental
authority having jurisdiction over any of the Parties, their respective facilities, or the respective
services they provide, and exercising or entitled to exercise any administrative, executive, police,
or taxing authority or power; provided, however, that such term does not include the NYISO, the
Developer, the Connecting Transmission Owner(s), the Affected System Operator(s), or any
Affiliate thereof.
In-Service Date shall mean the date upon which the Transmission Project is energized
consistent with the provisions of the Transmission Project Interconnection Agreement and
available to provide Transmission Service under the NYISO Tariffs.
ISO/TO Agreement shall mean the Agreement Between the New York Independent System
Operator and Transmission Owners, as filed with and accepted by the Commission in Cent.
Hudson Gas & Elec. Corp., et al., 88 FERC ¶ 61,138 (1999) in Docket Nos. ER97-1523, et al.,
and as amended or supplemented from time to time, or any successor agreement thereto.
New York State Transmission System shall mean the entire New York State electrical
transmission system, which includes: (i) the Transmission Facilities Under ISO Operational
Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining
transmission facilities within the New York Control Area.
NERC shall mean the North American Electric Reliability Corporation or its successor
organization.
NPCC shall mean the Northeast Power Coordinating Council or its successor organization.
NYPSC shall mean the New York State Public Service Commission or its successor.
NYSRC shall mean the New York State Reliability Council or its successor organization.
OATT shall mean the NYISO’s Open Access Transmission Tariff, as filed with the
Commission, and as amended or supplemented from time to time, or any successor tariff thereto.
Party or Parties shall mean the NYISO, the Developer, or both.
Point of Interconnection shall mean the point or points at which the Developer’s Transmission
Project will interconnect to the New York State Transmission System.
Project Description shall mean the description of the Transmission Project set forth in
Appendix A to this Agreement that is consistent with the project proposed and evaluated in the
NYISO’s Public Policy Transmission Planning Process and selected by the NYISO Board of
Directors as the more efficient or cost-effective transmission solution to the identified Public
Policy Transmission Need.
Public Policy Transmission Planning Process Manual shall mean the NYISO’s manual
adopted by the NYISO stakeholder Operating Committee describing the NYISO’s procedures for
implementing the Public Policy Transmission Planning Process component of the NYISO’s
Comprehensive System Planning Process, as the manual is amended or supplemented from time
to time, or any successor manual thereto.
Required Project In-Service Date shall mean the In-Service Date by which the Transmission
Project must be constructed and operating, which date shall be: (i) the date by which the Public
Policy Transmission Need must be satisfied as prescribed by the NYPSC in its order identifying
the need or in a subsequent order, or (ii) if the NYPSC has not prescribed a date, the date
proposed by the Developer and reviewed and accepted by the NYISO, which date may be either:
(A) the In-Service Date specified by the Developer in the project information it submitted under
Attachment Y of the OATT for use by the NYISO in its selection of the Transmission Project as
the more efficient or cost-effective transmission solution to satisfy the Public Policy
Transmission Need, or (B) such other date accepted by the NYISO as reasonable in light of the
Public Policy Transmission Need. The Required Project In-Service Date is set forth in the
Development Schedule contained in Appendix C to this Agreement.
Services Tariff shall mean the NYISO’s Market Administration and Control Area Services Tariff,
as filed with the Commission, and as amended or supplemented from time to time, or any
successor tariff thereto.
Significant Modification shall mean a Developer’s proposed modification to its Transmission
Project that: (i) could impair the Transmission Project’s ability to meet the identified Public
Policy Transmission Need, (ii) could delay the In-Service Date of the Transmission Project
beyond the Required Project In-Service Date, or (iii) would constitute a material change to the
project information submitted by the Developer under Attachment Y of the OATT for use by the
NYISO in evaluating the Transmission Project for purposes of selecting the more efficient or
cost-effective transmission solution to meet the identified Public Policy Transmission Need.
Scope of Work shall mean the description of the work required to implement the Transmission
Project as set forth in Appendix B to this Agreement. The Scope of Work shall be drawn from
the Developer’s submission of the “Information for a Proposed Solution to a Public Policy
Transmission Need” and the “Data Submission for Public Policy Transmission Projects,” which
are set forth in Attachments B and C of the NYISO Public Policy Transmission Planning Process
Manual, as may be updated as agreed upon by the Parties. The Scope of Work shall include, but
not be limited to, a description of: the acquisition of required rights-of-ways, the work associated
with the licensing, design, financing, environmental and regulatory approvals, engineering,
procurement of equipment, construction, installation, testing, and commissioning of the
Transmission Project; the relevant technical requirements, standards, and guidelines pursuant to
which the work will be performed; the major equipment and facilities to be constructed and/or
installed in connection with the Transmission Project, and the cost estimates for the work
associated with the Transmission Project.
Transmission Owner Technical Standards shall mean the technical requirements and
standards (e.g, equipment or facilities electrical and physical capabilities, design characteristics,
or construction requirements), as those requirements and standards are amended and modified and
in effect from time to time, of: (i) the Connecting Transmission Owner(s), (ii) [to insert the name(s)
of any other Transmission Owners or developers whose transmission facilities the NYISO has
determined may be impacted by the Transmission Project], and (iii) any Affected System
Operator.
Transmission Project shall mean the Developer’s proposed Public Policy Transmission Project
selected by the NYISO as the more efficient or cost-effective transmission solution to a Public
Policy Transmission Need that is subject to this Agreement, as described in the Project
Description set forth in Appendix A to this Agreement.
ARTICLE 2. EFFECTIVE DATE AND TERM
2.1.
Effective Date
This Agreement shall become effective on the date it has been executed by all Parties;
provided, however, if the Agreement is filed with FERC as a non-conforming or an unexecuted
agreement pursuant to Section 31.4.12.2 of Attachment Y of the OATT, the Agreement shall
become effective on the effective date accepted by FERC.
2.2.
Filing
If the Agreement must be filed with FERC pursuant to Section 31.4.12.2 of Attachment
Y of the OATT, the NYISO shall file this Agreement for acceptance with FERC within the
timeframe set forth for the filing in Section 31.4.12.2 of Attachment Y of the OATT. The
Developer shall cooperate in good faith with the NYISO with respect to such filing and provide
any information requested by the NYISO to comply with Applicable Laws and Regulations.
Any Confidential Information shall be treated in accordance with Article 11.2 of this Agreement.
2.3.
Term of Agreement
Subject to the termination provisions in Article 8 of this Agreement, this Agreement shall
remain in effect from the Effective Date until: (i) the Developer executes an operating agreement
with the NYISO, and (ii) the Transmission Project: (A) has been completed in accordance with
the terms and conditions of this Agreement, and (B) is in-service; provided, however, that the
terms of this Agreement shall continue in effect to the extent provided in Article 14 of this
Agreement.
ARTICLE 3. TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
3.1.
Application for Required Authorizations and Approvals
The Developer shall timely seek and obtain all authorizations and approvals from
Governmental Authorities required to develop, construct, and operate the Transmission Project
by the Required Project In-Service Date. The required authorizations and approvals shall be
listed in the Scope of Work in Appendix B to this Agreement. The Developer shall seek and
obtain the required authorizations and approvals in accordance with the milestones set forth in
the Development Schedule in Appendix C to this Agreement. The milestones for obtaining the
required authorizations and approvals shall be included in the Development Schedule as Critical
Path Milestones and Advisory Milestones, as designated by the Parties under Article 3.3.1. The
Developer shall notify the NYISO in accordance with the notice requirements in Article 3.3 if it
has reason to believe that it may be unable to timely obtain or is denied an approval or
authorization by a Governmental Authority required for the development, construction, or
operation of the Transmission Project, or if such approval or authorization is withdrawn or
modified.
3.2.
Development and Construction of Transmission Project
The Developer shall design, engineer, procure, install, construct, test and commission the
Transmission Project in accordance with: (i) the terms of this Agreement, including, but not
limited to, the Project Description in Appendix A to this Agreement, the Scope of Work in
Appendix B to this Agreement, and the Development Schedule in Appendix C to this
Agreement; (ii) Applicable Reliability Requirements; (iii) Applicable Laws and Regulations; (iv)
Good Utility Practice; (v) the Transmission Owner Technical Standards, and (vi) any
interconnection agreement(s) entered into by and among the NYISO, Developer, and Connecting
Transmission Owner(s) for the Transmission Project to interconnect to the New York State
Transmission System.
3.3.
Milestones
3.3.1.
The NYISO shall provide the Developer with the Required Project In-Service Date that
is set forth in the Public Policy Transmission Planning Report in accordance with Section
31.4.11 of Attachment Y of the OATT. Prior to executing and/or filing this Agreement
with FERC, the NYISO and the Developer shall agree to the Critical Path Milestones and
Advisory Milestones set forth in the Development Schedule in Appendix C to this
Agreement for the development, construction, and operation of the Transmission Project
by the Required Project In-Service Date in accordance with Section 31.4.12.2 of
Attachment Y of the OATT; provided that any such milestone for the Transmission
Project that requires action by a Connecting Transmission Owner or Affected System
Operator to complete must be included as an Advisory Milestone.
3.3.2.
The Developer shall meet the Critical Path Milestones in accordance with the
Development Schedule set forth in Appendix C to this Agreement. The Developer’s
inability or failure to meet a Critical Path Milestone specified in the Development
Schedule, as such Critical Path Milestone may be amended with the agreement of the
NYISO under this Article 3.3, shall constitute a Breach of this Agreement under Article
7.1.
3.3.3.
The Developer shall notify the NYISO thirty (30) Calendar Days prior to the date of each
Critical Path Milestone specified in the Development Schedule whether, to the best of its
knowledge, it expects to meet the Critical Path Milestone by the specified date; provided,
however, that notwithstanding this requirement:
(i) the Developer shall notify the NYISO as soon as reasonably practicable, and no later
than fifteen (15) Calendar Days, following the Developer’s discovery of a potential delay
in meeting a Critical Path Milestone, including a delay caused by a Force Majeure event;
and
(ii) the NYISO may request in writing at any time, and Developer shall submit to the
NYISO within five (5) Business Days of the request, a written response indicating
whether the Developer will meet, or has met, a Critical Path Milestone and providing all
required supporting documentation for its response.
3.3.4.
The Developer shall not make a change to a Critical Path Milestone without the prior
written consent of the NYISO. To request a change to a Critical Path Milestone, the
Developer must: (i) inform the NYISO in writing of the proposed change to the Critical
Path Milestone and the reason for the change, including the occurrence of a Force
Majeure event in accordance with Section 15.5, (ii) submit to the NYISO a revised
Development Schedule containing any necessary changes to Critical Path Milestones and
Advisory Milestones that provide for the Transmission Project to be completed and
achieve its In-Service Date no later than the Required Project In-Service Date, and (iii)
submit a notarized officer’s certificate certifying the Developer’s capability to complete
the Transmission Project in accordance with the modified schedule. If the Developer: (i)
must notify the NYISO of a potential delay in meeting a Critical Path Milestone in
accordance with one of the notification requirements in Section 3.3.3 or (ii) is requesting
a change to a Critical Path Milestone to cure a Breach in Section 7.2, the Developer shall
submit any request to change the impacted Critical Path Milestone(s) within the relevant
notification timeframe set forth in Section 3.3.3 or the cure period set forth in Section 7.2,
as applicable. The NYISO will promptly review the Developer’s requested change. The
Developer shall provide the NYISO with all required information to assist the NYISO in
making its determination and shall be responsible for the costs of any study work the
NYISO performs in making its determination. If the Developer demonstrates to the
NYISO’s satisfaction that the delay in meeting a Critical Path Milestone will not delay
the Transmission Project’s In-Service Date beyond the Required Project In-Service Date,
then the NYISO’s consent to extending the Critical Path Milestone date will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s written consent to a
revised Development Schedule proposed by the Developer will satisfy the amendment
requirements in Article 15.8, and the NYISO will not be required to file the revised
Development Schedule with FERC.
3.3.5.
Within fifteen (15) Calendar Days of the Developer’s discovery of a potential delay in
meeting an Advisory Milestone, the Developer shall inform the NYISO of the potential
delay and describe the impact of the delay on meeting the Critical Path Milestones. The
Developer may extend an Advisory Milestone date upon informing the NYISO of such
change; provided, however, that if the change to the Advisory Milestone will delay a
Critical Path Milestone, the NYISO’s written consent to make such change is required as
described in Article 3.3.4.
3.4.
Modifications to Required Project In-Service Date
3.4.1.
The Developer shall not make a change to the Required Project In-Service Date without
the prior written consent of the NYISO. To request a change, the Developer must: (i)
inform the NYISO in writing of the proposed change to the Required Project In-Service
Date and the reason for the change, including the occurrence of a Force Majeure event,
(ii) submit to the NYISO a revised Development Schedule that provides for the
Transmission Project to be completed and achieve its In-Service Date no later than the
proposed, modified Required Project In-Service Date, and (iii) demonstrate that the
Developer has made reasonable progress against the milestones set forth in the
Development Schedule, and is capable of completing the Transmission Project in
accordance with the modified schedule. If the Required Project In-Service Date is the
date prescribed by the NYPSC in its order identifying the Public Policy Transmission
Need or in a subsequent order, the Developer must also demonstrate that the NYPSC has
issued an order modifying its prescribed date.
3.4.2. The NYISO will promptly review Developer’s requested change to the Required Project
In-Service Date. The Developer shall provide the NYISO with all required information
to assist the NYISO in making its determination and shall be responsible for the costs of
any study work the NYISO performs in making its determination. If the Developer fails
to provide the NYISO with the information required to make its determination, the
NYISO shall not be obligated to make this determination. The NYISO’s consent to
extend the Required Project In-Service Date will not be unreasonably withheld,
conditioned, or delayed if the Developer demonstrates to the NYISO’s satisfaction that:
(i) its proposed modified Required Project In-Service Date is reasonable in light of the
Public Policy Transmission Need, (ii) it has made reasonable progress against the
milestones set forth in the Development Schedule, and (iii) its proposed modified date
will not result in a significant adverse impact to the reliability of the New York State
Transmission System. The Parties shall amend this Agreement in accordance with
Article 15.8 to incorporate a revised Required Project In-Service Date and Development
Schedule.
3.5.
Modifications to Transmission Project
The Developer shall not make a Significant Modification to the Transmission Project
without the prior written consent of the NYISO, including, but not limited to, modifications
necessary for the Developer to obtain required approvals or authorizations from Governmental
Authorities; provided, however, that a proposed Significant Modification that is a proposed
modification to the Required Project In-Service Date shall be addressed in accordance with
Article 3.4. The NYISO’s determination regarding a Significant Modification to the
Transmission Project under this Agreement shall be separate from, and shall not replace, the
NYISO’s review and determination of material modifications to the Transmission Project under
Attachment P of the OATT. The Developer may request that the NYISO review whether a
modification to the Transmission Project would constitute a Significant Modification. The
Developer shall provide the NYISO with all required information to assist the NYISO in making
its determination regarding a Significant Modification and shall be responsible for the costs of
any study work the NYISO must perform in making its determination. The NYISO’s consent to
the Significant Modification will not be unreasonably withheld, conditioned, or delayed if the
Developer demonstrates to the NYISO’s satisfaction that its proposed Significant Modification:
(i) does not impair the Transmission Project’s ability to satisfy the identified Public Policy
Transmission Need, (ii) does not delay the In-Service Date of the Transmission Project beyond
the Required Project In-Service Date, (iii) does not change the grounds upon which the NYISO
selected the Transmission Project as the more efficient or cost-effective transmission solution to
the identified Public Policy Transmission Need, and (iv) will not result in a significant adverse
impact to the reliability of the New York State Transmission System. The NYISO’s
performance of this review shall not constitute its consent to delay the completion of any Critical
Path Milestone.
3.6.
Billing and Payment
The NYISO shall charge, and the Developer shall pay, the actual costs of: (i) any study
work performed by the NYISO or its subcontractor(s) under Articles 3.3, 3.4, and 3.5, or (ii) any
assessment of the Transmission Project by the NYISO or its subcontractor(s) under Article 3.8.
The NYISO will invoice Developer on a monthly basis for the expenses incurred by the NYISO
each month, including estimated subcontractor costs, computed on a time and material basis.
The Developer shall pay invoiced amounts to the NYISO within thirty (30) Calendar Days of the
NYISO’s issuance of a monthly invoice. In the event the Developer disputes an amount to be
paid, the Developer shall pay the disputed amount to the NYISO, pending resolution of the
dispute. To the extent the dispute is resolved in the Developer’s favor, the NYISO will net the
disputed amount, including interest calculated from Developer’s date of payment at rates
applicable to refunds under FERC regulations, against any current amounts due from the
Developer and pay the balance to the Developer. This Article 3.6 shall survive the termination,
expiration, or cancellation of this Agreement.
3.7.
Project Monitoring
The Developer shall provide regular status reports to the NYISO in accordance with the
monitoring requirements set forth in the Development Schedule, the Public Policy Transmission
Planning Process Manual and Attachment Y of the OATT.
3.8.
Right to Inspect
Upon reasonable notice, the NYISO or its subcontractor shall have the right to inspect the
Transmission Project for the purpose of assessing the progress of the development and
construction of the Transmission Project and satisfaction of milestones. The exercise or non-
exercise by the NYISO or its subcontractor of this right shall not be construed as an endorsement
or confirmation of any element or condition of the development or construction of the
Transmission Project, or as a warranty as to the fitness, safety, desirability or reliability of the
same. Any such inspection shall take place during normal business hours, shall not interfere
with the construction of the Transmission Project and shall be subject to such reasonable safety
and procedural requirements as the Developer shall specify.
3.9.
Exclusive Responsibility of Developer
As between the Parties, the Developer shall be solely responsible for all planning, design,
engineering, procurement, construction, installation, management, operations, safety, and
compliance with Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards associated with the Transmission Project, including,
but not limited to, scheduling, meeting Critical Path Milestones and Advisory Milestones, timely
requesting review and consent to any project modifications, and obtaining all necessary permits,
siting, and other regulatory approvals. The NYISO shall have no responsibility and shall have
no liability regarding the management or supervision of the Developer’s development of the
Transmission Project or the compliance of the Developer with Applicable Laws and Regulations,
Applicable Reliability Requirements, and Transmission Owner Technical Standards. The
NYISO shall cooperate with the Developer in good faith in providing information to assist the
Developer in obtaining all approvals and authorizations from Governmental Authorities required
to develop, construct, and operate the Transmission Project by the Required Project In-Service
Date, including, if applicable, information describing the NYISO’s basis for selecting the
Transmission Project as the more efficient or cost-effective transmission solution to satisfy an
identified Public Policy Transmission Need.
3.10. Subcontractors
3.10.1. Nothing in this Agreement shall prevent a Party from using the services of any
subcontractor as it deems appropriate to perform its obligations under this Agreement;
provided, however, that each Party shall require, and shall provide in its contracts with its
subcontractors, that its subcontractors comply with all applicable terms and conditions of
this Agreement in providing such services; provided, further, that each Party shall remain
primarily liable to the other Party for the performance of such subcontractor.
3.10.2. The creation of any subcontractor relationship shall not relieve the hiring Party of any of
its obligations under this Agreement. The hiring Party shall be fully responsible to the
other Party for the acts or omissions of any subcontractor the hiring Party hires as if no
subcontract had been made.
3.11. No Services or Products Under NYISO Tariffs
This Agreement does not constitute a request for, nor agreement by the NYISO to provide,
Transmission Service, interconnection service, Energy, Ancillary Services, Installed Capacity,
Transmission Congestion Contracts or any other services or products established under the ISO
Tariffs. If Developer wishes to receive or supply such products or services, the Developer must
make application to do so under the applicable provisions of the ISO Tariffs, ISO Related
Agreements, and ISO Procedures.
3.12. Tax Status
Each Party shall cooperate with the other Party to maintain each Party’s tax status to the
extent the Party’s tax status is impacted by this Agreement. Nothing in this agreement is
intended to affect the tax status of any Party.
ARTICLE 4. COORDINATION WITH THIRD PARTIES
4.1.
Interconnection Requirements for Transmission Project
The Developer shall satisfy all requirements set forth in the Transmission Interconnection
Procedures in Attachment P of the OATT applicable to a “Transmission Project” to interconnect
the Transmission Project to the New York State Transmission System by the Required Project
In-Service Date, including, but not limited to, submitting a Transmission Interconnection
Application; participating in all necessary studies; executing, and/or requesting the NYISO to
file for FERC acceptance, a Transmission Project Interconnection Agreement; and constructing,
or arranging for the construction of, all required Network Upgrade Facilities; provided, however,
if the Developer began the interconnection process in Attachment X of the OATT or the
transmission expansion process in Sections 3.7 or 4.5 of the OATT prior to the effective date of
the Transmission Interconnection Procedures, the Developer shall satisfy the requirements of the
Transmission Interconnection Procedures in accordance with the transition rules in Section
22.3.3 of Attachment P of the OATT..
If the NYISO determines that the proposed interconnection of a “Transmission Project”
under Attachment P could affect the Transmission Project under this Agreement, the Developer
shall participate in the Transmission Interconnection Procedures as an Affected System Operator
in accordance with the requirements set forth in Section 22.4.4 of Attachment P. If the NYISO
determines that the proposed interconnection of a “Large Generating Facility,” “Small
Generating Facility,” or “Merchant Transmission Facility” under Attachments X or Z of the
OATT could affect the Transmission Project, the Developer shall participate in the
interconnection process as an Affected System Operator in accordance with the requirements set
forth in Section 30.3.5 of Attachment X of the OATT. If the NYISO determines that a proposed
transmission expansion under Sections 3.7 and 4.5 of the OATT could affect the Transmission
Project, the Developer shall participate in the transmission expansion process as an affected
Transmission Owner in accordance with the requirements set forth in Sections 3.7 and 4.5 of the
OATT.
4.2.
Interconnection with Affected System
If part of the Transmission Project will affect the facilities of an Affected System as
determined in Attachment P of the OATT, the Developer shall satisfy the requirements of the
Affected System Operator for the interconnection of the Transmission Project.
4.3.
Coordination of Interregional Transmission Project
If the Transmission Project is or seeks to become an Interregional Transmission Project
selected by the NYISO and by the transmission provider in one or more neighboring
transmission planning region(s) to address an identified Public Policy Transmission Need, the
Developer shall coordinate its development and construction of the Transmission Project in New
York with its responsibilities in the relevant neighboring transmission planning region(s) and
must satisfy the applicable planning requirements of the relevant transmission planning
region(s).
ARTICLE 5. OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
If the Developer is a Transmission Owner, the Developer shall comply with the operating
requirements set forth in the ISO/TO Agreement. If the Developer is not a Transmission Owner,
the Developer shall: (i) execute, and/or obtain a FERC accepted, interconnection agreement for
the Transmission Project in accordance with the requirements in Attachment P of the OATT; (ii)
satisfy the applicable requirements set forth in the interconnection agreement and ISO
Procedures for the safe and reliable operation of the Transmission Project consistent with the
Project Description set forth in Appendix A by the In-Service Date, including satisfying all
applicable testing, metering, communication, system protection, switching, start-up, and
synchronization requirements; (iii) enter into required operating protocols as determined by the
NYISO; (iv) register with NERC as a Transmission Owner, be certified as a Transmission
Operator unless otherwise agreed by the Parties, and comply with all NERC Reliability
Standards and Applicable Reliability Requirements applicable to Transmission Owners and
Transmission Operators; and (v) prior to energizing the Transmission Project, execute an
operating agreement with the NYISO.
ARTICLE 6. INSURANCE
The Developer shall, at its own expense, maintain in force throughout the period of this
Agreement, and until released by the NYISO, the following minimum insurance coverages, with
insurers authorized to do business in the state of New York and rated “A- (minus) VII” or better
by A.M. Best & Co. (or if not rated by A.M. Best & Co., a rating entity acceptable to the
NYISO):
6.1
Workers’ Compensation and Employers’ Liability Insurance providing statutory benefits
in accordance with the laws and regulations of New York State under NCCI Coverage Form No.
WC 00 00 00, as amended or supplemented from time to time, or an equivalent form acceptable
to the NYISO; provided, however, if the Transmission Project will be located in part outside of
New York State, Developer shall maintain such Employers’ Liability Insurance coverage with a
minimum limit of One Million Dollars ($1,000,000).
6.2
Commercial General Liability Insurance - under ISO Coverage Form No. CG 00 01
(04/13), as amended or supplemented from time to time, or an equivalent form acceptable to the
NYISO - with minimum limits of Two Million Dollars ($2,000,000) per occurrence/Four
Million Dollars ($4,000,000) aggregate combined single limit for personal injury, bodily injury,
including death and property damage.
6.3
Commercial Business Automobile Liability Insurance - under ISO Coverage Form No.
CA 00 01 10 13, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO - for coverage of owned and non-owned and hired vehicles, trailers or
semi-trailers designed for travel on public roads, with a minimum, combined single limit of One
Million Dollars ($1,000,000) per occurrence for bodily injury, including death, and property
damage.
6.4
Umbrella/Excess Liability Insurance over and above the Employers’ Liability,
Commercial General Liability, and Commercial Business Automobile Liability Insurance
coverage, with a minimum combined single limit of Twenty-Five Million Dollars ($25,000,000)
per occurrence/Twenty-Five Million Dollars ($25,000,000) aggregate.
6.5
Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility
Practice.
6.6
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies of the Developer shall name the
NYISO and its respective directors, officers, agents, servants and employees (“NYISO Parties”)
as additional insureds. For Commercial General Liability Insurance, the Developer shall name
the NYISO Parties as additional insureds under the following ISO form numbers, as amended or
supplemented from time to time, or an equivalent form acceptable to the NYISO: (i) ISO
Coverage Form No. CG 20 37 04 13 (“Additional Insured - Owners, Lessees or Contractors -
Completed Operations”) and (ii) (A) ISO Coverage Form No. CG 20 10 04 13 (“Additional
Insured - Owner, Lessees or Contractors - Scheduled Person or Organization”), or (B) ISO
Coverage Form No. CG 20 26 04 13 (“Additional Insured - Designated Person or
Organization”). For Commercial Business Automobile Liability Insurance, the Developer shall
name the NYISO Parties as additional insureds under ISO Coverage Form No. CA 20 48 10 13
(“Designated Insured for Covered Autos Liability Coverage”), as amended or supplemented
from time to time, or an equivalent form acceptable to the NYISO.
6.7
All policies shall contain provisions whereby the insurers waive all rights of subrogation
in accordance with the provisions of this Agreement against the NYISO Parties and provide
thirty (30) Calendar days advance written notice to the NYISO Parties prior to non-renewal,
cancellation or any material change in coverage or condition.
6.8
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies shall contain provisions that specify
that the policies are primary and shall apply to such extent without consideration for other
policies separately carried and shall state that each insured is provided coverage as though a
separate policy had been issued to each, except the insurer’s liability shall not be increased
beyond the amount for which the insurer would have been liable had only one insured been
covered. The Developer shall be responsible for its respective deductibles or retentions.
6.9
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies, if written on a Claims First Made
Basis in a form acceptable to the NYISO, shall be maintained in full force and effect for two (2)
years after termination of this Agreement, which coverage may be in the form of an extended
reporting period (ERP) or a separate policy, if agreed by the Developer and the NYISO.
6.10
The requirements contained herein as to the types and limits of all insurance to be
maintained by the Developer are not intended to and shall not in any manner, limit or qualify the
liabilities and obligations assumed by the Developer under this Agreement.
6.11
The Developer shall provide certification of all insurance required in this Agreement,
executed by each insurer or by an authorized representative of each insurer: (A) within ten (10)
days following: (i) execution of this Agreement, or (ii) the NYISO’s date of filing this
Agreement if it is filed unexecuted with FERC, and (B) as soon as practicable after the end of
each fiscal year or at the renewal of the insurance policy and in any event within thirty (30) days
thereafter.
6.12
Notwithstanding the foregoing, the Developer may self-insure to meet the minimum
insurance requirements of Articles 6.2 through 6.10 to the extent it maintains a self-insurance
program; provided that, the Developer’s senior debt is rated at investment grade, or better, by
Standard & Poor’s and that its self-insurance program meets the minimum insurance
requirements of Articles 6.2 through 6.10. For any period of time that the Developer’s senior
debt is unrated by Standard & Poor’s or is rated at less than investment grade by Standard &
Poor’s, the Developer shall comply with the insurance requirements applicable to it under
Articles 6.2 through 6.11. In the event that the Developer is permitted to self-insure pursuant to
this Article 6.12, it shall notify the NYISO that it meets the requirements to self-insure and that
its self-insurance program meets the minimum insurance requirements in a manner consistent
with that specified in Article 6.11.
6.13
The Developer and the NYISO agree to report to each other in writing as soon as
practical all accidents or occurrences resulting in injuries to any person, including death, and any
property damage arising out of this Agreement.
6.14
Notwithstanding the minimum insurance coverage types and amounts described in this
Article 6, the Developer: (i) shall also maintain any additional insurance coverage types and
amounts required under Applicable Laws and Regulations, including New York State law, and
under Good Utility Practice for the work performed by the Developer and its subcontractors
under this Agreement, and (ii) shall satisfy the requirements set forth in Articles 6.6 through 6.13
with regard to the additional insurance coverages, including naming the NYISO Parties as
additional insureds under these policies.
ARTICLE 7. BREACH AND DEFAULT
7.1.
Breach
A Breach of this Agreement shall occur when: (i) the Developer notifies the NYISO in
writing that it will not proceed to develop the Transmission Project for reasons other than those
set forth in Articles 8.1(i) through (iv); (ii) the Developer fails to meet a Critical Path Milestone,
as the milestone may be extended with the agreement of the NYISO under Article 3.3.4 of this
Agreement, set forth in the Development Schedule in Appendix C to this Agreement; (iii) the
Developer makes a Significant Modification to the Transmission Project without the prior
written consent of the NYISO; (iv) the Developer fails to pay a monthly invoice within the
timeframe set forth in Article 3.6; (v) the Developer misrepresents a material fact of its
representations and warranties set forth in Article 12; (vi) a Party assigns this Agreement in a
manner inconsistent with the terms of Article 10 of this Agreement; (vii) the Developer fails to
comply with any other material term or condition of this Agreement; (viii) a custodian, receiver,
trustee or liquidator of the Developer, or of all or substantially all of the assets of the Developer,
is appointed in any proceeding brought by the Developer; or (ix) any such custodian, receiver,
trustee, or liquidator is appointed in any proceeding brought against the Developer that is not
discharged within ninety (90) Days after such appointment, or if the Developer consents to or
acquiesces in such appointment. A Breach shall not occur as a result of a Force Majeure event in
accordance with Article 15.5. A Breach shall also not occur as a result of a delay caused by a
Connecting Transmission Owner or an Affected System Operator.
7.2.
Default
Upon a Breach, the non-Breaching Party shall give written notice of the Breach to the
Breaching Party describing in reasonable detail the nature of the Breach and, where known and
applicable, the steps necessary to cure such Breach, including whether and what such steps must
be accomplished to complete the Transmission Project by the Required Project In-Service Date.
The Breaching Party shall have thirty (30) Calendar Days from receipt of the Breach notice to
cure the Breach, or such other period of time as may be agreed upon by the Parties, which
agreement the NYISO will not unreasonably withhold, condition, or delay if it determines a
longer cure period will not threaten the Developer’s ability to complete the Transmission Project
by the Required Project In-Service Date; provided, however, that if the Breach is the result of a
Developer’s inability or failure to meet a Critical Path Milestone, the Developer may only cure
the Breach if either: (i) it meets the Critical Path Milestone within the cure period and
demonstrates to the NYISO’s satisfaction that, notwithstanding its failure to timely meet the
Critical Path Milestone, the Transmission Project will achieve its In-Service Date no later than
the Required Project In-Service Date, or (ii) the Developer requests in writing within the cure
period, and the NYISO consents to, a change to the missed Critical Path Milestone in accordance
with Article 3.3.4. If the Breach is cured within such timeframe, the Breach specified in the
notice shall cease to exist. If the Breaching Party does not cure its Breach within this timeframe
or cannot cure the Breach in a manner that provides for the Transmission Project to be completed
by the Required Project In-Service Date, the non-Breaching Party shall have the right to declare
a Default and terminate this Agreement pursuant to Article 8.1.
7.3.
Remedies
Upon the occurrence of an event of Default, the non-defaulting Party shall be entitled: (i)
to commence an action to require the defaulting Party to remedy such Default and specifically
perform its duties and obligations hereunder in accordance with the terms and conditions hereof;
and (ii) to exercise such other rights and remedies as it may have in equity or at law; provided,
however, the defaulting Party’s liability under this Agreement shall be limited to the extent set
forth in Article 9.1. No remedy conferred by any provision of this Agreement is intended to be
exclusive of any other remedy and each and every remedy shall be cumulative and shall be in
addition to every other remedy given hereunder or now or hereafter existing at law or in equity
or by statute or otherwise. The election of any one or more remedies shall not constitute a
waiver of the right to pursue other available remedies. This Article 7.3 shall survive the
termination, expiration, or cancellation of this Agreement.
ARTICLE 8. TERMINATION
8.1.
Termination by the NYISO
The NYISO may terminate this Agreement by providing written notice of termination to
the Developer in the event that: (i) the Developer notifies the NYISO that it is unable to or has
not received the required approvals or authorizations by Governmental Authorities required to
develop, construct, and operate the Transmission Project by the Required Project In-Service
Date; (ii) the Developer notifies the NYISO that its required approvals or authorizations by
Governmental Authorities have been withdrawn by the Governmental Authorities; (iii) the
Developer cannot complete the Transmission Project by the Required Project In-Service Date for
any reason: (A) including the occurrence of a Force Majeure event that will prevent the
Developer from completing the Transmission Project by the Required Project In-Service Date,
but (B) excluding a delay caused by a Connecting Transmission Owner or an Affected System
Operator; or (iv) the NYISO declares a default pursuant to Article 7.2 of this Agreement.
If the NYISO identifies grounds for termination under Articles 8.1(iii) or (iv) or receives
notice from the Developer under Articles 8.1(i) or (ii), the NYISO may, prior to providing a
written notice of termination, take action in accordance with Section 31.4.12.3.1.3 of Attachment
Y of the OATT to address the Public Policy Transmission Need and, notwithstanding the
confidentiality provisions in Article 11.2, may disclose information regarding the Transmission
Project to Governmental Authorities as needed to implement such action. If the NYISO decides
to terminate this Agreement under Article 8.1(i), (ii), (iii), or (iv), it will provide written notice of
termination to the Developer, which notice will specify the date of termination. If the
Agreement was filed and accepted by FERC pursuant to Section 31.4.12.2 of Attachment Y of
the OATT, the NYISO will, following its provision of a notice of termination to the Developer,
promptly file with FERC for its acceptance a notice of termination of this Agreement.
In the event of termination under Articles 8.1 (i) or (ii), the Developer may be eligible for
cost recovery under the OATT in the manner set forth in Attachment Y and Schedule 10 of the
OATT. In the event of termination under Articles 8.1(iii) or (iv), cost recovery may be permitted
as determined by FERC. In the event of termination for any reason under this Article 8.1, the
Developer shall use commercially reasonable efforts to mitigate the costs, damages, and charges
arising as a consequence of termination and any transfer or winding up of the Transmission
Project.
8.2.
Reporting of Inability to Comply with Provisions of Agreement
Notwithstanding the notification requirements in Article 3 and this Article 8 of this
Agreement, each Party shall notify the other Party promptly upon the notifying Party becoming
aware of its inability to comply with any provision of this Agreement. The Parties agree to
cooperate with each other and provide necessary information regarding such inability to comply,
including the date, duration, reason for inability to comply, and corrective actions taken or
planned to be taken with respect to such inability to comply.
8.3.
Transmission Project Transfer Rights Upon Termination
If the NYISO terminates this Agreement pursuant to Article 8.1, the NYISO shall have
the right, but shall not be required, to request an entity other than the Developer to complete the
Transmission Project. The NYISO may exercise this right by providing the Developer with
written notice within sixty (60) days after the date on which this Agreement is terminated. If the
NYISO exercises its right under this Article 8.3 and Section 31.4.12.3.1.3 of Attachment Y of
the OATT, the Developer shall work cooperatively with the NYISO’s designee pursuant to the
requirements set forth in Section 31.4.12.3.1.4 of Attachment Y of the OATT to implement the
transition, including entering into good faith negotiations with the NYISO’s designee to transfer
the Transmission Project to the NYISO’s designee. All liabilities under this Agreement existing
prior to such transfer shall remain with the Developer, unless otherwise agreed upon by the
Developer and the NYISO’s designee as part of their good faith negotiations regarding the
transfer. This Article 8.3 shall survive the termination, expiration, or cancellation of this
Agreement.
ARTICLE 9. LIABILITY AND INDEMNIFICATION
9.1.
Liability
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, neither Party shall be liable, whether based on contract, indemnification, warranty,
equity, tort, strict liability, or otherwise, to the Other Party or any Transmission Owner, NYISO
Market Participant, third party or any other person for any damages whatsoever, including,
without limitation, direct, incidental, consequential (including, without limitation, attorneys’ fees
and litigation costs), punitive, special, multiple, exemplary, or indirect damages arising or
resulting from any act or omission under this Agreement, except in the event the Party is found
liable for gross negligence or intentional misconduct in the performance of its obligations under
this Agreement, in which case the Party’s liability for damages shall be limited only to direct
actual damages. This Article 9.1 shall survive the termination, expiration, or cancellation of this
Agreement.
9.2.
Indemnity
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, each Party shall at all times indemnify and save harmless, as applicable, the other
Party, its directors, officers, employees, trustees, and agents or each of them from any and all
damages (including, without limitation, any consequential, incidental, direct, special, indirect,
exemplary or punitive damages and economic costs), losses, claims, including claims and actions
relating to injury to or death of any person or damage to property, liabilities, judgments,
demands, suits, recoveries, costs and expenses, court costs, attorney and expert fees, and all other
obligations by or to third parties, arising out of, or in any way resulting from this Agreement,
provided, however, that the Developer shall not have any indemnification obligation under this
Article 9.2 with respect to any loss to the extent the loss results from the negligence or
intentional misconduct of the NYISO; provided, further, that the NYISO shall not have any
indemnification obligation under this Article 9.2 with respect to any loss to the extent the loss
results from the negligence or intentional misconduct of the Developer. This Article 9.2 shall
survive the termination, expiration, or cancellation of this Agreement.
ARTICLE 10.
ASSIGNMENT
This Agreement may be assigned by a Party only with the prior written consent of the
other Party; provided that:
(i) any Change of Control shall be considered an assignment under this Article 10 and
shall require the other Party’s prior written consent;
(ii) an assignment by the Developer shall be contingent upon the Developer or assignee
demonstrating to the satisfaction of the NYISO prior to the effective date of the
assignment that: (A) the assignee has the technical competence, financial ability, and
materials, equipment, and plans to comply with the requirements of this Agreement and
to construct and place in service the Transmission Project by the Required Project In-
Service Date consistent with the assignor’s cost estimates for the Transmission Project;
and (B) the assignee satisfies the requirements for a qualified developer pursuant to
Section 31.4.4 of Attachment Y of the OATT; and
(iii) the Developer shall have the right to assign this Agreement, without the consent of
the NYISO, for collateral security purposes to aid in providing financing for the
Transmission Project and shall promptly notify the NYISO of any such assignment;
provided, however, that such assignment shall be subject to the following: (i) prior to or
upon the exercise of the secured creditor’s, trustee’s, or mortgagee’s assignment rights
pursuant to said arrangement, the secured creditor, the trustee, or the mortgagee will
notify the NYISO of the date and particulars of any such exercise of assignment right(s),
and (ii) the secured creditor, trustee, or mortgagee must demonstrate to the satisfaction of
the NYISO that any entity that it proposes to complete the Transmission Project meets
the requirements for the assignee of a Developer described in Article 10(ii).
For all assignments by any Party, the assignee must assume in a writing, to be provided to
the other Party, all rights, duties, and obligations of the assignor arising under this Agreement,
including the insurance requirements in Article 6 of this Agreement. Any assignment under this
Agreement shall not relieve a Party of its obligations, nor shall a Party’s obligations be enlarged,
in whole or in part, by reasons thereof, absent the written consent of the other Party. Where
required, consent to assignment will not be unreasonably withheld, conditioned, or delayed. Any
attempted assignment that violates this Article 10 is void and ineffective, is a Breach of this
Agreement under Article 7.1 and may result in the termination of this Agreement under Articles
8.1 and 7.2.
ARTICLE 11.
INFORMATION EXCHANGE AND CONFIDENTIALITY
11.1. Information Access
Subject to Applicable Laws and Regulations, each Party shall make available to the other
Party information necessary to carry out obligations and responsibilities under this Agreement
and Attachment Y of the OATT. The Parties shall not use such information for purposes other
than to carry out their obligations or enforce their rights under this Agreement or Attachment Y
of the OATT.
11.2. Confidentiality
11.2.1. Confidential Information shall mean: (i) all detailed price information and vendor
contracts; (ii) any confidential and/or proprietary information provided by one Party to
the other Party that is clearly marked or otherwise designated “Confidential Information”;
and (iii) information designated as Confidential Information by the NYISO Code of
Conduct contained in Attachment F of the OATT; provided, however, that Confidential
Information does not include information: (i) in the public domain or that has been
previously publicly disclosed; (ii) required by an order of a Governmental Authority to be
publicly submitted or divulged (after notice to the other Party); or (iii) necessary to be
divulged in an action to enforce this Agreement.
11.2.2. The NYISO shall treat any Confidential Information it receives in accordance with the
requirements of the NYISO Code of Conduct contained in Attachment F of the OATT. If
the Developer receives Confidential Information, it shall hold such information in
confidence, employing at least the same standard of care to protect the Confidential
Information obtained from the NYISO as it employs to protect its own Confidential
Information. Each Party shall not disclose the other Party’s Confidential Information to
any third party or to the public without the prior written authorization of the Party
providing the information, except: (i) to the extent required for the Parties to perform
their obligations under this Agreement, the ISO Tariffs, ISO Related Agreements, or ISO
Procedures, or (ii) to fulfill legal or regulatory requirements, provided that if the Party
must submit the information to a Governmental Authority in response to a request by the
Governmental Authority on a confidential basis, the Party required to disclose the
information shall request under applicable rules and regulations that the information be
treated as confidential and non-public by the Governmental Authority.
ARTICLE 12.
REPRESENTATIONS, WARRANTIES AND COVENANTS
12.1. General
The Developer makes the following representations, warranties, and covenants, which are
effective as to the Developer during the full time this Agreement is effective:
12.2. Good Standing
The Developer is duly organized, validly existing and in good standing under the laws of
the state in which it is organized, formed, or incorporated, as applicable. The Developer is
qualified to do business in the state or states in which the Transmission Project is located. The
Developer has the corporate power and authority to own its properties, to carry on its business as
now being conducted and to enter into this Agreement and carry out the transactions
contemplated hereby and to perform and carry out covenants and obligations on its part under
and pursuant to this Agreement.
12.3. Authority
The Developer has the right, power, and authority to enter into this Agreement, to
become a Party hereto, and to perform its obligations hereunder. This Agreement is a legal,
valid, and binding obligation of the Developer, enforceable against the Developer in accordance
with its terms, except as the enforceability thereof may be limited by applicable bankruptcy,
insolvency, reorganization, or other similar laws affecting creditors’ rights generally and by
general equitable principles (regardless of whether enforceability is sought in a proceeding in
equity or at law).
12.4. No Conflict
The execution, delivery and performance of this Agreement does not violate or conflict
with the organizational or formation documents, or bylaws or operating agreement, of the
Developer, or any judgment, license, permit, order, material agreement or instrument applicable
to or binding upon the Developer or any of its assets.
12.5. Consent and Approval
The Developer has sought or obtained, or, in accordance with this Agreement will seek or
obtain, such consent, approval, authorization, order, or acceptance by any Governmental
Authority in connection with the execution, delivery and performance of this Agreement, and it
will provide to any Governmental Authority notice of any actions under this Agreement that are
required by Applicable Laws and Regulations.
12.6. Compliance with All Applicable Laws and Regulations
The Developer will comply with all Applicable Laws and Regulations, including all
approvals, authorizations, orders, and permits issued by any Governmental Authority; all
Applicable Reliability Requirements, and all applicable Transmission Owner Technical
Standards in the performance of its obligations under this Agreement.
ARTICLE 13.
DISPUTE RESOLUTION
If a dispute arises under this Agreement, the Parties shall use the dispute resolution
process described in Article 11 of the NYISO’s Services Tariff, as such process may be amended
from time to time. Notwithstanding the process described in Article 11 of the NYISO’s Services
Tariff, the NYISO may terminate this Agreement in accordance with Article 8 of this
Agreement.
ARTICLE 14.
SURVIVAL
The rights and obligations of the Parties in this Agreement shall survive the termination,
expiration, or cancellation of this Agreement to the extent necessary to provide for the
determination and enforcement of said obligations arising from acts or events that occurred while
this Agreement was in effect. The remedies and rights and obligation upon termination
provisions in Articles 7.3 and 8.3 of this Agreement, the liability and indemnity provisions in
Article 9, and the billing and payment provisions in Article 3.6 of this Agreement shall survive
termination, expiration, or cancellation of this Agreement.
ARTICLE 15.
MISCELLANEOUS
15.1. Notices
Any notice or request made to or by any Party regarding this Agreement shall be made to
the Parties, as indicated below:
NYISO:
[Insert contact information.]
Developer:
[Insert contact information.]
15.2. Entire Agreement
Except as described below in this Section 15.2, this Agreement, including all Appendices
attached hereto, constitutes the entire agreement between the Parties with reference to the subject
matter hereof, and supersedes all prior and contemporaneous understandings of agreements, oral
or written, between the Parties with respect to the subject matter of this Agreement. There are no
other agreements, representations, warranties, or covenants that constitute any part of the
consideration for, or any condition to, either Party’s compliance with its obligation under this
Agreement.
Notwithstanding the foregoing, this Agreement is in addition to, and does not supersede
or limit the Developer’s and NYISO’s rights and responsibilities, under any interconnection
agreement(s) entered into by and among the NYISO, Developer, and Connecting Transmission
Owner(s) for the Transmission Project to interconnect to the New York State Transmission
System, as such interconnection agreements may be amended, supplemented, or modified from
time to time.
15.3. Cost Recovery
The Developer may recover the costs of the Transmission Project in accordance with the
cost recovery requirements in the ISO Tariffs.
15.4. Binding Effect
This Agreement, and the rights and obligations hereof, shall be binding upon and shall
inure to the benefit of the successors and permitted assigns of the Parties hereto.
15.5. Force Majeure
A Party that is unable to carry out an obligation imposed on it by this Agreement due to
Force Majeure shall notify the other Party in writing as soon as reasonably practicable after the
occurrence of the Force Majeure event and no later than the timeframe set forth in Article
3.3.3(i) if the Force Majeure event will result in a potential delay for the Developer to meet a
Critical Path Milestone. If the notifying Party is the Developer, it shall indicate in its notice
whether the occurrence of a Force Majeure event has the potential to delay its meeting one or
more Critical Path Milestones and/or completing the Transmission Project by the Required
Project In-Service Date. If the Force Majeure will delay the Developer’s ability to meet one or
more Critical Path Milestones, the Developer shall request with its notice a change to the
impacted milestones in accordance with the requirements in Section 3.3.4 and must satisfy the
requirements in Section 3.3.4 to change any Critical Path Milestones. A Party shall not be
responsible for any non-performance or considered in Breach or Default under this Agreement,
for any failure to perform any obligation under this Agreement to the extent that such failure is
due to Force Majeure and will not delay the Developer’s ability to complete the Transmission
Project by the Required Project In-Service Date. A Party shall be excused from whatever
performance is affected only for the duration of the Force Majeure and while the Party exercises
reasonable efforts to alleviate such situation. As soon as the nonperforming Party is able to
resume performance of its obligations excused because of the occurrence of Force Majeure, such
Party shall resume performance and give prompt notice thereof to the other Party. In the event
that Developer will not be able to complete the Transmission Project by the Required Project In-
Service Date because of the occurrence of Force Majeure, the NYISO may terminate this
Agreement in accordance with Section 8.1 of this Agreement.
15.6. Disclaimer
Except as provided in this Agreement, the Parties make no other representations,
warranties, covenants, guarantees, agreements or promises regarding the subject matter of this
Agreement.
15.7. No NYISO Liability for Review or Approval of Developer Materials
No review or approval by the NYISO or its subcontractor(s) of any agreement, document,
instrument, drawing, specifications, or design proposed by the Developer nor any inspection
carried out by the NYISO or its subcontractor(s) pursuant to this Agreement shall relieve the
Developer from any liability for any negligence in its preparation of such agreement, document,
instrument, drawing, specification, or design, or its carrying out of such works; or for its failure
to comply with the Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards with respect thereto, nor shall the NYISO be liable to
the Developer or any other person by reason of its or its subcontractor’s review or approval of an
agreement, document, instrument, drawing, specification, or design or such inspection.
15.8. Amendment
The Parties may by mutual agreement amend this Agreement, including the Appendices
to this Agreement, by a written instrument duly executed by both of the Parties. If the
Agreement was filed and accepted by FERC pursuant to Section 31.4.12.2 of Attachment Y of
the OATT, the NYISO shall promptly file the amended Agreement for acceptance with FERC.
15.9. No Third Party Beneficiaries
With the exception of the indemnification rights of the NYISO’s directors, officers,
employees, trustees, and agents under Article 9.2, this Agreement is not intended to and does not
create rights, remedies, or benefits of any character whatsoever in favor of any persons,
corporations, associations, or entities other than the Parties, and the obligations herein assumed
are solely for the use and benefit of the Parties, their successors in interest and their permitted
assigns.
15.10. Waiver
The failure of a Party to this Agreement to insist, on any occasion, upon strict
performance of any provision of this Agreement will not be considered a waiver of any
obligation, right, or duty of, or imposed upon, such Party. Any waiver at any time by either
Party of its rights with respect to this Agreement shall not be deemed a continuing waiver or a
waiver with respect to any other failure to comply with any other obligation, right, or duty of this
Agreement. Any waiver of this Agreement shall, if requested, be provided in writing.
15.11. Rules of Interpretation
This Agreement, unless a clear contrary intention appears, shall be construed and
interpreted as follows: (1) the singular number includes the plural number and vice versa; (2)
reference to any person includes such person’s successors and assigns but, in the case of a Party,
only if such successors and assigns are permitted by this Agreement, and reference to a person in
a particular capacity excludes such person in any other capacity or individually; (3) reference to
any agreement (including this Agreement), document, instrument or tariff means such
agreement, document, instrument, or tariff as amended or modified and in effect from time to
time in accordance with the terms thereof and, if applicable, the terms hereof; (4) reference to
any Applicable Laws and Regulations means such Applicable Laws and Regulations as
amended, modified, codified, or reenacted, in whole or in part, and in effect from time to time,
including, if applicable, rules and regulations promulgated thereunder; (5) unless expressly stated
otherwise, reference to any Article, Section or Appendix means such Article of this Agreement,
such Appendix to this Agreement, or such Section of this Agreement, as the case may be; (6)
“hereunder”, “hereof’, “herein”, “hereto” and words of similar import shall be deemed references
to this Agreement as a whole and not to any particular Article or other provision hereof or
thereof; (7) “including” (and with correlative meaning “include”) means including without
limiting the generality of any description preceding such term; and (8) relative to the
determination of any period of time, “from” means “from and including”, “to” means “to but
excluding” and “through” means “through and including”.
15.12. Severability
Each provision of this Agreement shall be considered severable and if, for any reason,
any provision is determined by a court or regulatory authority of competent jurisdiction to be
invalid, void, or unenforceable, the remaining provisions of this Agreement shall continue in full
force and effect and shall in no way be affected, impaired, or invalidated, and such invalid, void,
or unenforceable provision should be replaced with valid and enforceable provision or provisions
that otherwise give effect to the original intent of the invalid, void, or unenforceable provision.
15.13. Multiple Counterparts
This Agreement may be executed in two or more counterparts, each of which is deemed
an original, but all constitute one and the same instrument.
15.14. No Partnership
This Agreement shall not be interpreted or construed to create an association, joint
venture, agency relationship, or partnership among the Parties or to impose any partnership
obligation or partnership liability upon any Party. No Party shall have any right, power, or
authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an
agent or representative of, or otherwise bind, any other Party.
15.15. Headings
The descriptive headings of the various Articles and Sections of this Agreement have
been inserted for convenience of reference only and are of no significance in the interpretation or
construction of this Agreement.
15.16. Governing Law
This Agreement shall be governed, as applicable, by: (i) the Federal Power Act, and (ii)
the substantive law of the State of New York, without regard to any conflicts of laws provisions
thereof (except to the extent applicable, Sections 5-1401 and 5-1402 of the New York General
Obligations Law).
15.17. Jurisdiction and Venue
Any legal action or judicial proceeding regarding a dispute arising out of or relating to
this Agreement or any performance by either Party pursuant thereto that: (i) is within the primary
or exclusive jurisdiction of FERC shall be brought in the first instance at FERC, or (ii) is not
within the primary or exclusive jurisdiction of FERC shall be brought in, and fully and finally
resolved in, either, as applicable, the courts of the State of New York situated in Albany County,
New York or the United States District Court of the Northern District of New York situated in
Albany, New York.
IN WITNESS WHEREFORE, the Parties have executed this Agreement in duplicate originals,
each of which shall constitute an original Agreement between the Parties.
NYISO
By: _______________________
Title:______________________
Date:______________________
[Insert name of Developer]
By:_______________________
Title:______________________
Date:______________________
Appendix A
Project Description
Appendix C
Development Schedule
[To be prepared by Developer consistent with the Developer’s project information submission,
pursuant to Attachment C of the Public Policy Transmission Planning Process Manual, and
subject to acceptance by the NYISO, as required by Article 3.3 of this Agreement.]
The Developer shall demonstrate to the NYISO that it timely meets the following Critical
Path Milestones and Advisory Milestones and that such milestones remain in good standing.
Critical Path Milestones: [To be developed with consideration of each of the work plan
requirements submitted by the Developer pursuant to Attachment C to the Public Policy
Transmission Planning Process Manual and presented herein according to the sequence of the
critical path. The NYISO anticipates that the Developer’s critical path schedule will include
many of the example milestones set forth below and that most of the other example milestones
will be included as Advisory Milestones. The composition and sequence of the Critical Path
Milestones will differ depending on the Developer’s Transmission Project and schedule.]
Advisory Milestones: [To include in Development Schedule other milestones (e.g., periodic
project review meetings) that are not determined to be on the critical path, but that will be
monitored by the Developer and reported to NYISO.]
[Example Milestones:
Interconnection studies (e.g. Optional Feasibility Study, System Impact Study, Facilities
Study)
Siting activities (e.g. locating line routing, access roads, and substation site location
options)
Environmental impact studies (relative to siting options)
Engineering (initial)
Permitting and regulatory activities (e.g. Certificate of Environmental Compatibility and
Public Need)
Public outreach plan
Initiation of negotiation of key contracts and financing
Acquisition of all necessary approvals and authorizations of Governmental Authorities,
including identification of all required regulatory approvals
Closing of project financing
Completion of key contracts
Engineering (detailed)
Procurement of major equipment and materials
Environmental management & construction plan (for Article VII certification)
Acquisition of [all or %] required rights of way and property / demonstration of site
control
Surveying and geotechnical assessment (relative to line and station layouts)
Execution, or filing of unexecuted version, of interconnection agreement
Engineering (completed)
Delivery of major electrical equipment
Line and substation site work including milestones for foundations, towers, conductor
stringing, equipment delivery and installation, substation controls and communication,
security, etc.
Construction outage and restoration coordination plan
Completion, verification and testing
Operating and maintenance agreements and instructions
In-Service Date
Required Project In-Service Date]
6.10
Schedule 10 - Rate Mechanism for the Recovery of the Regulatedliability
Transmission Facilities Charge (“RTFC”)
6.10.1
Applicability.
6.10.1.1 Eligible Projects
This Schedule rate mechanism establishes the Regulatedliability Transmission Facilities
Charge (“RTFC”) for the recovery of the costs of a regulated transmission project that is eligible
for cost recovery in accordance with the Comprehensive System Planning Process requirements
set forth in Attachment Y of the ISO OATT.1 A Transmission Owner, Unregulated Transmitting
Utility,2 or Other Developer may recover through the RTFC the costs that it is eligible to recover
pursuant to Attachment Y of the ISO OATT for the recovery of costs related to: (i) a regulated
backstop transmission solution proposed by a Responsible Transmission Owneridentified by the
NYISO pursuant to Section 31.2.4.3.1 of Attachment Y of the ISO OATT and the NYISO/TO
Reliability Agreement or an Operating Agreement;, (ii) an alternative regulated transmission
solution provided that the ISO has selected such project pursuant to Section 31.2.6.5.2 of
Attachment Y of the ISO OATT as the more efficient or cost- effective solution to athe identified
Reliability Need;, or (iii) a regulated transmission Gap Solution proposed by a Responsible
Transmission Owner pursuant to Section 31.2.11.4 of Attachment Y of the ISO OATT; (iv) or an
alternative regulated transmission Gap Solution proposed by an Other Developer or
Transmission Owner that has been determined by the appropriate state regulatory agency(ies) as
the preferred solution(s) to athe identified Reliability Need pursuant to Section 31.2.11.5 of
Attachment Y of the ISO OATT; (v) a regulated economic transmission project that has been
1 Capitalized terms used in this Schedule that are not defined in this Schedule shall have the meaning set
forth in Section 31.1.1 of Attachment Y of the ISO OATT and, if not therein, in Section 1 of the OATT.
2 An “Unregulated Transmitting Utility” is a Transmission Owner, such as LIPA and NYPA, that,
pursuant to Section 201(f) of the Federal Power Act, is not subject to the Commission’s jurisdiction under
Sections 205 and 206(a) of the Federal Power Act.
approved pursuant to Section 31.5.4.6 of Attachment Y of the ISO OATT; (vi) a Public Policy
Transmission Project that the ISO has selected pursuant to Section 31.4.8.2 of Attachment Y of
the ISO OATT as the more efficient or cost-effective solution to a Public Policy Transmission
Need; (vii) a Public Policy Transmission Project proposed by a Developer in response to a
request by the NYPSC or Long Island Power Authority in accordance with Section 31.4.3.2 of
Attachment Y of the ISO OATT; or (viii) the portion of an Interregional Transmission Project
selected by the ISO in the CSPP that is allocated to the NYISO region pursuant to Section 31.5.7
of Attachment Y of the ISO OATT. For purposes of this Schedule, such a transmission project is
referred to as an “Eligible Project.” The costs incurred for an Eligible Project by LIPA or NYPA
will be billed and collected under a separate LIPA RTFC or NYPA RTFC, as applicable, as
described in Section 6.10.5.
6.10.1.2 Projects Not Eligible for Cost Recovery Through the RTFC
This Schedulee rate mechanism shall does not apply to projects that are not eligible
pursuant to Attachment Y of the ISO OATT for cost allocation and recovery under the ISO
OATT, including, but not limited to: (i) projects undertaken by Transmission Owners through
the pursuant to Local Transmission Owner Planning Processes pursuant to Section 31.1.3 and
Section 31.2.1 of Attachment Y of the NYISO OATT; (ii) market-based solutions to
transmission needs identified in the CSPP; (iii) any non-transmission components of an Eligible
Project (e.g., generation, energy efficiency, or demand response resources); (iv) transmission
Generator Deactivation Solutions selected in the Generator Deactivation Process pursuant to
Attachment FF of the ISO OATT and eligible for cost recovery through Schedule 16 (Section
6.16) of the ISO OATT; (v) transmission facilities eligible for cost recovery through another rate
schedule of the ISO OATT; and. The RFC shall be comprised of the revenue requirements
related to: (i) each regulated reliability transmission project filed with FERC by a Transmission
Owner pursuant to the provisions of this Attachment; (ii) any costs incurred by NYPA and filed
with FERC by the NYISO pursuant to the provisions of this Attachment; and (iii) any FERC
approved costs incurred by an Other Developer under Section 6.10.5 and filed with FERC by the
NYISO or Other Developer pursuant to the provisions of this Attachment. Any costs incurred by
LIPA and allocable to other Transmission Districts will be collected under a separate LIPA RFC
as set forth in Section 6.10.4.3 and filed with FERC by the NYISO pursuant to the provisions of
Section 6.10.4.3. This RFC will provide for full recovery of all reasonably incurred costs related
to the preparation of proposals for, and the development, construction, operation and
maintenance of any regulated reliability transmission project undertaken pursuant to
Attachment Y of this tariff, including all reasonable costs related to such a project that is halted
in accordance with the provisions of the NYISO’s tariff and the NYISO/TO Reliability
Agreement or an Operating Agreement. Subject to regulatory acceptance, the RFC shall include
a reasonable return on investment and any applicable incentives. The RFC established under this
Attachment shall be separate from (vi) facilities for which costs are recovered through the
Transmission Service Charge (“TSC”) orand the NYPA Transmission Adjustment Charge
(“NTAC”) determined in accordance with Attachment H of the NYISO OATT. With respect to
the recovery of costs incurred by LIPA and NYPA, the provisions of Sections 6.10.1, and 6.10.2
through 6.10.3.4 of this Attachment shall not apply to LIPA or NYPA, except as provided for in
Sections 6.10.4.3 and 6.10.4.4 of this Attachment. The recovery of costs related to development,
construction, operation and maintenance of a regulated reliability transmission project
undertaken by LIPA or NYPA shall be pursuant to the provisions of Sections 6.10.4.3 and
6.10.4.4 of this Attachment. The recovery of costs related to development, construction,
operation and maintenance of an alternative regulated solution proposed by an Other Developer
shall be pursuant to the provisions of Section 6.10.5 of this Attachment.
6.10.2
Recovery of Transmission Owner’s Costs Related to Regulated Reliability
Transmission Solutions.
Each Transmission Owner shall have on file at FERC the rate treatment that will be used
to derive and determine the revenue requirement to be included in the RFC, and for the LIPA
RFC as applicable, for regulated transmission projects undertaken pursuant to a determination by
the NYISO that a regulated solution is needed to address Reliability Needs identified by the
NYISO in its reliability planning process in accordance with Section 31.2.8 of Attachment Y of
the NYISO OATT. The filing will provide for the recovery of the full revenue requirement for a
regulated reliability transmission project consistent with FERC regulations including but not
limited to any incentives for the construction of transmission projects provided for in Section 219
of the Federal Power Act and the FERC regulations implementing that section. Pursuant to a
determination by the NYISO that a regulated solution is needed to address Reliability Needs
identified by the NYISO in its reliability planning process in accordance with Section 31.2.8 of
Attachment Y of the NYISO OATT, (i) the Responsible Transmission Owner(s) proceeding with
a regulated transmission backstop solution or (ii) a Transmission Owner proceeding with an
alternative regulated transmission solution that the ISO has selected as the more efficient or cost
effective solution, will proceed with the approval process for all necessary federal, state and local
authorizations for the requested project to which this RFC applies.
6.10.2.1
Upon receipt of all necessary federal, state, and local authorizations,
including FERC acceptance of the rate treatment, the Transmission Owner(s)
shall commence construction of the project.
6.10.2.2
Upon completion of the project, the Transmission Owner(s) or the NYISO
as applicable, will make an informational filing with FERC to provide the final
project cost and resulting revenue requirement to be recovered pursuant to this
Attachment. The final project cost and resulting revenue requirement will be
reduced by any amounts that, pursuant to Section 25.7.12.3.3 of Attachment S to
the NYISO OATT, have been previously committed by or collected from
Developers for the installation of System Deliverability Upgrades required for the
interconnection of generation or merchant transmission projects. The resulting
revenue requirement will become effective and recovery of project costs pursuant
to this Attachment will commence upon the making of the information filing with
FERC, and shall not require and shall not be dependent upon a re-opening or
review of the Transmission Owner(s)’ revenue requirements for the TSCs and
NTAC set forth in Attachment H of the NYISO OATT. This Section 6.10.2.2
also applies to the recovery of all reasonably incurred costs related to either (i) a
regulated backstop transmission project or (ii) an alternative regulated
transmission project that the ISO has selected as the more efficient or cost
effective solution and that is later halted, including but not limited to reasonable
and necessary expenses incurred to implement an orderly termination of the
project, in accordance with the provisions of the NYISO OATT and the
NYISO/TO Reliability Agreement or an Operating Agreement. Following the
information filing, the NYISO will bill the RFC or LIPA RFC, as applicable.
6.10.2.3
The Transmission Owners may propose a non-transmission solution
subject to state jurisdiction to address a Reliability Need included in the
Comprehensive Reliability Plan, provided that the appropriate state agency(ies)
has established procedures to ensure full and prompt recovery of all reasonably
incurred costs related to a project, comparable to those set forth in this tariff for
cost recovery for regulated reliability transmission projects.
6.10.23
RFC Revenue Requirement for RTFC Recovery.
The RTFC (including a LIPA RTFC or NYPA RTFC, as applicable) shall be calculated
in accordance with the formula set forth in Section 6.10.3 using the revenue requirement of the
Transmission Owner, Unregulated Transmitting Utility, or Other Developer, as applicable,
necessary to recover the costs of an Eligible Project. The revenue requirement to be used in the
calculation and recovery of the RTFC for a Transmission Owner or Other Developer, other than
an Unregulated Transmitting Utility, is described in Section 6.10.4. The development of a
revenue requirement and recovery of costs for an Eligible Project by an Unregulated
Transmitting Utility through a NYPA RTFC or a LIPA RTFC, as applicable, is described in
Section 6.10.5.
If an Eligible Project involves the construction of a facility identified as a Highway
System Deliverability Upgrade in a completed Class Year Interconnection Facilities Study, the
Project Cost Allocation for which has been accepted and Security posted by at least one Class
Year Developer, the project cost and resulting revenue requirement will be reduced to the extent
permitted by Section 25.7.12.3.3 of Attachment S of the ISO OATT.
6.10.3
Calculation and Recovery of RTFC and Payment of Recovered Revenue
6.10.3.1
The ISO will calculate and bill an RTFC (or a LIPA RTFC or NYPA
RTFC, as applicable) separately for each Eligible Project in accordance with this
Section 6.10.3. The ISO shall collect the RTFC from LSEs. The LSEs, including
Transmission Owners, competitive LSEs, municipal systems, and any other
LSEs, serving Load is to be billed by the NYISO and paid by the LSEs located in
the Load Zones and/or Subzones to which the costs of the Eligible
Projecttransmission facilities have been allocated (each a “Responsible LSE”)
shall pay the RTFC. The cost of each Eligible Project shall be allocated in
accordance with Attachment Y of the NYISO OATTas follows: (i) the costs of an
Eligible Project that is eligible for cost allocation and recovery through the
reliability planning process shall be allocated in accordance with Section 31.5.3 of
Attachment Y of the ISO OATT; (ii) the costs of an Eligible Project that is
eligible for cost allocation and recovery through the CARIS process shall be
allocated in accordance with Section 31.5.4 of Attachment Y of the ISO OATT;
(iii) the costs of an Eligible Project that is eligible for cost allocation and recovery
through the Public Policy Transmission Planning Process shall be allocated in
accordance with Section 31.5.5 of Attachment Y of the ISO OATT; and (iv) the
costs of an Eligible Project that is eligible for cost allocation and recovery as an
Interregional Transmission Project shall be allocated in accordance with Section
31.5.7 of Attachment Y of the ISO OATT. All LSEs in the Load Zones and/or
Subzones to which costs have been allocated, including Transmission Owners,
competitive LSEs and municipal systems, will be billed by the NYISO.
6.10.3.21
The revenue requirement established by the Transmission Owner or Other
Developer pursuant to Section 6.10.4 and an Unregulated Transmitting Utility
pursuant to Section 6.10.5filed pursuant to Section 6.10.2.2 will be the basis for
the applicable RTFC Rate ($/MWh) thatfor the Billing Period, and shall be
chargedapplied by the NYISO to each Responsible LSE based on its Actual
Energy Withdrawals as set forth in Section 6.10.3.54.
6.10.3.32
The Developer shall request Incremental TCCs with respect to the Eligible
Project in accordance with the requirements of Section 19.2.4 of Attachment M of
the ISO OATT and receive any Incremental TCCs to the extent awarded by the
ISO pursuant to such request. As it relates solely to the Eligible Project, the
Developer shall not be a “Transmission Owner” for purposes of Section 20.2.5 or
Section 20.3.7 of Attachment N of the ISO OATT and accordingly shall not
receive an allocation of Net Congestion Rents under Section 20.2.5 of Attachment
N of the ISO OATT or Net Auction Revenues under Section 20.3.7 of Attachment
N of the ISO OATT.
The Developer shall in relation to any Eligible Project exercise its right to
obtain and maintain in effect all Incremental TCCs, including temporary
Incremental TCCs, to which it has rights under Section 19.2.4 of Attachment M of
the ISO OATT and shall take the actions required to do so in accordance with the
procedures specified therein. Notwithstanding Sections 19.2.4.7 and 19.2.4.8 of
Attachment M of the ISO OATT, Incremental TCCs created and awarded to the
Developer as a result of implementation of an Eligible Project shall not be eligible
for sale in Secondary Markets. Incremental TCCs that may be created and
awarded to the Developer as a result of the implementation of an Eligible Project,
shall be offered by the Developer in all rounds of the six month Sub-Auction of
each Centralized TCC Auction conducted by the ISO. The ISO shall disburse the
associated auction revenues to the Developer. The total amount of the auction
revenues disbursed to the Developer pursuant to this Section 6.10.3.3 shall be
used in the calculation of the RTFC Rate, as set forth in Section 6.10.3.5.
Incremental TCCs associated with an Eligible Project shall continue to be offered
for the duration of the Incremental TCCs, established pursuant to the terms of
Attachment M of the ISO OATT.
The revenue offset discussed in this Section 6.10.3.3 shall commence
upon the first payment of revenues related to Incremental TCCs associated with
the implementation of an Eligible Project on or after the date the RTFC is
implemented. The RTFC and the revenue offset related to Incremental TCCs
associated with the implementation of an Eligible Project shall not require and
shall not be dependent upon a reopening or review of: (i) the Developer’s revenue
requirements for the RTFC of another Eligible Project pursuant to this Section
6.10 of the ISO OATT, (ii) the Developer’s revenue requirement for charges set
forth in another rate schedule of the ISO OATT, or (iii) the Transmission Owners’
revenue requirements for the TSCs or NTAC set forth in Attachment H of the ISO
OATT. To the extent that incremental transmission rights owned by the
Transmission Owner sponsoring the project are created as a result of a
transmission project implemented in accordance with Attachment Y of the
NYISO OATT, those incremental transmission rights that can be sold will be
auctioned or otherwise sold by the NYISO. The NYISO will disburse the
associated revenues to the Transmission Owner(s). The associated revenues will
be used in the calculation of the RFC as set forth in Section 6.10.3.4. The
incremental transmission rights will continue to be sold for the depreciable life of
the project, and the revenues offset discussed above will commence upon the first
payment of revenues related to a sale of incremental transmission rights on or
after the RFC is implemented for a specific project. These incremental revenues
shall not require and shall not be dependent upon any reopening or any review of
the Transmission Owner(s) TSCs or NTAC under Attachment H of the NYISO
OATT.
6.10.3.3.1
With respect to the Eligible Project only, the Developer shall receive the
outage charges described herein and shall not be charged O/R-t-S Congestion
Rent Shortfall Charges, U/D Congestion Rent Shortfall Charges, O/R-t-S Auction
Revenue Shortfall Charges or U/D Auction Revenue Shortfall Charges or be paid
O/R-t-S Congestion Rent Surplus Payments, U/D Congestion Rent Surplus
Payments, O/R-t-S Auction Revenue Surplus Payments or U/D Auction Revenue
Surplus Payments under Section 20.2.4 and Section 20.3.6 of Attachment N of the
ISO OATT. Outage charges related to any Incremental TCCs awarded by the ISO
for an Eligible Project shall be assessed to the Developer, and payable by the
Developer to the ISO, pursuant to Section 19.2.4 of Attachment M of the ISO
OATT for an Expander not subject to Section 20.2.5 of Attachment N of the ISO
OATT for any hour in the Day-Ahead Market during which an Expansion,
associated with an Eligible Project, is modeled to be wholly or partially out of
service.
The NYISO will collect the appropriate RFC revenues each Billing Period and
remit those revenues to the appropriate Transmission Owner(s) in accordance
with the NYISO’s billing and settlement procedures pursuant to Section 2.7.2.5 of
the NYISO OATT.
6.10.3.4
The Bbilling Uunits for the RTFC Rate for the Billing Period shall be
based on the Actual Energy Withdrawals available for the current Billing Period
for those Load Zones and/or Subzones determined to be allocated the costs of the
project in the manner described in Section 6.10.3.1in accordance with Attachment
Y of the NYISO OATT.
6.10.3.5 Cost Recovery Methodology
The ISO shall calculate the RTFC for each Eligible Project for each Responsible LSE as
follows:
Step 1: Calculate the $ assigned to each Load Zone or Subzone (as applicable)
ܴܨܥ௭, = � ��ܣ݊݊ݑ݈ܴܴܽ, − ܫ݊ܿݎ݁݉݁݊ݐ݈ܽܶݎܽ݊ݏ݉݅ݏݏܴ݅݊݅݃ℎݐݏܴ݁ݒ݁݊ݑ݁, � ∗ (ܼ݈݊ܽܥݏݐܣ݈݈ܿܽݐ݅݊% )�
∈
RTFCp,z,B = �AnnualRRp,B − IncrementalTransmissionRightsRevenuep,B + OutageCostAdjustmentp,B�
× �ZonalCostAllocationz,p�
Step 2: Calculate a per-MWh Rate for each Load Zone or Subzone (as applicable)
RTFCRatep,z,B = RTFCp,z,B/MWhz,B
Step 3: Calculate charge for each Billing Period for each Responsible LSE in each
Load Zone or Subzone (as applicable)
ChargeB,l1,z,p = RTFCRatep,z,B ∗ MWhl1,z,B
Step 4: Calculate charge for each Billing Period for each Responsible LSE across all
Load Zones or Subzones (as applicable)
ChargeB,l1,p = ��ChargeB,l1,z,p�
z∈Z
Where,
l = the relevant Responsible LSE;
p = an individual Eligible Project;
P = set of Projects.
z = an individual Load Zone or Subzone, as applicable;
Z = set of ISO Load Zones or Subzones, as applicable;.
B = the relevant Billing Period;.
MWhz,B = Actual Energy Withdrawals in Load Zone or Subzone, as applicable, z aggregated
across all hours in Billing Period B;.
MWh l, z, Bl1,z,B = Actual Energy Withdrawals for Responsible LSE l in Load Zone or Subzone,
as applicable, z aggregated across all hours in Billing Period B;.
AnnualRRp,B = the pro rata share of the annual Rrevenue Rrequirement for each Eligible Project
p as discussed in Section 6.10.2.2 above, allocated for Billing Period B;.
IncrementalTransmissionRightsRevenuep,B = the auction revenue derived from the sale of
Incremental TCCs plus Incremental TCC payments received by the Developer pursuant to
Section 20.2.3 of Attachment N of the ISO OATT for each Eligible Project p, as discussed in
Section 6.10.3.3 above, allocated for Billing Period B. The revenues from the sale of
Incremental TCCs in the ISO’s six month Sub-Auctions of each Centralized TCC Auction shall
be allocated uniformly across all hours of the Billing Period;the pro rata share of the Incremental
Transmission Rights Revenue for each Project as discussed in Section 6.10.3.2 above allocated
for Billing Period B.
OutageCostAdjustmentp,B = the Outage charges determined pursuant to Section 6.10.3.3.1 above
for any hour in the Day-Ahead Market during which the Eligible Project p is modeled to be
wholly or partially out of service aggregated across all hours in Billing Period B; and
ZonalCostAllocationz,p = the proportion of the cost of Eligible Project p allocated to Load Zone
or Subzone, as applicable, z, in the manner described in Section 6.10.3.1 above.
6.10.3.6
The NYISO will collect the appropriate RTFC revenues each Billing
Period and remit those revenues to the appropriate Transmission Owner(s),
Unregulated Transmitting Utility, or Other Developer in accordance with the
NYISO’s billing and settlement procedures pursuant to Section 2.7.2.5 of the
NYISO OATT; provided, however, that LIPA will be responsible for billing and
collecting the costs of an Eligible Project undertaken by LIPA that are allocated to
customers within the Long Island Transmission District in accordance with
Section 6.10.5.2.1.
6.10.4
Recovery of Costs Incurred by Transmission Owner or Other Developer
6.10.4.1
The RTFC shall be used as the cost recovery mechanism for the recovery
of the costs of an Eligible Project undertaken by a Transmission Owner or Other
Developer, other than an Unregulated Transmitting Utility, which project is
authorized by the Commission to recover costs under this rate mechanism;
provided, however, nothing in this cost recovery mechanism shall be deemed to
create any additional rights for a Transmission Owner or Other Developer to
proceed with a regulated transmission project that it does not otherwise have at
law. The costs that may be included in the revenue requirement for calculating
the RTFC pursuant to Section 6.10.3 include all reasonably incurred costs, as
determined by the Commission, related to the preparation of proposals for, and
the development, financing, construction, operation, and maintenance of, an
Eligible Project, including those costs explicitly permitted for recovery pursuant
to Attachment Y of the ISO OATT. These costs include, but are not limited to, a
reasonable return on investment and any incentives for the construction of
transmission projects approved under Section 205 or Section 219 of the Federal
Power Act and the Commission’s regulations implementing those sections.
6.10.4.2
The period for cost recovery will be determined by the Commission and
will begin if and when the Eligible Project enters into service, is halted, or as
otherwise determined by the Commission, including for the recovery of CWIP or
other permissible cost recovery. The Transmission Owner/Other Developer, or, at
its request, the ISO, shall either make a Section 205 filing with the Commission or
make an informational filing under a formula rate to provide for the
Commission’s review and approval or acceptance of the project cost and resulting
revenue requirement to be recovered through the RTFC. The filing may include
all reasonably incurred costs specified in Section 6.10.4.1 of this Schedule that are
related to the Transmission Owner’s or the Other Developer’s undertaking an
Eligible Project. The filing must be consistent with the Transmission Owner’s or
the Other Developer’s project proposal made to and evaluated by the ISO
pursuant to Attachment Y. The Transmission Owner or Other Developer shall
bear the burden of resolving all concerns about the contents of the filing that
might be raised in such proceeding. The ISO will begin to calculate and bill the
RTFC in accordance with the period for cost recovery determined by the
Commission after the Commission has accepted or approved the filing or
otherwise allowed the filing to go into effect pursuant to a formula rate.
6.10.5
Recovery of Costs by an Unregulated Transmitting Utility.
An Unregulated Transmitting Utility is a Transmission Owner that, pursuant to Section
201(f) of the FPA is not subject to the Commission’s jurisdiction under Sections 205 and 206 of
the FPA. The recovery of costs related to the preparation of proposals for, and the development,
construction, operation and maintenance of, a regulated reliability transmission project
undertaken pursuant to Attachment Y of the NYISO OATT by LIPA, as an Unregulated
Transmitting Utility, shall be conducted as follows:
6.10.4.1
Upon the request of the NYISO, an Unregulated Transmitting Utility will
proceed with the process of receiving any necessary authorization for the
requested project.
6.10.4.2
Upon receipt of all necessary federal, state and local authorizations, the
Unregulated Transmitting Utility shall commence with construction of the project.
6.10.5.1
The costs that may be included in the revenue requirement for an Eligible
Project undertaken by an Unregulated Transmitting Utility include all reasonably
incurred costs related to the preparation of proposals for, and the development,
financing, construction, operation, and maintenance of, an Eligible Project,
including those costs explicitly permitted for recovery pursuant to Attachment Y
of the ISO OATT, as well as a reasonable return on investment. Except as
otherwise provided in Section 6.10.5.2.1, for any recovery of a revenue
requirement by an Unregulated Transmitting Utility under the RTFC, the period
of cost recovery will be determined by the Commission and will begin if and
when the Eligible Project enters into service, is halted, or as otherwise determined
by the Commission, including for the recovery of CWIP or other permissible cost
recovery. Except as otherwise provided in Section 6.10.5.2.1, the ISO will begin
to calculate and bill the RTFC for an Unregulated Transmitting Utility pursuant to
Section 6.10.3 in accordance with the period for cost recovery determined by the
Commission after the Commission has accepted or approved the filing of its
revenue requirement or otherwise allowed the filing to go into effect pursuant to a
formula rate.
6.10.54.23 Cost Recovery for LIPA
Transmission Owners other than LIPA that propose an alternative regulated transmission
project on Long Island would recover any costs per Sections 6.10.2 through 6.10.3.4 of this
Attachment. Other Developers that propose an alternative regulated transmission project on
Long Island would recover any costs per Section 6.10.5 of this Attachment.
6.10.4.3.1
Any costs incurred for an regulated backstop reliability transmission
Eligible pProject or an alternative regulated transmission project undertaken by LIPA, as an
Unregulated Transmitting Utility, that are eligible for recovery under Section 6.10.5.1 under athe
LIPA RTFC shall be recovered over the period established by Long Island Power Authority’s
Board of Trustees as follows:
6.10.54.23.1.1 For costs to LIPA customers: Cost will be recovered pursuant to a rate
recovery mechanism approved by the Long Island Power Authority’s Board of
Trustees pursuant to Article 5, Title 1-A of the New York Public Authorities Law,
Sections 1020-f(u) and 1020-s. Upon approval of the rate recovery mechanism,
LIPA shall provide to the NYISO, for purposes of inclusion within the NYISO
OATT and filing with the CommissionFERC on an informational basis only, a
description of the rate recovery mechanism, the costs of the Eligible Project, and
the rate that LIPA will charge and collect from responsible entities within the
Long Island Transmission District in accordance with the NYISO cost allocation
methodology pursuant to Section 31.5.3.2 of Attachment Y of the NYISO OATT.
6.10.54.23.21.2
For Costs to Other Transmission Districts, As Applicable: Where
the NYISO determines that there are rResponsible LSEsentities serving Load
outside of the Long Island Transmission District that should be allocated a portion
of the costs of the Eligible Project regulated backstop reliability transmission
solution or an alternative regulated transmission solution undertaken by LIPA,
LIPA shall coordinate with and inform the NYISO of the amount of such costs.
Such costs will be an allocable amount of the cost base recovered through the
recovery mechanism described in Section 6.10.54.23.1.1 in accordance with the
formula set forth in Section 6.10.3.54. TheSuch costs of the Eligible Projecta
LIPA regulated backstop reliability transmission project or an alternative
regulated transmission solution, allocable to rResponsible LSEsentities serving
Load outside of the Long Island Transmission District shall constitute the
“revenue requirement.” that the NYISO shall include and, and recover through, a
separate “LIPA RFC”. The NYISO shall file the revenue requirementLIPA RFC
with the Commission if requested to do so by LIPA, as an informational filing.
The NYISO will file such RFC for Commission review under the same
“comparability” standard as is applied to review of changes in LIPA’s TSC under
Attachment H of the ISO OATTis tariff. The filing must be consistent with
LIPA’s project proposal made to and evaluated by the ISO pursuant to
Attachment Y. LIPA shall intervene in support of such filing at the Commission
and shall bear the burden of take the responsibility to resolvinge all concerns
about the contents of the filing that might be raised in such proceeding. Upon the
Commission’s acceptance for filing of LIPA’s revenue requirement and using the
procedures described in Sections 6.10.3.1 through 6.10.3.5 of this Schedule, Tthe
NYISO shall calculate a separate LIPA RTFC based on the revenue requirement
and shall bill for LIPA the LIPA RTFC as a separate line item to the rResponsible
LSEsentities serving Load in Transmission Districts located outside of other than
the Long Island Transmission District. consistent with Sections 6.10.3.1 through
6.10.3.4 and The ISO shall remit the revenues collected to LIPA in accordance
with the ISO’s billing and settlement procedureseach Billing Period.
6.10.5.3 Cost Recovery for NYPA
Any costs incurred for an Eligible Project undertaken by NYPA, as an Unregulated
Transmitting Utility, that are eligible for recovery under Section 6.10.5.1 shall be recovered
under a NYPA RTFC as described herein. A reasonable return on investment for an Eligible
Project undertaken by NYPA may include any incentives for construction of transmission
projects available under Section 205 or Section 219 of the Federal Power Act and the
Commission’s regulations implementing those sections, as determined by the Commission.
6.10.5.3.1
NYPA shall coordinate with and inform the ISO of the amount of the costs
it incurred in undertaking an Eligible Project. Such costs shall constitute the
revenue requirement. Either the ISO shall make a Section 205 filing with the
Commission on behalf of NYPA or NYPA shall make an informational filing
under a formula rate with the Commission, of the revenue requirement. The filing
must be consistent with NYPA’s project proposal made to and evaluated by the
ISO pursuant to Attachment Y. NYPA shall intervene in support of such filing at
the Commission and shall bear the burden of resolving all concerns about the
contents of the filing that might be raised in such proceeding, including being
solely responsible for making any arguments or reservations regarding its status
as a non-Commission-jurisdictional utility and the appropriate standard for
Commission review of its revenue requirement. After the Commission has
accepted or approved the filing or otherwise allowed the filing to go into effect
pursuant to a formula rate, the ISO shall calculate in accordance with Sections
6.10.3.1 through 6.10.3.5 of this Schedule a separate NYPA RTFC based on the
revenue requirement and bill for NYPA the NYPA RTFC to the Responsible
LSEs. The ISO shall remit the revenues collected to NYPA in accordance with
the ISO’s billing and settlement procedures.
6.10.54.4
Savings Clause. The inclusion in the NYISO OATT or in a FERC filing
with the Commission pursuant to Section 6.10.5 of the revenue requirement on an
informational basis of the charges for recovery of costs incurred by an
Unregulated Transmitting Utility, including LIPA or NYPA, related to an Eligible
Project regulated project undertaken pursuant to Attachment Y ofinto the NYISO
OATT, as provided for in this Sections 6.10.54.3 and 6.10.4.4, or the inclusion of
such revenue requirementcharges in the LIPA RTFC or NYPA RTFC NYISO
RFC pursuant to Section 6.10.4.3.1.2, shall not be deemed to modify the treatment
of such rates as non-jurisdictional pursuant to Section 201(f) of the FPA.
6.10.5
Recovery of Costs Incurred by an Other Developer Related to an
Alternative Regulated Solution.
6.10.5.1
The RFC shall be used as the cost recovery mechanism for the recovery of
the costs of an alternative regulated transmission solution that has been selected
by the ISO as the more efficient or cost effective solution to the identified
Reliability Need, and is authorized by FERC to recover costs under this rate
mechanism. Provided however, nothing in this cost recovery mechanism shall be
deemed to create any additional rights for an Other Developer to proceed with a
regulated transmission project that such Other Developer does not otherwise have
at law. The provisions of Sections 6.10.3 through 6.10.3.4 of this Attachment
shall be applicable to the recovery of the costs incurred by an Other Developer for
proposing, developing, constructing, operating, maintaining, and financing an
alternative regulated transmission project that the ISO has selected as the more
efficient or cost effective solution to the identified Reliability Need .
6.10.5.2
Upon receipt of all necessary federal, state, and local authorizations,
including FERC acceptance of a Section 205 filing authorizing cost recovery
under the NYISO tariff, the Other Developer shall commence construction of the
project . Upon completion of the project, the Other Developer and/or the NYISO,
as applicable, will make a filing with FERC to provide the final project cost and
resulting revenue requirement to be recovered pursuant to this Attachment. The
resulting revenue requirement will become effective and recovery of project costs
pursuant to this Attachment will commence upon the acceptance of the filing by
FERC. This Section 6.10.5.2 also applies to the recovery of all reasonably
incurred costs related to a project that the ISO has selected as the more efficient or
cost effective solution, and is later halted in accordance with the provisions of the
NYISO OATT, including but not limited to reasonable and necessary expenses
incurred to implement an orderly termination of the project.
6.10.5.3
Other Developers may also propose a non-transmission solution subject to
state jurisdiction to address a Reliability Need included in the Comprehensive
Reliability Plan.
31.2
Reliability Planning Process
31.2.1
Local Transmission Owner Planning Process
31.2.1.1 Scope
31.2.1.1.1 Criteria, Assumptions and Data
Each Transmission Owner will post on its website the planning criteria and assumptions
currently used in its LTPP as well as a list of any applicable software and/or analytical tools
currently used in the LTPP. Customers, Market Participants and other interested parties may
review and comment on the planning criteria and assumptions used by each Transmission
Owner, as well as other data and models used by each Transmission Owner in its LTPP. The
Transmission Owners will take into consideration any comments received. Any planning criteria
or assumptions for a Transmission Owner’s BPTFs will meet or exceed any applicable NERC,
NPCC or NYSRC criteria. The LTPP shall include a description of the needs addressed by the
LTPP as well as the assumptions, applicable planning criteria and methodology utilized and the
Public Policy Requirements considered. A link to each Transmission Owner’s website will be
posted on the ISO website.
31.2.1.1.2 Consideration of Transmission Needs Driven by Public Policy
Requirements
31.2.1.1.2.1 Procedures for the Identification of Transmission Needs Driven by
Public Policy Requirements in Local Transmission Plans and for the
Consideration of Transmission Solutions
In developing its LTP, each Transmission Owner shall consider whether there is a
transmission need on its system that is being driven by a Public Policy Requirement. The LTP
will identify any transmission project included in the LTP as a solution to a transmission need
being driven by a Public Policy Requirement. In evaluating potential transmission solutions, the
Transmission Owner will give consideration to the objectives of the Public Policy
Requirement(s) driving the need for transmission.
31.2.1.1.2.2 Determination of Local Transmission Needs Driven by Public Policy
Requirements
As part of its LTP process pursuant to Section 31.2.1.2 below, each Transmission Owner
will consider whether there is a transmission need on its local system that is being driven by a
Public Policy Requirement for which a local transmission solution should be evaluated,
including needs proposed by market participants and other interested parties. A market
participant or other interested party proposing a transmission need on a Transmission Owner’s
local system driven by a Public Policy Requirement shall submit its proposal to the ISO and the
relevant Transmission Owner, and will identify the specific Public Policy Requirement that is
driving the proposed transmission need and an explanation of why a local transmission upgrade
is necessary to implement the Public Policy Requirement. Any proposed local system
transmission need will be posted on the ISO website. The ISO will transmit proposed
transmission needs on a Transmission Owner’s local system driven by Public Policy
Requirements to the NYDPS, with a request that the NYDPS review the proposals and provide
the relevant Transmission Owner with input to assist the Transmission Owner in its
determination. The Transmission Owner, after considering the input provided by the NYDPS
and any information provided by a market participant or other party, will determine whether
there are transmission needs driven by Public Policy Requirements for which local transmission
solutions should be evaluated. The Transmission Owner will post on its website a list of the
transmission needs driven by Public Policy Requirements for which local transmission solutions
should be evaluated, with an explanation of why the Transmission Owner identified those
transmission needs and declined to identify other proposed transmission needs.
31.2.1.1.2.3 Evaluation of Proposed Local Transmission Solutions
In evaluating potential transmission solutions, if any, the Transmission Owner will give
consideration to the objectives of the Public Policy Requirement driving the need for a local
transmission solution. The Transmission Owner will evaluate solutions to identified
transmission needs, including transmission solutions proposed by market participants and other
parties for inclusion in its LTP. The Transmission Owner, in consultation with the NYDPS, will
evaluate proposed transmission solutions on its local system to determine the more efficient or
cost-effective transmission solutions. The Transmission Owner will consider the relative costs
and benefits of proposed transmission solutions and their impact on the Transmission Owner’s
transmission system and its customers. Any local transmission solution identified by the
Transmission Owner through the LTP process will be reviewed with stakeholders as part of each
Transmission Owner’s regular LTP process and will be included in the Transmission Owner’s
subsequent LTP. In conducting its evaluation the Transmission Owner will use criteria that are
relevant to the Public Policy Requirement driving the transmission need, which may include its
published local planning criteria and assumptions.
31.2.1.2 Process Timeline
31.2.1.2.1
Each Transmission Owner, in accordance with a schedule set forth in the
ISO Procedures, will post its current LTP on its website for review and comment
by interested parties sufficiently in advance of the time for submission to the ISO
for input to its RNA so as to allow adequate time for stakeholder review and
comment. Each LTP will include:
identification of the planning horizon covered by the LTP,
data and models used,
reliability needs, needs driven by Public Policy Requirements, and other needs
addressed,
potential solutions under consideration, and,
a description of the transmission facilities covered by the plan.
31.2.1.2.2
To the extent the current LTP utilizes data or inputs, related to the ISO’s
planning process, not already reported by the ISO in Form 715 and referenced on
its website, any such data will be provided to the ISO at the time each
Transmission Owner posts criteria and planning assumptions in accordance with
Section 31.2.1.1 and will be posted by the ISO on its website subject to any
confidentiality or Critical Energy Infrastructure Information restrictions or
requirements.
31.2.1.2.3
Each planning cycle, the ISO shall hold one or more stakeholder meetings
of the ESPWG and TPAS at which each Transmission Owner’s current LTP will
be discussed. Such meetings will be held either at the Transmission Owner’s
Transmission District, or at an ISO location. The ISO shall post notice of the
meeting and shall disclose the agenda and any other material distributed prior to
the meeting.
31.2.1.2.4
Interested parties may submit written comments to a Transmission Owner
with respect to its current LTP within thirty days after the meeting. Each
Transmission Owner shall list on its website, as part of its LTP, the person and/or
location to which comments should be sent by interested parties. All comments
will be posted on the ISO website. Each Transmission Owner will consider
comments received in developing any modifications to its LTP. Any such
modification will be explained in its current LTP posted on its website pursuant to
Section 31.2.1.2.2 above and discussed at the next meeting held pursuant to
Section 31.2.1.2.3 above.
31.2.1.2.5
Each planning cycle, each Transmission Owner will submit the finalized
portions of its current LTP to the ISO as contemplated in Section 31.2.2.4.2 below
for timely inclusion in the RNA.
31.2.1.3 ISO Evaluation of Transmission Owner Local Transmission Plans in
Relation to Regional and Local Transmission Needs
The ISO will review the Transmission Owner LTPs as they relate to the BPTFs as set
forth in Section 31.2.2.4.2. The ISO will also evaluate whether a regional transmission solution
- including, but not limited to, regional transmission solutions proposed by Developers pursuant
to this Attachment Y - could satisfy an identified regional transmission need on the BPTFs that
impacts more than one Transmission District more efficiently or more cost effectively than a
local transmission solution identified in a Transmission Owner’s LTP in accordance with Section
31.2.6.4.2 for the satisfaction of a regional Reliability Need, Section 31.3.1.3.6 for the reduction
of congestion identified in CARIS, or Section 31.4.7.2 for the satisfaction of a Public Policy
Transmission Need. The ISO will report the results of its evaluation solely for informational
purposes in the relevant ISO planning report prepared under this Attachment Y, and the
Transmission Owners shall not be required to revise their LTPs based on the results of the ISO’s
evaluation.
31.2.1.4 LTP Dispute Resolution Process
31.2.1.4.1 Disputes Related to the LTPP; Objective; Notice
Disputes related to the LTPP are subject to the DRP. The objective of the DRP is to
assist parties having disputes in communicating effectively and resolving disputes as
expeditiously as possible. Within fifteen (15) calendar days of the presentation by a
Transmission Owner of its LTP to the ESPWG and TPAS, a party with a dispute shall notify in
writing the Affected TO, the ISO, the ESPWG and TPAS of its intention to utilize the DRP. The
notice shall identify the specific issue in dispute and describe in sufficient detail the nature of the
dispute.
31.2.1.4.2 Review by the ESPWG/TPAS
The issue raised by a party with a dispute shall be reviewed and discussed at a joint
meeting of the ESPWG and the TPAS in an effort to resolve the dispute. The party with a
dispute and the Affected TO shall have an opportunity to present information concerning the
issue in dispute to the ESPWG and the TPAS.
31.2.1.4.3 Information Discussions
To the extent the ESPWG and the TPAS are unable to resolve the dispute, the dispute
will be subject to good faith informal discussions between the party with a dispute and the
Affected TO. Each of those parties will designate a senior representative authorized to enter into
informal discussions and to resolve the dispute. The parties to the dispute shall make a good
faith effort to resolve the dispute through informal discussions as promptly as practicable.
31.2.1.4.4 Alternative Dispute Resolution
In the event that the parties to the dispute are unable to resolve the dispute through
informal discussions within sixty (60) days, or such other period as the parties may agree upon,
the parties may, by mutual agreement, submit the dispute to mediation or any other form of
alternative dispute resolution. The parties shall attempt in good faith to resolve the dispute in
accordance with a mutually agreed upon schedule but in no event may the schedule extend
beyond ninety (90) days from the date on which the parties agreed to submit the dispute to
alternative dispute resolution.
31.2.1.4.5 Notice of Results of Dispute Resolution
The Affected TO shall notify the ISO and ESPWG and TPAS of the results of the DRP
and update its LTP to the extent necessary. The ISO shall use in its planning process the LTP
provided by the Affected TO.
31.2.1.4.6 Rights Under the Federal Power Act
Nothing in the DRP shall affect the rights of any party to file a complaint with the
Commission under relevant provisions of the FPA.
31.2.1.4.7 Confidentiality
All information disclosed in the course of the DRP shall be subject to the same
protections accorded to confidential information and CEII by the ISO under its confidentiality
and CEII policies.
31.2.2
Reliability Needs Assessment
31.2.2.1 General
The ISO shall prepare and publish the RNA as described below. The RNA will identify
Reliability Needs. The ISO shall also designate in the RNA the Responsible Transmission
Owner with respect to each Reliability Need.
31.2.2.2 Interested Party Participation in the Development of the RNA
The ISO shall develop the RNA in consultation with Market Participants and all other
interested parties. TPAS will have responsibility consistent with ISO Procedures for review of
the ISO’s reliability analyses. ESPWG will have responsibility consistent with ISO Procedures
for providing commercial input and assumptions to be used in the development of reliability
assessment scenarios provided under Section 31.2.2.5, and in the reporting and analysis of
historic congestion costs. Coordination and communication will be established and maintained
between these two groups and ISO staff to allow Market Participants and other interested parties
to participate in a meaningful way during each stage of the CSPP. The ISO staff shall report any
majority and minority views of these collaborative governance work groups when it submits the
RNA to the Operating Committee for a vote, as provided below.
31.2.2.3 Preparation of the Reliability Needs Assessment
31.2.2.3.1
The ISO shall evaluate bulk power system needs in the RNA over the
Study Period.
31.2.2.3.2
The starting point for the development of the RNA Base Case will be the
system as defined for the FERC Form No. 715 Base Case. The ISO shall develop
this system representation to be used for its evaluations of the Study Period by
primarily using: (1) the most recent NYISO Load and Capacity Data Report
published by the ISO on its web site; (2) the most recent versions of ISO
reliability analyses and assessments provided for or published by NERC, NPCC,
NYSRC, and neighboring Control Areas; (3) information reported by neighboring
Control Areas such as power flow data, forecasted load, significant new or
modified generation and transmission facilities, and anticipated system conditions
that the ISO determines may impact the BPTFs; and (4) data submitted pursuant
to paragraph 31.2.2.4 below; provided, however, the ISO shall not include in the
RNA Base Case an RMR Generator or an interim non-RMR Generator
Deactivation Solution selected by the ISO pursuant to Attachment FF of the ISO
OATT; provided, further, the ISO will include in the RNA Base Case a
permanent non-RMR Generator Deactivation Solution selected by the ISO
pursuant to Attachment FF of the ISO OATT if it meets the base case inclusion
requirements in the ISO Procedures. The details of the development of the RNA
Base Case are contained in the ISO Procedures. The RNA Base Case shall also
include Interregional Transmission Projects that have been approved by the
NYPSC transmission siting process and meet the base case inclusion requirements
in the ISO Procedures.
31.2.2.3.3
The ISO shall assess the RNA Base Case to determine whether the BPTFs
meet all Reliability Criteria for both resource and transmission adequacy in each
year, and report the results of its evaluation in the RNA. Transmission analyses
will include thermal, voltage, short circuit, and stability studies. Then, if any
Reliability Criteria are not met in any year, the ISO shall perform additional
analyses to determine whether additional resources and/or transmission capacity
expansion are needed to meet those requirements, and to determine the Target
Year of need for those additional resources and/or transmission. A short circuit
assessment will be performed for the tenth year of the Study Period. The study
will not seek to identify specific additional facilities. Reliability Needs will be
defined in terms of total deficiencies relative to Reliability Criteria and not
necessarily in terms of specific facilities.
31.2.2.4 Planning Participant Data Input
31.2.2.4.1
At the ISO’s request, Market Participants, Developers, and other parties
shall provide, in accordance with the schedule set forth in the ISO Procedures, the
data necessary for the development of the RNA. This data will include but not be
limited to (1) existing and planned additions to the New York State Transmission
System (to be provided by Transmission Owners and municipal electric utilities);
(2) proposals for merchant transmission facilities (to be provided by merchant
Developers); (3) generation additions and retirements (to be provided by
generator owners and Developers); (4) demand response programs (to be provided
by demand response providers); and (5) any long-term firm transmission requests
made to the ISO.
31.2.2.4.2
The Transmission Owners shall submit their current LTPs referenced in
Section 31.1.3 and Section 31.2.1 to the ISO. The Transmission Owners and the
ISO will coordinate with each other in reviewing the LTPs. The ISO will review
the Transmission Owners’ LTPs, as they relate to BPTFs, to determine whether
they will meet reliability needs identified in the LTPs, recommend an alternate
means to resolve the local needs from a regional perspective pursuant to Section
31.2.6.4, and indicate if it is not in agreement with a Transmission Owner’s
proposed additions. The ISO shall report its determinations under this section in
the RNA and in the CRP.
31.2.2.4.3
All data received from Market Participants, Developers, and other parties
shall be considered in the development of the system representation for the Study
Period in accordance with the ISO Procedures.
31.2.2.5 Reliability Scenario Development
The ISO, in consultation with the ESPWG and TPAS, shall develop reliability scenarios
addressing the Study Period. Variables for consideration in the development of these reliability
scenarios include but are not limited to: load forecast uncertainty, fuel prices and availability,
new resources, retirements, transmission network topology, and limitations imposed by proposed
environmental or other legislation.
31.2.2.6 Evaluation of Reliability Scenarios
The ISO will conduct additional reliability analyses for the reliability scenarios
developed pursuant to paragraph 31.2.2.5. These evaluations will test the robustness of the needs
assessment studies conducted under paragraphs 31.2.2.3. This evaluation will only identify
conditions under which Reliability Criteria may not be met. It will not identify or propose
additional Reliability Needs. In addition, the ISO will perform appropriate sensitivity studies to
determine whether Reliability Needs previously identified can be mitigated through alternate
system configurations or operational modes. The Reliability Needs may increase in some
reliability scenarios and may decrease, or even be eliminated, in others. The ISO shall report the
results of these evaluations in the RNA.
31.2.2.7 Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of the
reliability transmission projects on such ISO/RTO Regions using the respective planning criteria
of such ISO/RTO Regions. The ISO shall report the results in the CRP. The ISO shall not bear
the costs of required upgrades in another region.
31.2.2.8 Reliability Needs Assessment Report Preparation
Once all the analyses described above have been completed, ISO staff will prepare a draft
of the RNA including discussion of its assumptions, Reliability Criteria, and results of the
analyses and, if necessary, designate the Responsible Transmission Owner. One or more
compensatory MW/ Load adjustment scenarios will be developed by the ISO as a guide to the
development of proposed solutions to meet the identified Reliability Need.
31.2.3
RNA Review Process
31.2.3.1 Collaborative Governance Process
The draft RNA shall be submitted to both TPAS and the ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft RNA. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Market Participants and
other interested parties may submit at any time optional suggestions for changes to ISO rules or
procedures which could result in the identification of additional resources or market alternatives
suitable for meeting Reliability Needs. Following completion of the TPAS and ESPWG review,
the draft RNA reflecting the revisions resulting from the TPAS and ESPWG review, shall be
forwarded to the Operating Committee for discussion and action. The ISO shall notify the
Business Issues Committee of the date of the Operating Committee meeting at which the draft
RNA is to be presented. Following the Operating Committee vote, the draft RNA will be
transmitted to the Management Committee for discussion and action.
31.2.3.2 Board Action
Following the Management Committee vote, the draft RNA, with working group,
Operating Committee, and Management Committee input, will be forwarded to the ISO Board
for review and action. Concurrently, the draft RNA will be provided to the Market Monitoring
Unit for its review and consideration of whether market rules changes are necessary to address
an identified failure, if any, in one of the ISO’s competitive markets. The Board may approve
the RNA as submitted, or propose modifications on its own motion. If any changes are proposed
by the Board, the revised RNA shall be returned to the Management Committee for comment.
The Board shall not make a final determination on a revised RNA until it has reviewed the
Management Committee comments. Upon approval by the Board, the ISO shall issue the final
RNA to the marketplace by posting it on its web site.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of this Attachment are also addressed in Section 30.4.6.8.2 of the Market Monitoring
Plan, Attachment O to the ISO Services Tariff.
31.2.3.3 Needs Assessment Disputes
Notwithstanding any provision to the contrary in this Attachment, the ISO OATT, or the
NYISO Services Tariff, in the event that a Market Participant raises a dispute solely within the
NYPSC’s jurisdiction relating to the final conclusions or recommendations of the RNA, a
Market Participant may refer such dispute to the NYPSC for resolution. The NYPSC’s final
determination shall be binding, subject only to judicial review in the courts of the State of New
York pursuant to Article 78 of the NYCPLR.
31.2.3.4 Public Information Sessions
In order to provide ample exposure for the marketplace to understand the identified
Reliability Needs, the ISO will provide various opportunities for Market Participants and other
potentially interested parties to discuss the final RNA. Such opportunities may include
presentations at various ISO Market Participant committees, focused discussions with various
industry sectors, and/or presentations in public venues.
31.2.4
Development of Solutions to Reliability Needs
31.2.4.1 Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.2.4.1 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.2.4.1.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.2.4.1.1.1 to demonstrate its capability to satisfy the applicable qualification criteria,
and (ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with
signatory authority, in a form acceptable to the ISO, certifying that the Affiliate will participate
in the Developer’s project in the manner described by the Developer and will abide by the
requirements set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures related and
applicable to the Affiliate’s participation.
31.2.4.1.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate and maintain a transmission project to meet identified Reliability
Needs. The ISO shall consider the qualifications of each Developer in an evenhanded and non-
discriminatory manner, treating Transmission Owners and Other Developers alike.
31.2.4.1.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a transmission project as a solution to an identified Reliability Need based on the
following criteria:
31.2.4.1.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.2.4.1.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.2.4.1.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement, or equivalent information;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch, or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to solve a Reliability Need.
31.2.4.1.1.1.4 A detailed plan describing how the Developer - in the absence of previous
experience financing, developing, constructing, operating, or maintaining
transmission facilities - will finance, develop, construct, operate, and maintain a
transmission facility, including the financial, technical, and engineering
qualifications and experience and capabilities of any third parties with which it
will contract for these purposes.
31.2.4.1.1.2 Developer Qualification Determination
Any Developer seeking to become qualified may submit the required information, or
update any previously submitted information, at any time. The ISO shall treat on a confidential
basis in accordance with the requirements of its Code of Conduct in Attachment F of the ISO
OATT any non-public financial qualification information that is submitted to the ISO by the
Developer under Section 31.2.4.1.1.1.3 and is designated by the Developer as “Confidential
Information.” The ISO shall within 15 days of a Developer’s submittal, notify the Developer if
the information is incomplete. If the submittal is deemed incomplete, the Developer shall submit
the additional information within 30 days of the ISO’s request. The ISO shall notify the
Developer of its qualification status within 30 days of receiving all necessary information. A
Developer shall retain its qualification status for a three-year period following the notification
date; provided, however, that the ISO may revoke this status if it determines that there has been a
material change in the Developer’s qualifications and the Developer no longer meets the
qualification requirements. A Developer that has been qualified shall inform the ISO within
thirty days of any material change to the information it provided regarding its qualifications and
shall submit to the ISO each year its most recent audited annual financial statement when
available. At the conclusion of the three-year period or following the ISO’s revocation of a
Developer’s qualification status, the Developer may re-apply for a qualification status under this
section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated transmission project as a solution to an identified Reliability Need and
shall be eligible to use the cost allocation and cost recovery mechanism for regulated
transmission projects set forth in Section 31.5 of this Attachment Y and Rate Schedule 10,
Section 6.10, of the ISO OATT for any approved project.
31.2.4.2 Interregional Transmission Projects
Interregional Transmission Projects may be proposed under Section 31.2.5.1 of this
Attachment Y as regulated backstop solutions, alternative regulated solutions, or market-based
solutions, in response to a request by the ISO for solutions to a Reliability Need under the
relevant provisions of Section 31.2.4. Interregional Transmission Projects proposed as regulated
backstop solutions, alternative regulated solutions or market-based solutions shall be: (i)
evaluated by the ISO in accordance with the applicable requirements of the reliability planning
process of this Attachment Y, and (ii) jointly evaluated by the ISO and the relevant adjacent
transmission planning region(s) in accordance with Section 7.3 of the Interregional Planning
Protocol.
31.2.4.3 Regulated Backstop Solutions
31.2.4.3.1
When a Reliability Need is identified in any RNA issued under this tariff,
the ISO shall request and the Responsible Transmission Owner shall provide to
the ISO, as set forth in Section 31.2.5 below, a proposal for a regulated solution or
combination of solutions that shall serve as a backstop to meet the Reliability
Need if requested by the ISO due to the lack of sufficient viable market-based
solutions to meet such Reliability Needs identified for the Study Period. The
Responsible Transmission Owner shall be eligible to recover its costs for
developing its proposal and seeking necessary approvals under Rate Schedule 10
of the ISO OATT. Regulated backstop solutions may include generation,
transmission, or demand side resources. Such proposals may include reasonable
alternatives that would effectively address the Reliability Need; provided
however, the Responsible Transmission Owner’s obligation to propose and
implement regulated backstop solutions under this tariff is limited to regulated
transmission solutions. Prior to providing its response to the RNA, each
Responsible Transmission Owner will present for discussion at the ESPWG and
TPAS any updates in its LTP that impact a Reliability Need identified in the
RNA. The ISO will present at the ESPWG and TPAS any updates to its
determination under Section 31.2.2.4.2 with respect to the Transmission Owners’
LTPs. Should more than one regulated backstop solution be proposed by a
Responsible Transmission Owner to address a Reliability Need, it will be the
responsibility of that Responsible Transmission Owner to determine which of the
regulated backstop solutions will proceed following a finding by the ISO under
Section 31.2.8 of this Attachment Y. The determination by the Responsible
Transmission Owner will be made prior to the approval of the CRP which
precedes the Trigger Date for the regulated backstop solution with the longest
lead time. Contemporaneous with the request to the Responsible Transmission
Owner, the ISO shall solicit market-based and alternative regulated responses as
set forth in Sections 31.2.4.5 and 31.2.4.7, which shall not be a formal RFP
process.
31.2.4.4 Qualifications for Regulated Backstop Solutions
31.2.4.4.1
The submission of a regulated backstop solution to a Reliability Need for
purposes of the ISO’s evaluation under Section 31.2.5 of the viability and
sufficiency of the proposed solution and the determination of the Trigger Date for
the proposed solution shall include, at a minimum, the following details: (1)
contact information; (2) the lead time necessary to complete the project,
including, if available, the construction windows in which the Responsible
Transmission Owner can perform construction and what, if any, outages may be
required during these periods; (3) a description of the project, including type, size,
and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable
technology, (5) a major milestone schedule; (6) the schedule for obtaining any
permits and other certifications, if available; (7) status of ISO interconnection
studies and interconnection agreement, if available; and (8) status of equipment
availability and procurement, if available.
31.2.4.4.2 The submission of a regulated backstop solution to a Reliability Need for
purposes of the ISO’s evaluation of the proposed solution for possible selection as
the more efficient or cost effective solution to the Reliability Need shall include,
at a minimum, the following details: (1) updates to the information required
under Section 31.2.4.4.1; (2) the schedule for obtaining required permits and other
certifications; (3) a demonstration of Site Control or a schedule for obtaining such
control; (4) the status of any contracts (other than an interconnection agreement)
that are under negotiation or in place, including any contracts with third-party
contractors; (5) status of ISO interconnection studies and interconnection
agreement; (6) status of equipment availability and procurement; (7) evidence of
financing or ability to finance the project; (8) capital cost estimates for the
project; (9) a description of permitting or other risks facing the project at the stage
of project development, including evidence of the reasonableness of project cost
estimates, all based on the information available at the time of the submission;
and (10) any other information requested by the ISO.
A Responsible Transmission Owner shall submit the following
information to indicate the status of any contracts: (i) copies of all final contracts
the ISO determines are relevant to its consideration, or (ii) where one or more
contracts are pending, a timeline on the status of discussions and negotiations
with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The
ISO shall treat on a confidential basis in accordance with the requirements of its
Code of Conduct in Attachment F of the ISO OATT any contract that is submitted
to the ISO and is designated by the Responsible Transmission Owner as
“Confidential Information.”
A Responsible Transmission Owner shall submit the following
information to indicate the status of any required permits: (i) copies of all final
permits received that the ISO determines are relevant to its consideration, or (ii)
where one or more permits are pending, the completed permit application(s) with
information on what additional actions must be taken to meet the permit
requirements and a timeline providing the expected timing for finalization and
receipt of the final permit(s). The final permits shall be submitted to the ISO
when available.
A Responsible Transmission Owner shall submit the following
information, as appropriate, to indicate evidence of financing by it or any Affiliate
upon which it is relying for financing: (i) evidence of self-financing or project
financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such
financing is pending, the status of the application for any relevant financing,
including a timeline providing the status of discussions and negotiations of
relevant documents and when the negotiations are expected to be completed. The
final contracts or approved rates shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission expansion
study of a proposed regulated backstop solution that is performed under Sections
3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO OATT, the
Responsible Transmission Owner of the proposed project shall notify the ISO that
the study has been completed and, at the ISO’s request, shall submit to the ISO
any study report and related materials prepared in connection with the study.
31.2.4.4.3
If the regulated backstop solution does not meet the Reliability Needs , the
ISO will provide sufficient information to the Responsible Transmission Owner to
determine how the regulated backstop should be modified to meet the identified
Reliability Needs. The Responsible Transmission Owner will make necessary
changes to its proposed regulated backstop solution to address reliability
deficiencies identified by the ISO, and submit a revised proposal to the ISO for
review and approval.
31.2.4.5 Market-Based Responses
At the same time that a proposal for a regulated backstop solution is requested from the
Responsible Transmission Owner under Section 31.2.4.3, the ISO shall also request market-
based responses from the market place. Subject to the execution of appropriately drawn
confidentiality agreements and the Commission’s standards of conduct, the ISO and the
appropriate Transmission Owner or Transmission Owners shall provide any party who wishes to
develop such a response access to the data that is necessary to develop its response. Such data
shall only be used for the purposes of preparing a market-based response to a Reliability Need
under this section. Such responses will be open on a comparable basis to all resources, including
generation, demand response providers, and merchant transmission Developers.
31.2.4.6 Qualifications for a Valid Market-Based Response
The submission of a proposed market-based solution must include, at a minimum:
(1) contact information; (2) the lead time necessary to complete the project, including, if
available, the construction windows in which the Developer can perform construction and what,
if any, outages may be required during these periods; (3) a description of the project, including
type, size, and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable technology;
(5) a major milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining Site Control; (8)
the status of any contracts (other than an interconnection agreement) that are under negotiation or
in place; (9) the status of ISO interconnection studies and interconnection agreement; (10) the
status of equipment availability and procurement; (11) evidence of financing or ability to finance
the project; and (12) any other information requested by the ISO.
A Developer shall submit the following information to indicate the status of any
contracts: (i) copies of all final contracts the ISO determines are relevant to its consideration, or
(ii) where one or more contracts are pending, a timeline on the status of discussions and
negotiations with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The ISO shall treat
on a confidential basis in accordance with the requirements of its Code of Conduct in
Attachment F of the ISO OATT any contract that is submitted to the ISO and is designated by
the Developer as “Confidential Information.”
A Developer shall submit the following information to indicate the status of any required
permits: (i) copies of all final permits received that the ISO determines are relevant to its
consideration, or (ii) where one or more permits are pending, the completed permit application(s)
with information on what additional actions must be taken to meet the permit requirements and a
timeline providing the expected timing for finalization and receipt of the final permit(s). The
final permits shall be submitted to the ISO when available.
A Developer shall submit the following information, as appropriate, to indicate evidence
of financing by it or any Affiliate upon which it is relying for financing: (i) copies of all loan
commitment letter(s) and signed financing contract(s), or (ii) where such financing is pending,
the status of the application for any relevant financing, including a timeline providing the status
of discussions and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission expansion study of a
proposed market-based solution that is performed under Sections 3.7 or 4.5 of the ISO OATT or
Attachments P or X of the ISO OATT, the Developer of the proposed project shall notify the ISO
that the study has been completed and, at the ISO’s request, shall submit to the ISO any study
report and related materials prepared in connection with the study.
Failure to provide any data requested by the ISO within the timeframe set forth in Section
31.2.5.1 of this Attachment Y will result in the rejection of the proposed market-based solution
from further consideration during that planning cycle.
31.2.4.7 Alternative Regulated Responses
31.2.4.7.1
The ISO will request alternative regulated responses to Reliability Needs
at the same time that it requests market-based responses and regulated backstop
solutions. Such proposals may include reasonable alternatives that would
effectively address the identified Reliability Need.
31.2.4.7.2
In response to the ISO’s request, Other Developers may develop
alternative regulated proposals for generation, demand side alternatives, and/or
other solutions to address a Reliability Need and submit such proposals to the
ISO. Transmission Owners, at their option, may submit additional proposals for
regulated solutions to the ISO. Transmission Owners and Other Developers may
submit such proposals to the NYDPS for review at any time. Subject to the
execution of appropriately drawn confidentiality agreements and the
Commission’s standards of conduct, the ISO and the appropriate Transmission
Owner(s) shall provide Other Developers access to the data that is needed to
develop their proposals. Such data shall be used only for purposes of preparing
an alternative regulated proposal in response to a Reliability Need.
31.2.4.8 Qualifications for Alternative Regulated Solutions
31.2.4.8.1
The submission of an alternative regulated solution to a Reliability Need
for purposes of the ISO’s evaluation under Section 31.2.5 of the viability and
sufficiency of the proposed solution and the determination of the Trigger Date for
the proposed solution shall include, at a minimum, the following details: (1)
contact information; (2) the lead time necessary to complete the project,
including, if available, the construction windows in which the Other Developer or
Transmission Owner can perform construction and what, if any, outages may be
required during these periods; (3) a description of the project, including type, size,
and geographic and electrical location, as well as planning and engineering
specifications and drawings as appropriate; (4) evidence of a commercially viable
technology; (5) a major milestone schedule; (6) the schedule for obtaining any
permits and other certifications, if available; (7) status of ISO interconnection
studies and interconnection agreement, if available; and (8) status of equipment
availability and procurement, if available.
31.2.4.8.2
The submission of a proposed alternative regulated solution to a
Reliability Need for purposes of the ISO’s evaluation of the proposed solution for
possible selection as the more efficient or cost effective solution for the
Reliability Need must include, at a minimum: (1) updates to the information
required under Section 31.2.4.8.1;
(2) a demonstration of Site Control or a
schedule for obtaining Site Control; (3) the status of any contracts (other than an
Interconnection Agreement) that are under negotiation or in place, including any
contracts with third-party contractors; (4) the status of any interconnection studies
and interconnection agreement; (5) the schedule for obtaining any required
permits and other certifications; (6) the status of equipment availability and
procurement; (7) evidence of financing or ability to finance the project; (8) capital
cost estimates for the project; (9) a description of permitting or other risks facing
the project at the stage of project development, including evidence of the
reasonableness of project cost estimates, all based on the information available at
the time of the submission; and (10) any other information requested by the ISO.
An Other Developer or Transmission Owner shall submit the following
information to indicate the status of any contracts: (i) copies of all final contracts
the ISO determines are relevant to its consideration, or (ii) where one or more
contracts are pending, a timeline on the status of discussions and negotiations
with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The
ISO shall treat on a confidential basis in accordance with the requirements of its
Code of Conduct in Attachment F of the ISO OATT any contract that is submitted
to the ISO and is designated by the Other Developer or Transmission Owner as
“Confidential Information.”
An Other Developer or Transmission Owner shall submit the following
information to indicate the status of any required permits: (i) copies of all final
permits received that the ISO determines are relevant to its consideration, or (ii)
where one or more permits are pending, the completed permit application(s) with
information on what additional actions must be taken to meet the permit
requirements and a timeline providing the expected timing for finalization and
receipt of the final permit(s). The final permits shall be submitted to the ISO
when available.
An Other Developer or Transmission Owner shall submit the following
information, as appropriate, to indicate evidence of financing by it or any Affiliate
upon which it is relying for financing: (i) evidence of self-financing or project
financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such
financing is pending, the status of the application for any relevant financing,
including a timeline providing the status of discussions and negotiations of
relevant documents and when the negotiations are expected to be completed. The
final contracts or approved rates shall be submitted to the ISO when available.
Upon the completion of any interconnection study or transmission
expansion study of a proposed alternative regulated solution that is performed
under Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO
OATT, the Other Developer or Transmission Owner of the proposed project shall
notify the ISO that the study has been completed and, at the ISO’s request, shall
submit to the ISO any study report and related materials prepared in connection
with the study.
31.2.4.8.3
Failure to provide any data requested by the ISO within the timeframe
provided in Sections 31.2.5.1 and 31.2.6.1 of this Attachment Y will result in the
rejection of the proposed alternative regulated solution from further consideration
during that planning cycle. A proponent of a proposed alternative regulated
solution must notify the ISO immediately of any material change in status of a
proposed alternative regulated solution. For purposes of this provision, a material
change includes, but is not limited to, a change in the financial viability of the
developer, a change in the siting status of the project, or a change in a major
element of the project’s development. If the ISO, at any time, learns of a material
change in the status of a proposed alternative regulated solution, it may, at that
time, make a determination as to the continued viability of the proposed
alternative regulated solution.
31.2.4.9 Additional Solutions
Should the ISO determine that it has not received adequate regulated backstop or market-
based solutions to satisfy the Reliability Need, the ISO may, in its discretion, solicit additional
regulated backstop or market-based solutions. Other Developers or Transmission Owners may
submit additional alternative regulated solutions for the ISO’s consideration at that time.
31.2.5
ISO Evaluation of Viability, Sufficiency, and Trigger Date of Proposed
Solutions to Reliability Needs
31.2.5.1 Timing for Submittal of Project Information and Developer Qualification
Information and Opportunity to Provide Additional Information
Within 60 days after a request for solutions to a Reliability Need is made by the ISO after
completion of the RNA, which time period may be extended by the ISO pursuant to Section
31.1.8.7, all Developers proposing solutions to an identified Reliability Need shall submit to the
ISO for purposes of its evaluation the project information, as applicable, for: (i) a proposed
regulated backstop solution under Section 31.2.4.4.1, (ii) a proposed market-based solution under
Section 31.2.4.6, or (iii) a proposed alternative regulated solution under Section 31.2.4.8.1 of this
Attachment Y. In response to a solicitation for a solution to a Reliability Need identified after
the 2014-2015 planning cycle, the Developer of a proposed transmission solution must also
demonstrate to the ISO, simultaneous with its submission of project information, that it has
submitted a valid Transmission Interconnection Application or Interconnection Request, as
applicable.
Any Developer that the ISO has determined under Section 31.2.4.1.1.2 or as set forth in
this Section 31.2.5.1 below to be qualified to propose to develop a project as a transmission
solution to an identified Reliability Need may submit the required project information; provided,
however, that: (i) the Developer shall provide a non-refundable application fee of $10,000 and
(ii) based on the actual identified need, the ISO may request that the qualified Developer provide
additional Developer qualification information. Any Developer that has not been determined by
the ISO to be qualified, but that wants to propose to develop a project, must submit to the ISO
the information required for Developer qualification under Section 31.2.4.1.1 within 30 days
after a request for solutions is made by the ISO. The ISO shall within 30 days of a Developer’s
submittal of its Developer qualification information, notify the Developer if this information is
incomplete. The Developer shall submit additional Developer qualification information or
project information required by the ISO within 15 days of the ISO’s request. A Developer that
fails to submit the additional Developer qualification information or the required project
information will not be eligible for its project to be considered in that planning cycle.
31.2.5.2 Comparable Evaluation of All Proposed Solutions
The ISO shall evaluate: (i) any proposed market-based solution submitted by a Developer
pursuant to Section 31.2.4.5, (ii) any proposed regulated backstop solution submitted by a
Responsible Transmission Owner pursuant to Section 31.2.4.3, and (iii) any proposed alternative
regulated solution submitted by a Transmission Owner or Other Developer pursuant to Section
31.2.4.7. The ISO will evaluate whether each proposed solution is viable and is sufficient to
satisfy the identified Reliability Need by the need date pursuant to Sections 31.2.5.3 and
31.2.5.4. The proposed solutions may include multiple components and resource types. When
evaluating proposed solutions to Reliability Needs from any Developer, all resource types -
generation, transmission, demand response, or a combination of these resource types - shall be
considered on a comparable basis as potential solutions to the Reliability Needs identified. All
solutions will be evaluated in the same general time frame.
31.2.5.3 Evaluation of Viability of Proposed Solution
The ISO will determine the viability of a solution - transmission, generation, demand
response, or a combination of these resource types - proposed to satisfy a Reliability Need. For
purposes of its analysis, the ISO will evaluate whether: (i) the Developer has provided the
required Developer qualification data pursuant to Section 31.2.4.1 and the required project
information data under Sections 31.2.4.4.1, 31.2.4.6, or 31.2.4.8.1; (ii) the proposed solution is
technically practicable; (iii) the Developer has indicated possession of, or an approach for
acquiring, any necessary rights-of-way, property, and facilities that will make the proposal
reasonably feasible in the required timeframe; and (iv) the proposed solution can be completed in
the required timeframe. If the ISO determines that the proposed solution is not viable and, for
regulated solutions, the Developer does not address any identified deficiency pursuant to Section
31.2.5.6, the ISO shall reject the proposed solution from further consideration during that
planning cycle.
31.2.5.4 Evaluation of Sufficiency of Proposed Solution
The ISO will perform a comparable analysis of each proposed solution - transmission,
generation, demand response, or a combination of these resource types - through the Study
Period to identify whether it satisfies the Reliability Need(s). The ISO will evaluate each
solution to determine whether the solution proposed by the Developer fully eliminates the
Reliability Need(s). If the ISO determines that a proposed regulated solution is not sufficient and
the Developer does not address any identified deficiency pursuant to Section 31.2.5.6, the ISO
shall reject the proposed regulated solution from further consideration during that planning cycle.
31.2.5.5 Establishment of Trigger Date of Proposed Regulated Solutions
Upon receipt of all Developers’ proposed regulated solutions pursuant to Section
31.2.5.1, the ISO will notify all Developers if any Developer has proposed a lead time for the
implementation of its regulated solution that could result in a Trigger Date for the regulated
solution within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG, provided that the ISO will not disclose the identity of
such Developer or the details of its project at that time. The ISO will independently analyze the
lead time proposed by each Developer for the implementation of its regulated solution. The ISO
will use the Developer’s estimate and the ISO’s analysis to establish the ISO’s Trigger Date for
each regulated solution. The ISO will also establish benchmark lead times for proposed market-
based solutions.
31.2.5.6 Resolution of Deficiencies
Following initial review of the proposals, as described above, ISO staff will identify any
reliability deficiencies in each of the proposed solutions. The Responsible Transmission Owner,
Transmission Owner or Other Developer will discuss any identified deficiencies with the ISO
staff. Other Developers and Transmission Owners that propose alternative regulated solutions
shall have the option to remedy their proposals to address any deficiency within 30 days of
notification by the ISO. With respect to regulated backstop solutions proposed by a Responsible
Transmission Owner pursuant to Section 31.2.4.3, the Responsible Transmission Owner shall
make necessary changes to its proposed backstop solution to address any reliability deficiencies
identified by the ISO, and submit a revised proposal to the ISO for review within 30 days. The
ISO shall review all such revised proposals to determine whether the identified deficiencies have
been resolved.
31.2.5.7 ISO Report of Evaluation Results
The ISO shall present its Viability and Sufficiency Assessment to stakeholders, interested
parties, and the NYDPS for comment and will indicate at that time whether any of the proposed
regulated solutions found to be viable and sufficient under this Section 31.2.5 will have a Trigger
Date within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG.
The ISO shall report in the CRP the results of its evaluation under this Section 31.2.5: (i)
whether each proposed regulated backstop solution, alternative regulated solution, and market-
based solution is viable and is sufficient to satisfy the identified Reliability Need by the need
date, and (ii) the Trigger Dates for the proposed regulated solutions.
31.2.6
ISO Evaluation and Selection of Proposed Regulated Transmission
Solutions
31.2.6.1 Submission of Project Information for Selection of Proposed Regulated
Transmission Solution
If the ISO determines that the Trigger Date of any Developer’s proposed regulated
solution that was found to be viable and sufficient under Section 31.2.5 will occur within thirty-
six months of the date of the ISO’s presentation of the Viability and Sufficiency Assessment to
the ESPWG, the ISO will request that all Developers of regulated transmission solutions that the
ISO determined were viable and sufficient submit to the ISO their project information, as
applicable, for: (i) a proposed regulated backstop transmission solution under Section 31.2.4.4.2,
or (ii) a proposed alternative regulated transmission solution under Section 31.2.4.8.2. If the ISO
determines that none of the Developers’ proposed regulated solutions that were found to be
viable and sufficient under Section 31.2.5 have a Trigger Date that will occur within the thirty-
six month period, the ISO will not request further project information, perform the evaluation, or
make a selection of a more efficient or cost effective regulated solution under this Section 31.2.6
for that planning cycle.
The ISO will make its request, if necessary, for project information under this Section
31.2.6.1 sufficiently in advance of the earliest Trigger Date of the viable and sufficient regulated
solutions to enable the ISO to evaluate and select the more efficient or cost effective
transmission solution. Upon the ISO’s request for project information, the Developers shall
submit such information for their regulated transmission solution within thirty (30) days, which
time period may be extended by the ISO pursuant to Section 31.1.8.7. The Developer must
include with its project information a demonstration that it has an executed System Impact Study
Agreement or System Reliability Impact Study Agreement, as applicable. A Developer shall
submit additional project information required by the ISO within 15 days of the ISO’s request.
A Developer that fails to submit the required project information will not be eligible for its
project to be considered in that planning cycle.
31.2.6.2 Study Deposit for Proposed Regulated Transmission Solutions
A Developer that proposes a regulated backstop transmission solution or an alternative
regulated transmission solution to satisfy the identified Reliability Need shall submit to the ISO,
at the same time that it provides the project information required pursuant to Section 31.2.6.1, a
study deposit of $100,000, which shall be applied to study costs and subject to refund as
described in this Section 31.2.6.2.
The ISO shall charge, and a Developer proposing a regulated backstop transmission
solution or an alternative regulated transmission solution shall pay, the actual costs of the ISO’s
evaluation of the Developer’s proposed transmission solution for purposes of the ISO’s selection
of the more efficient or cost effective transmission solution to satisfy a Reliability Need for cost
allocation purposes, including costs associated with the ISO’s use of subcontractors. The ISO
will track its staff and administrative costs, including any costs associated with using
subcontractors, that it incurs in performing the evaluation of a Developer’s proposed
transmission solution under this Section 31.2.6 and any supplemental evaluation or re-evaluation
of the proposed transmission solution. If the ISO or its subcontractors perform study work for
multiple proposed transmission solutions on a combined basis, the ISO will allocate the costs of
the combined study work equally among the applicable Developers. The ISO shall invoice the
Developer monthly for study costs incurred by the ISO in evaluating the Developer’s proposed
transmission solution as described above. Such invoice shall include a description and an
accounting of the study costs incurred by the ISO and estimated subcontractor costs. The
Developer shall pay the invoiced amount within thirty (30) calendar days of the ISO’s issuance
of the monthly invoice. The ISO shall continue to hold the full amount of the study deposit until
settlement of the final monthly invoice; provided, however, if a Developer: (i) does not pay its
monthly invoice within the timeframe described above, or (ii) does not pay a disputed amount
into an independent escrow account as described below, the ISO may draw upon the study
deposit to recover the owed amount. If the ISO must draw on the study deposit, the ISO shall
provide notice to the Developer, and the Developer shall within thirty (30) calendar days of such
notice make payments to the ISO to restore the full study deposit amount. If the Developer fails
to make such payments, the ISO may halt its evaluation of the Developer’s proposed
transmission solution and may disqualify the Developer’s proposed transmission solution from
further consideration. After the conclusion of the ISO’s evaluation of the Developer’s proposed
transmission solution or if the Developer: (i) withdraws its proposed transmission solution or (ii)
fails to pay an invoiced amount and the ISO halts its evaluation of the proposed transmission
solution, the ISO shall issue a final invoice and refund to the Developer any portion of the
Developer’s study deposit submitted to the ISO under this Section 31.2.6.2 that exceeds
outstanding amounts that the ISO has incurred in evaluating that Developer’s proposed
transmission solution, including interest on the refunded amount calculated in accordance with
Section 35.19a(a)(2) of FERC’s regulations. The ISO shall refund the remaining portion within
sixty (60) days of the ISO’s receipt of all final invoices from its subcontractors and involved
Transmission Owners.
In the event of a Developer’s dispute over invoiced amounts, the Developer shall: (i)
timely pay any undisputed amounts to the ISO, and (ii) pay into an independent escrow account
the portion of the invoice in dispute, pending resolution of such dispute. If the Developer fails to
meet these two requirements, then the ISO shall not be obligated to perform or continue to
perform its evaluation of the Developer’s proposed transmission solution. Disputes arising under
this section shall be addressed through the Dispute Resolution Procedures set forth in Section
2.16 of the ISO OATT and Section 11 of the ISO Services Tariff. Within thirty (30) Calendar
Days after resolution of the dispute, the Developer will pay the ISO any amounts due with
interest calculated in accordance with Section 35.19a(a)(2) of FERC’s regulations.
31.2.6.3 Evaluation of System Impact of Proposed Regulated Transmission
Solution
A proposed regulated transmission solution that will have a significant adverse impact on
the reliability of the New York State Transmission System shall not be eligible for selection by
the ISO under Section 31.2.6.5. The ISO shall evaluate the system impacts for the entire Study
Period of a proposed regulated transmission solution that the ISO has determined under Section
31.2.5 is viable and sufficient. As part of this evaluation, the ISO shall give due consideration to
the results of any completed System Impact Study or System Reliability Impact Study, as
applicable. The ISO shall perform power flow and short circuit studies for the proposed
regulated transmission solutions and additional studies, as appropriate. If the ISO identifies a
significant adverse impact based on these studies, the ISO shall request that the Developer make
an adjustment to its proposed regulated transmission solution to address this impact and remain
eligible for selection. The Developer shall submit the adjustment within 30 days of the ISO’s
notification.
If the Developer modifies its proposed regulated transmission solution, the ISO shall
confirm that the adjusted solution still satisfies the viability and sufficiency requirements set
forth in Section 31.2.5. If the ISO determines that the proposed regulated transmission solution
does not satisfy the viability and sufficiency requirements or continues to have a significantly
adverse impact on the reliability of the New York State Transmission System, the ISO shall
remove the proposed solution from further consideration during that planning cycle.
31.2.6.4 Evaluation of Regional Transmission Solutions to Address Local and
Regional Reliability Needs More Efficiently or More Cost Effectively
Than Local Transmission Solutions
The ISO will review the LTPs as they relate to BPTFs. The results of the ISO’s analysis
will be reported in the CRP.
31.2.6.4.1 Evaluation of Regional Transmission Solutions to Address Local
Reliability Needs Identified in Local Transmission Plans More Efficiently
or More Cost Effectively than Local Transmission Solutions
The ISO, using engineering judgment, will determine whether proposed regional
transmission solutions on the BPTFs may more efficiently or cost effectively satisfy reliability
needs identified in the LTPs. If the ISO identifies that a regional transmission solution on the
BPTFs has the potential to more efficiently or cost effectively satisfy the reliability need
identified in the LTPs, it will perform a sensitivity analysis to determine whether the proposed
regional transmission solution on the BPTFs would satisfy the reliability needs identified in the
LTPs. If the ISO determines that the proposed regional transmission solutions on the BPTFs
would satisfy the reliability need, the ISO will evaluate the proposed regional transmission
solution using the metrics set forth in Section 31.2.6.5.1 to determine whether it may be a more
efficient or cost effective solution on the BPTFs to satisfy the reliability needs identified in the
LTPs than the local solutions proposed in the LTPs.
31.2.6.4.2 Evaluation of Regional Transmission Solutions to Address Regional
Reliability Needs More Efficiently or More Cost Effectively than Local
Transmission Solutions
As referenced in Section 31.2.1.3, the ISO, using engineering judgment, will determine
whether a regional transmission solution might more efficiently or more cost effectively satisfy
an identified regional Reliability Need on the BPTFs that impacts more than one Transmission
District than any local transmission solutions identified by the Transmission Owners in their
LTPs in the event the LTPs specify such transmission solutions are included to address local
reliability needs.
31.2.6.5 ISO Selection of More Efficient or Cost Effective Transmission Solution
for Cost Allocation Purposes
A proposed regulated transmission solution - including a regulated backstop transmission
solution submitted by a Responsible Transmission Owner pursuant to Section 31.2.4.3 and an
alternative regulated transmission solution submitted by a Transmission Owner or Other
Developer pursuant to Section 31.2.4.7 - that the ISO has determined satisfies the viability and
sufficiency requirements in Section 31.2.5 and the system impact requirements in Section
31.2.6.3 shall be eligible under this Section 31.2.6.5 for selection in the CRP for the purpose of
cost allocation and recovery under the ISO Tariffs. The ISO shall evaluate any eligible proposed
regulated transmission solutions for the planning cycle using the metrics set forth in Section
31.2.6.5.1 below. For purposes of this evaluation, the ISO will review the information submitted
by the Developer and determine whether it is reasonable and how such information should be
used for purposes of the ISO evaluating each metric. In its review, the ISO will give due
consideration to the status of, and any available results of, any applicable interconnection or
transmission expansion studies concerning the proposed regulated transmission solution
performed in accordance with Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the
ISO OATT. The ISO may engage an independent consultant to review the reasonableness and
comprehensiveness of the information submitted by the Developer and may rely on the
independent consultant’s analysis in evaluating each metric. The ISO shall select in the CRP for
cost allocation purposes the more efficient or cost effective transmission solution to satisfy a
Reliability Need in the manner set forth in Section 31.2.6.5.2 below.
31.2.6.5.1 Metrics for Evaluating More Efficient or Cost Effective Regulated
Transmission Solution to Satisfy Reliability Need
In determining which of the eligible proposed regulated transmission solutions is the
more efficient or cost effective solution to satisfy the Reliability Need, the ISO will consider, and
will consult with the NYDPS regarding, the following metrics set forth in this Section 31.2.6.5.1
and rank each proposed solution based on the quality of its satisfaction of these metrics:
31.2.6.5.1.1 The capital cost estimates for the proposed regulated transmission
solutions, including the accuracy of the proposed estimates. For this evaluation,
the Developer shall provide the ISO with credible capital cost estimates for its
proposed solution, with itemized supporting work sheets that identify all material
and labor cost assumptions, and related drawings to the extent applicable and
available. The work sheets should include an estimated quantification of cost
variance, providing an assumed plus/minus range around the capital cost estimate.
The estimate shall include all components that are needed to meet the
Reliability Need throughout the Study Period. To the extent information is
available, the Developer should itemize: material and labor cost by equipment,
engineering and design work, permitting, site acquisition, procurement and
construction work, and commissioning needed for the proposed solution, all in
accordance with Good Utility Practice. For each of these cost categories, the
Developer should specify the nature and estimated cost of all major project
components and estimate the cost of the work to be done at each substation and/or
on each feeder to physically and electrically connect each facility to the existing
system. The work sheets should itemize to the extent applicable and available all
equipment for: (i) the proposed project; (ii) interconnection facilities (including
Attachment Facilities and Direct Assignment Facilities); and (iii) Network
Upgrade Facilities, System Upgrade Facilities, System Deliverability Upgrades,
Network Upgrades, and Distribution Upgrades.
31.2.6.5.1.2 The cost per MW ratio of the proposed regulated transmission solutions.
For this evaluation, the ISO will first determine the present worth, in dollars, of
the total capital cost of the proposed solution in current year dollars. The ISO will
then determine the MW value of the solution by summing the Reliability Need, in
MW, with the additional improvement, in MW, that the proposed solution offers
beyond serving the Reliability Need. The ISO will then determine the cost per
MW ratio by dividing the present worth of the total capital cost by the MW value.
31.2.6.5.1.3 The expandability of the proposed regulated transmission solution. The
ISO will consider the impact of the proposed solution on future construction. The
ISO will also consider the extent to which any subsequent expansion will continue
to use this proposed solution within the context of system expansion.
31.2.6.5.1.4 The operability of the proposed regulated transmission solution. The ISO
will consider how the proposed solution may affect additional flexibility in
operating the system, such as dispatch of generation, access to operating reserves,
access to ancillary services, or ability to remove transmission for maintenance.
The ISO will also consider how the proposed solution may affect the cost of
operating the system, such as how it may affect the need for operating generation
out of merit for reliability needs, reducing the need to cycle generation, or
providing more balance in the system to respond to system conditions that are
more severe than design conditions.
31.2.6.5.1.5 The performance of the proposed regulated transmission solution. The
ISO will consider how the proposed project may affect the utilization of the
system (e.g. interface flows, percent loading of facilities).
31.2.6.5.1.6 The extent to which the Developer of a proposed regulated transmission
solution has the property rights, or ability to obtain the property rights, required to
implement the solution. The ISO will consider whether the Developer: (i) already
possesses the rights of way necessary to implement the solution; (ii) has
completed a transmission routing study, which (a) identifies a specific routing
plan with alternatives, (b) includes a schedule indicating the timing for obtaining
siting and permitting, and (c) provides specific attention to sensitive areas (e.g.,
wetlands, river crossings, protected areas, and schools); or (iii) has specified a
plan or approach for determining routing and acquiring property rights.
31.2.6.5.1.7 The potential issues associated with delay in constructing the proposed
regulated transmission solution consistent with the major milestone schedule and
the schedule for obtaining any permits and other certifications as required to
timely meet the need.
31.2.6.5.2 ISO Selection of More Efficient or Cost Effective Regulated Transmission
Solution to Satisfy Reliability Need
The ISO shall select under this Section 31.2.6.5.2 the proposed regulated transmission
solution, if any, that is the more efficient or cost effective transmission solution proposed in the
planning cycle to satisfy the identified Reliability Need. The ISO shall report the selected
regulated transmission solution in the CRP. The selected regulated transmission solution
reported in the CRP shall be eligible to be triggered by the ISO to satisfy the identified
Reliability Need pursuant to Section 31.2.8 at any point within thirty-six months of the date of
the ISO’s presentation of the Viability and Sufficiency Assessment to the ESPWG. An Other
Developer or Transmission Owner of an alternative regulated transmission project shall not be
eligible for cost allocation and cost recovery under the ISO OATT for its project unless its
project is selected pursuant to this Section 31.2.6.5.2. Once such project is selected, the Other
Developer or Transmission Owner shall be eligible for cost allocation and cost recovery under
the ISO OATT for its project. Within thirty (30) days of the ISO’s selection of an alternative
regulated transmission solution, the Other Developer or Transmission Owner shall submit to the
ISO for the ISO’s approval a proposed schedule and scope of work that describe the preparation
work, if any, that the Developer must perform prior to the Trigger Date of the project, including
a good faith estimate of the costs of such work. Costs will be recovered when the project enters
into service, is completed or halted, or as otherwise determined by the Commission in
accordance with the cost recovery requirements set forth in Section 31.5.6 of this Attachment Y
and Rate Schedule 10 of the ISO OATT, or as otherwise determined by the Commission. Actual
project cost recovery, including any issues related to cost recovery and project cost overruns, will
be submitted to and decided by the Commission.
31.2.7
Comprehensive Reliability Plan
Following the ISO’s evaluation of the proposed market-based and regulated solutions to
Reliability Need(s), the ISO will prepare a draft CRP that sets forth the ISO’s findings regarding
the viability and sufficiency of solutions, the trigger dates of regulated solutions, and any
recommendations that implementation of regulated solutions (which may be a Gap Solution) is
necessary to ensure system reliability. The draft CRP will reflect any input from the NYDPS. If
the CRP cannot be completed in the two-year planning cycle, the ISO will notify stakeholders
and provide an estimated completion date and an explanation of the reasons the additional time is
required.
The ISO will include in the draft CRP the list of Developers that qualify pursuant to
Section 31.2.4.1 and will identify the proposed solutions that it has determined under Section
31.2.5 are viable and sufficient to satisfy the identified Reliability Need(s) by the need date. The
ISO will identify in the CRP the regulated backstop solution that the ISO has determined will
meet the Reliability Need by the need date and the Responsible Transmission Owner. If the ISO
determines at the time of the issuance of the CRP that sufficient market-based solutions will not
be available in time to meet a Reliability Need, and finds that it is necessary to take action to
ensure reliability, it will state in the CRP that the development of regulated solutions (regulated
backstop or alternative regulated solution) is necessary. The draft CRP will also include the
results of the ISO’s analysis of the LTPs consistent with Section 31.2.6.4.
The draft CRP shall indicate whether the ISO has determined that the Trigger Date to any
proposed regulated solution will occur within thirty-six months of the date of ISO’s presentation
of the Viability and Sufficiency Assessment to the ESPWG. If the Trigger Date of any proposed
regulated solution will occur within the thirty-six month period and the ISO makes a selection of
the more efficient or cost effective transmission solution under Section 31.2.6.5.2, the draft CRP
shall include the regulated transmission solution selected for cost allocation purposes pursuant to
Section 31.2.6.5.2 as the more efficient or cost effective transmission solution to satisfy the
Reliability Need(s) and shall indicate whether that transmission solution should be triggered.
The draft CRP shall also indicate the date by which a solution must be in-service to satisfy the
Reliability Need.
If: (i) none of the proposed regulated solutions has a Trigger Date within the thirty-six
month period, or (ii) the Trigger Date of any proposed regulated solution will occur within the
thirty-six month period but the ISO determines in its discretion that it is not necessary at that
time to select a more efficient or cost effective transmission solution under Section 31.2.6.5.2
prior to the completion of the CRP, the draft CRP will not select a regulated transmission
solution. If: (i) the Trigger Date of any proposed regulated solution will occur within the thirty-
six month period, and (ii) the ISO selects a more efficient or cost effective solution subsequent to
the completion of the CRP but prior to the completion of that thirty-six month period, the ISO
shall issue an updated CRP report pursuant to Section 31.2.7.3 that indicates the regulated
transmission solution selected for cost allocation purposes pursuant to Section 31.2.6.5.2 as the
more efficient or cost effective transmission solution to satisfy the Reliability Need(s) whether
that transmission solution should be triggered, and the date by which a solution must be in-
service to satisfy the Reliability Need.
The draft CRP shall include a comparison of a proposed regional solution to an identified
Reliability Need to an Interregional Transmission Project identified and evaluated under the
“Analysis and Consideration of Interregional Transmission Projects” section of the Interregional
Planning Protocol, if any. An Interregional Transmission Project proposed in the ISO’s
reliability planning process may be selected as a market based response, regulated backstop
solution, or an alternative regulated solution under the provisions of the ISO’s reliability
planning process.
31.2.7.1 Collaborative Governance Process
The ISO staff shall submit the draft CRP to the TPAS and ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft CRP. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Following completion
of the TPAS and ESPWG review, the draft CRP reflecting the revisions resulting from the TPAS
and ESPWG review shall be forwarded to the Operating Committee for a discussion and action.
The ISO shall notify the Business Issues Committee of the date of the Operating Committee
meeting at which the draft CRP is to be presented. Following the Operating Committee vote, the
draft CRP will be transmitted to the Management Committee for a discussion and action.
31.2.7.2 Board Review, Consideration, and Approval of CRP
Following the Management Committee vote, the draft CRP, with working group,
Operating Committee, and Management Committee input, will be forwarded to the ISO Board
for review and action. Concurrently, the draft CRP will also be provided to the Market
Monitoring Unit for its review and consideration of whether market rule changes are necessary to
address an identified failure, if any, in one of the ISO’s competitive markets. The Board may
approve the draft CRP as submitted or propose modifications on its own motion, including the
recommendations regarding the selection of transmission projects for cost allocation and cost
recovery under the ISO Tariffs if such selection will occur during that planning cycle. If any
changes are proposed by the Board, the revised CRP shall be returned to the Management
Committee for comment. The Board shall not make a final determination on the draft CRP until
it has reviewed the Management Committee comments. Upon final approval by the Board, the
ISO shall issue the CRP to the marketplace by posting the CRP on its website. The ISO will
provide the CRP to the appropriate regulatory agency(ies) for consideration and appropriate
action.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.3 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.2.7.3 Updated CRP Report
If, pursuant to Section 31.2.7, the ISO identifies a proposed regulated transmission
solution as the more efficient or cost effective transmission solution following the completion of
the CRP, the ISO will prepare a draft updated CRP report that indicates the regulated
transmission solution recommended for selection for cost allocation purposes pursuant to Section
31.2.6.5.2 as the more efficient or cost effective transmission solution to satisfy the Reliability
Need(s), whether that transmission solution should be triggered at that time, and the date by
which a solution must be in-service to satisfy the Reliability Need. The draft updated CRP
report shall be reviewed in accordance with the stakeholder process set forth in Section 31.2.7.1
and will be then forwarded to the ISO Board for its review and action pursuant to Section
31.2.7.2.
31.2.7.4 Reliability Disputes
Notwithstanding any provision to the contrary in this Attachment, the ISO OATT, or the
ISO Services Tariff, in the event that a Market Participant or other interested party raises a
dispute solely within the NYPSC’s jurisdiction concerning ISO’s final determination in the CRP
that a proposed solution will or will not meet a Reliability Need, a Market Participant or other
interested party seeking further review shall refer such dispute to the NYPSC for resolution, as
provided for in the ISO Procedures. The NYPSC’s final determination of such disputes shall be
binding, subject only to judicial review in the courts of the State of New York pursuant to Article
78 of the New York Civil Practice Law and Rules.
31.2.7.5 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers that have undertaken a
commitment to the ISO to build a project (which may be a regulated backstop solution, market-
based response, alternative regulated response or gap solution) that is necessary to ensure system
reliability, as identified in the CRP and approved by the appropriate governmental agency(ies)
and/or authority(ies).
31.2.8
Determination of Necessity
31.2.8.1 Determination of Necessity of a Regulated Solution
31.2.8.1.1
The ISO shall review proposals for market-based solutions pursuant to
Sections 31.2.5, 31.2.8.3, and 31.2.13.1 of this Attachment Y. The ISO will not
trigger a regulated solution if, based on this review, it determines prior to or at the
Trigger Date for a regulated solution that sufficient market-based solutions are
timely progressing to meet the Reliability Need by the need date. If the ISO
decides not to trigger a regulated backstop solution or selected alternative
regulated transmission solution, the Responsible Transmission Owner, Other
Developer, or Transmission Owner will be eligible to recover its costs incurred up
to that point in the same manner it may recover the costs of a halted project in
accordance with Section 31.2.8.2.1 for the Responsible Transmission Owner and
Section 31.2.8.2.2 for the Other Developer or Transmission Owner.
31.2.8.1.2
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date, (ii) the
regulated backstop solution proposed by the Responsible Transmission Owner is
the only proposed viable and sufficient regulated solution or is selected by the
ISO as the more efficient or cost effective transmission solution to meet the
identified Reliability Need, and (iii) the Trigger Date for the regulated backstop
solution has or will occur within thirty-six months of the date of the ISO’s
presentation of the Viability and Sufficiency Assessment to the ESPWG, the ISO
will trigger the regulated backstop solution at its Trigger Date. The ISO will
inform the Responsible Transmission Owner that it should submit the regulated
backstop solution to the appropriate governmental agency(ies) and/or
authority(ies) to begin the necessary approval process to site, construct, and
operate the solution. In response to the ISO’s request, the Responsible
Transmission Owner shall make such a submission to the appropriate
governmental agency(ies) and/or authority(ies).
31.2.8.1.3
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date; (ii) the ISO
selects an alternative regulated transmission solution as the more efficient or cost-
effective transmission solution to meet the identified Reliability Need; (iii) the
Trigger Date for the regulated backstop solution is later than the Trigger Date for
the selected alternative regulated transmission solution; and (iv) the Trigger Date
for the selected alternative regulated transmission solution has or will occur
within thirty-six months of the date of the ISO’s presentation of the Viability and
Sufficiency Assessment to the ESPWG, the ISO shall trigger the selected
alternative regulated transmission solution at its Trigger Date. The ISO will
inform the Other Developer or Transmission Owner that it should submit the
selected alternative regulated transmission solution to the appropriate
governmental agency(ies) and/or authority(ies) to begin the necessary approval
process to site, construct, and operate the solution. In response to the ISO’s
request, the Other Developer or Transmission Owner shall make such a
submission to the appropriate governmental agency(ies) and/or authority(ies).
Prior to the Trigger Date for the regulated backstop solution, the ISO will review
the status of the development by the Other Developer or Transmission Owner of
the selected alternative regulated transmission solution, including, but not limited
to, reviewing: (i) whether the Developer has executed a Development Agreement
or requested that it be filed unexecuted with the Commission pursuant to Section
31.2.8.1.6; (ii) whether the Developer is timely progressing against the
milestones set forth in the Development Agreement; and (iii) the status of the
Developer’s obtaining required permits or authorizations, including whether the
Developer has received its Article VII certification or other applicable siting
permits or authorizations under New York State law. If, based on its review, the
ISO determines prior to or at the Trigger Date for the regulated backstop solution
that it is necessary for the Responsible Transmission Owner to proceed with a
regulated backstop solution in parallel with the selected alternative regulated
transmission solution to ensure the identified Reliability Need is satisfied by the
need date, the ISO will trigger the regulated backstop solution and report to
stakeholders the reasons for its determination. The Responsible Transmission
Owner shall proceed with due diligence to develop its regulated backstop solution
in accordance with Good Utility Practice and to submit its proposed solution to
the appropriate governmental agency(ies) and/or authority(ies), unless or until
notified by the ISO that it has determined that the regulated backstop solution is
no longer needed as described in Section 31.2.8.2.1 below. If, based on its
review, the ISO decides not to trigger the regulated backstop solution, the ISO
will notify the Responsible Transmission Owner that its regulated backstop
solution is no longer needed and will not be triggered. In such case, the
Responsible Transmission Owner shall be eligible to recover its costs incurred up
to that point in the same manner as it may recover the costs of a halted project in
accordance with Section 31.2.8.2.1.
31.2.8.1.4
If: (i) the ISO determines that there are not sufficient market-based
solutions to meet the identified Reliability Need by the need date; (ii) the ISO
selects an alternative regulated transmission solution as the more efficient or cost-
effective transmission solution to meet the identified Reliability Need; (iii) the
Trigger Date for the regulated backstop solution is earlier than the Trigger Date
for the selected alternative regulated transmission solution; and (iv) the Trigger
Date for the regulated backstop solution has or will occur within thirty-six months
of the date of the ISO’s presentation of the Viability and Sufficiency Assessment
to the ESPWG, the ISO shall trigger both the selected alternative regulated
transmission solution and the regulated backstop solution at the Trigger Date for
the regulated backstop solution. The ISO will inform the Responsible
Transmission Owner that proposed the regulated backstop solution and the Other
Developer or Transmission Owner that proposed the selected alternative regulated
transmission solution that they should submit the proposed solutions to the
appropriate governmental agency(ies) and/or authority(ies) to begin the necessary
approval process to site, construct, and operate the solution. In response to the
ISO’s request, the Responsible Transmission Owner, Other Developer or
Transmission Owner shall make such a submission to the appropriate
governmental agency(ies) and/or authority(ies).
31.2.8.1.5
The ISO may make its determination regarding the triggering of a
regulated solution pursuant to Sections 31.2.8.1.1 through 31.2.8.1.4 in the CRP
or at any time before the approval of the next CRP.
31.2.8.1.6
A Responsible Transmission Owner, Other Developer, or Transmission
Owner must enter into a Development Agreement with the ISO if: (i) the ISO has
selected the regulated transmission solution proposed by the Developer as the
more efficient or cost-effective transmission solution to the Reliability Need, (ii)
the ISO has triggered the regulated backstop transmission solution pursuant to
Sections 31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4, or (iii) the Responsible Transmission
Owner has agreed to complete a selected alternative regulated transmission
solution pursuant to Section 31.2.10.1.3. The ISO shall tender the Responsible
Transmission Owner, Other Developer, or Transmission Owner a draft
Development Agreement with draft appendices as soon as reasonably practicable
considering the project’s Trigger Date following, as applicable: (i) the ISO’s
selection of the proposed solution, (ii) the ISO’s triggering of a regulated
backstop transmission solution pursuant to Sections 31.2.8.1.2, 31.2.8.1.3, or
31.2.8.1.4, or (iii) the Responsible Transmission Owner’s agreement to complete
an alternative regulated transmission solution pursuant to Section 31.2.10.1.3.
The draft will be completed by the ISO to the extent practicable for review and
completion by the Developer. The draft Development Agreement shall be in the
form of the ISO’s Commission-approved Development Agreement, which is in
Appendix C in Section 31.7 of this Attachment Y. The ISO and the Developer
shall finalize the Development Agreement and appendices and negotiate
concerning any disputed provisions. For purposes of finalizing the Development
Agreement, the ISO and Developer shall develop the description and dates for the
milestones necessary to develop and construct the selected project by the required
in-service date identified in the CRP report or updated CRP report, as applicable,
including the milestones for obtaining all necessary authorizations. Any
milestone that requires action by a Connecting Transmission Owner or Affected
System Operator identified pursuant to Attachment P of the ISO OATT to
complete must be included as an Advisory Milestone, as that term is defined in
the Development Agreement. Unless otherwise agreed by the ISO and the
Developer, the Developer must execute the Development Agreement within three
(3) months of the ISO’s tendering of the draft Development Agreement; provided,
however, if, during the negotiation period, the ISO or the Developer determines
that negotiations are at an impasse, the ISO may file the Development Agreement
in unexecuted form with the Commission on its own or following the Developer’s
request in writing that the agreement be filed unexecuted. If the Development
Agreement resulting from the negotiation between the ISO and the Developer
does not conform with the Commission-approved standard form in Appendix C in
Section 31.7 of this Attachment Y, the ISO shall file the agreement with the
Commission for its acceptance within thirty (30) Business Days after the
execution of the Development Agreement by both parties. If the Developer
requests that the Development Agreement be filed unexecuted, the ISO shall file
the agreement at the Commission within thirty (30) Business Days of receipt of
the request from the Developer. The ISO will draft to the extent practicable the
portions of the Development Agreement and appendices that are in dispute and
will provide an explanation to the Commission of any matters as to which the
parties disagree. The Developer will provide in a separate filing any comments
that it has on the unexecuted agreement, including any alternative positions it may
have with respect to the disputed provisions.
31.2.8.1.7
Upon the ISO’s and Developer’s execution of the Development
Agreement or the ISO’s filing of an unexecuted Development Agreement with the
Commission pursuant to Section 31.2.8.1.6, the ISO and Developer shall perform
their respective obligations in accordance with the terms of the Development
Agreement that are not in dispute, subject to modifications by the Commission.
The Connecting Transmission Owner(s) and Affected System Operator(s) that are
identified in Attachment P of the ISO OATT in connection with the selected
alternative regulated transmission solution shall act in good faith in timely
performing their obligations that are required for the Developer to satisfy its
obligations under the Development Agreement.
31.2.8.1.8
Other Developers and Transmission Owners proposing alternative
regulated solutions that the ISO has determined will resolve the identified
Reliability Need may submit these proposals to the appropriate governmental
agency(ies) and/or authority(ies) for review. The ISO does not determine the
solution that will be permitted by the appropriate governmental agency(ies) and/or
authority(ies) with jurisdiction over siting or whether the regulated backstop
solution or an alternative regulated solution will be constructed to address the
identified Reliability Need. If the appropriate governmental agency(ies) and/or
authority(ies) makes a final determination that an alternative regulated solution
should be permitted and constructed to satisfy a Reliability Need and that the
regulated backstop solution should not proceed, implementation of the alternative
regulated solution will be the responsibility of the Transmission Owner or Other
Developer that proposed the alternative regulated solution, and the Responsible
Transmission Owner will not be responsible for addressing the Reliability Need
through the implementation of its regulated backstop solution. Should a regulated
solution not be implemented, the ISO may request a Gap Solution pursuant to
Section 31.2.11 of this Attachment Y.
31.2.8.2 Halting and Related Cost Recovery Requirements
31.2.8.2.1
If the ISO has triggered a regulated backstop solution under Sections
31.2.8.1.2, 31.2.8.1.3, 31.2.8.1.4, or 31.2.8.1.5, the ISO will immediately notify
the Responsible Transmission Owner, post such notice on its website, and will
state in the next CRP if it determines that the regulated backstop solution is no
longer needed and should be halted because either: (i) the ISO has determined that
there are sufficient market-based solutions to ensure that the identified Reliability
Need is met by the need date, or (ii) the ISO: (A) has triggered an alternative
regulated transmission solution that the ISO selected in the CRP as the more
efficient or cost effective transmission solution and (B) has determined that it is
no longer necessary for the Responsible Transmission Owner to proceed with a
regulated backstop solution in parallel with the selected alternative regulated
transmission solution to ensure the identified Reliability Need is satisfied by the
need date. In making its determination under Section 31.2.8.2.1(ii), the ISO will
review the status of the development by the Other Developer or Transmission
Owner of the selected alternative regulated transmission solution, including, but
not limited to, reviewing: (i) whether the Developer has executed a Development
Agreement or requested that it be filed unexecuted with the Commission pursuant
to Section 31.2.8.1.6; (ii) whether the Developer is timely progressing against the
milestones set forth in the Development Agreement; and (iii) the status of the
Developer’s obtaining required permits or authorizations, including whether the
Developer has received its Article VII certification or other applicable siting
permits or authorizations under New York State law.
If a regulated backstop solution is halted by the ISO, all of the costs
incurred and commitments made by the Responsible Transmission Owner up to
that point, including reasonable and necessary expenses incurred to implement an
orderly termination of the project, to the extent permitted by the Commission in
accordance with its regulations on abandoned plant recovery, will be recoverable
by the Responsible Transmission Owner under the cost recovery mechanism in
Rate Schedule 10 of this tariff regardless of the nature of the solution.
31.2.8.2.2
If the ISO has triggered an alternative regulated transmission project under
Sections 31.2.8.1.3 or 31.2.8.1.4 that the ISO has selected as the more efficient or
cost effective solution, the ISO will immediately notify the Other Developer or
Transmission Owner, post such notice on its website, and will state in the next
CRP if it determines that the regulated transmission solution is no longer needed
and should be halted because the ISO has determined that there are sufficient
market-based solutions to ensure that the identified Reliability Need is met by the
need date.
If a selected alternative regulated transmission solution is halted by the
ISO, all of the costs incurred and commitments made by the Other Developer or
Transmission Owner up to that point, including reasonable and necessary
expenses incurred to implement an orderly termination of the project, to the extent
permitted by the Commission in accordance with its regulations on abandoned
plant recovery, will be recoverable by the Other Developer or Transmission
Owner under the cost recovery mechanism in Rate Schedule 10 of this tariff.
31.2.8.2.3
Once the Responsible Transmission Owner receives state regulatory
approval of the regulated backstop solution, or, if state regulatory approval is not
required, once the Responsible Transmission Owner receives necessary regulatory
approval, the entry of a market-based solution or an alternative regulated
transmission solution will not result in the halting by the ISO of the regulated
backstop solution pursuant to Section 31.2.8.2.1. Similarly, once the Other
Developer or Transmission Owner receives its state regulatory approval or any
other necessary regulatory approval of its triggered alternative regulated
transmission solution, the entry of a market-based solution will not result in the
halting by the ISO of the regulated transmission solution pursuant to Section
31.2.8.2.2.
31.2.8.2.4
The ISO is not required to review market-based solutions to determine
whether they will meet the identified Reliability Need by the need date after the
triggered alternative regulated transmission solution or regulated backstop
solution has received federal and state regulatory approval, unless a federal or
state regulatory agency requests the ISO to conduct such a review. The ISO will
report the results of its review to the federal or state regulatory agency, with
copies to the Responsible Transmission Owner, Other Developer, or Transmission
Owner.
31.2.8.2.5
If the appropriate federal, state or local agency(ies) does not approve a
necessary authorization for the triggered regulated backstop solution or alternative
regulated transmission solution, all of the necessary and reasonable costs incurred
and commitments made up to the final federal, state or local regulatory decision,
including reasonable and necessary expenses incurred to implement an orderly
termination of the project, to the extent permitted by the Commission in
accordance with its regulations on abandoned plant recovery, will be recoverable
by the Responsible Transmission Owner, Other Developer, or Transmission
Owner under the ISO cost recovery mechanism in Rate Schedule 10 of the ISO
OATT regardless of the nature of the solution.
31.2.8.2.6
If a necessary federal, state or local authorization for a triggered
alternative regulated transmission solution or regulated backstop solution is
withdrawn, all expenditures and commitments made up to that point including
reasonable and necessary expenses incurred to implement an orderly termination
of the project, to the extent permitted by the Commission in accordance with its
regulations on abandoned plant recovery, will be recoverable under the ISO cost
recovery mechanism in Rate Schedule 10 of the ISO OATT by the Responsible
Transmission Owner, Other Developer, or Transmission Owner regardless of the
nature of the solution.
31.2.8.2.7
If a material modification to the regulated backstop solution or the
alternative regulated transmission solution is proposed by any federal, state or
local agency, the Responsible Transmission Owner, Other Developer, or
Transmission Owner will request the ISO to conduct a supplemental reliability
review. If the ISO identifies any reliability deficiency in the modified solution,
the ISO will so advise the Responsible Transmission Owner, Other Developer, or
Transmission Owner and the appropriate federal, state or local regulatory
agency(ies).
31.2.8.3 Criteria for Cutoff Date of Market-Based Solution
31.2.8.3.1
The ISO will apply the criteria in this Section 31.2.8.3 for determining the
cutoff date for a determination that a market-based solution will not be available
to meet a Reliability Need by the need date.
31.2.8.3.2
In the first instance, the ISO shall employ its procedures for monitoring
the viability of a market-based solution to determine when it may no longer be
viable. Under the conditions where a market-based solution is proceeding after
the Trigger Date for the relevant regulated solution, it becomes even more critical
for the ISO to conduct a continued analysis of the viability of such market-based
solutions.
31.2.8.3.3
The Developer of such a market-based solution shall submit updated
information to the ISO twice during each reliability planning process cycle, first
during the input phase of the RNA, and again during the solutions phase during
the period allowed for the solicitation for market-based and regulated solutions.
If no solutions are requested in a particular year, then the second update will be
provided during the ISO’s analysis of whether existing solutions continue to meet
identified Reliability Needs. The updated information of the project status shall
include: status of final permits, status of major equipment, current status of
construction schedule, estimated in-service date, any potential impediments to
completion by the Target Year, and any other information requested by the ISO.
31.2.8.3.4
The Developer shall immediately report to the ISO when it has any
indication of a material change in the project status or that the project in-service
date may slip beyond the Target Year. A material change shall include, but not be
limited to, a change in the financial viability of the Developer, a change in siting
status, or a change in a major element of the project development.
31.2.8.3.5
Based upon the above information, the ISO will perform an independent
review of the development status of the market-based solution to determine
whether it remains viable to meet the identified Reliability Need by the need date.
If the ISO, at any time, learns of a material change in the project status of a
market-based solution, it may, at that time, make a determination as to the
continued viability of such project.
31.2.8.3.6
The ISO, prior to making a determination about the viability of a specific
proposed solution, will communicate its intended determination to the project
Developer along with the basis for its intended determination. The ISO shall
provide the Developer a reasonable period (not more than 2 weeks) to respond to
the ISO’s intended determination, including an opportunity to provide additional
information to the ISO to support the continued viability of the proposed solution.
31.2.8.3.7
If the ISO determines that a market-based solution that is needed to meet
an identified Reliability Need is no longer viable, it will request that a regulated
solution proceed or seek other measures including, but not limited to, a Gap
Solution, to ensure the reliability of the system.
31.2.8.3.8
If the ISO determines that the market-based solution is still viable, but that
its in-service date is likely to slip beyond the Target Year, the ISO may, if needed,
request the Responsible Transmission Owner to prepare a Gap Solution in
accordance with the provisions of Section 31.2.11 of this Attachment Y.
31.2.9
Process for Consideration of Regulated Backstop Solution and Alternative
Regulated Solutions
Upon a determination by the ISO under Section 31.2.8 that a regulated solution should
proceed, the Responsible Transmission Owner, Other Developer, or Transmission Owner will
make a presentation to the ESPWG that will provide a description of the regulated solution. The
presentation will include a non-binding preliminary cost estimate of that regulated solution;
provided, however, that the Responsible Transmission Owner, Other Developer or Transmission
Owner shall be entitled to full recovery of all reasonably incurred costs as described in Rate
Schedule 10 of the ISO OATT. The ISO and stakeholders through this process will have the
opportunity to review and discuss the scope of the projects and their associated non-binding
preliminary cost estimates prior to implementation.
31.2.10 Process for Addressing Inability of Responsible Transmission Owner,
Other Developer, or Transmission Owner to Complete Triggered
Regulated Solution
31.2.10.1
The ISO may take the actions described in Sections 31.2.10.1.1 through
31.2.10.1.4 as soon as practicable if: (i) a Responsible Transmission Owner, Other
Developer or Transmission Owner of a regulated transmission solution is required
to enter into a Development Agreement pursuant to Section 31.2.8.1.6, and (ii)
one of the following events occur: (A) the Responsible Transmission Owner,
Other Developer or Transmission Owner responsible for the regulated
transmission solution does not execute the Development Agreement, or does not
request that it be filed unexecuted with the Commission, within the timeframes set
forth in Section 31.2.8.1.6, or (B) the ISO determines that an effective
Development Agreement may be terminated or terminates the Development
Agreement under the terms of the agreement prior to the completion of the term
of the agreement.
31.2.10.1.1
If the Development Agreement has been filed with and accepted by the
Commission and is terminated under the terms of the agreement, the ISO shall,
upon terminating the Development Agreement, file a notice of termination with
the Commission.
31.2.10.1.2
The ISO may revoke its selection of the regulated transmission solution
and the eligibility of the Developer to recover its costs pursuant to the ISO’s
regional cost allocation mechanism; provided, however, the Developer may
recover its costs to the extent provided in Sections 31.2.8.1.1, 31.2.8.2.1,
31.2.8.2.2, 31.2.8.2.5, and 31.2.8.2.6 or as otherwise determined by the
Commission; provided, further, that if the Developer is the Responsible
Transmission Owner, it may also recover costs to the extent permitted under the
ISO/TO Reliability Agreement.
31.2.10.1.3
The ISO may take one or more of the following actions to address the
Reliability Need based on the particular circumstances: (i) address the Reliability
Need in the CRP for the next planning cycle; (ii) direct the Developer to continue
with the development of its regulated transmission solution for completion
beyond the in-service date required to address the Reliability Need; (iii) direct the
Responsible Transmission Owner to proceed with its regulated backstop solution
if it has not yet been halted by the ISO pursuant to Section 31.2.8.2.1; (iv) request
that the Responsible Transmission Owner complete the selected alternative
regulated transmission solution; (v) commence the Gap Solution process under
Section 31.2.11; (vi) adopt new ISO or Transmission Owner operating
procedures; and/or (vii) take any other action the ISO reasonably considers is
appropriate to address the Reliability Need. If a Responsible Transmission Owner
agrees to complete the selected alternative regulated transmission solution, it shall
enter into a Development Agreement with the ISO in accordance with Sections
31.2.8.1.6 and 31.2.8.1.7.
31.2.10.1.4
If the Responsible Transmission Owner agrees to complete the selected
alternative regulated transmission solution, the Responsible Transmission Owner
and the Other Developer or Transmission Owner that proposed the selected
alternative regulated transmission solution shall work cooperatively with each
other to implement the transition, including negotiating in good faith with each
other to transfer the project; provided, however, that the transfer is subject to: (i)
any required approvals by the appropriate governmental agency(ies) and/or
authority(ies), (ii) any requirements or restrictions on the transfer of Developer’s
rights-of-way under federal or state law, regulation, or contract (including
mortgage trust indentures or debt instruments), and (iii), if the Developer is a New
York public authority, any requirements or restrictions on the transfer under the
New York Public Authorities Law; provided, further, that the Responsible
Transmission Owner and the Developer will address any disputes regarding the
transfer of the project in accordance with the dispute resolution provisions in
Article 11 of the ISO Services Tariff.
31.2.10.2 If: (i) the Responsible Transmission Owner’s non-transmission or partial
transmission regulated backstop solution has been triggered by the ISO under
Sections 31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4, and the regulated backstop solution
has not been halted by the ISO under Section 31.2.8.2.1, and (ii) the ISO
determines that the Responsible Transmission Owner: (A) has not submitted its
proposed regulated backstop solution for necessary regulatory action within a
reasonable period of time, (B) is unable to or fails to obtain the approvals or
property rights necessary to construct the project, or (C) is otherwise not taking
the actions necessary to construct the project to satisfy the Reliability Need by the
need date, the ISO shall: (i) submit a report to the Commission for its
consideration and determination of whether action is appropriate under federal
law, and (ii) take such action as it reasonably considers is appropriate to ensure
that the Reliability Need is satisfied by the need date.
31.2.11 Gap Solutions
31.2.11.1
If the ISO determines that neither market-based proposals nor regulated
proposals can satisfy the Reliability Needs by the need date, the ISO will set forth
its determination that a Gap Solution is necessary in the CRP. The ISO will also
request the Responsible Transmission Owner to seek a Gap Solution. Gap
Solutions may include generation, transmission, or demand side resources.
31.2.11.2
If there is an imminent threat to the reliability of the New York State
Power System, the ISO Board, after consultation with the NYDPS, may request
the appropriate Transmission Owner or Transmission Owners to propose a Gap
Solution outside of the normal planning cycle.
31.2.11.3
Notwithstanding Sections 31.2.11.1 and 31.2.11.2, if a Market Participant
notifies the ISO of its intent for its Generator to be Retired or to enter into a
Mothball Outage pursuant to Section 38.3.1 of Attachment FF of the ISO OATT
or if a Market Participant’s Generator enters into an ICAP Ineligible Forced
Outage pursuant to Section 5.18.2.1 of the ISO Services Tariff, the ISO will
evaluate whether a Generator Deactivation Reliability Need or an immediate
reliability need will result from the Generator’s deactivation and will address any
resulting Generator Deactivation Reliability Need or immediate reliability need in
accordance with the Generator Deactivation Process set forth in Attachment FF of
the ISO OATT.
31.2.11.4
Upon the ISO’s determination of the need for a Gap Solution, pursuant to
Sections 31.2.11.1 or 31.2.11.2 above, the Responsible Transmission Owner will
propose such a solution as soon as reasonably possible, for consideration by the
ISO and NYDPS. The Responsible Transmission Owner shall be eligible to
recover its costs for developing its Gap Solution proposal and seeking necessary
approvals pursuant to the cost recovery requirements in Section 31.5.6 of this
Attachment Y and Rate Schedule 10 of the ISO OATT.
31.2.11.5
Any party may submit an alternative Gap Solution proposal to the ISO and
the NYDPS for their consideration. The ISO shall evaluate all Gap Solution
proposals to determine whether they will meet the Reliability Need or imminent
threat. The ISO will also evaluate, as an alternative Gap Solution proposal, any
Generator in a Mothball Outage or an ICAP Ineligible Forced Outage to
determine whether its return to service would meet the Reliability Need or
imminent threat; provided, however, that the Mothball Outage began on or after
May 1, 2015 and the ICAP Ineligible Forced Outage followed a Forced Outage
that began after May 1, 2015. The ISO will report the results of its evaluation to
the party making the proposal, or to the Generator when evaluating its return to
service, as well as to the NYDPS and/ or other appropriate governmental
agency(ies) and/or authority(ies) for consideration in their review of the
proposals. The appropriate governmental agency(ies) and/or authority(ies) with
jurisdiction over the implementation or siting of Gap Solutions will determine
whether the Gap Solution or an alternative Gap Solution will be implemented to
address the identified Reliability Need. When the return to service of a Generator
in a Mothball Outage or an ICAP Ineligible Forced Outage has been selected as
either the Gap Solution or to resolve a reliability issue arising on a non-New York
State Bulk Power Transmission Facility during its outage, the compensation and
return to service procedures set forth in Section 5.18.4 of the Services Tariff shall
apply.
31.2.11.6
A Responsible Transmission Owner, Other Developer, or Transmission
Owner may recover its costs with respect to a transmission Gap Solution that is
implemented pursuant to Section 31.2.11.5 in accordance with the cost recovery
requirements in Section 31.5.6 of this Attachment Y and Rate Schedule 10 of the
ISO OATT.
31.2.11.76
Gap Solution proposals submitted under Sections 31.2.11.4 and 31.2.11.5
shall be designed to be temporary solutions and to strive to be compatible with
permanent market-based proposals.
31.2.11.87
A permanent regulated solution, if appropriate, may proceed in parallel
with a Gap Solution.
31.2.12 Confidentiality of Solutions
31.2.12.1
The term “Confidential Information” shall include all types of solutions to
Reliability Needs that are submitted to the ISO as a response to Reliability Needs
identified in any RNA issued by the ISO as part of the reliability planning process
if the Developer of that solution designates such reliability solutions as
“Confidential Information.” Notwithstanding the requirements in this Section
31.2.12 or the Developer’s designation of project information as “Confidential
Information,” the ISO may publicly disclose information regarding the proposed
facility that the ISO is required to disclose under its interconnection or
transmission expansion processes pursuant to Sections 3.7 or 4.5 of the ISO
OATT or Attachments X or P of the ISO OATT.
31.2.12.2
For regulated backstop solutions and plans submitted by the Responsible
Transmission Owner in response to the findings of the RNA, the ISO shall
maintain the confidentiality of same until the ISO and the Responsible
Transmission Owner have agreed that the Responsible Transmission Owner has
submitted viable and sufficient regulated backstop solutions and plans to meet the
Reliability Needs identified in an RNA and the Responsible Transmission Owner
consents to the ISO’s inclusion of the proposed solution in the CRP. Thereafter,
the ISO shall disclose the regulated backstop solutions and plans to the Market
Participants; however, any preliminary cost estimates that may have been
provided to the ISO shall not be disclosed.
31.2.12.3
For an alternative regulated response, the ISO shall determine, after
consulting with the Developer thereof, whether the response would meet a
Reliability Need identified in an RNA, whether the response is viable and
sufficient to meet all or part of the Reliability Need, and the Developer consents
to the ISO’s inclusion of the proposed solution in the CRP. Thereafter, the ISO
shall disclose the alternative regulated response to the Market Participants and
other interested parties; however, any preliminary cost estimates that may have
been provided to the ISO shall not be disclosed.
31.2.12.4
For a market-based response, the ISO shall maintain the confidentiality of
same during the reliability planning process and in the CRP, except for the
following information which may be disclosed by the ISO: (i) the type of
resource proposed (e.g., generation, transmission, demand side); (ii) the size of
the resource expressed in megawatts of equivalent load that would be served by
that resource; (iii) the subzone in which the resource would interconnect or
otherwise be located; and (iv) the proposed in-service date of the resource.
31.2.12.5
In the event that the Developer of a market-based response has made a
public announcement of its project or has submitted a proposal for
interconnection with the ISO, the ISO shall disclose the identity of the market-
based Developer and the specific project during the reliability planning process
and in the CRP.
31.2.13 Monitoring of Reliability Project Status
31.2.13.1
The ISO will monitor and report on the status of market-based solutions to
ensure their continued viability to meet Reliability Needs by the need date in the
CRP. The ISO shall assess the continued viability of such projects using the
following criteria:
31.2.13.1.1
Between three and five years before the Trigger Date for a regulated
solution, the ISO will use a screening analysis to verify the feasibility of the
proposed market-based solution (this analysis will not require final permit
approvals or final contract documents).
31.2.13.1.2
Between one and two years before the Trigger Date for a regulated
solution, the ISO will perform a more extensive review of the proposed market-
based solution, including such elements as: status of the required interconnection
studies, contract negotiations, permit applications, financing, and Site Control.
31.2.13.1.3
Less than one year before the Trigger Date of a regulated solution, the ISO
will perform a detailed review of the market-based solution’s status and schedule,
including the status of: (1) final permits; (2) required interconnection studies; (3)
the status of an interconnection agreement; (4) financing; (5) equipment; and (6)
the implementation of construction schedules.
31.2.13.1.4
If the ISO, following its analysis, determines that a proposed market-based
solution is no longer viable to meet the Reliability Need, the proposed market-
based solution will be removed from the list of potential market-based solutions.
31.2.13.2
The ISO will monitor and report on the status of regulated solutions to
ensure their continued viability to meet Reliability Needs by the need date in the
CRP. The ISO will undertake this monitoring and reporting in accordance with
this Attachment Y, ISO Procedures, and the terms of the Development Agreement
(if applicable) until the project has been completed and is in-service or has been
halted in accordance with this Attachment Y or the terms of the Development
Agreement (if applicable). Prior to the Trigger Date for the regulated solution,
the ISO shall assess the continued viability of regulated solutions using the
following criteria:
31.2.13.2.1
Between three and five years before the Trigger Date for the regulated
solution, the ISO will use a screening analysis to verify the feasibility of the
regulated solution.
31.2.13.2.2
Between one and two years before the Trigger Date for the regulated
solution, the ISO will perform a more extensive review of the proposed regulated
solution, including such elements as: the status of the required interconnection
studies, contract negotiations, permit applications, financing, and Site Control.
31.2.13.2.3
Less than one year before the Trigger Date for the regulated solution, the
ISO will perform a detailed review of the regulated solution’s status, including the
status of: (1) final permits; (2) required interconnection studies; (3) the status of
an interconnection agreement; (4) financing; (5) equipment; and (6) the
implementation of construction schedules.
31.2.13.2.4
Prior to making a determination about the viability of a regulated solution,
the ISO will communicate its intended determination to the project sponsor along
with the basis for its intended determination, and will provide the sponsor a
reasonable period (not more than two weeks) to respond to the ISO’s intended
determination, including an opportunity to provide additional information to the
ISO to support the continued viability of the proposed regulated solution. If the
ISO, following its analysis, determines that a proposed regulated solution is no
longer viable to meet the Reliability Need, the proposed regulated solution will be
removed from the list of potential regulated solutions.
31.3
Economic Planning Process
31.3.1
Congestion Assessment and Resource Integration Study for Economic
Planning
31.3.1.1 General
The ISO shall prepare and publish the CARIS as described below. Each CARIS shall (1)
develop a ten-year projection of congestion and shall identify, rank, and group the most
congested elements on the New York bulk power system based on historic and projected
congestion; and (2) include three studies, selected pursuant to Section 31.3.1.2.2, of the potential
impacts of generic solutions to mitigate the identified congestion.
The CARIS process shall determine whether to approve an Interregional Transmission
Project, identified and evaluated under the “Analysis and Consideration of Interregional
Transmission Projects” section of the Interregional Planning Protocol, if any, and proposed in the
NYISO’s economic planning process, as an economic transmission project in lieu of a proposed
regional economic transmission project for regulated cost allocation and recovery under the ISO
Tariff.
The CARIS will align with the reliability planning process.
31.3.1.2 Interested Party Participation in the Development of the CARIS
31.3.1.2.1
The ISO shall develop the CARIS in consultation with Market Participants
and all other interested parties. The TPAS will have responsibilities consistent
with ISO Procedures for review of the ISO’s technical analyses. ESPWG will
have responsibilities consistent with ISO Procedures for providing commercial
input and assumptions to be used in the development of the congestion assessment
and the congestion assessment scenarios provided for under Section 31.3.1.5, and
in the reporting and analysis of congestion costs. Coordination and
communication will be established and maintained between these two groups and
ISO staff to allow Market Participants and other interested parties to participate in
a meaningful way during each stage of the economic planning process. The ISO
staff shall report any majority and minority views of these collaborative
governance work groups when it submits the CARIS to the Business Issues
Committee for a vote, as provided below.
31.3.1.2.2
The ISO, in conjunction with ESPWG, will develop criteria for the
selection and grouping of the three congestion and resource integration studies
that comprise each CARIS, as well as for setting the associated timelines for
completion of the selected studies. Study selection criteria may include
congestion estimates, and shall include a process to prioritize the three studies that
comprise each CARIS. Criteria shall also include a process to set the cut off date
for inputs into and completion of each CARIS study cycle.
31.3.1.2.3
The ISO, in conjunction with ESPWG, will develop a process by which
interested parties can request and fund other congestion and resource integration
studies, in addition to those included in each CARIS. These individual congestion
and resource integration studies are in addition to those studies that a customer
can request related to firm point-to-point transmission service pursuant to Section
3.7 of the ISO OATT, studies that a customer can request related to Network
Integration Transmission Service pursuant to Section 4.5 of the ISO OATT,
studies related to interconnection requests under Attachment X or Attachment Z
of the ISO OATT, or studies related to Transmission Interconnection Applications
under Attachment P.
31.3.1.2.4
The ISO shall post all requests for congestion and resource integration
studies on its website.
31.3.1.3 Preparation of the CARIS
31.3.1.3.1
The Study Period for the CARIS shall be the same ten-year Study Period
covered by the most recently approved CRP.
31.3.1.3.2
The CARIS will assume a reliable system throughout the Study Period,
based first upon the solutions identified in the most recently completed viability
and sufficiency analysis performed pursuant to 31.2.5.7, as part of the CRP
process, and reported to stakeholders and the NYDPS for comment. The baseline
system for the CARIS shall first incorporate sufficient viable market-based
solutions to meet the identified Reliability Needs as well as any regulated
backstop solutions triggered by an ISO request pursuant to Section 31.2.8 of this
Attachment Y. The ISO, in conjunction with the ESPWG, will develop
methodologies to scale back market-based solutions to the minimum needed to
meet the identified Reliability Needs, if more have been proposed than are
necessary to meet the identified Reliability Needs. Regulated backstop solutions
that have been proposed but not triggered pursuant to Section 31.2.8 shall also be
used if there are insufficient market-based solutions for the ten-year Study Period.
Multiple market-based solutions, as well as regulated solutions to Reliability
Needs, may be included in the scenario assessments described in Section 31.3.1.5.
31.3.1.3.3
In conducting the CARIS, the ISO shall combine the component studies
selected and assess system congestion and resource integration over the Study
Period, measuring congestion by the metrics discussed in Appendix A to this
Attachment Y. The ISO, in conjunction with the ESPWG, will develop the
specific production costing model to be used in the CARIS. All resource types
shall be considered on a comparable basis as potential solutions to the congestion
identified: generation, transmission, demand response, and energy efficiency.
The CARIS may include consideration of the economic impacts of advancing a
regulated back stop solution contained in the CRP.
31.3.1.3.4
In conducting the CARIS, the ISO shall conduct benefit/cost analysis of
each potential solution to the congestion identified, applying benefit/cost metrics
that are described in this Section 31.3.1.3. The principal benefit metric for the
CARIS analysis will be expressed as the present value of the NYCA-wide
production cost reduction that would result from each potential solution. The
present value of the NYCA-wide production cost reduction will be determined in
accordance with the following formula:
Present Value in year 1 = Sum of the Present Values from each of the 10 years of the
Study Period.
The discount rate to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners.
31.3.1.3.5
Additional benefit metrics shall include estimates of reductions in losses,
LBMP load costs, generator payments, ICAP costs, Ancillary Services costs,
emission costs, and TCC payments. The ISO will work with the ESPWG to
determine the most useful metrics for each CARIS cycle, given overall ISO
resource requirements. The additional metrics will estimate the benefits of the
potential generic solutions in mitigating the congestion identified for information
purposes only. All the quantities, except ICAP, will be the result of the forward
looking production cost simulation. The additional benefit metrics will be
determined by measuring the difference between the CARIS base case system
value and a system value when the potential generic solution is added. All four
resource types will be considered as potential generic solutions to the congestion
identified, such as generation, transmission, and/or demand response. The value
of the additional metrics will be expressed in present value by using the following
formula:
Present Value in year 1 = Sum of the Present Values from each of the 10 years of the
Study Period.
The discount rate to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners. The
definitions of the LBMP load cost metric, generator payments metric, reduction in
losses metric, Ancillary Services costs metric, and TCC payment metric are set
forth below.
31.3.1.3.5.1 LBMP load costs measure the change in total load payments and
unhedged load payments. Total load payments will include the LBMP payments
(energy, congestion and losses) paid by electricity demand (forecasted load,
exports, and wheeling). Exports will be consistent with the input assumptions for
each neighboring control area. Unhedged load payments will represent total load
payments minus the TCC payments.
31.3.1.3.5.2 Reductions in losses measure the change in marginal losses payments.
Losses payments will be based upon the loss component of the zonal LBMP load
payments.
31.3.1.3.5.3 Generator payments measure the change in generation payments.
Generation payments will include the LBMP payments (energy, congestion,
losses), and Ancillary Services payments made to electricity suppliers. Ancillary
Services costs will include payments for Regulation Services and Operating
Reserves, including 10 Minute Synchronous, 10 Minute Non-synchronous and 30
Minute Non-synchronous. Generator payments will be the sum of the LBMP
payments and Ancillary Services payments to generators and imports. Imports
will be consistent with the input assumptions for each neighboring Control Area.
31.3.1.3.5.4 The TCC payment metric set forth below will be used for purposes of the
study phase of the CARIS process, and will not be used for regulated economic
transmission project cost allocation under Section 31.5.4.4 of this Attachment Y.
The TCC payment metric will measure the change in total congestion rents
collected in the day-ahead market. These congestion rents shall be calculated as
the product of the Congestion Component of the Day-Ahead LBMP in each Load
Zone or Proxy Generator Bus and the withdrawals scheduled in each hour at that
Load Zone or Proxy Generator Bus, minus the product of the Congestion
Component of the Day-Ahead LBMP at each Generator Bus or Proxy Generator
Bus and the injections scheduled in each hour at that Generator bus or Proxy
Generator Bus, summed over all locations and hours.
31.3.1.3.5.5 The emission metric will measure the change in CO2, NOx, and SO2,
emissions in tons on a zonal basis as well as the change in emission cost by
emission type. Emission costs will be reflected in the development of the
production cost curve.
31.3.1.3.5.6 The calculation of the ICAP cost metric will be determined as set forth
below. The ICAP cost metric will be highly dependent on the rules and
procedures guiding the calculation of the IRM, LCR, and the ICAP Demand
Curves, both for the next capability period and future capability periods. In each
CARIS cycle, the ISO will review, with the ESPWG and, as appropriate, other
ISO committees, the results of the ICAP cost metric.
31.3.1.3.5.6.1 The ICAP metric, in the form of a megawatt impact, will be computed for
both generic and actual economic project proposals based on a methodology that:
(1) determines the base system LOLE for the applicable horizon year; (2) adds the
proposed project; and (3) calculates the LOLE for the system with the addition of
the proposed project. If the system LOLE is lower than that of the base system,
the ISO will reduce generation in all NYCA zones proportionally (i.e., based on
proportion of zonal capacity to total NYCA capacity) until the base system LOLE
is achieved. That amount of reduced generation is the NYCA megawatt impact.
31.3.1.3.5.6.2 The ISO will calculate both of the following ICAP cost metrics described
in subsections (1) and (2) below by first determining the megawatt impact
described above in Section 31.3.1.3.5.6.1 and then:
(1)
For Rest of State, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in Rest of State under the assumption that the proposed generic
project is not in place, with that forecast based on the latest available ICAP
Demand Curve for the NYCA and the amount of Installed Capacity available in
the NYCA, as shown in the NYISO Load and Capacity Data Report developed for
that year; and (ii) multiplying that forecasted cost per megawatt-year for Rest of
State in that year by the sum of the megawatt impact for all Load Zones contained
within Rest of State, as calculated in accordance with subsection (A) of this
Section 31.3.1.3.5.4.
For each Locality, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in that Locality under the assumption that the proposed generic
project is not in place, with that forecast based on the latest available ICAP
Demand Curve for that Locality and the amount of Installed Capacity available in
that Locality as shown in the relevant NYISO Load and Capacity Data Report
developed for that year, and (ii) multiplying that forecasted cost per megawatt-
year for that Locality in each year by the sum of the megawatt impact for all Load
Zones contained within that Locality, as calculated in accordance with subsection
(A) of this Section 31.3.1.3.5.4.
This ICAP cost metric will then be presented for each applicable planning year as
a stream of present value benefits for each Locality and for Rest of State. The
applicable planning years start with the proposed commercial operation date of
the proposed generic project and end ten years after the proposed commercial
operation date of the proposed generic project.
(2)
For Rest of State, the ISO will measure the cost impact of a proposed economic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in Rest of State under the assumption that the proposed generic
project is in place, with that forecast based on the latest available ICAP Demand
Curve for the NYCA and the amount of Installed Capacity available in the
NYCA; (ii) subtracting that forecasted cost per megawatt-year from the forecasted
cost per megawatt-year of Installed Capacity in Rest of State calculated in
subsection (1) under the assumption that the proposed generic project is not in
place; and (iii) multiplying that difference by fifty percent (50%) of the assumed
amount of Installed Capacity available in Rest of State as calculated from the
relevant NYISO Load and Capacity Data Report developed for the CARIS
process.
For each Locality, the ISO will measure the cost impact of a proposed generic
project for each planning year by: (i) forecasting the cost per megawatt-year of
Installed Capacity in that Locality under the assumption that the proposed generic
project is in place, with that forecast based on the latest available ICAP Demand
Curve for that Locality and the amount of Installed Capacity available in that
Locality as shown in the relevant NYISO Load and Capacity Data Report
developed for that year; (ii) subtracting the greater of that forecasted cost per
megawatt-year with the proposed generic project in place or the forecasted Rest of
State Installed Capacity cost per megawatt-year with the proposed generic project
in place from the forecasted cost of Installed Capacity in that Locality calculated
in subsection (1) under the assumption that the proposed generic project is not in
place; and (iii) multiplying that difference by fifty percent (50%) of assumed
amount of Installed Capacity available in that Locality, as taken from the relevant
Load and Capacity tables developed for the CARIS process.
This ICAP cost metric will then be represented for each applicable planning year
as a stream of present value benefits for each Locality and for Rest of State. The
applicable planning years start with the proposed commercial operation date of
the proposed generic project and end with the earlier of: (i) the year when the
system, with the proposed generic project in place, reaches an LOLE of 0.1, or (ii)
ten years after the proposed commercial operation date of the proposed generic
project.
(3)
The forecast of Installed Capacity costs per megawatt-year are developed by: first,
escalating the Net Cost of New Entry (“CONE”) for the NYCA or a Locality from
the most recently completed ICAP Demand Curves for each year of the planning
period; second, determining the future proxy Locational Minimum Installed
Capacity Requirement or Minimum Installed Capacity Requirement for the
NYCA as the actual amount of Installed Capacity in the Locality or the NYCA for
the year that NYCA reaches 0.1 LOLE; third, reducing the cost per megawatt-
year in each year from the escalated Net CONE to reflect the excess Installed
Capacity from the NYISO Load and Capacity Data Report above the future proxy
Minimum Installed Capacity Requirement with the adjustment calculated from
the excess and the slope of the ICAP Demand Curve.
The forecasts of Installed Capacity costs for Localities or Rest of State performed
in subsections (1) and (2) above shall, in addition to the assumptions listed above,
be based upon: (i) the forecasted Net CONE for the Locality (the NYCA in the
case of the Rest of State forecast); (ii) the amount of Installed Capacity required
to meet the future proxy Locational Minimum Installed Capacity Requirement
(the Minimum Installed Capacity Requirement for the NYCA in the case of the
Rest of State forecast); (iii) the slope of the relevant ICAP Demand Curve, and
(iv) the smallest quantity where the cost of Installed Capacity on that ICAP
Demand Curve reaches zero.
31.3.1.3.6
As referenced in Section 31.2.1.3, the ISO, using engineering judgment,
will determine whether a regional alternative transmission solution might more
efficiently or more cost effectively address congestion on the BPTFs identified in
the CARIS that impacts more than one Transmission District than any local
transmission solutions identified by the Transmission Owners in their LTPs in the
event the LTPs specify that such transmission solutions are included to address
congestion for economic reasons.
31.3.1.4 Planning Participant Data Input
At the ISO’s request, Market Participants, Developers, and other parties shall provide, in
accordance with the schedule set forth in the ISO Procedures, the data necessary for the
development of the CARIS. This input will include but not be limited to existing and planned
additions and modifications to the New York State Transmission System (to be provided by
Transmission Owners and municipal electric utilities); proposals for merchant transmission
facilities (to be provided by merchant Developers); generation additions and retirements (to be
provided by generator owners and Developers); demand response programs (to be provided by
demand response providers); and any long-term firm transmission requests made to the ISO.
The relevant Transmission Owners will assist the ISO in developing the potential solution cost
estimates to be used by the ISO to conduct benefit/cost analysis of each of the potential
solutions.
31.3.1.5 Congestion and Resource Integration Scenario Development
The ISO, in consultation with the ESPWG, shall develop congestion and resource
integration scenarios addressing the Study Period. Variables for consideration in the
development of these congestion and resource integration scenarios include but are not limited
to: load forecast uncertainty, fuel price uncertainty, new resources, retirements, emission data,
the cost of allowances and potential requirements imposed by proposed environmental and
energy efficiency mandates, as well as overall ISO resource requirements. The ISO shall report
the results of these scenario analyses in the CARIS.
31.3.1.6 Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of an
economic transmission project on such neighboring ISO/RTO Regions using the respective
planning criteria of such ISO/RTO Regions. The ISO shall report the results in the CARIS. The
ISO shall not bear the costs of required upgrades in another region.
31.3.1.7 CARIS Report Preparation
Once all the analyses described above have been completed, ISO staff will prepare a draft
of the CARIS including a discussion of its assumptions, inputs, methodology, and the results of
its analyses.
31.3.2
CARIS Review Process and Actual Project Proposals
31.3.2.1 Collaborative Governance Process
The draft CARIS shall be submitted to both TPAS and the ESPWG for review and
comment. The ISO shall make available to any interested party sufficient information to
replicate the results of the draft CARIS. The information made available will be electronically
masked and made available pursuant to a process that the ISO reasonably determines is
necessary to prevent the disclosure of any Confidential Information or Critical Energy
Infrastructure Information contained in the information made available. Following completion
of that review, the draft CARIS reflecting the revisions resulting from the TPAS and ESPWG
review shall be forwarded to the Business Issues Committee and the Management Committee for
discussion and action.
31.3.2.2 Board Action
Following the Management Committee vote, the draft CARIS, with Business Issues
Committee and Management Committee input, will be forwarded to the ISO Board for review
and action. Concurrently, the draft CARIS will be provided to the Market Monitoring Unit for
its review and consideration. The Board may approve the CARIS as submitted, or propose
modifications on its own motion. If any changes are proposed by the Board, the revised CARIS
shall be returned to the Management Committee for comment. The Board shall not make a final
determination on a revised CARIS until it has reviewed the Management Committee comments.
Upon approval by the Board, the ISO shall issue the CARIS to the marketplace by posting it on
its website.
The responsibilities of the Market Monitoring Unit that are addressed in the above
section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.4 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.3.2.3 Public Information Sessions
In order to provide ample exposure for the market place to understand the content of the
CARIS, the ISO will provide various opportunities for Market Participants and other potentially
interested parties to discuss final CARIS. Such opportunities may include presentations at
various ISO Market Participant committees, focused discussions with various industry sectors,
and /or presentations in public venues.
31.3.2.4 Actual Project Proposals
As discussed in Section 31.3.1 of this Attachment Y, the CARIS analyzes system
congestion over the Study Period and, for informational purposes, provides benefit/cost analysis
and other analysis of potential generic solutions to the congestion identified. If, in response to
the CARIS, a Developer proposes an actual project, including an Interregional Transmission
Project, to address specific congestion identified in the CARIS, then the ISO will: (i) process that
project proposal in accordance with the relevant provisions of Sections 31.5.1, 31.5.4 and 31.5.6
of this Attachment Y, and (ii) for Interregional Transmission Projects, jointly evaluate the project
proposal with the relevant adjacent transmission planning region(s) in accordance with Section
7.3 of the Interregional Planning Protocol.
31.3.2.4.1 Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.3.2.4.1 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.3.2.4.1.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.3.2.4.1.1.1 to demonstrate its capability to satisfy the applicable qualification criteria,
and (ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with
signatory authority, in a form acceptable to the ISO, certifying that the Affiliate will participate
in the Developer’s project in the manner described by the Developer and will abide by the
requirements set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures related and
applicable to the Affiliate’s participation.
31.3.2.4.1.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate and maintain a transmission project proposed to address specific
congestion identified in the CARIS. The ISO shall consider the qualifications of each Developer
in an even-handed and non-discriminatory manner, treating Transmission Owners and Other
Developers alike.
31.3.2.4.1.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a transmission project as a solution to address specific congestion identified in the
CARIS based on the following criteria:
31.3.2.4.1.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.3.2.4.1.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.3.2.4.1.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement or equivalent information;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to address specific congestion identified in the CARIS.
31.3.2.4.1.1.1.4 A detailed plan describing how the Developer - in the absence of
previous experience financing, developing, constructing, operating, or
maintaining transmission facilities - will finance, develop, construct, operate, and
maintain a transmission facility, including the financial, technical, and
engineering qualifications and experience and capabilities of any third parties
with which it will contract for these purposes.
31.3.2.4.1.1.2 Developer Qualification Determination
Any Developer seeking to become qualified may submit the required information, or
update any previously submitted information, at any time. The ISO shall treat on a confidential
basis in accordance with the requirements of its Code of Conduct in Attachment F of the ISO
OATT any non-public financial qualification information that is submitted to the ISO by the
Developer under Section 31.3.2.4.1.1.1.3 and is designated by the Developer as “Confidential
Information.” The ISO shall within 15 days of a Developer’s submittal, notify the Developer if
the information is incomplete. If the submittal is deemed incomplete, the Developer shall submit
the additional information within 30 days of the ISO’s request. The ISO shall notify the
Developer of its qualification status within 30 days of receiving all necessary information. A
Developer shall retain its qualification status for a three-year period following the notification
date; provided, however, that the ISO may revoke this status if it determines that there has been a
material change in the Developer’s qualifications and the Developer no longer meets the
qualification requirements. A Developer that has been qualified shall inform the ISO within
thirty days of any material change to the information it provided regarding its qualifications and
shall submit to the ISO each year its most recent audited annual financial statement when
available. At the conclusion of the three-year period or following the ISO’s revocation of a
Developer’s qualification status, the Developer may re-apply for a qualification status under this
section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated transmission project as a solution to address specific congestion identified
in the CARIS and shall be eligible to use the cost allocation and cost recovery mechanism for
regulated transmission projects set forth in Section 31.5 of this Attachment Y and the appropriate
rRate sSchedule 10 of the ISO OATT for any approved project.
31.3.2.4.1.2 Information Requirements for Projects
The ISO shall consider the criteria in Section 31.3.2.4.2 when determining whether a
proposed project is eligible to be offered as a regulated economic transmission project.
31.3.2.4.1.3 Timing for Submittal of Project Information and Entity Qualification
Information and Opportunity to Provide Additional Information
The required project information may be submitted at any time, but the proposed
regulated economic transmission project will be evaluated against the most recently available
CARIS Phase II database. Any Developer that the ISO has determined under Section
31.3.2.4.1.1.2 to be qualified to propose to develop a transmission project to address specific
congestion identified in the CARIS may submit the required project information; provided,
however, that based on the specific congestion identified that requires a solution, the ISO may
request that the qualified Developer provide additional Developer information. Any Developer
that the ISO has not determined to be qualified, but that wants to propose to develop a project,
must submit to the ISO the information required for Developer qualification under Section
31.3.2.4.1.1. The ISO shall within 30 days of a Developer’s submittal of its Developer
qualification information, notify the Developer if this information is incomplete. The Developer
shall submit additional Developer or project information required by the ISO within 15 days of
the ISO’s request. A Developer that fails to submit the additional Developer qualification
information or the required project information will not be eligible for its project to be
considered in that planning cycle.
31.3.2.4.2 Project Information Requirements
Any Developer seeking to offer a regulated economic transmission project as a solution
to address specific congestion identified in the CARIS must provide, at a minimum, the
following details:
(1) contact information; (2) the lead time necessary to complete the project
including, if available, the construction windows in which the Developer can perform
construction and what, if any, outages may be required during these periods; (3) a description of
the project, including type, size, and geographic and electrical location, as well as planning and
engineering specifications as appropriate; (4) evidence of a commercially viable technology; (5)
a major milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining such control; (8)
status of any contracts (other than an interconnection agreement) that are under negotiation or in
place, including any contracts with third-party contractors; (9) status of ISO interconnection
studies and interconnection agreement; (10) status of equipment availability and procurement;
(11) evidence of financing or ability to finance the project; (12) detailed capital cost estimates for
each segment of the project; (13) a description of permitting or other risks facing the project at
the stage of project development, including evidence of the reasonableness of project cost
estimates, all based on the information available at the time of the submission; and (14) any other
information requested by the ISO.
A Developer shall submit the following information to indicate the status of any
contracts: (i) copies of all final contracts the ISO determines are relevant to its consideration, or
(ii) where one or more contracts are pending, a timeline on the status of discussions and
negotiations with the relevant documents and when the negotiations are expected to be
completed. The final contracts shall be submitted to the ISO when available. The ISO shall treat
on a confidential basis in accordance with the requirements of its Code of Conduct in
Attachment F of the ISO OATT any contract that is submitted to the ISO and is designated by
the Developer as “Confidential Information.”
A Developer shall submit the following information to indicate the status of any required
permits: (i) copies of all final permits received that the ISO determines are relevant to its
consideration, or (ii) where one or more permits are pending, the completed permit application(s)
with information on what additional actions must be taken to meet the permit requirements and a
timeline providing the expected timing for finalization and receipt of the final permit(s). The
final permits shall be submitted to the ISO when available.
A Developer shall submit the following information, as appropriate, to indicate evidence
of financing by it or any Affiliate upon which it is relying for financing: (i) evidence of self-
financing or project financing through approved rates or the ability to do so, (ii) copies of all loan
commitment letter(s) and signed financing contract(s), or (iii) where such financing is pending,
the status of the application for any relevant financing, including a timeline providing the status
of discussions and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts or approved rates shall be submitted to the ISO when
available.
Upon the completion of any interconnection study or transmission expansion study of a
proposed regulated economic transmission project that is performed under Sections 3.7 or 4.5 of
the ISO OATT or Attachments P or X of the ISO OATT, the Developer of the proposed project
shall notify the ISO that the study has been completed and, at the ISO’s request, shall submit to
the ISO any study report and related materials prepared in connection with the study.
Failure to provide any data requested by the ISO within the timeframe provided in
Section 31.3.2.4.1.3 of this Attachment Y will result in the rejection of the proposed solution
from further consideration during that planning cycle.
31.3.2.5 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers who have undertaken a
commitment to build a project that has been approved by project beneficiaries, in accordance
with Section 31.5.4.6 of this Attachment Y.
31.4
Public Policy Transmission Planning Process
31.4.1
General
The Public Policy Transmission Planning Process shall consist of three steps: (1)
identification of Public Policy Transmission Needs; (2) requests for proposed Public Policy
Transmission Projects and Other Public Policy Projects to address those Public Policy
Transmission Needs and the evaluation of those projects; and (3) selection of the more efficient
or cost-effective Public Policy Transmission Project, if any, to satisfy each Public Policy
Transmission Need to be eligible for cost allocation under the ISO OATT. Sections 31.4.2.1
through 31.4.2.3 provide for the identification of transmission needs driven by Public Policy
Requirements and warranting evaluation by the ISO. The ISO shall request and evaluate
proposed Public Policy Transmission Projects and Other Public Policy Projects to address such
needs. The ISO shall select the more efficient or cost-effective Public Policy Transmission
Project, if any, to satisfy each need. The Public Policy Transmission Planning Process will be
conducted on a two-year cycle, unless requested by the NYPSC to be conducted out of that
cycle. If the Public Policy Transmission Planning Process cannot be completed in the two-year
cycle, the ISO will notify stakeholders and provide an estimated completion date and an
explanation of the reasons the additional time is required. The NYPSC’s issuance of a written
statement pursuant to Section 31.4.2.1 below will occur after the draft RNA study results are
posted.
31.4.2
Identification and Posting of Proposed Transmission Needs Driven by
Public Policy Requirements
At the start of each cycle for the Public Policy Transmission Planning Process, the ISO
will provide a 60-day period, which time period may be extended by the ISO pursuant to Section
31.1.8.7, to allow any stakeholders or interested parties to submit to the ISO, or for the ISO on its
own initiative to identify, any proposed transmission need(s) that it believes are being driven by
Public Policy Requirement(s) and for which transmission solutions should be requested and
evaluated. Each submittal will identify the Public Policy Requirement(s) that the party believes
is driving the need for transmission, propose criteria for the evaluation of transmission solutions
to that need, and describe how the construction of transmission will fulfill the Public Policy
Requirement(s).
For submittals to identify transmission needs pursuant to Section 31.4.2.1, the ISO will
post all submittals on its website after the end of the needs solicitation period, and will submit to
the NYPSC all submittals proposed by stakeholders, other interested parties, and any additional
transmission needs and criteria identified by the ISO. For submittals to identify transmission
needs that require a physical modification to transmission facilities in the Long Island
Transmission District pursuant to Section 31.4.2.3, the ISO will post all submittals on its website
after the end of the needs solicitation period, and will provide to the NYPSC and the Long Island
Power Authority all submittals proposed by stakeholders, other interested parties, and any
additional transmission needs and criteria identified by the ISO.
31.4.2.1 Identification and Determination of Transmission Needs Driven by
Public Policy Requirements
The NYPSC will review all proposed transmission need(s) and, with input from the ISO
and interested parties, identify the transmission needs, if any, for which specific transmission
solutions should be requested and evaluated. The NYPSC will maintain procedures to govern
the process by which it will review proposed transmission need(s), which procedures shall:
ensure that such process is open and transparent, provide the ISO and interested parties a
meaningful opportunity to participate in such process, provide input regarding the NYPSC’s
considerations, and result in the development of a written determination as required by law,
inclusive of the input provided by the ISO and interested parties. In addition, the NYPSC may,
on its own, identify a transmission need driven by a Public Policy Requirement. Any such
transmission need identified by the NYPSC on its own shall be described by the NYPSC in
accordance with the requirements for stakeholder submittals set forth in Section 31.4.2, and shall
be identified and posted to the ISO’s website prior to NYPSC’s issuance of the required written
statement discussed below in this Section 31.4.2.1 so as to provide the ISO and interested parties
an opportunity to provide input to the NYPSC relating thereto.
The ISO shall assist the NYPSC in its analyses as requested. The NYPSC may also
request that the ISO, pursuant to Section 3.8.1 of the ISO OATT, conduct an evaluation of
alternative options to address the transmission needs.
The NYPSC shall issue a written statement that identifies the relevant Public Policy
Requirements driving transmission needs and explains why it has identified the Public Policy
Transmission Needs for which transmission solutions will be requested by the ISO. The
statement shall also explain why transmission solutions to other suggested transmission needs
should not be requested. The NYPSC’s statement may also provide: (i) additional criteria for the
evaluation of transmission solutions and non-transmission projects, (ii) the required timeframe, if
any, for completion of the proposed solution, and (iii) the type of analyses that it will request
from the ISO.
If the NYPSC does not identify any transmission needs driven by Public Policy
Requirements, it will provide confirmation of that conclusion to the ISO, and the ISO shall not
request solutions. The ISO shall post the NYPSC’s statement on the ISO’s website.
31.4.2.2 Disputes of NYPSC Determinations
In the event that a dispute is raised solely within the NYPSC’s jurisdiction relating to any
NYPSC decision to either accept or deny a proposed transmission need as one for which
transmission solutions should be requested, the dispute shall be addressed through judicial
review in the courts of the State of New York pursuant to Article 78 of the New York Civil
Practice Law and Rules.
31.4.2.3 Identification and Determination of Transmission Needs Within the Long
Island Transmission District Driven by Public Policy Requirements
The Long Island Power Authority, pursuant to its jurisdiction under Title 1-A of Article 5
(§1020 et seq.) of the Public Authorities Law of the State of New York, shall identify and
determine whether a Public Policy Requirement drives the need for a physical modification to
transmission facilities in the Long Island Transmission District. The identification and
determination of such transmission needs shall be consistent with Section 31.4.2.1, as further
supplemented by this Section 31.4.2.3. The Long Island Power Authority shall have no authority
to identify a transmission need outside of the Long Island Transmission District.
Based on the information provided by the ISO pursuant to Section 31.4.2, the Long
Island Power Authority shall review whether a proposed Public Policy Requirement drives the
need for a physical modification to transmission facilities in the Long Island Transmission
District. In addition, the following requirements shall apply to the Long Island Power Authority:
(i)
The Long Island Power Authority shall consult with the NYDPS on the
identification of transmission needs driven by a Public Policy Requirement solely
within the Long Island Transmission District;
(ii)
Upon completion of its review, the Long Island Power Authority shall issue a
written statement explaining whether a Public Policy Requirement does or does
not drive the need for a physical modification to transmission facilities solely
within the Long Island Transmission District, and describing the consultation
undertaken with the NYDPS;
(iii)
In conjunction with the issuance of its written statement, the Long Island Power
Authority shall transmit to the NYPSC and request that it review and determine
whether a transmission need solely within the Long Island Transmission District
identified by the Long Island Power Authority as being driven by a Public Policy
Requirement should be considered a Public Policy Transmission Need for
purposes of the evaluation of solutions by the ISO and the potential eligibility of
transmission solutions for selection and regional cost allocation under the ISO
OATT. Any transmission need within the Long Island Transmission District that
has been identified by the Long Island Power Authority, but which the NYPSC
has not determined to be a Public Policy Transmission Need that would be
evaluated by the ISO, shall be addressed under the Long Island Power Authority’s
Local Transmission Plan.
(iv)
The determination of whether there is a transmission need solely within the Long
Island Transmission District is the sole responsibility of the Long Island Power
Authority;
(v)
The NYDPS and Long Island Power Authority shall consult and coordinate on
procedures to be adopted by the NYPSC and Long Island Power Authority to
ensure that their respective determinations under this Section 31.4.2.3, including
any NYPSC determination that there is a Public Policy Transmission Need within
the Long Island Transmission District for which solutions should be evaluated by
the ISO, are completed, publicly posted and transmitted to the ISO at the same
time as the NYPSC makes its final determinations pursuant to Section 31.4.2.1;
and
(vi)
In the event that a dispute is raised solely within the Long Island Power
Authority’s jurisdiction relating to a decision by the Long Island Power Authority
to either accept or deny a proposed transmission need solely within the Long
Island Transmission District, the dispute shall be addressed through judicial
review in the courts of the State of New York pursuant to Article 78 of the New
York Civil Practice Law and Rules.
31.4.3
Request for Proposed Solutions
The ISO will request proposed Public Policy Transmission Projects, including
Interregional Transmission Projects, to satisfy each Public Policy Transmission Need identified
pursuant to Sections 31.4.2.1 through 31.4.2.3. An Interregional Transmission Project shall be:
(i) evaluated in accordance with the applicable requirements of the Public Policy Transmission
Planning Process of this Attachment Y, and (ii) jointly evaluated by the ISO and the relevant
adjacent transmission planning region(s) in accordance with Section 7.3 of the Interregional
Planning Protocol. The ISO shall also accept specific proposed Other Public Policy Projects to
satisfy a Public Policy Transmission Need identified pursuant to Sections 31.4.2.1 through
31.4.2.3.
31.4.3.1 Timing of ISO Request for Proposed Solutions
Following posting of a determination pursuant to Sections 31.4.2.1 through 31.4.2.3, the
ISO will provide a 60-day period, which time period may be extended by the ISO pursuant to
Section 31.1.8.7, for Developers to propose specific solutions, whether Public Policy
Transmission Project(s) or Other Public Policy Project(s), to satisfy each identified Public Policy
Transmission Need in accordance with the requirements set forth in Section 31.4.4.3. Any
proposed transmission needs that are under appeal pursuant to Section 31.4.2.2 or Section
31.4.2.3(vi) may be addressed with proposed solutions, if required, except where the NYPSC
order has been stayed pending the resolution of that appeal.
31.4.3.2 NYPSC and LIPA Requests for Solutions
To ensure that there will be a response to a Public Policy Transmission Need, the NYPSC
may request the appropriate Transmission Owner(s) or Other Developer, as identified by the
NYPSC, to propose a Public Policy Transmission Project. With respect to a transmission need
identified by the Long Island Power Authority and determined to be a Public Policy
Transmission Need by the NYPSC pursuant to Section 31.4.2.3, the Long Island Power
Authority’s Board of Trustees may request that an appropriate Transmission Owner(s) or Other
Developer propose a Public Policy Transmission Project or Other Public Policy Project. A
request for the provision of a Public Policy Transmission Project or Other Public Policy Project
by either the NYPSC or the Long Island Power Authority’s Board of Trustees, pursuant to this
section, is supplementary to, and not to the exclusion of, the submission of proposed projects
pursuant to Section 31.4.3.1. Costs incurred by a Transmission Owner or Other Developer in
preparing a proposed transmission solution in response to a request under this Section 31.4.3.2
will be recoverable under Section 31.5.6 and Rate Schedule 10 of the ISO OATT. The ISO shall
allocate these costs among Load Serving Entities in accordance with Section 31.5.5.4.3, except
as otherwise determined by the Commission.
31.4.4
Eligibility and Qualification Criteria for Developers and Projects
For purposes of fulfilling the requirements of the Developer qualification criteria in this
Section 31.4.4 and its subsections, the term “Developer” includes Affiliates, as that term is
defined in Section 2 of the ISO Services Tariff and Section 1 of the ISO OATT. To the extent
that a Developer relies on Affiliate(s) to satisfy any or all of the qualification criteria set forth in
Section 31.4.4.1.1, the Affiliate(s) shall provide to the ISO: (i) the information required in
Section 31.4.4.1.1 to demonstrate its capability to satisfy the applicable qualification criteria and
(ii) a notarized officer’s certificate, signed by an authorized officer of the Affiliate with signatory
authority, in a form acceptable to the ISO, certifying that the Affiliate will participate in the
Developer’s project in the manner described by the Developer and will abide by the requirements
set forth in this Attachment Y, the ISO Tariffs, and ISO Procedures, related and applicable to the
Affiliate’s participation.
31.4.4.1 Developer Qualification and Timing
The ISO shall provide each Developer with an opportunity to demonstrate that it has or
can draw upon the financial resources, technical expertise, and experience needed to finance,
develop, construct, operate, and maintain a Public Policy Transmission Project. The ISO shall
consider the qualification of each Developer in an evenhanded and non-discriminatory manner,
treating Transmission Owners and Other Developers alike.
31.4.4.1.1 Developer Qualification Criteria
The ISO shall make a determination on the qualification of a Developer to propose to
develop a Public Policy Transmission Project based on the following criteria:
31.4.4.1.1.1 The technical and engineering qualifications and experience of the
Developer relevant to the development, construction, operation and maintenance
of a transmission facility, including evidence of the Developer’s demonstrated
capability to adhere to standardized construction, maintenance, and operating
practices and to contract with third parties to develop, construct, maintain, and/or
operate transmission facilities;
31.4.4.1.1.2 The current and expected capabilities of the Developer to develop and
construct a transmission facility and to operate and maintain it for the life of the
facility. If the Developer has previously developed, constructed, maintained or
operated transmission facilities, the Developer shall provide the ISO a description
of the transmission facilities (not to exceed ten) that the Developer has previously
developed, constructed, maintained or operated and the status of those facilities,
including whether the construction was completed, whether the facility entered
into commercial operations, whether the facility has been suspended or terminated
for any reason, and evidence demonstrating the ability of the Developer to address
and timely remedy any operational failure of the facilities; and
31.4.4.1.1.3 The Developer’s current and expected capability to finance, or its
experience in arranging financing for, transmission facilities. For purposes of the
ISO’s determination, the Developer shall provide the ISO:
(1)
evidence of its demonstrated experience financing or arranging financing for
transmission facilities, if any, including a description of such projects (not to
exceed ten) over the previous ten years, the capital costs and financial structure of
such projects, a description of any financing obtained for these projects through
rates approved by the Commission or a state regulatory agency, the financing
closing date of such projects, and whether any of the projects are in default;
(2)
its audited annual financial statements from the most recent three years and its
most recent quarterly financial statement or equivalent information, if available;
(3)
its credit rating from Moody’s Investor Services, Standard & Poor’s, or Fitch or
equivalent information, if available;
(4)
a description of any prior bankruptcy declarations, material defaults, dissolution,
merger or acquisition by the Developer or its predecessors or subsidiaries
occurring within the previous five years; and
(5)
such other evidence that demonstrates its current and expected capability to
finance a project to solve a Public Policy Transmission Need.
31.4.4.1.1.4 A detailed plan describing how the Developer - in the absence of previous
experience financing, developing, constructing, operating, or maintaining
transmission facilities - will finance, develop, construct, operate, and maintain a
transmission facility, including the financial, technical, and engineering
qualifications and experience and capabilities of any third parties with which it
will contract for these purposes.
31.4.4.1.2 Developer Qualification Determination
Any Developer seeking to be qualified may submit the required information, or update
any previously submitted information, at any time. The ISO shall treat on a confidential basis in
accordance with the requirements of its Code of Conduct in Attachment F of the ISO OATT any
non-public financial qualification information that is submitted to the ISO by the Developer
under Section 31.4.4.1.1.3 and is designated by the Developer as “Confidential Information.”
The ISO shall within 15 days of a Developer’s submittal, notify the Developer if the information
is incomplete. If the submittal is deemed incomplete, the Developer shall submit the additional
information within 30 days of the ISO’s request. The ISO shall notify the Developer of its
qualification status within 30 days of receiving all necessary information. A Developer shall
retain its qualification status for a three-year period following the notification date; provided,
however, that the ISO may revoke this status if it determines that there has been a material
change in the Developer’s qualifications and the Developer no longer meets the qualification
requirements. A Developer that has been qualified shall inform the ISO within thirty days of any
material change to the information it provided regarding its qualifications and shall submit to the
ISO each year its most recent audited annual financial statement when available. At the
conclusion of the three-year period or following the ISO’s revocation of a Developer’s
qualification status, the Developer may re-apply for a qualification status under this section.
Any Developer determined by the ISO to be qualified under this section shall be eligible
to propose a regulated Public Policy Transmission Project and shall be eligible to use the cost
allocation and cost recovery mechanism for regulated Public Policy Transmission Projects set
forth in Section 31.5 of this Attachment Y and the appropriate rRate sSchedule 10 of the ISO
OATT for any approved project.
31.4.4.3 Timing for Submittal of Project Information and Developer Qualification
Information and Opportunity to Provide Additional Information
31.4.4.3.1
All Developers of Public Policy Transmission Projects or Other Public
Policy Projects proposed to satisfy a Public Policy Transmission Need shall
submit to the ISO within 60 days of the ISO’s request for solutions to a Public
Policy Transmission Need, which time period may be extended by the ISO
pursuant to Section 31.1.8.7, the project information required under Section
31.4.5. In response to a solicitation for a solution to a Public Policy Transmission
Need identified after the 2014-2015 planning cycle, the Developer of a Public
Policy Transmission Project must also demonstrate to the ISO, simultaneous with
its submission of project information, that it has submitted a valid Transmission
Interconnection Application or Interconnection Request as applicable. If: (i) the
ISO determines that a Developer’s submission of its project information is
incomplete, or (ii) the ISO determines at any time in the planning process that
additional project information is required, the ISO shall request that the Developer
provide additional project information within the timeframe set forth in Section
31.4.4.3.4. A Developer’s failure to provide the data requested by the ISO within
the timeframes provided in Sections 31.4.4.3.1 and 31.4.4.3.4 of this Attachment
Y will result in the rejection of the Developer’s proposed Public Policy
Transmission Project or Other Public Policy Project from further consideration
during that planning cycle.
31.4.4.3.2
Any Developer that the ISO has determined under Section 31.4.4.1.2 of
this Attachment Y to be qualified to propose to develop a transmission project as
a transmission solution to a Public Policy Transmission Need may submit the
required project information for its proposed Public Policy Transmission Project;
provided, however, that based on the actual identified need that requires
resolution, the ISO may request that the qualified Developer provide additional
Developer qualification information within the timeframe set forth in Section
31.4.4.3.4.
31.4.4.3.3
Any Developer that has not been determined by the ISO to be qualified,
but that wants to propose to develop a Public Policy Transmission Project, must
submit to the ISO the information required for Developer qualification under
Section 31.4.4.1 within 30 days after a request for solutions is made by the ISO.
The ISO shall within 30 days of a Developer’s submittal of its Developer
qualification information, notify the Developer if this information is incomplete
and request that the Developer provide additional Developer qualification
information within the timeframe set forth in Section 31.4.4.3.4. The ISO shall
notify a Developer that has submitted the requested Developer qualification
information whether it is qualified to propose to develop a Public Policy
Transmission Project to be considered in that planning cycle.
31.4.4.3.4
The Developer shall submit additional Developer qualification
information or project information required by the ISO within 15 days of the
ISO’s request.
31.4.4.3.5
If a Developer fails to timely submit the additional Developer qualification
information requested by the ISO, the Developer will not be eligible for its
proposed Public Policy Transmission Project to be considered in that planning
cycle.
31.4.4.4. Application Fee and Study Deposit for Proposed Regulated Public Policy
Transmission Project
Within sixty (60) days of the ISO’s request for solutions to a Public Policy Transmission
Need, which time period may be extended by the ISO pursuant to Section 31.1.8.7, all
Developers that propose Public Policy Transmission Projects shall, at the same time that they
provide project information pursuant to Section 31.4.4.3.1, (i) execute a study agreement with
the ISO in the form set forth in Section 31.12 (Appendix I) of this Attachment Y for purposes of
the ISO’s evaluation of the proposed Public Policy Transmission Project under Sections 31.4.7,
31.4.8, 31.4.9, and 31.4.10, and (ii) submit to the ISO: (A) a non-refundable application fee of
$10,000, and (B) a study deposit of $100,000, which shall be applied to study costs and subject
to refund as described in this Section 31.4.4.4.
The ISO shall charge, and a Developer proposing a regulated Public Policy Transmission
Project shall pay, the actual costs of the ISO’s evaluation of the Developer’s proposed Public
Policy Transmission Project for purposes of the ISO’s selection of the more efficient or cost
effective Public Policy Transmission Project to satisfy a Public Policy Transmission Need for
cost allocation purposes, including costs associated with the ISO’s use of subcontractors. The
ISO will track its staff and administrative costs, including any costs associated with using
subcontractors, that it incurs in performing the evaluation of a Developer’s proposed Public
Policy Transmission Project under Sections 31.4.7, 31.4.8, 31.4.9, and 31.4.10 and any
supplemental evaluation or re-evaluation of the proposed Public Policy Transmission Project. If
the ISO or its subcontractors perform study work for multiple proposed Public Policy
Transmission Projects on a combined basis, the ISO will allocate the costs of the combined study
work equally among the applicable Developers.
The ISO shall invoice the Developer monthly for study costs incurred by the ISO in
evaluating the Developer’s proposed Public Policy Transmission Projects as described above.
Such invoice shall include a description and an accounting of the study costs incurred by the ISO
and estimated subcontractor costs. The Developer shall pay the invoiced amount within thirty
(30) calendar days of the ISO’s issuance of the monthly invoice. The ISO shall continue to hold
the full amount of the study deposit until settlement of the final monthly invoice; provided,
however, if a Developer: (i) does not pay its monthly invoice within the timeframe described
above, or (ii) does not pay a disputed amount into an independent escrow account as described
below, the ISO may draw upon the study deposit to recover the owed amount. If the ISO must
draw on the study deposit, the ISO shall provide notice to the Developer, and the Developer shall
within thirty (30) calendar days of such notice make payments to the ISO to restore the full study
deposit amount. If the Developer fails to make such payments, the ISO may halt its evaluation
of the Developer’s proposed Public Policy Transmission Project and may disqualify the
Developer’s proposed Public Policy Transmission Project from further consideration. After the
conclusion of the ISO’s evaluation of the Developer’s proposed Public Policy Transmission
Project or if the Developer: (i) withdraws its proposed Public Policy Transmission Project or (ii)
fails to pay an invoiced amount and the ISO halts its evaluation of the proposed Public Policy
Transmission Project, the ISO shall issue a final invoice and refund to the Developer any portion
of the Developer’s study deposit submitted to the ISO under this Section 31.4.4.4 that exceeds
outstanding amounts that the ISO has incurred in evaluating that Developer’s proposed Public
Policy Transmission Project, including interest on the refunded amount calculated in accordance
with Section 35.19a(a)(2) of FERC’s regulations. The ISO shall refund the remaining portion
within sixty (60) days of the ISO’s receipt of all final invoices from its subcontractors and
involved Transmission Owners.
In the event of a Developer’s dispute over invoiced amounts, the Developer shall: (i)
timely pay any undisputed amounts to the ISO, and (ii) pay into an independent escrow account
the portion of the invoice in dispute, pending resolution of such dispute. If the Developer fails to
meet these two requirements, then the ISO shall not be obligated to perform or continue to
perform its evaluation of the Developer’s proposed Public Policy Transmission Project.
Disputes arising under this section shall be addressed through the Dispute Resolution Procedures
set forth in Section 2.16 of the ISO OATT and Section 11 of the ISO Services Tariff. Within
thirty (30) Calendar Days after resolution of the dispute, the Developer will pay the ISO any
amounts due with interest calculated in accordance with Section 35.19a(a)(2) of FERC’s
regulations.
31.4.5
Project Information Requirements
31.4.5.1 Requirements for Public Policy Transmission Projects
31.4.5.1.1
A Developer proposing a Public Policy Transmission Project to satisfy a
Public Policy Transmission Need must provide, at a minimum, the following
details:
(1) contact information; (2) the lead time necessary to complete the
project, including, if available, the construction windows in which the Developer
can perform construction and what, if any, outages may be required during these
periods; (3) a description of the project, including type, size, and geographic and
electrical location, as well as planning and engineering specifications as
appropriate; (4) evidence of a commercially viable technology; (5) a major
milestone schedule; (6) a schedule for obtaining any required permits and other
certifications; (7) a demonstration of Site Control or a schedule for obtaining such
control; (8) status of any contracts (other than an interconnection agreement) that
are under negotiations or in place, including any contracts with third-party
contractors; (9) status of ISO interconnection studies and interconnection
agreement; (10) status of equipment availability and procurement; (11) evidence
of financing or ability to finance the project; (12) capital cost estimates for the
project; (13) a description of permitting or other risks facing the project at the
stage of project development, including evidence of the reasonableness of project
cost estimates all based on the information available at the time of the submission;
and (14) any other information requested by the ISO.
31.4.5.1.2
A Developer shall submit the following information to indicate the status
of any contracts: (i) copies of all final contracts the ISO determines are relevant to
its consideration, or (ii) where one or more contracts are pending, a timeline on
the status of discussions and negotiations with the relevant documents and when
the negotiations are expected to be completed. The final contracts shall be
submitted to the ISO when available. The ISO shall treat on a confidential basis
in accordance with the requirements of its Code of Conduct in Attachment F of
the ISO OATT any contract that is submitted to the ISO and is designated by the
Developer as “Confidential Information.”
31.4.5.1.3
A Developer shall submit the following information to indicate the status
of any required permits: (i) copies of all final permits received that the ISO
determines are relevant to its consideration, or (ii) where one or more permits are
pending, the completed permit application(s) with information on what additional
actions must be taken to meet the permit requirements and a timeline providing
the expected timing for finalization and receipt of the final permit(s). The final
permits shall be submitted to the ISO when available.
31.4.5.1.4
A Developer shall submit the following information, as appropriate, to
indicate evidence of financing by it or any Affiliate upon which it is relying for
financing: (i) evidence of self-financing or project financing through approved
rates or the ability to do so, (ii) copies of all loan commitment letter(s) and signed
financing contract(s), or (iii) where such financing is pending, the status of the
application for any relevant financing, including a timeline providing the status of
discussions and negotiations of relevant documents and when the negotiations are
expected to be completed. The final contracts or approved rates shall be
submitted to the ISO when available.
31.4.5.1.5
Upon the completion of any interconnection study or transmission
expansion study of a proposed Public Policy Transmission Project that is
performed under Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of
the ISO OATT, the Developer of the proposed project shall notify the ISO that the
study has been completed and, at the ISO’s request, shall submit to the ISO any
study report and related materials prepared in connection with the study.
31.4.5.2 Requirements for Other Public Policy Projects
31.4.5.2.1
A Developer proposing an Other Public Policy Project to satisfy a Public
Policy Transmission Need must provide, at a minimum: (1) contact information;
(2) the lead time necessary to complete the project, including, if available, the
construction windows in which the Developer can perform construction and what,
if any, outages may be required during these periods; (3) a description of the
project, including type, size, and geographic and electrical location, as well as
planning and engineering specifications and drawings as appropriate; (4) evidence
of a commercially viable technology; (5) a major milestone schedule; (6) a
schedule for obtaining any required permits and other certifications; (7) a
demonstration of Site Control or a schedule for obtaining Site Control, as
applicable; (8) the status of any contracts (other than an interconnection
agreement) that are under negotiation or in place; (9) the status of ISO
interconnection studies and interconnection agreement, as applicable; (10) the
status of equipment availability and procurement, as applicable; (11) evidence of
financing or ability to finance the project; and (12) any other information
requested by the ISO.
31.4.5.2.2
A Developer shall submit the following information to indicate the status
of any contracts: (i) copies of all final contracts the ISO determines are relevant
to its consideration, or (ii) where one or more contracts are pending, a timeline on
the status of discussions and negotiations with the relevant documents and when
the negotiations are expected to be completed. The final contracts shall be
submitted to the ISO when available. The ISO shall treat on a confidential basis
in accordance with the requirements of its Code of Conduct in Attachment F of
the ISO OATT any contract that is submitted to the ISO and is designated by the
Developer as “Confidential Information.”
31.4.5.2.3
A Developer shall submit the following information to indicate the status
of any required permits: (i) copies of all final permits received that the ISO
determines are relevant to its consideration, or (ii) where one or more permits are
pending, the completed permit application(s) with information on what additional
actions must be taken to meet the permit requirements and a timeline providing
the expected timing for finalization and receipt of the final permit(s). The final
permits shall be submitted to the ISO when available.
31.4.5.2.4
A Developer shall submit the following information, as appropriate, to
indicate evidence of financing by it or any Affiliate upon which it is relying for
financing: (i) copies of all loan commitment letter(s) and signed financing
contract(s), or (ii) where such financing is pending, the status of the application
for any relevant financing, including a timeline providing the status of discussions
and negotiations of relevant documents and when the negotiations are expected to
be completed. The final contracts shall be submitted to the ISO when available.
31.4.5.2.5
Upon the completion of any interconnection study or transmission
expansion study of a proposed Other Public Policy Project that is performed under
Sections 3.7 or 4.5 of the ISO OATT or Attachments P or X of the ISO OATT,
the Developer of the proposed project shall notify the ISO that the study has been
completed and, at the ISO’s request, shall submit to the ISO any study report and
related materials prepared in connection with the study.
31.4.6
ISO Evaluation of Proposed Solutions to Public Policy Transmission
Needs
31.4.6.1 Evaluation Time Period
The ISO will study proposed Public Policy Transmission Projects and Other Public
Policy Projects using: (i) the most recent base case from the reliability planning process, (ii)
updates in accordance with ISO Procedures, and (iii) compensatory MWs as needed to resolve
the Reliability Needs over the ten-year Study Period. The ISO will extend the most recent
reliability and economic planning models for modeling solutions for Public Policy Transmission
Needs by up to an additional twenty years following the Study Period, as appropriate based upon
the Public Policy Requirement and the identified Public Policy Transmission Need.
31.4.6.2 Comparable Evaluation of All Proposed Solutions
The ISO shall evaluate any proposed Public Policy Transmission Project or Other Public
Policy Project submitted by a Developer to a Public Policy Transmission Need. The ISO will
evaluate whether each proposed solution is viable pursuant to Section 31.4.6.3 below and is
sufficient to satisfy the Public Policy Transmission Need pursuant to Section 31.4.6.4. The
proposed solution may include multiple components and resource types. When evaluating
proposed solutions to a Public Policy Transmission Need from any Developer, the ISO shall
consider all resource types - including generation, transmission, demand response, or a
combination of these resource types - on a comparable basis as potential solutions. All solutions
will be evaluated in the same general time frame.
31.4.6.3 Evaluation of Viability of Proposed Solution
The ISO will determine the viability of a Public Policy Transmission Project or Other
Public Policy Project - whether transmission, generation, demand response, or a combination of
these resource types - proposed to satisfy a Public Policy Transmission Need. For purposes of
its analysis, the ISO will consider: (i) the Developer qualification data provided pursuant to
Section 31.4.4 and the project information data provided under Section 31.4.5; (ii) whether the
proposed solution is technically practicable; (iii) the Developer’s possession of, or approach for
acquiring, any necessary rights-of-way, property, and facilities that will make the proposal
reasonably feasible in the required timeframe; and (iv) whether the proposed solution can be
completed in the required timeframe, if any. If the ISO determines that the proposed solution is
not viable, the ISO shall reject the proposed solution from further consideration during that
planning cycle.
31.4.6.4 Evaluation of Sufficiency of Proposed Solution
The ISO will perform a comparable analysis of each proposed Public Policy
Transmission Project or Other Public Policy Project - whether transmission, generation, demand
response, or a combination of these resource types - to confirm that the proposed solution
satisfies the Public Policy Transmission Need. The ISO will evaluate each solution to measure
the degree to which the proposed solution independently satisfies the Public Policy Transmission
Need, including the evaluation criteria provided by the NYPSC. If the ISO determines that the
proposed solution is not sufficient, the ISO shall reject the proposed solution from further
consideration during that planning cycle.
31.4.6.5 Viability and Sufficiency Assessment
The ISO will present its Viability and Sufficiency Assessment to stakeholders, interested
parties, and the NYPSC for comment. The ISO shall report in the Public Policy Transmission
Planning Report the results of its evaluation under this Section 31.4.6 of whether each proposed
Public Policy Transmission Project or Other Public Policy Project is viable and is sufficient to
satisfy the identified Public Policy Transmission Need.
31.4.6.6 Developer’s Determination to Proceed
Within 15 Calendar Days following the NYPSC’s issuance of an order in accordance
with Section 31.4.6.7 indicating that the ISO should proceed with its evaluation of transmission
solutions to a Public Policy Transmission Need, which time period may be extended by the ISO
pursuant to Section 31.1.8.7, all Developers of proposed Public Policy Transmission Projects that
the ISO has determined satisfy the viability and sufficiency requirements in this Section 31.4.6
shall notify the ISO whether they intend for their projects to proceed to be evaluated by the ISO
for purposes of the ISO’s selection of the more efficient or cost effective Public Policy
Transmission Project to satisfy an identified Public Policy Transmission Need. To proceed, a
Developer must include with its notification to the ISO under this Section 31.4.6.6: (i) its consent
to the ISO’s disclosure of the details of its proposed Public Policy Transmission Project in the
Public Policy Transmission Planning Report, except for the information that shall remain
confidential in accordance with Section 31.4.15, and (ii) a demonstration that it has an executed
System Impact Study Agreement or System Reliability Impact Study Agreement, as applicable.
If a Developer: (i) notifies the ISO that it does not intend for its proposed Public Policy
Transmission Project to proceed to be evaluated for purposes of the ISO’s selection, or (ii) does
not provide the required notification to the ISO under this Section 31.4.6.6, the ISO will remove
the project from further consideration during that planning cycle.
31.4.6.7 NYPSC Determination on Whether to Proceed with Evaluation of
Transmission Solutions to a Public Policy Transmission Need
31.4.6.7.1
Following the ISO’s presentation of the Viability and Sufficiency
Assessment, the NYPSC will review the Viability and Sufficiency Assessment and will issue an
order, subject to and in accordance with the State Administrative Procedure Act, explaining
whether the ISO should continue to evaluate transmission solutions to a Public Policy
Transmission Need or whether non-transmission solutions should be pursued. If the NYPSC
concludes that non-transmission solutions should be pursued outside of the Public Policy
Transmission Planning Process, the NYPSC will indicate in its order that either: (i) there is no
longer a transmission need driven by a Public Policy Requirement that requires the ISO’s
evaluation of potential transmission solutions, or (ii) the transmission need should be modified.
31.4.6.7.2
If the NYPSC concludes that there is no longer a transmission need driven
by a Public Policy Requirement in its order as set forth in Section 31.4.6.7.1, the ISO will not
perform an evaluation, or make a selection of, a more efficient or cost-effective transmission
solution under Sections 31.4.7 through 31.4.11 for the Public Policy Transmission Need initially
identified by the NYPSC for that planning cycle pursuant to Section 31.4.2.1.
31.4.6.7.3
If the NYPSC modifies the transmission need driven by a Public Policy
Requirement in its order as set forth in Section 31.4.6.7.1, the ISO will re-start its Public Policy
Transmission Planning Process as an out-of-cycle process to evaluate Public Policy
Transmission Projects to address the modified Public Policy Transmission Need. This out-of-
cycle process will begin with the ISO’s solicitation for Public Policy Transmission Projects to
address the modified Public Policy Transmission Need in accordance with Sections 31.4.3 and
31.4.4.3. The ISO shall evaluate the viability and sufficiency of the proposed Public Policy
Transmission Projects in accordance with Sections 31.4.6.3 and 31.4.6.4. Within 30 Calendar
Days following the ISO’s presentation of the Viability and Sufficiency Assessment for the out-
of-cycle process, which time period may be extended by the ISO pursuant to Section 31.1.8.7, all
Developers of proposed Public Policy Transmission Projects that the ISO has determined satisfy
the viability and sufficiency requirements in this Section 31.4.6 shall notify the ISO whether they
intend for their projects to proceed to be evaluated for purposes of selection in accordance with
the requirements in Section 31.4.6.6. The ISO will then proceed to evaluate the viable and
sufficient Public Policy Transmission Projects that have elected to proceed in accordance with
Sections 31.4.7 through 31.4.11 for purposes of selecting the more efficient or cost-effective
transmission solution to the modified Public Policy Transmission Need. The requirements in
Section 31.4.6.7.1 that the NYPSC review the Viability and Sufficiency Assessment and issue an
order concerning the Public Policy Transmission Need do not apply in this out-of-cycle process.
31.4.7
Evaluation of Regional Public Policy Transmission Projects to Address
Local and Regional Needs Driven by Public Policy Requirements More
Efficiently or More Cost Effectively Than Local Transmission Solutions
The ISO will review the LTPs as they relate to the BPTFs. The ISO will include the
results of its analysis in its Public Policy Transmission Planning Report, as approved by the ISO
Board.
31.4.7.1 Evaluation of Regional Public Policy Transmission Projects to Address
Local Needs Driven By Public Policy Requirements Identified in Local
Transmission Plans More Efficiently or More Cost Effectively than Local
Transmission Solutions
The ISO, using engineering judgment, will determine whether any proposed regional
Public Policy Transmission Project on the BPTFs more efficiently or cost-effectively satisfies
any needs driven by a Public Policy Requirement identified in the LTPs. If the ISO identifies
that a regional Public Policy Transmission Project has the potential to more efficiently or cost
effectively satisfy the needs driven by a Public Policy Requirement identified in the LTPs, it will
perform a sensitivity analysis to determine whether the proposed regional Public Policy
Transmission Project on the BPTFs would satisfy the needs driven by a Public Policy
Requirement identified in the LTPs. If the ISO determines that the proposed regional Public
Policy Transmission Project would satisfy the need, the ISO will evaluate the proposed regional
Public Policy Transmission Project using the metrics set forth in Section 31.4.8.1 below to
determine whether it may be a more efficient or cost effective solution on the BPTFs to the needs
driven by a Public Policy Requirement identified in the LTPs than the local solutions proposed in
the LTPs.
31.4.7.2 Evaluation of Regional Public Policy Transmission Project to Address
Regional Pubic Policy Transmission Needs More Efficiently or More Cost
Effectively than Local Transmission Solutions
As referenced in Section 31.2.1.3, the ISO, using engineering judgment, will determine
whether a regional Public Policy Transmission Project might more efficiently or more cost
effectively satisfy an identified regional Public Policy Transmission Need on the BPTFs that
impacts more than one Transmission District than any local transmission solutions identified by
the Transmission Owners in their LTPs in the event the LTPs specify that such transmission
solutions are included to address local transmission needs driven by Public Policy Requirements.
31.4.8
ISO Selection of More Efficient or Cost Effective Public Policy
Transmission Project to Satisfy a Public Policy Transmission Need
A proposed regulated Public Policy Transmission Project submitted by a Developer that
the ISO has determined has provided the required notification to proceed under Section 31.4.6.6
shall be eligible under this Section 31.4.8 for selection in the Public Policy Transmission
Planning Report for the purpose of cost allocation under the ISO Tariffs. The ISO shall evaluate
any proposed regulated Public Policy Transmission Projects that are eligible for selection in the
planning cycle of the Public Policy Transmission Planning Process using the metrics set forth in
Section 31.4.8.1 below. For purposes of this evaluation, the ISO will review the information
submitted by the Developer and determine whether it is reasonable and how such information
should be used for purposes of the ISO evaluating each metric. In its review, the ISO will give
due consideration to the status of, and any available results of, any applicable interconnection or
transmission expansion studies concerning the proposed Public Policy Transmission Project
performed in accordance with Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the
ISO OATT. The ISO may engage an independent consultant to review the reasonableness and
comprehensiveness of the information submitted by the Developer and may rely on the
independent consultant’s analysis in evaluating each metric. The ISO shall select in the Public
Policy Transmission Planning Report for cost allocation purposes the more efficient or cost
effective transmission solution to satisfy a Public Policy Transmission Need in the manner set
forth in Section 31.4.8.2 below.
31.4.8.1 Metrics for Evaluating More Efficient or Cost Effective Regulated Public
Policy Transmission Project to Satisfy Public Policy Transmission Need
In determining which of the eligible proposed regulated Public Policy Transmission
Projects is the more efficient or cost effective solution to satisfy a Public Policy Transmission
Need, the ISO will consider, and will consult with the NYDPS regarding, the metrics set forth
below in this Section 31.4.8.1 and rank each proposed project based on the quality of its
satisfaction of these metrics:
31.4.8.1.1
The capital cost estimates for the proposed regulated Public Policy
Transmission Project, including the accuracy of the proposed estimates. For this
evaluation, the Developer shall provide the ISO with credible capital cost
estimates for its proposed project, with itemized supporting work sheets that
identify all material and labor cost assumptions, and related drawings to the extent
applicable and available. The work sheets should include an estimated
quantification of cost variance, providing an assumed plus/minus range around
the capital cost estimate.
The estimate shall include all components that are needed to meet the
Public Policy Transmission Need. To the extent information is available, the
Developer should itemize: material and labor cost by equipment, engineering and
design work, permitting, site acquisition, procurement and construction work, and
commissioning needed for the proposed project, all in accordance with Good
Utility Practice. For each of these cost categories, the Developer should specify
the nature and estimated cost of all major project components and estimate the
cost of the work to be done at each substation and/or on each feeder to physically
and electrically connect each facility to the existing system. The work sheets
should itemize to the extent applicable and available all equipment for: (i) the
proposed project, (ii) interconnection facilities (including Attachment Facilities
and Direct Assignment Facilities), and (iii) Network Upgrade Facilities, System
Upgrade Facilities, System Deliverability Upgrades, Network Upgrades, and
Distribution Upgrades.
31.4.8.1.2
The cost per MW ratio of the proposed regulated Public Policy
Transmission Project. For this evaluation, the ISO will first determine the present
worth, in dollars, of the total capital cost of the proposed project in current year
dollars. The ISO will then determine the cost per MW ratio by dividing the
capital cost by the MW value of increased transfer capability.
31.4.8.1.3
The expandability of the proposed regulated Public Policy Transmission
Project. The ISO will consider the impact of the proposed project on future
construction. The ISO will also consider the extent to which any subsequent
expansion will continue to use this proposed project within the context of system
expansion.
31.4.8.1.4
The operability of the proposed regulated Public Policy Transmission
Project. The ISO will consider how the proposed project may affect additional
flexibility in operating the system, such as dispatch of generation, access to
operating reserves, access to ancillary services, or ability to remove transmission
for maintenance. The ISO will also consider how the proposed project may affect
the cost of operating the system, such as how it may affect the need for operating
generation out of merit for reliability needs, reducing the need to cycle generation,
or providing more balance in the system to respond to system conditions that are
more severe than design conditions.
31.4.8.1.5
The performance of the proposed regulated Public Policy Transmission
Project. The ISO will consider how the proposed project may affect the
utilization of the system (e.g. interface flows, percent loading of facilities).
31.4.8.1.6
The extent to which the Developer of a proposed regulated Public Policy
Transmission Project has the property rights, or ability to obtain the property
rights, required to implement the project. The ISO will consider whether the
Developer: (i) already possesses the rights of way necessary to implement the
project; (ii) has completed a transmission routing study, which (a) identifies a
specific routing plan with alternatives, (b) includes a schedule indicating the
timing for obtaining siting and permitting, and (c) provides specific attention to
sensitive areas (e.g., wetlands, river crossings, protected areas, and schools); or
(iii) has specified a plan or approach for determining routing and acquiring
property rights.
31.4.8.1.7
The potential issues associated with delay in constructing the proposed
regulated Public Policy Transmission Project consistent with the major milestone
schedule and the schedule for obtaining any permits and other certifications as
required to timely meet the need.
31.4.8.1.8
The ISO shall apply any criteria specified by the Public Policy
Requirement or provided by the NYPSC and perform the analyses requested by
the NYPSC, to the extent compliance with such criteria and analyses are feasible.
31.4.8.1.9
The ISO, in consultation with stakeholders, shall, as appropriate, consider
other metrics in the context of the Public Policy Requirement, such as: change in
production costs; LBMP; losses; emissions; ICAP; TCC; congestion; impact on
transfer limits; and deliverability.
31.4.8.2 ISO Selection of More Efficient or Cost Effective Regulated Public Policy
Transmission Project to Satisfy a Public Policy Transmission Need
The ISO shall identify under this Section 31.4.8 the proposed regulated Public Policy
Transmission Project, if any, that is the more efficient or cost effective transmission solution
proposed in the planning cycle for the Public Policy Transmission Planning Process to satisfy a
Public Policy Transmission Need. The ISO shall include the more efficient or cost effective
transmission solution in the Public Policy Transmission Planning Report. The Developer of a
regulated Public Policy Transmission Project shall be eligible to recover costs for the project
only if the project is selected by the ISO, except as otherwise provided in Section 31.4.3.2 or as
otherwise determined by the Commission. Costs will be recovered when the project enters into
service, is halted,completed pursuant to a rate schedule filed with and accepted by the
Commission or as otherwise determined by the Commission in accordance with the cost
recovery requirements set forth in Section 31.5.6 of this Attachment Y and Rate Schedule 10 of
the ISO OATT.5, or as otherwise determined by the Commission. Actual project cost recovery,
including any issues related to cost recovery and project cost overruns, will be submitted to and
decided by the Commission.
Any selection of a Public Policy Transmission Project by the ISO under Section 31.4.8,
including but not limited to the selection of a project that involves the physical modification of
facilities within the Long Island Transmission District, shall not affect the obligation and
responsibility of the Developer to apply for, and receive, all necessary authorizations or permits
required by federal or state law for such project.
31.4.9
Consequences for Other Regions
The ISO will coordinate with the ISO/RTO Regions to identify the consequences of a
transmission solution driven by Public Policy Requirements on neighboring ISO/RTO Regions
using the respective planning criteria of such ISO/RTO Regions. The ISO shall report the results
in its Public Policy Transmission Planning Report. The ISO shall not bear the costs of required
upgrades in another region.
31.4.10 Evaluation of Impact of Proposed Public Policy Transmission Project on
ISO Wholesale Electricity Markets
The ISO shall evaluate using the metrics set forth in Section 31.4.8.1.9 the impacts on the
ISO-administered wholesale electricity markets of a proposed Public Policy Transmission
Project that the ISO has determined under Section 31.4.6 is viable and sufficient. The ISO shall
include the results of its analysis in the Public Policy Transmission Planning Report.
31.4.11 Public Policy Transmission Planning Report
Following the ISO’s evaluation of the proposed solutions to Public Policy Transmission
Need(s), the ISO will prepare a draft Public Policy Transmission Planning Report that sets forth
the ISO’s assumptions, inputs, methodologies and the results of its analyses. The draft Public
Policy Transmission Planning Report will reflect any input from the NYDPS.
Except as otherwise provided in the confidentiality requirements in Section 31.4.15, the
ISO will include in the draft Public Policy Transmission Planning Report: (i) the list of
Developers and their proposed Public Policy Transmission Projects and Other Public Policy
Projects that qualify pursuant to Sections 31.4.4 and 31.4.5; (ii) the proposed Public Policy
Transmission Projects and Other Public Policy Projects that the ISO has determined under
Section 31.4.6 are viable and sufficient to satisfy the identified Public Policy Transmission
Need(s); and (iii) the regulated Public Policy Transmission Project, if any, that the ISO staff
recommends for selection for cost allocation purposes pursuant to Section 31.4.8 as the more
efficient or cost effective transmission solution to satisfy each identified Public Policy
Transmission Need. The draft Public Policy Transmission Planning Report will also include the
results of the ISO’s analysis of the LTPs consistent with Section 31.4.7.
The draft Public Policy Transmission Planning Report shall also indicate the date by
which the Public Policy Transmission Project must be in-service to address the Public Policy
Transmission Need. The in-service date shall be: (i) the date prescribed by the NYPSC in its
order identifying the Public Policy Transmission Need as described in Section 31.4.2.1 or in a
subsequent order, or (ii) if the NYPSC has not prescribed a date, the date proposed by the
Developer and reviewed and accepted by the ISO, which date may be either: (A) the in-service
date included in the Developer’s project proposal, or (B) such other date accepted by the ISO as
reasonable in light of the Public Policy Transmission Need.
The draft Public Policy Transmission Planning Report shall include a comparison of a
proposed Public Policy Transmission Project to an Interregional Transmission Project proposed
in the Public Policy Transmission Planning Process, if any, identified and evaluated under the
“Analysis and Consideration of Interregional Transmission Projects” section of the Interregional
Planning Protocol. An Interregional Transmission Project proposed in the ISO’s Public Policy
Transmission Planning Process may be selected as a regulated Public Policy Transmission
Project under the provisions of this process.
31.4.11.1 Collaborative Governance Process
The draft Public Policy Transmission Planning Report shall be submitted to both TPAS
and the ESPWG for review and comment. Concurrently, the draft report will be provided to the
Market Monitoring Unit for its review and consideration. The Market Monitoring Unit’s
evaluation will be provided to the Management Committee prior to the Management
Committee’s advisory vote. The ISO shall make available to any interested party sufficient
information to replicate the results of the draft Public Policy Transmission Planning Report. The
information made available will be electronically masked and made available pursuant to a
process that the ISO reasonably determines is necessary to prevent the disclosure of any
Confidential Information or Critical Energy Infrastructure Information contained in the
information made available. Following completion of that review, the draft report reflecting the
revisions resulting from the TPAS and ESPWG review shall be forwarded to the Business Issues
Committee and the Management Committee for discussion and an advisory vote.
31.4.11.2 Board Review, Consideration, and Approval of Public Policy
Transmission Planning Report
Following the Management Committee vote, the draft Public Policy Transmission
Planning Report, with Business Issues Committee and Management Committee input, will be
forwarded to the ISO Board for review and action. Concurrently, the Market Monitoring Unit’s
evaluation will be provided to the Board. The Board may approve the Public Policy
Transmission Planning Report as submitted or propose modifications on its own motion,
including a determination not to select a Public Policy Transmission Project to satisfy a Public
Policy Transmission Need. If any changes are proposed by the Board, the revised report shall be
returned to the Management Committee for comment. The Board shall not make a final
determination on a revised report until it has reviewed the Management Committee comments,
including comments regarding the Market Monitoring Unit’s evaluation. Upon approval by the
Board, the ISO shall issue the report to the marketplace by posting it on its website. If the ISO
Board determines not to select a Public Policy Transmission Project under this Section 31.4.11.2,
the Board shall state the reasons for its determination.
The responsibilities of the Market Monitoring Unit that are addressed in the above
Section of Attachment Y to the ISO OATT are also addressed in Section 30.4.6.8.5 of the Market
Monitoring Plan, Attachment O to the ISO Services Tariff.
31.4.12 Developer’s Responsibilities Following Selection of Its Public Policy
Transmission Project
31.4.12.1 Developer’s Responsibility to Obtain Necessary Approvals and
Authorizations
Upon its selection of a Public Policy Transmission Project, the ISO will inform the
Developer that it should submit the selected Public Policy Transmission Project to the
appropriate governmental agency(ies) and/or authority(ies) to begin the necessary approval
process to the site, construct, and operate the project. In response to the ISO’s request, the
Developer shall make such a submission to the appropriate governmental agency(ies) and/or
authority(ies) to the extent such authorization has not already been requested or obtained.
If the appropriate federal, state or local agency(ies) either rejects a necessary
authorization, or approves and later withdraws authorization, for the selected Public Policy
Transmission Project, the Developer may recover all of the necessary and reasonable costs
incurred and commitments made up to the final federal, state or local regulatory decision,
including reasonable and necessary expenses incurred to implement an orderly termination of the
project, to the extent permitted by the Commission in accordance with its regulations on
abandoned plant recovery. The ISO shall allocate these costs among Load Serving Entities in
accordance with Section 31.5.5.4.3, except as otherwise determined by the Commission. The
ISO shall recover such costs in accordance with Section 31.5.6 of this Attachment Y and Rate
Schedule 10 of the ISO OATT.5.
31.4.12.2 Development Agreement
As soon as reasonably practicable following the ISO’s selection of the proposed project,
the ISO shall tender to the Developer that proposed the selected Public Policy Transmission
Project a draft Development Agreement with draft appendices completed by the ISO to the
extent practicable for review and completion by the Developer. The draft Development
Agreement shall be in the form of the ISO’s Commission-approved Development Agreement,
which is in Appendix D in Section 31.7 of this Attachment Y. The ISO and the Developer, as
applicable, shall finalize the Development Agreement and appendices and negotiate concerning
any disputed provisions. For purposes of finalizing the Development Agreement, the ISO and
Developer shall develop the description and dates for the milestones necessary to develop and
construct the selected project by the required in-service date identified in the Public Policy
Transmission Planning Report, including the milestones for obtaining all necessary
authorizations. Any milestone that requires action by a Connecting Transmission Owner or
Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete
must be included as an Advisory Milestone, as that term is defined in the Development
Agreement.
Unless otherwise agreed by the ISO and the Developer, the Developer must execute the
Development Agreement within three (3) months of the ISO’s tendering of the draft
Development Agreement; provided, however, if, during the negotiation period, the ISO or the
Developer determines that negotiations are at an impasse, the ISO may file the Development
Agreement in unexecuted form with the Commission on its own or following the Developer’s
request in writing that the agreement be filed unexecuted. If the Development Agreement
resulting from the negotiation between the ISO and the Developer does not conform with the
Commission-approved standard form in Appendix D in Section 31.7 of this Attachment Y, the
ISO shall file the agreement with the Commission for its acceptance within thirty (30) Business
Days after the execution of the Development Agreement by both parties. If the Developer
requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement
at the Commission within thirty (30) Business Days of receipt of the request from the Developer.
The ISO will draft to the extent practicable the portions of the Development Agreement and
appendices that are in dispute and will provide an explanation to the Commission of any matters
as to which the parties disagree. The Developer will provide in a separate filing any comments
that it has on the unexecuted agreement, including any alternative positions it may have with
respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the
Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the
Commission, the ISO and the Developer shall perform their respective obligations in accordance
with the terms of the Development Agreement that are not in dispute, subject to modification by
the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that
are identified in Attachment P of the ISO OATT in connection with the selected Public Policy
Transmission Project shall act in good faith in timely performing their obligations that are
required for the Developer to satisfy its obligations under the Development Agreement.
31.4.12.3 Process for Addressing Inability of Developer to Complete Selected
Public Policy Transmission Project
31.4.12.3.1
The ISO may take the actions described in Sections 31.4.12.3.1.1 through
31.4.12.3.1.3 as soon as practicable if one of the following events occur: (i) the
Developer that proposed the selected Public Policy Transmission Project and is
required to execute the Development Agreement pursuant to Section 31.4.12.2
does not execute the Development Agreement, or does not request that it be filed
unexecuted with the Commission, within the timeframes set forth in Section
31.4.12.2, or (ii) the ISO determines that an effective Development Agreement
may be terminated or terminates the Development Agreement under the terms of
the agreement prior to the completion of the term of the agreement.
31.4.12.3.1.1 If the Development Agreement has been filed with and accepted by the
Commission and is terminated under the terms of the agreement, the ISO shall,
upon terminating the Development Agreement file a notice of termination with
the Commission.
31.4.12.3.1.2 The ISO may take one or more of the following actions to address a Public
Policy Transmission Need based on the particular circumstances: (i) address the
Public Policy Transmission Need in the subsequent planning cycle or, if requested
by the NYPSC pursuant to Section 31.4.1, in an out-of-cycle process; (ii) direct
the Developer to continue with the development of its Public Policy Transmission
Project for completion beyond the in-service date required to address the Public
Policy Transmission Need; or (iii) solicit bids from qualified Developers to
complete the selected Public Policy Transmission Project in accordance with
Section 31.4.12.3.1.3.
31.4.12.3.1.3 If the ISO determines in accordance with Section 31.4.12.3.1.2 that an
alternative Developer should be identified to complete a selected Public Policy
Transmission Project, the ISO shall solicit bids from Developers to finance and
complete the development and construction of the project to bring it into service.
Any Developer that is qualified at the time of the ISO’s solicitation to propose a
Public Policy Transmission Project may submit a proposal to complete the Public
Policy Transmission Project. The ISO will specify in its solicitation for bids by
Developers those categories of project information described in Section 31.4.5.1.1
that the Developer must submit and will identify the metrics in Section 31.4.8 that
the ISO will use to select among the bidding Developers. The ISO will determine
the appropriate project information and metrics based on the current status of
development of the Public Policy Transmission Project. The ISO will make any
selection of an alternative Developer using the selection metrics identified in its
solicitation for bids and consistent with the selection processes set forth in
Sections 31.4.8 and 31.4.11, including issuing an updated Public Policy
Transmission Planning Report. The ISO shall charge, and a Developer bidding
for the Public Policy Transmission Project, shall pay the actual costs of the ISO’s
evaluation of its bid for purposes of selecting a Developer to complete the project
consistent with Section 31.4.4.4. Each bidding Developer will reimburse the ISO
for its actual study costs consistent with the requirements in Section 31.4.4.4. The
selected alternative Developer must enter into a Development Agreement with the
ISO in accordance with the requirements in Section 31.4.12.2. The selected
alternative Developer will be eligible for cost allocation under the ISO OATT for
its development and construction of the Public Policy Transmission Project. The
selected alternative Developer and the Developer that initially proposed the
selected Public Policy Transmission Project shall work cooperatively with each
other to implement the transition, including negotiating in good faith with each
other to transfer the project; provided, however, that the transfer is subject to: (i)
any required approvals by the appropriate governmental agency(ies) and/or
authority(ies), (ii) any requirements or restrictions on the transfer of Developer’s
rights-of-way under federal or state law, regulation, or contract (including
mortgage trust indentures or debt instruments), and (iii) if the Developer is a New
York public authority, any requirements or restrictions on the transfer under the
New York Public Authorities Law; provided, further, that the selected alternative
Developer and the initial Developer will address any disputes regarding the
transfer of the project in accordance with the dispute resolution provisions in
Article 11 of the ISO Services Tariff.
31.4.12.4 Execution of ISO/TO Agreement or Comparable Agreement
The Developer of a selected Public Policy Transmission Project shall execute the ISO/TO
Agreement or an Operating Agreement in accordance with Section 31.1.7 of this Attachment Y
prior to energizing the Public Policy Transmission Project.
31.4.13 ISO Monitoring of Selected Public Policy Transmission Projects
The ISO shall monitor Public Policy Transmission Projects selected by the ISO as the
more efficient or cost effective transmission solutions to Public Policy Transmission Needs to
confirm that they continue to develop consistent with the conditions, actions, or schedules for the
projects.
31.4.14 Posting of Approved Solutions
The ISO shall post on its website a list of all Developers who have accepted the terms
and conditions of an Article VII certificate under the New York Public Service Law, or any
successor statute, or any other applicable permits to build a Public Policy Transmission Project
in response to a need driven by a Public Policy Requirement.
31.4.15 Confidentiality of Solutions
31.4.15.1
The term “Confidential Information” shall include all proposed solutions
to Public Policy Transmission Needs that are submitted to the ISO in response to
a request for solutions under Section 31.4.3 of this Attachment Y if the Developer
of that solution designates the solution as “Confidential Information”; provided,
however, that “Confidential Information” shall not include: (i) the identity of the
Developer, (ii) the proposed facility type, (iii) the proposed facility size, (iv) the
proposed location of the facility, (v) the proposed in-service date for the facility,
and (vi) information regarding the proposed facility that the ISO is required to
disclose under its interconnection or transmission expansion processes pursuant to
Sections 3.7 or 4.5 of the ISO OATT or Attachments X or P of the ISO OATT.
31.4.15.2
The ISO shall maintain the confidentiality of the Developer’s proposed
solution and plans designated as “Confidential Information” until the ISO
determines that the Developer’s proposed solution and plans are viable and
sufficient to meet the Public Policy Transmission Need and the Developer
provides its consent to the ISO’s inclusion of the proposed solution in the Public
Policy Transmission Planning Report under Section 31.4.6.6. Thereafter, the ISO
shall disclose the proposed solution and plans to Market Participants and other
interested parties; provided, however, any preliminary cost estimates that may
have been provided to the ISO, any non-public financial qualification information
provided under Section 31.4.4.1.2, and any contract provided under Sections
31.4.5.1.2 or 31.4.5.2.2 that is designated as “Confidential Information” shall not
be disclosed.
31.5
Cost Allocation and Cost Recovery
31.5.1
The Scope of Attachment Y Cost Allocation
31.5.1.1 Regulated Responses
The cost allocation principles and methodologies in this Attachment Y cover only
regulated transmission solutions to Reliability Needs, regulated transmission responses to
congestion identified in the CARIS, and regulated Public Policy Transmission Projects whether
proposed by a Responsible Transmission Owner or a Transmission Owner or Other Developer.
The cost allocation principles and methodology for: (i) regulated transmission solutions to
Reliability Needs are contained in Sections 31.5.3.1 and 31.5.3.2 of this Attachment Y, (ii)
regulated transmission responses to congestion identified in the CARIS are contained in Sections
31.5.4.1 and 31.5.4.2 of this Attachment Y, and (iii) regulated Public Policy Transmission
Projects are contained in Sections 31.5.5 and 31.5.6 of this Attachment Y.
31.5.1.2 Market-Based Responses
The cost allocation principles and methodologies in this Attachment Y do not apply to
market-based solutions to Reliability Needs, to market-based responses to congestion identified
in the CARIS, or to Other Public Policy Projects. The cost of a market-based project shall be the
responsibility of the developer of that project.
31.5.1.3 Interconnection Cost Allocation
The cost allocation principles and methodologies in this Attachment Y do not apply to the
interconnection costs of generation and merchant transmission projects. Interconnection costs
are determined and allocated in accordance with Attachment P, Attachment S, Attachment X and
Attachment Z of the ISO OATT. Cost related to the deliverability of a resource will be
addressed under the ISO’s deliverability procedures in Attachment S of the ISO OATT.
31.5.1.4 Individual Transmission Service Requests
The cost allocation principles and methodologies in this Attachment Y do not apply to the
cost of transmission expansion projects undertaken in connection with an individual request for
Transmission Service. The cost of such a project is determined and allocated in accordance with
Section 3.7 or Section 4.5 of the ISO OATT.
31.5.1.5 LTP Facilities
The cost allocation principles and methodologies in this Attachment Y do not apply to the
cost of transmission projects included in LTPs or LTP updates. Each Transmission Owner will
recover the cost of such transmission projects in accordance with its then existing rate recovery
mechanisms.
31.5.1.6 Regulated Non-Transmission Projects
Costs related to regulated non-transmission projects will be recovered by Responsible
Transmission Owners, Transmission Owners and Other Developers in accordance with the
provisions of New York Public Service Law, New York Public Authorities Law, or other
applicable state law. Nothing in this section shall affect the Commission’s jurisdiction over the
sale and transmission of electric energy subject to the jurisdiction of the Commission.
31.5.1.7 Eligibility for Cost Allocation and Cost Recovery
Any entity, whether a Responsible Transmission Owner, Other Developer, or
Transmission Owner, shall be eligible for cost allocation and cost recovery as set forth in Section
31.5 of this Attachment Y and associated rRate sSchedule 10 of the ISO OATTs, as applicable,
for any transmission project proposed to satisfy an identified Reliability Need, regulated
economic transmission project, or Public Policy Transmission Project that is determined by the
ISO to be eligible under Sections 31.2, 31.3, or 31.4, as applicable. Interregional Transmission
Projects identified in accordance with the Interregional Planning Protocol, and that have been
accepted in each region’s planning process, shall be eligible for interregional cost allocation and
cost recovery, as set forth in Section 31.5 of this Attachment Y and associated rRate sSchedules
10 of the ISO OATT. The ISO’s share of the cost of an Interregional Transmission Project
selected pursuant to this Attachment Y to meet a Reliability Need, congestion identified in the
CARIS, or a Public Policy Transmission Need shall be eligible for cost allocation consistent with
the cost allocation methodology applicable to the type of regional transmission project that
would be replaced through the construction of such Interregional Transmission Project.
31.5.2
Cost Allocation Principles Required Under Order No. 1000
31.5.2.1
In compliance with Commission Order No. 1000, the ISO shall implement
the specific cost allocation methodology in Section 31.5.3.2, 31.5.4.4, and
31.5.5.4 in accordance with the following Regional Cost Allocation Principles
(“Order No. 1000 Regional Cost Allocation Principles”):
Regional Cost Allocation Principle 1: The ISO shall allocate the cost of
transmission facilities to those within the transmission planning region that
benefit from those facilities in a manner that is at least roughly commensurate
with estimated benefits. In determining the beneficiaries of transmission
facilities, the ISO’s CSPP will consider benefits including, but not limited to, the
extent to which transmission facilities, individually or in the aggregate provide for
maintaining reliability and sharing reserves, production cost savings and
congestion relief, and/or meeting Public Policy Requirements.
Regional Cost Allocation Principle 2: The ISO shall not involuntarily allocate
any of the costs of transmission facilities to those that receive no benefit from
transmission facilities.
Regional Cost Allocation Principle 3: In the event that the ISO adopts a benefit
to cost threshold in its CSPP to determine which transmission facilities have
sufficient net benefits to be selected in a regional transmission plan for the
purpose of cost allocation, such benefit to cost threshold will not be so high that
transmission facilities with significant positive net benefits are excluded from cost
allocation. If the ISO chooses to adopt such a threshold in its CSPP it will not
include a ratio of benefits to costs that exceeds 1.25 unless the ISO justifies and
the Commission approves a higher ratio.
Regional Cost Allocation Principle 4: The ISO’s allocation method for the cost
of a transmission facility selected pursuant to the process in the CSPP shall
allocate costs solely within the ISO’s transmission planning region unless another
entity outside the region or another transmission planning region voluntarily
agrees to assume a portion of those costs. Costs for an Interregional Transmission
Project must be assigned only to regions in which the facility is physically
located. Costs cannot be assigned involuntarily to another region. The ISO shall
not bear the costs of required upgrades in another region.
Regional Cost Allocation Principle 5: The ISO’s cost allocation method and
data requirements for determining benefits and identifying beneficiaries for a
transmission facility shall be transparent with adequate documentation to allow a
stakeholder to determine how they were applied to a proposed transmission
facility, as consistent with confidentiality requirements set forth in this
Attachment Y and the ISO Code of Conduct in Attachment F of the OATT.
Regional Cost Allocation Principle 6: The ISO’s CSPP provides a different cost
allocation method for different types of transmission facilities in the regional
transmission plan and each cost allocation method is set out clearly and explained
in detail in this Section 31.5.
31.5.2.2
In compliance with Commission Order No. 1000, the ISO shall implement
the specific cost allocation methodology in Section 31.5.7 of this Attachment Y in
accordance with the following Interregional Cost Allocation Principles:
Interregional Cost Allocation Principle 1: The ISO shall allocate the cost of
new Interregional Transmission Projects to each region in which an Interregional
Transmission Project is located in a manner that is at least roughly commensurate
with estimated benefits of the Interregional Transmission Project in each of the
regions. In determining the beneficiaries of Interregional Transmission Projects,
the ISO will consider benefits including, but not limited to, those associated with
maintaining reliability and sharing reserves, production cost savings and
congestion relief, and meeting Public Policy Requirements.
Interregional Cost Allocation Principle 2: The ISO shall not involuntarily
allocate any of the costs of an Interregional Transmission Project to a region that
receives no benefit from an Interregional Transmission Project that is located in
that region, either at present or in a likely future scenario.
Interregional Cost Allocation Principle 3: In the event that the ISO adopts a
benefit-cost threshold ratio to determine whether an Interregional Transmission
Project has sufficient net benefits to qualify for interregional cost allocation, this
ratio shall not be so large as to exclude an Interregional Transmission Project with
significant positive net benefits from cost allocation. If the ISO chooses to adopt
such a threshold, they will not include a ratio of benefits to costs that exceeds 1.25
unless the Parties justify and the Commission approves a higher ratio.
Interregional Cost Allocation Principle 4: The ISO’s allocation of costs for an
Interregional Transmission Project shall be assigned only to regions in which the
Interregional Transmission Project is located. The ISO shall not assign costs
involuntarily to a region in which that Interregional Transmission Project is not
located. The ISO shall, however, identify consequences for other regions, such as
upgrades that may be required in a third region. The ISO’s interregional cost
allocation methodology includes provisions for allocating the costs of upgrades
among the beneficiaries in the region in which the Interregional Transmission
Project is located to the transmission providers in such region that agree to bear
the costs associated with such upgrades.
Interregional Cost Allocation Principle 5: The ISO’s cost allocation
methodology and data requirements for determining benefits and identifying
beneficiaries for an Interregional Transmission Project shall be transparent with
adequate documentation to allow a stakeholder to determine how they were
applied to a proposed Interregional Transmission Project, as consistent with the
confidentiality requirements set forth in this Attachment Y and the ISO Code of
Conduct in Attachment F of the OATT.
Interregional Cost Allocation Principle 6: Though Order No. 1000 allows the
ISO to provide a different cost allocation methodology for different types of
interregional transmission facilities, such as facilities needed for reliability,
congestion relief, or to achieve Public Policy Requirements, the ISO has chosen to
adopt one interregional cost allocation methodology for all Interregional
Transmission Planning Projects. The interregional cost allocation methodology is
set out clearly and explained in detail in Section 31.5.7 of this Attachment Y. The
share of the cost related to any Interregional Transmission Project assigned to the
ISO shall be allocated as described in Section 31.5.7.1.
31.5.3
Regulated Responses to Reliability Needs
31.5.3.1 Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.3.2 of this
Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as set
forth in Section 31.5.2.1. This methodology shall apply to cost allocation for a regulated
transmission solution to an identified Reliability Need, including the ISO’s share of the costs of
an Interregional Transmission Project proposed as a regulated transmission solution to an
identified Reliability Need allocated in accordance with Section 31.5.7 of this Attachment Y.
The specific cost allocation methodology in Section 31.5.3.2 incorporates the following
elements:
31.5.3.1.1
The focus of the cost allocation methodology shall be on solutions to
Reliability Needs.
31.5.3.1.2
Potential impacts unrelated to addressing the Reliability Needs shall not be
considered for the purpose of cost allocation for regulated solutions.
31.5.3.1.3
Primary beneficiaries shall initially be those Load Zones or Subzones
identified as contributing to the reliability violation.
31.5.3.1.4
The cost allocation among primary beneficiaries shall be based upon their
relative contribution to the need for the regulated solution.
31.5.3.1.5
The ISO will examine the development of specific cost allocation rules
based on the nature of the reliability violation (e.g., thermal overload, voltage,
stability, resource adequacy and short circuit).
31.5.3.1.6
Cost allocation shall recognize the terms of prior agreements among the
Transmission Owners, if applicable.
31.5.3.1.7
Consideration should be given to the use of a materiality threshold for cost
allocation purposes.
31.5.3.1.8
The methodology shall provide for ease of implementation and
administration to minimize debate and delays to the extent possible.
31.5.3.1.9
Consideration should be given to the “free rider” issue as appropriate.
The methodology shall be fair and equitable.
31.5.3.1.10
The methodology shall provide cost recovery certainty to investors to the
extent possible.
31.5.3.1.11
The methodology shall apply, to the extent possible, to Gap Solutions.
31.5.3.1.12
Cost allocation is independent of the actual triggered project(s), except
when allocating cost responsibilities associated with meeting a Locational
Minimum Installed Capacity Requirement (“LCR”), and is based on a separate
process that results in NYCA meeting its LOLE requirement.
31.5.3.1.13
Cost allocation for a solution that meets the needs of a Target Year
assumes that backstop solutions of prior years have been implemented.
31.5.3.1.14
Cost allocation will consider the most recent values for LCRs. LCRs must
be met for the Target Year.
31.5.3.2 Cost Allocation Methodology
The cost allocation mechanism under this Section 31.5.3.2 sets forth the basis for
allocating costs associated with a Responsible Transmission Owner’s regulated backstop solution
or an Other Developer’s or Transmission Owner’s alternative regulated transmission solution
selected by the ISO as the more efficient or cost-effective transmission solution to an identified
Reliability Need.
The formula is not applicable to that portion of a project beyond the size of the solution
needed to provide the more efficient or cost effective solution appropriate to the Reliability Need
identified in the RNA. Nor is the formula applicable to that portion of the cost of a regulated
transmission reliability project that is, pursuant to Section 25.7.12 of Attachment S to the ISO
OATT, paid for with funds previously committed by or collected from Developers for the
installation of System Deliverability Upgrades required for the interconnection of generation or
merchant transmission projects.
This Section 31.5.3.2 establishes the allocation of the costs related to resolving
Reliability Needs resulting from resource adequacy, BPTF thermal transmission security, BPTF
voltage security, dynamic stability, and short circuit issues. Costs will be allocated in
accordance with the following hierarchy: (i) resource adequacy pursuant to Section 31.5.3.2.1,
(ii) BPTF thermal transmission security pursuant to Section 31.5.3.2.2, (iii) BPTF voltage
security pursuant to Section 31.5.3.2.3, (iv) dynamic stability pursuant to Section 31.5.3.2.4, and
(v) short circuit pursuant to Section 31.5.3.2.5.
31.5.3.2.1 Resource Adequacy Reliability Solution Cost Allocation Formula
For purposes of solutions eligible for cost allocation under this Section 31.5.3.2, this
section sets forth the cost allocation methodology applicable to that portion of the costs of the
solution attributable to resolving resource adequacy. The same cost allocation formula is applied
regardless of the project or sets of projects being triggered; however, the nature of the solution
set may lead to some terms equaling zero, thereby dropping out of the equation. To ensure that
appropriate allocation to the LCR and non-LCR zones occurs, the zonal allocation percentages
are developed through a series of steps that first identify responsibility for LCR deficiencies,
followed by responsibility for remaining need. The following formula shall apply to the
allocation of the costs of the solution attributable to resource adequacy:
+
*
+
*
*100%
Where i is for each applicable zone, n represent the total zones in NYCA, m represents
the zones isolated by the binding interfaces, IRM is the statewide reserve margin, and where
LCR is defined as the locational capacity requirement in terms of percentage and is equal to zero
for those zones without an LCR requirement, LCRdefi is the applicable zonal LCR deficiency,
SolnSTWdef is the STWdef for each applicable project, SolnCIdef is the CIdef for each
applicable project, and Soln_Size represents the total compensatory MW addressed by each
applicable project for all reliability cost allocation steps in this Section 31.5.3.2.
Three step cost allocation methodology for regulated reliability solutions:
31.5.3.2.1.1 Step 1 - LCR Deficiency
31.5.3.2.1.1.1 Any deficiencies in meeting the LCRs for the Target Year will be referred
to as the LCRdef. If the reliability criterion is met once the LCR deficiencies
have been addressed, that is LOLE 0.1 for the Target Year is achieved, then the
only costs allocated will be those related to the LCRdef MW. Cost responsibility
for the LCRdef MW will be borne by each deficient locational zone(s), to the
extent each is individually deficient.
For a single solution that addresses only an LCR deficiency in the applicable LCR zone,
the equation would reduce to:
Where i is for each applicable LCR zone, LCRdefi represents the applicable zonal LCR
deficiency, and Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.1.1.2 Prior to the LOLE calculation, voltage constrained interfaces will be
recalculated to determine the resulting transfer limits when the LCRdef MW are
added.
31.5.3.2.1.2 Step 2 - Statewide Resource Deficiency. If the reliability criterion is not
met after the LCRdef has been addressed, that is an LOLE > 0.1, then a NYCA
Free Flow Test will be conducted to determine if NYCA has sufficient resources
to meet an LOLE of 0.1.
31.5.3.2.1.2.1 If NYCA is found to be resource limited, the ISO, using the transfer limits
and resources determined in Step 1, will determine the optimal distribution of
additional resources to achieve a reduction in the NYCA LOLE to 0.1.
31.5.3.2.1.2.2 Cost allocation for compensatory MW added for cost allocation purposes
to achieve an LOLE of 0.1, defined as a Statewide MW deficiency (STWdef), will
be prorated to all NYCA zones, based on the NYCA coincident peak load. The
allocation to locational zones will take into account their locational requirements.
For a single solution that addresses only a statewide deficiency, the equation
would reduce to:
*
*100%
Where i is for each applicable zone, n is for the total zones in NYCA, IRM is the
statewide reserve margin, and LCR is defined as the locational capacity
requirement in terms of percentage and is equal to zero for those zones without an
LCR requirement, Soln STWdef is the STWdef for the applicable project, and
Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.1.3 Step 3 - Constrained Interface Deficiency. If the NYCA is not resource
limited as determined by the NYCA Free Flow Test, then the ISO will examine
constrained transmission interfaces, using the Binding Interface Test.
31.5.3.2.1.3.1 The ISO will provide output results of the reliability simulation program
utilized for the RNA that indicate the hours that each interface is at limit in each
flow direction, as well as the hours that coincide with a loss of load event. These
values will be used as an initial indicator to determine the binding interfaces that
are impacting LOLE within the NYCA.
31.5.3.2.1.3.2 The ISO will review the output of the reliability simulation program
utilized for the RNA along with other applicable information that may be
available to make the determination of the binding interfaces.
31.5.3.2.1.3.3 Bounded Regions are assigned cost responsibility for the compensatory
MW, defined as CIdef, needed to reach an LOLE of 0.1.
31.5.3.2.1.3.4 If one or more Bounded Regions are isolated as a result of binding
interfaces identified through the Binding Interface Test, the ISO will determine
the optimal distribution of compensatory MW to achieve a NYCA LOLE of 0.1.
Compensatory MW will be added until the required NYCA LOLE is achieved.
31.5.3.2.1.3.5 The Bounded Regions will be identified by the ISO’s Binding Interface
Test, which identifies the bounded interface limits that can be relieved and have
the greatest impact on NYCA LOLE. The Bounded Region that will have the
greatest benefit to NYCA LOLE will be the area to be first allocated costs in this
step. The ISO will determine if after the first addition of compensating MWs the
Bounded Region with the greatest impact on LOLE has changed. During this
iterative process, the Binding Interface Test will look across the state to identify
the appropriate Bounded Region. Specifically, the Binding Interface Test will be
applied starting from the interface that has the greatest benefit to LOLE (the
greatest LOLE reduction per interface compensatory MW addition), and then
extended to subsequent interfaces until a NYCA LOLE of 0.1 is achieved.
31.5.3.2.1.3.6 The CIdef MW are allocated to the applicable Bounded Region isolated as
a result of the constrained interface limits, based on their NYCA coincident peaks.
Allocation to locational zones will take into account their locational requirements.
For a single solution that addresses only a binding interface deficiency, the
equation would reduce to:
*
*100%
Where i is for each applicable zone, m is for the zones isolated by the binding
interfaces, IRM is the statewide reserve margin, and where LCR is defined as the
locational capacity requirement in terms of percentage and is equal to zero for
those zones without an LCR requirement, SolnCIdef is the CIdef for the
applicable project and Soln_Size represents the total compensatory MW
addressed by the applicable project.
31.5.3.2.2 BPTF Thermal Transmission Security Cost Allocation Formula
For purposes of solutions eligible for cost allocation under this Section 31.5.3.2, this
section sets forth the cost allocation methodology applicable to that portion of the costs of the
solution attributable to resolving BPTF thermal transmission security issues. If, after
consideration of the compensatory MW identified in the resource adequacy reliability solution
cost allocation in accordance with Section 31.5.3.2.1, there remains a BPTF thermal transmission
security issue, the ISO will allocate the costs of the portion of the solution attributable to
resolving the BPTF thermal transmission security issue(s) to the Subzones that contribute to the
BPTF thermal transmission security issue(s) in the following manner.
31.5.3.2.2.1 Calculation of Nodal Distribution Factors. The ISO will calculate the
nodal distribution factor for each load bus modeled in the power flow case
utilizing the output of the reliability simulation program that identified the
Reliability Need, including the NYCA generation dispatch and NYCA coincident
peak Load. The nodal distribution factor represents the percentage of the Load
that flows across the facility subject to the Reliability Need. The sign (positive or
negative) of the nodal distribution factor represents the direction of flow.
31.5.3.2.2.2 Calculation of Nodal Flow. The ISO will calculate the nodal megawatt
flow, defined as Nodal Flow, for each load bus modeled in the power flow case
by multiplying the amount of Load in megawatts for the bus, defined as Nodal
Load, by the nodal distribution factor for the bus. Nodal Flow represents the
number of megawatts that flow across the facility subject to the Reliability Need
due to the Load.
31.5.3.2.2.3 Calculation of Contributing Load and Contributing Flow. The Nodal
Load for a load bus with a positive nodal distribution factor is a contributing
Load, defined as CLoad, and the Nodal Flow for that Load is contributing flow,
defined as CFlow. To identify contributing Loads that have a material impact on
the Reliability Need, the ISO will calculate a contributing materiality threshold,
defined as CMT, as follows:
Where m is for the total number of Subzones and n is for the total number of load
buses in a given Subzone.
31.5.3.2.2.4 Calculation of Helping Load and Helping Flow. The Nodal Load for a
load bus with a negative or zero nodal distribution factor is a helping Load,
defined as HLoad, and the Nodal Flow for that Load is helping flow, defined as
HFlow. To identify helping Loads that have a material impact on the Reliability
Need, the ISO will calculate a helping materiality threshold, defined as HMT, as
follows:
Where m is for the total number of Subzones and n is for the total number of load
buses in a given Subzone.
31.5.3.2.2.5 Calculation of Net Material Flow for Each Subzone. The ISO will
identify material Nodal Flow for each Subzone and calculate the net material flow
for each Subzone. For each load bus, the Nodal Flow will be identified as
material flow, defined as MFlow, if the nodal distribution factor is (i) greater than
or equal to CMT, or (ii) less than or equal to HMT. The net material flow for
each Subzone, defined as SZ_NetFlow, is calculated as follows:
Where j is for each Subzone and n is for the total number of load buses in a given
Subzone.
31.5.3.2.2.6 Identification of Allocated Flow for Each Subzone. The ISO will identify
the allocated flow for each Subzone and verify that sufficient contributing flow is
being allocated costs. For each Subzone, if the SZ_NetFlow is greater than zero,
that Subzone has a net material contribution to the Reliability Need and the
SZ_NetFlow is identified as allocated flow, defined as SZ_AllocFlow. If the
SZ_NetFlow is less than or equal to zero, that Subzone does not have a net
material contribution to the Reliability Need and the SZ_AllocFlow is zero for
that Subzone. If the total SZ_AllocFlow for all Subzones is less than 60% of the
total CFlow for all Subzones, then the CMT will be reduced and SZ_NetFlow
recalculated until the total SZ_AllocFlow for all Subzones is at least 60% of the
total CFlow for all Subzones.
31.5.3.2.2.7 Cost Allocation for a Single BPTF Thermal Transmission Security Issue.
For a single solution that addresses only a BPTF thermal transmission security
issue, the equation for cost allocation would reduce to:
Where j is for each Subzone; m is for the total number of Subzones;
SZ_AllocFlow is the allocated flow for each Subzone; SolnBTSdef is the number
of compensatory MW for the BPTF thermal transmission security issue for the
applicable project; and Soln_Size represents the total compensatory MW
addressed by the applicable project.
31.5.3.2.2.8 Cost Allocation for Multiple BPTF Thermal Transmission Security Issues.
If a single solution addresses multiple BPTF thermal transmission security issues,
the ISO will calculate weighting factors based on the ratio of the present value of
the estimated costs for individual solutions to each BPTF thermal transmission
security issue. The present values of the estimated costs for the individual
solutions shall be based on a common base date that will be the beginning of the
calendar month in which the cost allocation analysis is performed (the “Base
Date”). The ISO will apply the weighting factors to the cost allocation calculated
for each Subzone for each individual BPTF thermal transmission security issue.
The following example illustrates the cost allocation for such a solution:
A cost allocation analysis for the selected solution is to be performed during a
given month establishing the beginning of that month as the Base Date.
The ISO has identified two BPTF thermal transmission security issues, Overload
X and Overload Y, and the ISO has selected a single solution (Project Z) to
address both BPTF thermal transmission security issues.
The cost of a solution to address only Overload X (Project X) is Cost(X),
provided in a given year’s dollars. The number of years from the Base Date to the
year associated with the cost estimate of Project (X) is N(X).
The cost of a solution to address only Overload Y (Project Y) is Cost(Y),
provided in a given year’s dollars. The number of years from the Base Date to the
year associated with the cost estimate of Project Y is N(Y).
The discount rate, D, to be used for the present value analysis shall be the current
after-tax weighted average cost of capital for the Transmission Owners.
Based on the foregoing assumptions, the following formulas will be used:
Present Value of Cost (X) = PV Cost (X) = Cost (X) / (1+D)N(X)
Present Value of Cost (Y) = PV Cost (Y) = Cost (Y) / (1+D)N(Y)
Overload X weighting factor = PV Cost (X)/[PV Cost (X) + PV Cost (Y)]
Overload Y weighting factor = PV Cost (Y)/[PV Cost (X) + PV Cost (Y)]
Applying those formulas, if:
Cost (X) = $100 Million and N(X) = 6.25 years
Cost (Y) = $25 Million and N(Y) = 4.75 years
D = 7.5% per year
Then:
PV Cost (X) = 100/(1+0.075) 6.25 = 63.635 Million
PV Cost (Y) = 25/(1+0.075)4.75
= 17.732 Million
Overload X weighting factor = 63.635 / (63.635 + 17.732) = 78.21%
Overload Y weighting factor = 17.732 / (63.635 + 17.732) = 21.79%
Applying those weighing factors, if:
Subzone A cost allocation for Overload X is 15%
Subzone A cost allocation for Overload Y is 70%
Then:
Subzone A cost allocation % for Project Z =
(15% * 78.21%) + (70% * 21.79%) = 26.99%
31.5.3.2.2.9 Exclusion of Subzone(s) Based on De Minimis Impact. If a Subzone is
assigned a BPTF thermal transmission security cost allocation less than a de
minimis dollar threshold of the total project costs, that Subzone will not be
allocated costs; provided however, that the total de minimis Subzones may not
exceed 10% of the total BPTF thermal transmission security cost allocation. The
de minimis threshold is initially $10,000. If the total allocation percentage of all
de minimis Subzones is greater than 10%, then the de minimis threshold will be
reduced until the total allocation percentage of all de minimis Subzones is less
than or equal to 10%.
31.5.3.2.3 BPTF Voltage Security Cost Allocation
If, after consideration of the compensatory MW identified in the resource adequacy cost
allocation in accordance with Section 31.5.3.2.1 and BPTF thermal transmission security cost
allocation in accordance with Section 31.5.3.2.2, there remains a BPTF voltage security issue,
the ISO will allocate the costs of the portion of the solution attributable to resolving the BPTF
voltage security issue(s) to the Subzones that contribute to the BPTF voltage security issue(s).
The cost responsibility for the portion (MW or MVAr) of the solution attributable to resolving
the BPTF voltage security issue(s), defined as SolnBVSdef, will be allocated on a Load-ratio
share to each Subzone to which each bus with a voltage issue is connected, as follows:
Where j is for each Subzone; m is for the total number of Subzones that are subject to
BPTF voltage cost allocation; Coincident Peak is for the total peak Load for each Subzone;
SolnBVSdef is for the portion of the solution necessary to resolve the BPTF voltage security
issue(s); and Soln_Size represents the total compensatory MW addressed by the applicable
project.
31.5.3.2.4 Dynamic Stability Cost Allocation
If, after consideration of the compensatory MW identified in the resource adequacy cost
allocation in accordance with Section 31.5.3.2.1, BPTF thermal transmission security cost
allocation in accordance with Section 31.5.3.2.2, and BPTF voltage security cost allocation in
accordance with Section 31.5.3.2.3, there remains a dynamic stability issue, the ISO will allocate
the costs of the portion of the solution attributable to resolving the dynamic stability issue(s) to
all Subzones in the NYCA on a Load-ratio share basis, as follows:
Where j is for each Subzone; m is for the total number of Subzones; Coincident Peak is
for the total peak Load for each Subzone; DynamicMW is for the megawatt portion of the
solution necessary to resolve the dynamic stability issue(s) for the applicable project; and
Soln_Size represents the total compensatory MW addressed by the applicable project.
31.5.3.2.5 Short Circuit Issues
If, after the completion of the prior reliability cost allocation steps, there remains a short
circuit issue, the short circuit issue will be deemed a local issue and related costs will not be
allocated under this process.
31.5.4
Regulated Economic Projects
31.5.4.1 The Scope of Section 31.5.4
As discussed in Section 31.5.1 of this Attachment Y, the cost allocation principles and
methodologies of this Section 31.5.4 apply only to regulated economic transmission projects
(“RETPs”) proposed in response to congestion identified in the CARIS.
This Section 31.5.4 does not apply to generation or demand side management projects,
nor does it apply to any market-based projects. This Section 31.5.4 does not apply to regulated
backstop solutions triggered by the ISO pursuant to the CSPP, provided, however, the cost
allocation principles and methodologies in this Section 31.5.4 will apply to regulated backstop
solutions when the implementation of the regulated backstop solution is accelerated solely to
reduce congestion in earlier years of the Study Period. The ISO will work with the ESPWG to
develop procedures to deal with the acceleration of regulated backstop solutions for economic
reasons.
Nothing in this Attachment Y mandates the implementation of any project in response to
the congestion identified in the CARIS.
31.5.4.2 Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.4.4 of
this Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as
set forth in Section 31.5.2.1. The specific cost allocation methodology in Section 31.5.4.4
incorporates the following elements:
31.5.4.2.1
The focus of the cost allocation methodology shall be on responses to
specific conditions identified in the CARIS.
31.5.4.2.2
Potential impacts unrelated to addressing the identified congestion shall
not be considered for the purpose of cost allocation for RETPs.
31.5.4.2.3
Projects analyzed hereunder as proposed RETPs may proceed on a market
basis with willing buyers and sellers at any time.
31.5.4.2.4
Cost allocation shall be based upon a beneficiaries pay approach. Cost
allocation under the ISO tariff for a RETP shall be applicable only when a super
majority of the beneficiaries of the project, as defined in Section 31.5.4.6 of this
Attachment Y, vote to support the project.
31.5.4.2.5
Beneficiaries of a RETP shall be those entities economically benefiting
from the proposed project. The cost allocation among beneficiaries shall be based
upon their relative economic benefit.
31.5.4.2.6
Consideration shall be given to the proposed project’s payback period.
31.5.4.2.7
The cost allocation methodology shall address the possibility of cost
overruns.
31.5.4.2.8
Consideration shall be given to the use of a materiality threshold for cost
allocation purposes.
31.5.4.2.9
The methodology shall provide for ease of implementation and
administration to minimize debate and delays to the extent possible.
31.5.4.2.10
Consideration should be given to the “free rider” issue as appropriate. The
methodology shall be fair and equitable.
31.5.4.2.11
The methodology shall provide cost recovery certainty to investors to the
extent possible.
31.5.4.2.12
Benefits determination shall consider various perspectives, based upon the
agreed-upon metrics for analyzing congestion.
31.5.4.2.13
Benefits determination shall account for future uncertainties as appropriate
(e.g., load forecasts, fuel prices, environmental regulations).
31.5.4.2.14
Benefits determination shall consider non-quantifiable benefits as
appropriate (e.g., system operation, environmental effects, renewable integration).
31.5.4.3 Project Eligibility for Cost Allocation
The methodologies in this Section 31.5.4.3 will be used to determine the eligibility of a
proposed RETP to have its cost allocated and recovered pursuant to the provisions of this
Attachment Y.
31.5.4.3.1
The ISO will evaluate the benefits against the costs (as provided by the
Developer) of each proposed RETP over a ten-year period commencing with the
proposed commercial operation date for the project. The Developer of each
project will pay the cost incurred by the ISO to conduct the ten-year benefit/cost
analysis of its project. The ISO, in conjunction with the ESPWG, will develop
methodologies for extending the most recently completed CARIS database as
necessary to evaluate the benefits and costs of each proposed RETP.
31.5.4.3.2
The benefit metric for eligibility under the ISO’s benefit/cost analysis will
be expressed as the present value of the annual NYCA-wide production cost
savings that would result from the implementation of the proposed project,
measured for the first ten years from the proposed commercial operation date for
the project.
31.5.4.3.3
The cost for the ISO’s benefit/cost analysis will be supplied by the
Developer of the project, and the cost metric for eligibility will be expressed as
the present value of the first ten years of annual total revenue requirements for the
project, reasonably allocated over the first ten years from the proposed
commercial operation date for the project.
31.5.4.3.4
For informational purposes only, the ISO will also calculate the present
value of the annual total revenue requirement for the project over a 30 year period
commencing with the proposed commercial operation date of the project.
31.5.4.3.5
To be eligible for cost allocation and recovery under this Attachment Y,
the benefit of the proposed project must exceed its cost measured over the first ten
years from the proposed commercial operation date for the project, and the
requirements of section 31.5.4.2 must be met. The total capital cost of the project
must exceed $25 million. In addition, a super-majority of the beneficiaries must
vote in favor of the project, as specified in Section 31.5.4.6 of this Attachment Y.
31.5.4.3.6
In addition to calculating the benefit metric as defined in Section
31.5.4.3.2, the ISO will calculate additional metrics to estimate the potential
benefits of the proposed project, for information purposes only, in accordance
with Section 31.3.1.3.5, for the applicable metric. These additional metrics shall
include those that measure reductions in LBMP load costs, changes to generator
payments, ICAP costs, Ancillary Service costs, emissions costs, and losses. TCC
revenues will be determined in accordance with Section 31.5.4.4.2.3. The ISO
will provide information on these additional metrics to the maximum extent
practicable considering its overall resource commitments.
31.5.4.3.7
In addition to the benefit/cost analysis performed by the ISO under this
Section 31.5.4.3, the ISO will work with the ESPWG to consider the development
and implementation of scenario analyses, for information only, that shed
additional light on the benefit/cost analysis of a proposed project. These
additional scenario analyses may cover fuel and load forecast uncertainty,
emissions data and the cost of allowances, pending environmental or other
regulations, and alternate resource and energy efficiency scenarios. Consideration
of these additional scenarios will take into account the resource commitments of
the ISO.
31.5.4.4 Cost Allocation for Eligible Projects
As noted in Section 31.5.4.2 of this Attachment Y, the cost of a RETP will be allocated to
those entities that would economically benefit from implementation of the proposed project. This
methodology shall apply to cost allocation for a RETP, including the ISO’s share of the costs of
an Interregional Transmission Project proposed as a RETP allocated in accordance with Section
31.5.7 of this Attachment Y.
31.5.4.4.1
The ISO will identify the beneficiaries of the proposed project over a ten-
year time period commencing with the proposed commercial operation date for
the project. The ISO, in conjunction with the ESPWG, will develop
methodologies for extending the most recently completed CARIS database as
necessary for this purpose.
31.5.4.4.2
The ISO will identify beneficiaries of a proposed project as follows:
31.5.4.4.2.1 The ISO will measure the present value of the annual zonal LBMP load
savings for all Load Zones which would have a load savings, net of reductions in
TCC revenues, and net of reductions from bilateral contracts (based on available
information provided by Load Serving Entities to the ISO as set forth in
subsection 31.5.4.4.2.5 below) as a result of the implementation of the proposed
project. For purposes of this calculation, the present value of the load savings will
be equal to the sum of the present value of the Load Zone’s load savings for each
year over the ten-year period commencing with the project’s commercial
operation date. The load savings for a Load Zone will be equal to the difference
between the zonal LBMP load cost without the project and the LBMP load cost
with the project, net of reductions in TCC revenues and net of reductions from
bilateral contracts.
31.5.4.4.2.2 The beneficiaries will be those Load Zones that experience net benefits
measured over the first ten years from the proposed commercial operation date for
the project. If the sum of the zonal benefits for those Load Zones with load
savings is greater than the revenue requirements for the project (both load savings
and revenue requirements measured in present value over the first ten years from
the commercial operation date of the project), the ISO will proceed with the
development of the zonal cost allocation information to inform the beneficiary
voting process.
31.5.4.4.2.3 Reductions in TCC revenues will reflect the forecasted impact of the
project on TCC auction revenues and day-ahead residual congestion rents
allocated to load in each zone, not including the congestion rents that accrue to
any Incremental TCCs that may be made feasible as a result of this project. This
impact will include forecasts of: (1) the total impact of that project on the
Transmission Service Charge offset applicable to loads in each zone (which may
vary for loads in a given zone that are in different Transmission Districts); (2) the
total impact of that project on the NYPA Transmission Adjustment Charge offset
applicable to loads in that zone; and (3) the total impact of that project on
payments made to LSEs serving load in that zone that hold Grandfathered Rights
or Grandfathered TCCs, to the extent that these have not been taken into account
in the calculation of item (1) above. These forecasts shall be performed using the
procedure described in Appendix B to this Attachment Y.
31.5.4.4.2.4 Estimated TCC revenues from any Incremental TCCs created by a
proposed RETP over the ten-year period commencing with the project’s
commercial operation date will be added to the Net Load Savings used for the
cost allocation and beneficiary determination.
31.5.4.4.2.5 The ISO will solicit bilateral contract information from all Load Serving
Entities, which will provide the ISO with bilateral energy contract data for
modeling contracts that do not receive benefits, in whole or in part, from LBMP
reductions, and for which the time period covered by the contract is within the
ten-year period beginning with the commercial operation date of the project.
Bilateral contract payment information that is not provided to the ISO will not be
included in the calculation of the present value of the annual zonal LBMP savings
in section 31.5.4.4.2.1 above.
31.5.4.4.2.5.1 All bilateral contract information submitted to the ISO must identify the
source of the contract information, including citations to any public documents
including but not limited to annual reports or regulatory filings
31.5.4.4.2.5.2 All non-public bilateral contract information will be protected in
accordance with the ISO’s Code of Conduct, as set forth in Section 12.4 of
Attachment F of the ISO OATT, and Section 6 of the ISO Services Tariff.
31.5.4.4.2.5.3 All bilateral contract information and information on LSE-owned
generation submitted to the ISO must include the following information:
(1)
Contract quantities on an annual basis:
(a)
For non-generator specific contracts, the Energy (in MWh) contracted to serve
each Zone for each year.
(b)
For generator specific contracts or LSE-owned generation, the name of the
generator(s) and the MW or percentage output contracted or self-owned for use by
Load in each Zone for each year.
(2)
For all Load Serving Entities serving Load in more than one Load Zone, the
quantity (in MWh or percentage) of bilateral contract Energy to be applied to each
Zone, by year over the term of the contract.
(3)
Start and end dates of the contract.
(4)
Terms in sufficient detail to determine that either pricing is not indexed to LBMP,
or, if pricing is indexed to LBMP, the manner in which prices are connected to
LBMP.
(5)
Identify any changes in the pricing methodology on an annual basis over the term
of the contract.
31.5.4.4.2.5.4 Bilateral contract and LSE-owned generation information will be used to
calculate the adjusted LBMP savings for each Load Zone as follows:
AdjLBMPSy,z, the adjusted LBMP savings for each Load Zone z in each year y, shall be
calculated using the following equation:
Where:
TLy,z is the total annual amount of Energy forecasted to be consumed by Load in year y in
Load Zone z;
By,z is the set of blocks of Energy to serve Load in Load Zone z in year y that are sold
under bilateral contracts for which information has been provided to the ISO that meets the
requirements set forth elsewhere in this Section 31.5.4.4.2.5
BCLb,y,z is the total annual amount of Energy sold into Load Zone z in year y under
bilateral contract block b;
Indb,y,z is the ratio of (1) the increase in the amount paid by the purchaser of Energy,
under bilateral contract block b, as a result of an increase in the LBMP in Load Zone z in year y
to (2) the increase in the amount that a purchaser of that amount of Energy would pay if the
purchaser paid the LBMP for that Load Zone in that year for all of that Energy (this ratio shall be
zero for any bilateral contract block of Energy that is sold at a fixed price or for which the cost of
Energy purchased under that contract otherwise insensitive to the LBMP in Load Zone z in year
y);
SGy,z is the total annual amount of Energy in Load Zone z that is forecasted to be served
by LSE-owned generation in that Zone in year y;
LBMP1y,z is the forecasted annual load-weighted average LBMP for Load Zone z in year
y, calculated under the assumption that the project is not in place; and
LBMP2y,z is the forecasted annual load-weighted average LBMP for Load Zone z in year
y, calculated under the assumption that the project is in place.
31.5.4.4.2.6 NZSz, the Net Zonal Savings for each Load Zone z resulting from a given
project, shall be calculated using the following equation:
Where:
PS is the year in which the project is expected to enter commercial operation;
AdjLBMPSy,z is as calculated in Section 31.5.4.4.2.5;
TCCRevImpacty,z is the forecasted impact of TCC revenues allocated to Load Zone z in
year y, calculated using the procedure described in Appendix B in Section 31.7 of this
Attachment Y; and
DFy is the discount factor applied to cash flows in year y to determine the present value
of that cash flow in year PS.
31.5.4.4.3
Load Zones not benefiting from a proposed RETP will not be allocated
any of the costs of the project under this Attachment Y. There will be no “make
whole” payments to non-beneficiaries.
31.5.4.4.4
Costs of a project will be allocated to beneficiaries as follows:
31.5.4.4.4.1 The ISO will allocate the cost of the RETP based on the zonal share of
total savings to the Load Zones determined pursuant to Section 31.5.4.4.2 to be
beneficiaries of the proposed project. Total savings will be equal to the sum of
load savings for each Load Zone that experiences net benefits pursuant to Section
31.5.4.4.2. A Load Zone’s cost allocation will be equal to the present value of the
following calculation:
31.5.4.4.4.2 Zonal cost allocation calculations for a RETP will be performed prior to
the commencement of the ten-year period that begins with the project’s
commercial operation date, and will not be adjusted during that ten-year period.
31.5.4.4.4.3 Within zones, costs will be allocated to LSEs based on MWhs calculated
for each LSE for each zone using data from the most recent available 12 month
period. Allocations to an LSE will be calculated in accordance with the following
formula:
31.5.4.4.5
Project costs allocated under this Section 31.5.4.4 will be determined as
follows:
31.5.4.4.5.1 The project cost allocated under this Section 31.5.4.4 will be based on the
total project revenue requirement, as supplied by the Developer of the project, for
the first ten years of project operation. The total project revenue requirement will
be determined in accordance with the formula rate on file at the Commission. If
there is no formula rate on file at the Commission, then the Developer shall
provide to the ISO the project-specific parameters to be used to calculate the total
project revenue requirement.
31.5.4.4.5.2 Once the benefit/cost analysis is completed the amortization period and
the other parameters used to determine the costs that will be recovered for the
project should not be changed, unless so ordered by the Commission or a court of
applicable jurisdiction, for cost recovery purposes to maintain the continued
validity of the benefit/cost analysis.
31.5.4.4.5.3 The ISO, in conjunction with the ESPWG, will develop procedures to
allocate the risk of project cost increases that occur after the ISO completes its
benefit/cost analysis under this Attachment Y. These procedures may include
consideration of an additional review and vote prior to the start of construction
and whether the developer should bear all or part of the cost of any overruns.
31.5.4.4.6
The Commission must approve the cost of a proposed RETP for that cost
to be recovered through Rate Schedule 10 of the ISO OATT. The developer’s
filing of its project revenue requirement with the Commission pursuant to Rate
Schedule 10 must be consistent with the project proposal evaluated by the ISO
under this Attachment Y in order to be cost allocated to beneficiaries.
31.5.4.5 Collaborative Governance Process and Board Action
31.5.4.5.1
The ISO shall submit the results of its project benefit/cost analysis and
beneficiary determination to the ESPWG and TPAS, and to the identified
beneficiaries of the proposed RETP for comment. The ISO shall make available
to any interested party sufficient information to replicate the results of the
benefit/cost analysis and beneficiary determination. The information made
available will be electronically masked and made available pursuant to a process
that the ISO reasonably determines is necessary to prevent the disclosure of any
Confidential Information or Critical Energy Infrastructure Information contained
in the information made available. Following completion of the review by the
ESPWG and TPAS of the project benefit/cost analysis, the ISO’s analysis
reflecting any revisions resulting from the TPAS and ESPWG review shall be
forwarded to the Business Issues Committee and Management Committee for
discussion and action.
31.5.4.5.2
Following the Management Committee vote, the ISO’s project benefit/cost
analysis and beneficiary determination will be forwarded, with the input of the
Business Issues Committee and Management Committee, to the ISO Board for
review and action. In addition, the ISO’s determination of the beneficiaries’
voting shares will be forwarded to the ISO Board for review and action. The
Board may approve the analysis and beneficiary determinations as submitted or
propose modifications on its own motion. If any changes to the benefit/cost
analysis or the beneficiary determinations are proposed by the Board, the revised
analysis and beneficiary determinations shall be returned to the Management
Committee for comment. If the Board proposes any changes to the ISO’s voting
share determinations, the Board shall so inform the LSE or LSEs impacted by the
proposed change and shall allow such an LSE or LSEs an opportunity to comment
on the proposed change. The Board shall not make a final determination on the
project benefit/cost analysis and beneficiary determination until it has reviewed
the Management Committee comments. Upon final approval of the Board,
project benefit/cost analysis and beneficiary determinations shall be posted by the
ISO on its website and shall form the basis of the beneficiary voting described in
Section 31.5.4.6 of this Attachment Y.
31.5.4.6 Voting by Project Beneficiaries
31.5.4.6.1
Only LSEs serving Load located in a beneficiary zone determined in
accordance with the procedures in Section 31.5.4.4 of this Attachment Y shall be
eligible to vote on a proposed project. The ISO will, in conjunction with the
ESPWG, develop procedures to determine the specific list of voting entities for
each proposed project. Prior to a vote being conducted, the Developer of the
RETP must have a completed System Impact Study or System Reliability Impact
Study, as applicable.
31.5.4.6.2
The voting share of each LSE shall be weighted in accordance with its
share of the total project benefits, as allocated by Section 31.5.4.4 of this
Attachment Y.
31.5.4.6.3
The costs of a RETP shall be allocated under this Attachment Y if eighty
percent (80%) or more of the actual votes cast on a weighted basis are cast in
favor of implementing the project.
31.5.4.6.4
If the proposed RETP meets the required vote in favor of implementing
the project, and the project is implemented, all beneficiaries, including those
voting “no,” will pay their proportional share of the cost of the project.
31.5.4.6.5
The ISO will tally the results of the vote in accordance with procedures set
forth in the ISO Procedures, and report the results to stakeholders. Beneficiaries
voting against approval of a project must submit to the ISO their rationale for
their vote within 30 days of the date that the vote is taken. Beneficiaries must
provide a detailed explanation of the substantive reasons underlying the decision,
including, where appropriate: (1) which additional benefit metrics, either
identified in the tariff or otherwise, were used; (2) the actual quantification of
such benefit metrics or factors; (3) a quantification and explanation of the net
benefit or net cost of the project to the beneficiary; and (4) data supporting the
metrics and other factors used. Such explanation may also include uncertainties,
and/or alternative scenarios and other qualitative factors considered, including
state public policy goals. The ISO will report this information to the Commission
in an informational filing to be made within 60 days of the vote. The
informational filing will include: (1) a list of the identified beneficiaries; (2) the
results of the benefit/cost analysis; and (3) where a project is not approved,
whether the developer has provided any formal indication to the ISO as to the
future development of the project.
31.5.5
Regulated Transmission Solutions to Public Policy Transmission Needs
31.5.5.1 The Scope of Section 31.5.5
As discussed in Section 31.5.1 of this Attachment Y, the cost allocation principles and
methodologies of this Section 31.5.5 apply only to regulated Public Policy Transmission
Projects. This Section 31.5.5 does not apply to Other Public Policy Projects, including
generation or demand side management projects, or any market-based projects. This Section
31.5.5 does not apply to regulated reliability solutions implemented pursuant to the reliability
planning process, nor does it apply to RETPs proposed in response to congestion identified in the
CARIS.
A regulated solution shall only utilize the cost allocation methodology set forth in Section
31.5.3 where it is: (1) a Responsible Transmission Owner’s regulated backstop solution, (2) an
alternative regulated transmission solution selected by the ISO as the more efficient or cost
effective regulated transmission solution to satisfy a Reliability Need, or (3) seeking cost
recovery where it has been halted or cancelled pursuant to the provisions of Section 31.2.8.2. A
regulated economic transmission solution proposed in response to congestion identified in the
CARIS, and approved pursuant to Section 31.5.4.6, shall only be eligible to utilize the cost
allocation principles and methodologies set forth in Section 31.5.4.
31.5.5.2
Cost Allocation Principles
The ISO shall implement the specific cost allocation methodology in Section 31.5.5.4 of
this Attachment Y in accordance with the Order No. 1000 Regional Cost Allocation Principles as
set forth in Section 31.5.2.1. The specific cost allocation methodology in Section 31.5.5.4
incorporates the following elements:
31.5.5.2.1
The focus of the cost allocation methodology shall be on regulated Public
Policy Transmission Projects.
31.5.5.2.2
Projects analyzed hereunder as Public Policy Transmission Projects may
proceed on a market basis with willing buyers and sellers at any time.
31.5.5.2.3
Cost allocation shall be based on a beneficiaries pay approach.
31.5.5.2.4
Project benefits will be identified in accordance with Section 31.5.5.4.
31.5.5.2.5
Identification of beneficiaries for cost allocation and cost allocation
among those beneficiaries shall be according to the methodology specified in
Section 31.5.5.4.
31.5.5.3 Project Eligibility for Cost Allocation
The Developer of a Public Policy Transmission Project will be eligible for cost allocation
in accordance with the process set forth in Section 31.5.5.4 when its project is selected by the
ISO as the more efficient or cost effective regulated Public Policy Transmission Project;
provided, however, that if the appropriate federal, state, or local agency(ies) rejects the selected
project’s necessary authorizations, or such authorizations are withdrawn, the costs the Developer
is eligible to recover under Section 31.4.12.1 shall be allocated in accordance with Section
31.5.5.4.3, except as otherwise determined by the Commission. The Developer of the selected
regulated transmission solution may recover its costs in accordance with Section 31.5.6 and Rate
Schedule 10 of the ISO OATT. If the Developer proposed its Public Policy Transmission Project
in response to a request by the NYPSC or Long Island Power Authority pursuant to Section
31.4.3.2 and its project was not selected by the ISO, the costs that the Developer is eligible to
recover pursuant to Section 31.4.3.2 shall be allocated in accordance with Section 31.5.5.4.3,
except as otherwise determined by the Commission. The Developer may recover these costs in
accordance with Section 31.5.6 and Rate Schedule 10 of the ISO OATT.
31.5.5.4 Cost Allocation for Eligible Projects
As noted in Section 31.5.5.2 of this Attachment Y, the identification of beneficiaries for
cost allocation and the cost allocation of a selected Public Policy Transmission Project will be
conducted in accordance with the process described in this Section 31.5.5.4. This Section will
also apply to the allocation within New York of the ISO’s share of the costs of an Interregional
Transmission Project proposed as a solution to a Public Policy Transmission Need allocated in
accordance with Section 31.5.7 of this Attachment Y. The establishment of a cost allocation
methodology and rates for a proposed solution that is undertaken by LIPA or NYPA as an
Unregulated Transmitting Utility to a Public Policy Transmission Need as determined in
Sections 31.4.2.1 through 31.4.2.3, as applicable, or an Interregional Transmission Project shall
occur pursuant to Section 31.5.5.4.4 through 31.5.5.4.6, as applicable. Nothing herein shall
deprive a Transmission Owner or Other Developer of any rights it may have under Section 205
of the Federal Power Act to submit filings proposing any other cost allocation methodology to
the Commission or create any Section 205 filing rights for any Transmission Owner, Other
Developer, the ISO, or any other entity. The ISO shall apply the cost allocation methodology
accepted by the Commission. The cost allocation methodology that is accepted or approved by
the Commission for a particular Public Policy Transmission Project in accordance with this
Section 31.5.5.4 will be set forth in Appendix E (Section 31.8) of this Attachment Y.
31.5.5.4.1
If the Public Policy Requirement that results in the identification by the
NYPSC of a Public Policy Transmission Need prescribes the use of a particular
cost allocation and recovery methodology, then the ISO shall file that
methodology with the Commission within 60 days of the issuance by the NYPSC
of its identification of a Public Policy Transmission Need. Nothing herein shall
deprive a Transmission Owner or Other Developer of any rights it may have
under Section 205 of the Federal Power Act to submit filings proposing any other
cost allocation methodology to the Commission or create any Section 205 filing
rights for any Transmission Owner, Other Developer, the ISO, or any other entity.
If the Developer files a different proposed cost allocation methodology under
Section 205 of the Federal Power Act, it shall have the burden of demonstrating
that its proposed methodology is compliant with the Order No. 1000 Regional
Cost Allocation Principles taking into account the methodology specified in the
Public Policy Requirement.
31.5.5.4.2
Subject to the provisions of Section 31.5.5.4.1, the Developer may submit
to the NYPSC for its consideration - no later than 30 days after the ISO’s
selection of the regulated Public Policy Transmission Project - a proposed cost
allocation methodology, which may include a cost allocation based on load ratio
share, adjusted to reflect, as applicable, the Public Policy Requirement or Public
Policy Transmission Need, the party(ies) responsible for complying with the
Public Policy Requirement, and the party(ies) who benefit from the transmission
facility.
31.5.5.4.2.1 The NYPSC shall have 150 days to review the Developer’s proposed cost
allocation methodology and to inform the Developer regarding whether it
supports the methodology.
31.5.5.4.2.2. If the NYPSC supports the proposed cost allocation methodology, the
Developer shall file that cost allocation methodology with the Commission for its
acceptance under Section 205 of the Federal Power Act within 30 days of the
NYPSC informing the Developer of its support. The Developer shall have the
burden of demonstrating that the proposed cost allocation methodology is
compliant with the Order No. 1000 Regional Cost Allocation Principles.
31.5.5.4.2.3 If the NYPSC does not support the proposed cost allocation methodology,
then the Developer shall take reasonable steps to respond to the NYPSC’s
concerns and to develop a mutually agreeable cost allocation methodology over a
period of no more than 60 days after the NYPSC informing the Developer that it
does not support the methodology.
31.5.5.4.2.4 If a mutually acceptable cost allocation methodology is developed during
the timeframe set forth in Section 31.5.5.4.2.3, the Developer shall file it with the
Commission for acceptance under Section 205 of the Federal Power Act no later
than 30 days after the conclusion of the 60 day discussion period with the
NYPSC. The Developer shall have the burden of demonstrating that the proposed
cost allocation methodology is compliant with the Order No. 1000 Regional Cost
Allocation Principles.
31.5.5.4.2.5 If no mutually agreeable cost allocation methodology is developed, the
Developer shall file its preferred cost allocation methodology with the
Commission for acceptance under Section 205 of the Federal Power Act no later
than 30 days after the conclusion of the 60 day discussion period with the
NYPSC. The Developer shall have the burden of demonstrating that its proposed
methodology is compliant with the Order No. 1000 Regional Cost Allocation
Principles in consideration of the position of the NYPSC. The filing shall include
the methodology supported by NYPSC for the Commission’s consideration. If the
Developer elects to use the load ratio share cost allocation methodology
referenced below in Section 31.5.5.4.3, the Developer shall notify the
Commission of its intent to utilize the load ratio share methodology and shall
include in its notice the NYPSC supported methodology for the Commission’s
consideration.
31.5.5.4.3.
Unless the Commission has accepted an alternative cost allocation
methodology pursuant to this Section, the ISO shall allocate the costs of the
Public Policy Transmission Project to all Load Serving Entities in the NYCA
using the default cost allocation methodology, based upon a load ratio share
methodology.
31.5.5.4.4
The NYISO will make any Section 205 filings related to this Section on
behalf of NYPA to the extent requested to do so by NYPA. NYPA shall bear the
burden of demonstrating that such a filing is compliant with the Order No. 1000
Regional Cost Allocation Principles. NYPA shall also be solely responsible for
making any jurisdictional reservations or arguments related to their status as non-
Commission-jurisdictional utilities that are not subject to various provisions of the
Federal Power Act.
31.5.5.4.5
The cost allocation methodology and any rates for cost recovery for a
proposed solution to a Public Policy Transmission Need undertaken by LIPA, as
an Unregulated Transmitting Utility (for purposes of this section a “LIPA
project”), shall be established and recovered as follows:
31.5.5.4.5.1 For costs solely to LIPA customers. The cost allocation methodology and
rates to be established for a LIPA project, for which cost recovery will only occur
from LIPA customers, will be established pursuant to Article 5, Title 1-A of the
New York Public Authorities Law, Sections 1020-f(u) and 1020-s. Prior to the
adoption of any cost allocation mechanism or rates for such a LIPA project, and
pursuant to Section 1020-f(u), the Long Island Power Authority’s Board of
Trustees shall request that the NYDPS provide a recommendation with respect to
the cost allocation methodology and rate that LIPA has proposed and the Board of
Trustees shall consider such recommendation in accordance with the requirements
of Section 1020-f(u). Upon approval of the cost allocation mechanism and/or
rates by the Long Island Power Authority’s Board of Trustees, LIPA shall provide
to the ISO, for purposes of inclusion within the ISO OATT and filing with FERC
on an informational basis only, a description of the cost allocation mechanism and
the rate that LIPA will charge and collect within the Long Island Transmission
District.
31.5.5.4.5.2 For Costs for a LIPA Project That May be Allocated to Other
Transmission Districts. A LIPA project that meets a Public Policy Transmission
Need as determined by the NYPSC pursuant to Section 31.4.2.3(iii) may be
allocated to market participants outside of the Long Island Transmission District.
The cost allocation methodology and rate for such a LIPA project shall be
established in accordance with the following procedures. LIPA’s proposed cost
allocation methodology and/or rate shall be reviewed and approved by the Long
Island Power Authority’s Board of Trustees pursuant to Article 5, Title 1-A of the
New York Public Authorities Law, Sections 1020-f(u) and 1020-s. Prior to the
adoption of any cost allocation mechanism or rates for such project and pursuant
to Section 1020-f(u), the Long Island Power Authority’s Board of Trustees shall
request that the NYDPS provide a recommendation with respect to the cost
allocation methodology and rate that LIPA has proposed and the Board of
Trustees shall consider such recommendation in accordance with the requirements
of Section 1020-f(u). LIPA shall inform the ISO of the cost allocation
methodology and rate that has been approved by the Long Island Power
Authority’s Board of Trustees for filing with the Commission.
Upon approval by the Long Island Power Authority’s Board of Trustees,
LIPA shall submit and request that the ISO file the LIPA cost allocation
methodology for approval with the Commission. Any cost allocation
methodology for a LIPA project that allocates costs to market participants outside
of the Long Island Transmission District shall be reviewed as to whether there is
comparability in the derivation of the cost allocation for market participants such
that LIPA has demonstrated that the proposed cost allocation is compliant with
the Order No. 1000 cost allocation principles, there are benefits provided by the
project to market participants outside of the Long Island Transmission District,
and that the proposed allocation is roughly commensurate to the identified
benefits.
Article 5, Title 1-A of the New York Public Authorities Law, Sections
1020-f(u) and 1020-s, requires that LIPA’s rates be established at the lowest level
consistent with sound fiscal and operating practices of the Long Island Power
Authority and which provide for safe and adequate service. Upon approval of a
LIPA rate by the Long Island Power Authority’s Board of Trustees pursuant to
Section 1020-f(u), LIPA shall submit, and request that the ISO file, the LIPA rate
with the Commission for review under the same comparability standard as applied
to the review of changes in LIPA’s TSC under Attachment H of this tariff.
In the event that the cost allocation methodology or rate approved by the
Long Island Power Authority’s Board of Trustees did not adopt the NYDPS
recommendation, the NYDPS recommendation shall be included in the filing for
the Commission’s consideration.
31.5.5.4.5.3 Support for Filing. LIPA shall intervene in support of the filing(s) made
pursuant to Section 31.5.5.4.5 at the Commission and shall take the responsibility
to demonstrate that: (i) the cost allocation methodology and/or rate approved by
the Long Island Power Authority’s Board of Trustees meets the applicable
standard of comparability, and (ii) the Commission should accept such
methodology or rate for filing. LIPA shall also be responsible for responding to,
and seeking to resolve, concerns about the contents of the filing that might be
raised in such proceeding.
31.5.5.4.5.4 Billing of LIPA Charges Outside of the Long Island Transmission District.
For Transmission Districts other than the Long Island Transmission District, the
ISO shall bill for LIPA, as a separate charge, the costs incurred by LIPA for a
solution to a Public Policy Transmission Need allocated using the cost allocation
methodology and rates established pursuant to Section 31.5.5.4.5.2 and accepted
for filing by the Commission and shall remit the revenues collected to LIPA each
Billing Period in accordance with the ISO’s billing and settlement procedures.
31.5.5.4.6
The inclusion in the ISO OATT or in a filing with the Commission of the
cost allocation and charges for recovery of costs incurred by NYPA or LIPA
related to a solution to a transmission need driven by a Public Policy Requirement
or Interregional Transmission Project as provided for in Sections 31.5.5.4.4 and
31.5.5.4.5 shall not be deemed to modify the treatment of such rates as non-
jurisdictional pursuant to Section 201(f) of the FPA.
31.5.6
Cost Recovery for Regulated Projects
31.5.6.1
Cost Recovery for Regulated Transmission Project to Address a
Reliability Need
31.5.6.1.1
A Responsible Transmission Owners, a Transmission Owner,s orand an
Other Developers may recover in accordance with Rate Schedule 10 of the ISO
OATT the costs incurred with respect to the implementation of: (i) a regulated
backstop transmission solution proposed by a Responsible Transmission Owner
pursuant to Section 31.2.4.3.1 of this Attachment Y and the ISO/TO Reliability
Agreement or an Operating Agreement; (ii) an alternative regulated transmission
solution that the ISO has selected pursuant to Section 31.2.6.5.2 of this
Attachment Y as the more efficient or cost-effective solution to a Reliability
Need; (iii) a regulated transmission Gap Solution proposed by a Responsible
Transmission Owner pursuant to Section 31.2.11.4 of this Attachment Y; or (iv)
an alternative regulated transmission Gap Solution that has been determined by
the appropriate state regulatory agency(ies) as the preferred solution(s) to a
Reliability Need pursuant to Section 31.2.11.5 of Attachment Y of the ISO
OATT. will be entitled, if eligible for cost recovery under Section 31.2 of this
Attachment Y, to full recovery of all reasonably incurred costs, including a
reasonable return on investment and any applicable incentives, related to the
development, construction, operation and maintenance of regulated solutions,
including Gap Solutions, proposed or undertaken pursuant to the provisions of
this Attachment Y to meet a Reliability Need. Transmission Owners and Other
Developers will be entitled to recovery of costs associated with the
implementation of a regulated economic transmission project (“RETP”) in
accordance with the provisions of Section 31.5.6 of this Attachment Y.
Developers will be entitled to recover the costs, to the extent permitted under
Sections 31.4 and 31.5.6.5 of this Attachment Y, associated with the
implementation of a regulated Public Policy Transmission Project in accordance
with the requirements in Section 31.5.6.5 of this Attachment Y.
31.5.6.1.2
The Responsible Transmission Owner, Transmission Owner or Other
Developer will receive cost recovery for If a regulated solution: (i) is eligible for
cost recovery as described in Section 31.5.6.1.1 and (ii) isit undertakes to meet a
Reliability Need pursuant to Section 31.2 of this Attachment Y that is not
triggered or is halted pursuant to Sections 31.2.8 or 31.2.10.1.2 of this Attachment
Ysubsequently halted in accordance with the criteria established pursuant to
Section 31.2.8.2 of this Attachment Y, the Responsible Transmission Owner,
Transmission Owner or Other Developer of that solution may recover the costs
that it eligible to recover pursuant to Sections 31.2.8 or 31.2.10.1.2 in accordance
with Rate Schedule 10 of the ISO OATT. Such costs will include reasonably
incurred costs through the time of cancellation, including any forward
commitments made.
31.5.6.2
The Responsible Transmission Owner, Transmission Owner or Other
Developer will recover its costs described in this Section 31.5 incurred with
respect to the implementation of a regulated transmission solution to Reliability
Needs, in accordance with the provisions of Rate Schedule 10 of this ISO OATT,
or as determined by the Commission. Provided further that cost recovery for
regulated transmission projects undertaken by a Transmission Owner pursuant to
this Attachment Y shall be in accordance with the provisions of the NYISO/TO
Reliability Agreement or an Operating Agreement.
31.5.6.1.3
Costs related to non-transmission regulated solutions to Reliability Needs
will be recovered by a Responsible Transmission Owners, Transmission Owners,
or and Other Developers in accordance with the provisions of New York Public
Service Law, New York Public Authorities Law, or other applicable state law. A
Responsible Transmission Owner, a Transmission Owner, or Other Developer
may propose and undertake a regulated non-transmission solution, provided that
the appropriate state agency(ies) has established cost recovery procedures
comparable to those provided in this tariff for regulated transmission solutions to
ensure the full and prompt recovery of all reasonably-incurred costs related to
such non-transmission solutions. Nothing in this section shall affect the
Commission’s jurisdiction over the sale and transmission of electric energy
subject to the jurisdiction of the Commission.
31.5.6.24
Cost Recovery for Regulated Economic Transmission Project
A Transmission Owner or an Other Developer may recover in accordance
with Rate Schedule 10 of the ISO OATT the costs incurred with respect to the
implementation For a regulated economic transmission project that has been is
approved pursuant to Section 31.5.4.6 of this Attachment Y., the Transmission
Owner or Other Developer shall have the right to make a filing with the
Commission, under Section 205 of the Federal Power Act, for approval of its
costs associated with implementation of the project. The filing of the
Transmission Owner or Other Developer must be consistent with its project
proposal made to and evaluated by the ISO under Section 31.5.4 of this
Attachment Y. Costs will be recovered when the project is completed pursuant to
a rate schedule filed with and accepted by the Commission in accordance with the
cost recovery requirements set forth in this Section, or as otherwise determined by
the Commission. Upon request by NYPA, the ISO will make a filing on behalf of
NYPA.
31.5.6.35
Cost Recovery for Regulated Transmission Project to Address a Public
Policy Transmission Need
For a regulated Public Policy Transmission Project, the Developer shall have the right to
make a filing with the Commission under Section 205 of the Federal Power Act,
for approval of its costs eligible for recovery under Section 31.4 and this Section
31.5.6.5.
31.5.6.35.1
A Transmission Owner or an Other Developer may recover in accordance
with Rate Schedule 10 of the ISO OATT the costs incurred with respect to the
implementation of: (i) The Developer of a Public Policy Transmission Project that
the ISO has selected by the ISO as the more efficient or cost-effective solution to
a Public Policy Transmission NeedProject, or will be entitled to full recovery of
all reasonably incurred costs, including a reasonable return on investment and any
applicable incentives, related to the development, construction, operation, and
maintenance of the selected Public Policy Transmission Project. (ii) a Public
Policy Transmission Project proposed by a Developer in response to a request by
the NYPSC or Long Island Power Authority in accordance with Section 31.4.3.2
of Attachment Y of the ISO OATT. Such cost recovery will also include
reasonable costs incurred by the Developer to provide a more detailed study or
cost estimate for such project at the request of the NYPSC, and to prepare the
application required to comply with New York Public Service Law Article VII, or
any successor statute or any other applicable permits, and to seek other necessary
authorizations. The filing of the Developer must be consistent with its project
proposal submitted to, evaluated by and selected by the ISO under Section 31.4 of
this Attachment Y. The period for cost recovery, if any cost recovery is approved,
will be determined by the Commission and will begin if and when the project is
completed, or as otherwise determined by the Commission.
31.5.6.35.2
If a regulated solution that: (i) is eligible for cost recovery as described in
Section 31.5.6.3.1 and (ii) is halted If the appropriate federal, state or local
agency(ies) either rejects a necessary authorization, or approves and later
withdraws authorizationas described in Section 31.4.12.1 of this Attachment Y,
for the selected Public Policy Transmission Project, the Transmission Owner or
Other Developer of that solution may recover the costs that it is eligible to recover
pursuant to Section 31.4.12.1 in accordance with Rate Schedule 10 of the ISO
OATT.all of the necessary and reasonable costs incurred and commitments made
up to the final federal, state or local regulatory decision, including reasonable and
necessary expenses incurred to implement an orderly termination of the project, to
the extent permitted by the Commission in accordance with its regulations on
abandoned plant recovery. The period for cost recovery will be determined by the
Commission and will begin as determined by the Commission.
31.5.6.5.3
Upon request by NYPA, the ISO will make a filing on behalf of NYPA
under this Section 31.5.6.5.
31.5.6.6
To the extent that Incremental TCCs are created as a result of a regulated
economic transmission project that has been approved for cost recovery under the
NYISO Tariff, those Incremental TCCs that can be sold will be auctioned or
otherwise sold by the ISO. The ISO shall determine the amount of Incremental
TCCs that may be awarded to an expansion in accordance with the provisions of
Section 19.2.2 of Attachment M of the ISO OATT. The ISO will use these
revenues to offset the revenue requirements for the project. The Incremental
TCCs shall continue to be sold for the depreciable life of the project, and the
revenues offset will commence upon the first payment of revenues related to a
sale of Incremental TCCs on or after the charge for a specific RETP is
implemented.
31.5.6.4
Cost Recovery for Interregional Transmission Project
A Responsible Transmission Owner, a Transmission Owner, or an Other
Developer may recover in accordance with Rate Schedule 10 of the ISO OATT
the costs incurred with respect to the implementation of the portion of an
Interregional Transmission Project selected by the ISO in the CSPP that is
allocated to the NYISO region pursuant to Section 31.5.7 of Attachment Y of the
ISO OATT.
31.5.7
Cost Allocation for Eligible Interregional Transmission Projects
31.5.7.1 Costs of Approved Interregional Transmission Projects
The cost allocation methodology reflected in this Section 31.5.7.1 shall be referred to as
the “Northeastern Interregional Cost Allocation Methodology” (or “NICAM”), and shall not be
modified without the mutual consent of the Section 205 rights holders in each region.
The costs of Interregional Transmission Projects, as defined in the Interregional Planning
Protocol, evaluated under the Interregional Planning Protocol and selected by ISO-NE, PJM and
the ISO in their regional transmission plans for purposes of cost allocation under their respective
tariffs shall, when applicable, be allocated to the ISO-NE region, PJM region and the ISO region
in accordance with the cost allocation principles of FERC Order No. 1000, as follows:
(a)
To be eligible for interregional cost allocation, an Interregional Transmission
Project must be selected in the regional transmission plan for purposes of cost allocation in each
of the transmission planning regions in which the transmission project is proposed to be located,
pursuant to agreements and tariffs on file at FERC for each region. With respect to Interregional
Transmission Projects and other transmission projects involving the ISO and PJM, the cost
allocation of such projects shall be in accordance with the Joint Operating Agreement (“JOA”)
among and between the ISO and PJM. With respect to Interregional Transmission Projects and
other transmission projects involving the ISO and ISO-NE, the cost allocation for such projects
shall be in accordance with this Section 31.5.7 of Attachment Y of the NYISO Open Access
Transmission Tariff and with the respective tariffs of ISO-NE.
(b)
The share of the costs of an Interregional Transmission Project allocated to a
region will be determined by the ratio of the present value of the estimated costs of such region’s
displaced regional transmission project to the total of the present values of the estimated costs of
the displaced regional transmission projects in all regions that have selected the Interregional
Transmission Project in their regional transmission plans.
(i)
The present values of the estimated costs of each region’s displaced regional
transmission project shall be based on a common base date that will be the
beginning of the calendar month of the cost allocation analysis for the subject
Interregional Transmission Project (the “Base Date”).
(ii)
In order to perform the analysis in this Section 31.5.7.1(b), the estimated cost of
the displaced regional transmission projects shall specify the year’s dollars in
which those estimates are provided.
(iii)
The present value analysis for all displaced regional transmission projects shall
use a common discount rate. The regions having displaced projects will mutually
agree, in consultation with their respective transmission owners, and for purposes
of the ISO, its other stakeholders, on the discount rate to be used for the present
value analysis.
(iv)
For the purpose of this allocation, cost estimates shall use comparable cost
estimating procedures. In the Interregional Planning Stakeholder Advisory
Committee review process, the regions having displaced projects will review and
determine, in consultation with their respective transmission owners, and for
purposes of the NYISO, its other stakeholders, that reasonably comparable
estimating procedures have been used prior to applying this cost allocation.
(c)
No cost shall be allocated to a region that has not selected the Interregional
Transmission Project in its regional transmission plan.
(d)
When a portion of an Interregional Transmission Project evaluated under the
Interregional Planning Protocol is included by a region (Region 1) in its regional transmission
plan but there is no regional need or displaced regional transmission project in Region 1, and the
neighboring region (Region 2) has a regional need or displaced regional project for the
Interregional Transmission Project and selects the Interregional Transmission Project in its
regional transmission plan, all of the costs of the Interregional Transmission Project shall be
allocated to Region 2 in accordance with the NICAM and none of the costs shall be allocated to
Region 1. However, Region 1 may voluntarily agree, with the mutual consent of the Section 205
rights holders in the other affected region(s) (including the Long Island Power Authority and the
New York Power Authority in the NYISO region) to use an alternative cost allocation method
filed with and accepted by the Commission.
(e)
The portion of the costs allocated to a region pursuant to the NICAM shall be
further allocated to that region’s transmission customers pursuant to the applicable provisions of
the region’s FERC-filed documents and agreements, for the ISO in accordance with Section
31.5.1.7 of Attachment Y of the ISO OATT.
(f)
The following example illustrates the cost allocation for such an Interregional
Transmission Project:
A cost allocation analysis of the costs of Interregional Transmission Project Z is to be
performed during a given month establishing the beginning of that month as the Base
Date.
Region A has identified a reliability need in its region and has selected a transmission
project (Project X) as the preferred solution in its regional plan. The estimated cost of
Project X is: Cost (X), provided in a given year’s dollars. The number of years from
the Base Date to the year associated with the cost estimate of Project (X) is: N(X).
Region B has identified a reliability need in its region and has selected a transmission
project (Project Y) as the preferred solution in its Regional Plan. The estimated cost
of Project Y is: Cost (Y), provided in a given year’s dollars. The number of years
from the Base Date to the year associated with the cost estimate of Project (Y) is:
N(Y).
Regions A and B, through the interregional planning process have determined that an
Interregional Transmission Project (Project Z) will address the reliability needs in
both regions more efficiently and cost-effectively than the separate regional projects.
The estimated cost of Project Z is: Cost (Z). Regions A and B have each determined
that Interregional Transmission Project Z is the preferred solution to their reliability
needs and have adopted that Interregional Transmission Project in their respective
regional plans in lieu of Projects X and Y respectively. If Regions A and B have
agreed to bear the costs of upgrades in other affected transmission planning regions,
these costs will be considered part of Cost (Z).
The discount rate used for all displaced regional transmission projects is: D
Based on the foregoing assumptions, the following formulas will be used:
Present Value of Cost (X) = PV Cost (X) = Cost (X) / (1+D)N(X)
Present Value of Cost (Y) = PV Cost (Y) = Cost (Y) / (1+D)N(Y)
Cost Allocation to Region A = Cost (Z) x PV Cost (X)/[PV Cost (X) + PV
Cost (Y)]
Cost Allocation to Region B = Cost (Z) x PV Cost (Y)/[PV Cost (X) + PV
Cost (Y)]
Applying those formulas, if:
Cost (X) = $60 Million and N(X) = 8.25 years
Cost (Y) = $40 Million and N(Y) = 4.50 years
Cost (Z) = $80 Million
D = 7.5% per year
Then:
PV Cost (X) = 60/(1+0.075) 8.25 = 33.039 Million
PV Cost (Y) = 40/(1+0.075)4.50
= 28.888 Million
Cost Allocation to Region A = $80 x 33.039/(33.039 + 28.888) = $42,681 Million
Cost Allocation to Region B = $80 x 28.888/(33.039+28.888) = $37.319 Million
31.5.7.2 Other Cost Allocation Arrangements
(a)
Except as provided in Section 31.5.7.2(b), the NICAM is the exclusive means by
which any costs of an Interregional Transmission Project may be allocated between or among
PJM, the ISO, and ISO-NE.
(b)
Nothing in the FERC-filed documents of ISO-NE, the ISO or PJM shall preclude
agreement by entities with cost allocation rights under Section 205 of the Federal Power Act for
their respective regions (including the Long Island Power Authority and the New York Power
Authority in the ISO region) to enter into separate agreements to allocate the cost-of
Interregional Transmission Projects proposed to be located in their regions as an alternative to
the NICAM, or other transmission projects identified pursuant to assessments and studies
conducted pursuant to Section 6 of the Interregional Planning Protocol. Such other cost-
allocation methodologies must be approved in each region pursuant to the Commission-approved
rules in each region, filed with and accepted by the Commission, and shall apply only to the
region's share of the costs of an Interregional Transmission Project or other transmission projects
pursuant to Section 6 of the Interregional Planning Protocol, as applicable.
31.5.7.3 Filing Rights
Nothing in this Section 31.5.7 will convey, expand, limit or otherwise alter any rights of
ISO-NE, the ISO, PJM, each region’s transmission owners, market participants, or other entities
to submit filings under Section 205 of the Federal Power Act regarding interregional cost
allocation or any other matter.
Where applicable, the regions have been authorized by entities that have cost allocation
rights for their respective regions to implement the provisions of this Section 31.5.7.
31.5.7.4. Merchant Transmission and Individual Transmission Owner Projects
Nothing in this Section 31.5.7 shall preclude the development of Interregional
Transmission Projects that are funded solely by merchant transmission developers or by
individual transmission owners.
31.5.7.5 Consequences to Other Regions from Regional or Interregional
Transmission Projects
Except as provided herein in Sections 31.5.7.1 and 31.5.7.2, or where cost responsibility
is expressly assumed by ISO-NE, the ISO or PJM in other documents, agreements or tariffs on
file with FERC, neither the ISO-NE region, the ISO region nor the PJM region shall be
responsible for compensating another region or each other for required upgrades or for any other
consequences in another planning region associated with regional or interregional transmission
facilities, including but not limited to, transmission projects identified pursuant to Section 6 of
the Interregional Planning Protocol and Interregional Transmission Projects identified pursuant
to Section 7 of the Interregional Planning Protocol.
APPENDIX A - REPORTING OF HISTORIC AND PROJECTED CONGESTION
1.0
General
As part of its CSPP, the ISO will prepare summaries and detailed analysis of historic and
projected congestion across the NYS Transmission System. This will include analysis to identify
the significant causes of historic congestion in an effort to help Market Participants and other
interested parties distinguish persistent and addressable congestion from congestion that results
from one time events or transient adjustments in operating procedures that may or may not recur.
This information will assist Market Participants and other stakeholders to make appropriately
informed decisions.
2.0
Definition of Cost of Congestion
The ISO will report the cost of congestion as the change in bid production costs that
results from transmission congestion. The following elements of congestion-related costs also
will be reported: (i) impact on load payments; (ii) impact on generator payments; and
(iii) hedged and unhedged congestion payments.
The determination of the change in bid production costs and the other elements of
congestion will be based upon the difference in costs between the actual constrained system
prices computed in the ISO’s Day-Ahead Market and a simulation of an unconstrained system.
The simulation shall be developed by the use of the PROBE model approved by the ISO
Operating Committee on January 22, 2004 or by such other software as may provide the required
congestion information.
3.0
Analysis
Each RNA will include the ISO’s summaries and detailed analysis of the prior year’s
congestion across the NYS Transmission System. The ISO’s analysis will identify the
significant causes of the historic congestion.
Each study of projected congestion for economic planning will include the results of the
ISO’s analysis conducted in accordance with Section 31.3.1 of this Attachment Y. The ISO’s
analysis will identify the significant causes of the projected congestion.
4.0
Detailed Cause Analysis for Unusual Events
The ISO will perform an analysis to identify unusual events causing significant
congestion levels. Such analysis will include the following elements: (i) identification of major
transmission or generation outages; and (ii) quantification of the market impact of relieving
historic constraints.
Some of the information necessary to this analysis may constitute critical energy
infrastructure information and will need to be handled with appropriate confidentiality
limitations to protect national security interests.
5.0
Summary Reports
The ISO will prepare various reports of historic and projected congestion costs. Historic
congestion reports will be based upon the actual congestion data from the ISO Day-Ahead
Market, and will include summaries, aggregated by month and calendar year, such as: (i) NYCA;
(ii) by zone; (iii) by contingency in rank order; (iv) by constraint in rank order; (v) total dollars;
and (vi) number of hours. Results of projected congestion studies conducted pursuant to Section
31.3.1 of this Attachment Y will include summaries of selected additional metrics and scenarios.
These reports will be based upon the foregoing definitions of congestion.
APPENDIX B - PROCEDURE FOR FORECASTING THE NET REDUCTIONS IN
TCC REVENUES THAT WOULD RESULT FROM A PROPOSED
PROJECT
For the purpose of determining the allocation of costs associated with a proposed project as
described in Section 31.5.4.4 of this Attachment Y, the ISO shall use the procedure described herein
to forecast the net reductions in TCC revenues allocated to Load in each Load Zone as a result of a
proposed project.
Definitions
The following definitions will apply to this appendix:
Pre-CARIS Centralized TCC Auction: The last Centralized TCC Auction that had been completed
as of the date the input assumptions were determined for the CARIS in which the Project was
identified as a candidate for development under the provisions of this Attachment Y.
Project: The proposed transmission project for which the evaluation of the net benefits forecasted
for Load in each Load Zone, as described in Section 31.5.4.4.2 of this Attachment Y, is being
performed.
TCC Revenue Factor: A factor that is intended to reflect the expected ratio of (1) revenue realized in
the TCC auction from the sale of a TCC to (2) the Congestion Rents that a purchaser of that TCC
would expect to realize. The value to be used for the TCC Revenue Factor shall be stated in the ISO
Procedures.
Steps 1 Through 6 of the Procedure
For each Project, the ISO will perform Steps 1 through 6 of this procedure twice for each of the ten
(10) years following the proposed commercial operation date of the Project: once under the
assumption that the Project is in place in each of those years, and once under the assumption that the
Project is not in place in each of those years.
Forecasting the Value of Grandfathered TCCs and TCC Auction Revenue
Step 1. The ISO shall forecast Congestion Rents collected on the New York electricity system in
each year, which shall be equal to:
(a) the product of:
(i) the forecasted Congestion Component of the Day-Ahead LBMP for each hour at
each Load Zone or Proxy Generator Bus and
(ii) forecasted withdrawals scheduled in that hour in that Load Zone or Proxy
Generator Bus,
summed over all locations and over all hours in that year, minus:
(b) the product of:
(i) the forecasted Congestion Component of the Day-Ahead LBMP for each hour at
each Generator bus or Proxy Generator Bus and
(ii) forecasted injections scheduled in that hour at that Generator bus or Proxy
Generator Bus,
summed over all locations and over all hours in that year.
Step 2. The ISO shall forecast:
(a) payments in each year associated with any Incremental TCCs that the ISO projects would
be awarded in conjunction with that Project (which will be zero for the calculation that is
performed under the assumption that the Project is not in place);
(b) payments in each year associated with any Incremental TCCs that the ISO has awarded,
or that the ISO projects it would award, in conjunction with other projects that have entered
commercial operation or are expected to enter commercial operation before the Project enters
commercial operation; and
(c) payments that would be made to holders of Grandfathered Rights and imputed payments
that would be made to the Primary Holders of Grandfathered TCCs that would be in effect in
each year, under the following assumptions:
(i) all Grandfathered Rights and Grandfathered TCCs expire at their stated expiration
dates;
(ii) imputed payments to holders of Grandfathered Rights are equal to the payments
that would be made to the Primary Holder of a TCC with the same Point of Injection
and Point of Withdrawal as that Grandfathered Right; and
(iii) in cases where a Grandfathered TCC is listed in Table 1 of Attachment M of the
ISO OATT, the number of those TCCs held by their Primary Holders shall be set to
the number of such TCCs remaining at the conclusion of the ETCNL reduction
procedure conducted before the Pre-CARIS Centralized TCC Auction.
Step 3. The ISO shall forecast TCC auction revenues for each year by subtracting:
(a) the forecasted payments calculated for that year in Steps 2(a), 2(b) and 2(c) of this
procedure
from:
(b) the forecasted Congestion Rents calculated for that year in Step 1 of this procedure, and
multiplying the difference by the TCC Revenue Factor.
Forecasting the Allocation of TCC Auction Revenues Among the Transmission Owners
Step 4. The ISO shall forecast the following:
(a) payments in each year to the Primary Holders of Original Residual TCCs and
(b) payments in each year to the Primary Holders of TCCs that correspond to the amount of
ETCNL remaining at the conclusion of the ETCNL reduction procedure conducted before the
Pre-CARIS Centralized TCC Auction,
and multiply each by the TCC Revenue Factor to determine the forecasted payments to the Primary
Holders of Original Residual TCCs and the Transmission Owners that have been allocated ETCNL.
Step 5. The ISO shall forecast residual auction revenues for each year by subtracting:
(a) the sum of the forecasted payments for each year to the Primary Holders of Original
Residual TCCs and the Transmission Owners that have been allocated ETCNL, calculated in
Step 4 of this procedure
from:
(b) forecasted TCC auction revenues for that year calculated in Step 3 of this procedure.
Step 6. The ISO shall forecast each Transmission Owner’s share of residual auction revenue for
each year by multiplying:
(a) the forecast of residual auction revenue calculated in Step 5 of this procedure and
(b) the ratio of:
(i) the amount of residual auction revenue allocated to that Transmission Owner in
the Pre-CARIS Centralized TCC Auction to
(ii) the total amount of residual auction revenue allocated in the Pre-CARIS
Centralized TCC Auction.
Steps 7 Through 10 of the Procedure
The ISO will perform Steps 7 through 10 of this procedure once for each of the ten (10) years
following the proposed commercial operation date of the Project, using the results of the preceding
calculations performed both under the assumption that the Project is in place in each of those years,
and under the assumption that the Project is not in place in each of those years.
Forecasting the Impact of the Project on TSC Offsets and the NTAC Offset
Step 7. The ISO shall calculate the forecasted net impact of the Project on the TSC offset for each
megawatt-hour of electricity consumed by Load in each Transmission District (other than the NYPA
Transmission District) in each year by:
(a) summing the following, each forecasted for that Transmission District for that year under
the assumption that the Project is in place:
(i) forecasted Congestion Rents associated with any Incremental TCCs that the ISO
has awarded, or that the ISO projects it would award, as calculated in Step 2(b) of this
procedure, in conjunction with other projects that have entered commercial operation
or are expected to enter commercial operation before the Project enters commercial
operation, if those Congestion Rents would affect the TSC for that Transmission
District;
(ii) forecasted Congestion Rents associated with any Grandfathered TCCs and
forecasted imputed Congestion Rents associated with any Grandfathered Rights held
by the Transmission Owner serving that Transmission District that would be paid to
that Transmission Owner for that year, as calculated in Step 2(c) of this procedure, if
those Congestion Rents would affect the TSC for that Transmission District;
(iii) the payments that are forecasted to be made for that year to the Primary Holders
of Original Residual TCCs and ETCNL that have been allocated to the Transmission
Owner serving that Transmission District, as calculated in Step 4 of this procedure;
and
(iv) that Transmission District’s forecasted share of residual auction revenues for that
year, as calculated in Step 6 of this procedure for the Transmission Owner serving
that Transmission District;
(b) subtracting the sum of items (i) through (iv) above, each forecasted for that Transmission
District for that year under the assumption that the Project is not in place; and
(c) dividing this difference by the amount of Load forecasted to be served in that
Transmission District in that year, stated in terms of megawatt-hours, net of any Load served
by municipally owned utilities that is not subject to the TSC.
Step 8. The ISO shall calculate the forecasted net impact of the Project on the NTAC offset for each
megawatt-hour of electricity consumed by Load in each year by:
(a) summing the following, each forecasted for that year under the assumption that the
Project is in place:
(i) forecasted Congestion Rents associated with any Incremental TCCs that the ISO
has awarded, or that the ISO projects it would award, as calculated in Step 2(b) of this
procedure, in conjunction with other projects that have entered commercial operation
or are expected to enter commercial operation before the Project enters commercial
operation, if those Congestion Rents would affect the NTAC;
(ii) forecasted Congestion Rents associated with any Grandfathered TCCs and
forecasted imputed Congestion Rents associated with any Grandfathered Rights held
by NYPA that would be paid to NYPA for that year, as calculated in Step 2(c) of this
procedure, if those Congestion Rents would affect the NTAC;
(iii) the payments that are forecasted to be made for that year to NYPA in association
with Original Residual TCCs allocated to NYPA, as calculated in Step 4 of this
procedure; and
(iv) NYPA’s forecasted share of residual auction revenues for that year, as calculated
in Step 6 of this procedure;
(b) subtracting the sum of items (i) through (iv) above, each forecasted for that year under the
assumption that the Project is not in place; and
(c) dividing this difference by the amount of Load expected to be served in the NYCA in that
year, stated in terms of megawatt-hours, net of any Load served by municipally owned
utilities that is not subject to the NTAC.
Forecasting the Net Impact of the Project on TCC Revenues Allocated to Load in Each Zone
Step 9. The ISO shall calculate the forecasted net impact of the Project in each year in each Load
Zone on payments made in conjunction with TCCs and Grandfathered Rights that benefit Load but
which do not affect TSCs or the NTAC, which shall be the sum of:
(a) Forecasted Congestion Rents paid or imputed to municipally owned utilities serving Load
in that Load Zone that own Grandfathered Rights or Grandfathered TCCs that were not
included in the calculation of the TSC offset in Step 7(a)(ii) of this procedure or the NTAC
offset in Step 8(a)(ii) of this procedure, which the ISO shall calculate by:
(i) summing forecasted Congestion Rents that any such municipally owned utilities
serving Load in that Load Zone would be paid for that year in association with any
such Grandfathered TCCs and any forecasted imputed Congestion Rents that such a
municipally owned utility would be paid for that year in association with any such
Grandfathered Rights, as calculated in Step 2(c) of this procedure under the
assumption that the Project is in place; and
(ii) subtracting forecasted Congestion Rents that any such municipally owned utilities
would be paid for that year in association with any such Grandfathered TCCs, and
any forecasted imputed Congestion Rents that such a municipally owned utility
would be paid for that year in association with any such Grandfathered Rights, as
calculated in Step 2(c) of this procedure under the assumption that the Project is not
in place.
(b) Forecasted Congestion Rents collected from Incremental TCCs awarded in conjunction
with projects that were previously funded through this procedure, if those Congestion Rents
are used to reduce the amount that Load in that Load Zone must pay to fund such projects,
which the ISO shall calculate by:
(i) summing forecasted Congestion Rents that would be collected for that year in
association with any such Incremental TCCs, as calculated in Step 2(b) of this
procedure under the assumption that the Project is in place; and
(ii) subtracting forecasted Congestion Rents that would be collected for that year in
association with any such Incremental TCCs, as calculated in Step 2(b) of this
procedure under the assumption that the Project is not in place.
Step 10. The ISO shall calculate the forecasted net reductions in TCC revenues allocated to Load in
each Load Zone as a result of a proposed Project by summing the following:
(a) the product of:
(i) the forecasted net impact of the Project on the TSC offset for each megawatt-hour
of electricity consumed by Load, as calculated for each Transmission District (other
than the NYPA Transmission District) in Step 7 of this procedure; and
(ii) the number of megawatt-hours of energy that are forecasted to be consumed by
Load in that year, in the portion of that Transmission District that is in that Load
Zone, for Load that is subject to the TSC;
summed over all Transmission Districts;
(b) the product of:
(i) the forecasted net impact of the Project on the NTAC offset for each megawatt-
hour of electricity consumed by Load, as calculated in Step 8 of this procedure; and
(ii) the number of megawatt-hours of energy that are forecasted to be consumed by
Load in that year in that Load Zone, for Load that is subject to the NTAC; and
(c) the forecasted net impact of the Project on payments and imputed payments made in
conjunction with TCCs and Grandfathered Rights that benefit Load but which do not affect
TSCs or the NTAC, as calculated in Step 9 of this procedure.
Additional Notes Concerning the Procedure
For the purposes of Steps 2(c) and 4(b) of this procedure, the ISO will utilize the currently effective
version of Attachment L of the ISO OATT to identify Existing Transmission Agreements and
Existing Transmission Capacity for Native Load.
Each Transmission Owner, other than NYPA, will inform the ISO of any Grandfathered Rights and
Grandfathered TCCs it holds whose Congestion Rents should be taken into account in Step 7 of this
procedure because those Congestion Rents affect its TSC.
NYPA will inform the ISO of any Grandfathered Rights and Grandfathered TCCs it holds whose
Congestion Rents should be taken into account in Step 8 of this procedure because those Congestion
Rents affect the NTAC.
APPENDIX C - RELIABILITY PLANNING PROCESS DEVELOPMENT
AGREEMENT
TABLE OF CONTENTS
Page
ARTICLE 1.
DEFINITIONS
2
ARTICLE 2.
EFFECTIVE DATE AND TERM
6
2.1.
Effective Date
6
2.2.
Filing
7
2.3.
Term of Agreement
7
ARTICLE 3.
TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
7
3.1.
Application for Required Authorizations and Approvals
7
3.2.
Development and Construction of Transmission Project
7
3.3.
Milestones
8
3.4.
Modifications to Transmission Project
9
3.5.
Billing and Payment
10
3.6.
Project Monitoring
10
3.7.
Right to Inspect
10
3.8.
Exclusive Responsibility of Developer
10
3.9.
Subcontractors
11
3.10.
No Services or Products Under NYISO Tariffs
11
3.11.
Tax Status
11
ARTICLE 4.
COORDINATION WITH THIRD PARTIES
11
4.1.
Interconnection Requirements for Transmission Project
11
4.2.
Interconnection with Affected System
12
4.3.
Coordination of Interregional Transmission Project
12
ARTICLE 5.
OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
12
ARTICLE 6.
INSURANCE
13
ARTICLE 7.
BREACH AND DEFAULT
15
7.1.
Breach
15
7.2.
Default
15
7.3.
Remedies
16
ARTICLE 8.
TERMINATION
16
8.1.
Termination by the NYISO
16
8.2.
Reporting of Inability to Comply with Provisions of Agreement
17
8.3.
Transmission Project Transfer Rights Upon Termination
17
ARTICLE 9.
LIABILITY AND INDEMNIFICATION
18
9.1.
Liability
18
9.2.
Indemnity
18
ARTICLE 10. ASSIGNMENT
18
ARTICLE 11. INFORMATION EXCHANGE AND CONFIDENTIALITY
19
11.1.
Information Access
19
11.2.
Confidentiality
20
ARTICLE 12. REPRESENTATIONS, WARRANTIES AND COVENANTS
20
12.1.
General
20
12.2.
Good Standing
20
12.3.
Authority
21
12.4.
No Conflict
21
12.5.
Consent and Approval
21
12.6.
Compliance with All Applicable Laws and Regulations
21
ARTICLE 13. DISPUTE RESOLUTION
21
ARTICLE 14. SURVIVAL
21
ARTICLE 15. MISCELLANEOUS
22
15.1.
Notices
22
15.2.
Entire Agreement
22
15.3.
Cost Recovery
22
15.4.
Binding Effect
22
15.5.
Force Majeure
23
15.6.
Disclaimer
23
15.7.
No NYISO Liability for Review or Approval of Developer Materials
23
15.8.
Amendment
24
15.9.
No Third Party Beneficiaries
24
15.10.
Waiver
24
15.11.
Rules of Interpretation
24
15.12.
Severability
25
15.13.
Multiple Counterparts
25
15.14.
No Partnership
25
15.15.
Headings
25
15.16.
Governing Law
25
15.17.
Jurisdiction and Venue
25
Appendices
THIS DEVELOPMENT AGREEMENT (“Agreement”) is made and entered into this ___ day
of ______ 20__, by and between _______________, a [corporate description] organized and
existing under the laws of the State/Commonwealth of _________ (“Developer”), and the New
York Independent System Operator, Inc., a not-for-profit corporation organized and existing
under the laws of the State of New York (“NYISO”). Developer or NYISO each may be referred
to as a “Party” or collectively referred to as the “Parties.”
RECITALS
WHEREAS, the NYISO administers the Comprehensive System Planning Process (“CSPP”) in
the New York Control Area pursuant to the terms set forth in Attachment Y of the NYISO’s
Open Access Transmission Tariff (“OATT”), as accepted by the Federal Energy Regulatory
Commission (“FERC”);
WHEREAS, as part of the CSPP, the NYISO administers a reliability planning process pursuant
to which the reliability of the New York State Bulk Power Transmission Facilities is assessed
over a ten-year Study Period; Reliability Need(s) that may arise over this period are identified;
proposed solutions to the identified need(s) are solicited by the NYISO; and the more efficient or
cost-effective transmission solution to satisfy the identified need(s) is selected by the NYISO and
reported in the NYISO’s Comprehensive Reliability Plan report;
[Alternative 1 - To include if the Developer’s regulated transmission solution was selected as
the more efficient or cost effective solution:
WHEREAS, the Developer has proposed a regulated transmission solution to satisfy an
identified Reliability Need (“Transmission Project”);
WHEREAS, the NYISO has selected the Developer’s Transmission Project as the more efficient
or cost-effective transmission solution to satisfy an identified Reliability Need and has directed
the Developer to proceed with the Transmission Project pursuant to Section 31.2.8.1 of
Attachment Y of the OATT;]
[Alternative 2 - To include if the NYISO triggers a Developer’s regulated backstop
transmission solution that has not been selected pursuant to Sections 31.2.8.1.2, 31.2.8.1.3, or
31.2.8.1.4:
WHEREAS, the Developer has proposed a regulated backstop transmission solution to satisfy
an identified Reliability Need (“Transmission Project”);
WHEREAS, the NYISO has triggered the Transmission Project to proceed pursuant to Sections
31.2.8.1.2, 31.2.8.1.3, or 31.2.8.1.4;]
[Alternative 3 - To include if a Transmission Owner agrees to complete an alternative selected
transmission solution pursuant to Section 31.2.10.1.3:
WHEREAS, the Developer has agreed to step-in to complete a regulated transmission project to
satisfy an identified Reliability Need (“Transmission Project”) pursuant to Section 31.2.10.1.3 of
Attachment Y of the OATT;]
WHEREAS, the Developer has agreed to obtain the required authorizations and approvals from
Governmental Authorities needed for the Transmission Project, to develop and construct the
Transmission Project, and to abide by the related requirements in Attachment Y of the OATT,
the ISO Tariffs, and the ISO Procedures;
WHEREAS, the Developer and the NYISO have agreed to enter into this Agreement pursuant to
Section 31.2.8.1.6 of Attachment Y of the OATT for the purpose of ensuring that the
Transmission Project will be constructed and in service in time to satisfy the Reliability Need
(“Required Project In-Service Date”); and
WHEREAS, the Developer has agreed to construct, and the NYISO has requested that the
Developer proceed with construction of, the Transmission Project to address the identified
Reliability Need by the Required Project In-Service Date.
NOW, THEREFORE, in consideration of and subject to the mutual covenants contained herein,
it is agreed:
ARTICLE 1. DEFINITIONS
Whenever used in this Agreement with initial capitalization, the following terms shall have the
meanings specified in this Article 1. Terms used in this Agreement with initial capitalization that
are not defined in this Article 1 shall have the meanings specified in Section 31.1.1 of
Attachment Y of the OATT or, if not therein, in Article 1 of the OATT.
Advisory Milestones shall mean the milestones set forth in the Development Schedule in
Attachment C to this Agreement that are not Critical Path Milestones.
Affected System Operator shall mean any Affected System Operator(s) identified in connection
with the Transmission Project pursuant to Attachment P of the ISO OATT.
Applicable Laws and Regulations shall mean: (i) all duly promulgated applicable federal, state
and local laws, regulations, rules, ordinances, codes, decrees, judgments, directives, or judicial or
administrative orders, permits and other duly authorized actions of any Governmental Authority,
and (ii) all applicable requirements of the ISO Tariffs, ISO Procedures, and ISO Related
Agreements.
Applicable Reliability Organizations shall mean the NERC, the NPCC, and the NYSRC.
Applicable Reliability Requirements shall mean the requirements, criteria, rules, standards,
and guidelines, as they may be amended and modified and in effect from time to time, of: (i) the
Applicable Reliability Organizations, (ii) the Connecting Transmission Owner(s), (iii) [to insert
the name(s) of any other Transmission Owners or developers whose transmission facilities the
NYISO has determined may be impacted by the Transmission Project], and (iv) any Affected
System Operator; provided, however, that no Party shall waive its right to challenge the
applicability or validity of any requirement, criteria, rule, standard, or guideline as applied to it in
the context of this Agreement.
Breach shall have the meaning set forth in Article 7.1 of this Agreement.
Breaching Party shall mean a Party that is in Breach of this Agreement.
Business Day shall mean Monday through Friday, excluding federal holidays.
Calendar Day shall mean any day including Saturday, Sunday, or a federal holiday.
Change of Control shall mean a change in ownership of more than 50% of the membership or
ownership interests or other voting securities of the Developer to a third party in one or more
related transactions, or any other transaction that has the effect of transferring control of the
Developer to a third party.
Confidential Information shall mean any information that is defined as confidential by Article
11.2.
Connecting Transmission Owner shall be the Connecting Transmission Owner(s) identified in
connection with the Transmission Project pursuant to Attachment P of the ISO OATT.
Critical Path Milestones shall mean the milestones identified as such in the Development
Schedule in Attachment C to this Agreement that must be met for the Transmission Project to be
constructed and operating by the Required Project In-Service Date.
Default shall mean the failure of a Party in Breach of this Agreement to cure such Breach in
accordance with Article 7.2 of this Agreement.
Developer shall have the meaning set forth in the introductory paragraph.
Development Schedule shall mean the schedule of Critical Path Milestones and Advisory
Milestones set forth in Appendix C to this Agreement.
Effective Date shall mean the date upon which this Agreement becomes effective as determined
in Article 2.1 of this Agreement.
FERC shall mean the Federal Energy Regulatory Commission or its successor.
Force Majeure shall mean any act of God, labor disturbance, act of the public enemy, war,
insurrection, riot, fire, storm or flood, explosion, breakage or accident to machinery or
equipment, any order, regulation or restriction imposed by governmental, military or lawfully
established civilian authorities, or any other cause beyond a Party’s control. A Force Majeure
event does not include acts of negligence or intentional wrongdoing by the Party claiming Force
Majeure.
Good Utility Practice shall mean any of the practices, methods and acts engaged in or approved
by a significant portion of the electric industry during the relevant time period, or any of the
practices, methods and acts which, in the exercise of reasonable judgment in light of the facts
known at the time the decision was made, could have been expected to accomplish the desired
result at a reasonable cost consistent with good business practice, reliability, safety and
expedition. Good Utility Practice is not intended to be limited to the optimum practice, method,
or act to the exclusion of all others, but rather to delineate acceptable practices, methods, or acts
generally accepted in the region.
Governmental Authority shall mean any federal, state, local or other governmental regulatory
or administrative agency, public authority, court, commission, department, board, or other
governmental subdivision, legislature, rulemaking board, tribunal, or other governmental
authority having jurisdiction over any of the Parties, their respective facilities, or the respective
services they provide, and exercising or entitled to exercise any administrative, executive, police,
or taxing authority or power; provided, however, that such term does not include the NYISO, the
Developer, the Connecting Transmission Owner(s), the Affected System Operator(s), or any
Affiliate thereof.
In-Service Date shall mean the date upon which the Transmission Project is energized
consistent with the provisions of the Transmission Project Interconnection Agreement and
available to provide Transmission Service under the NYISO Tariffs.
ISO/TO Agreement shall mean the Agreement Between the New York Independent System
Operator and Transmission Owners, as filed with and accepted by the Commission in Cent.
Hudson Gas & Elec. Corp., et al., 88 FERC ¶ 61,138 (1999) in Docket Nos. ER97-1523, et al.,
and as amended or supplemented from time to time, or any successor agreement thereto.
New York State Transmission System shall mean the entire New York State electrical
transmission system, which includes: (i) the Transmission Facilities Under ISO Operational
Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining
transmission facilities within the New York Control Area.
NERC shall mean the North American Electric Reliability Corporation or its successor
organization.
NPCC shall mean the Northeast Power Coordinating Council or its successor organization.
NYISO/TO Reliability Agreement shall mean the Agreement Between the New York
Independent System Operator, Inc., and the New York Transmission Owners on the
Comprehensive Planning Process for Reliability Needs, as filed with and accepted by the
Commission in New York Independent System Operator, Inc., 109 FERC ¶ 61,372 (2004) and
111 FERC ¶ 61,182 (2005) in Docket No. ER04-1144, and as amended or supplemented from
time to time, or any successor agreement thereto.
NYSRC shall mean the New York State Reliability Council or its successor organization.
OATT shall mean the NYISO’s Open Access Transmission Tariff, as filed with the
Commission, and as amended or supplemented from time to time, or any successor tariff thereto.
Party or Parties shall mean the NYISO, the Developer, or both.
Point of Interconnection shall mean the point or points at which the Developer’s Transmission
Project will interconnect to the New York State Transmission System.
Project Description shall mean the description of the Transmission Project set forth in
Appendix A to this Agreement that is consistent with the project proposed and evaluated in the
NYISO’s reliability planning process and, if applicable, selected by the NYISO Board of
Directors as the more efficient or cost-effective transmission solution to the identified Reliability
Need.
Reliability Planning Process Manual shall mean the NYISO’s manual adopted by the NYISO
stakeholder Operating Committee describing the NYISO’s procedures for implementing the
reliability planning process component of the NYISO’s Comprehensive System Planning
Process, as the manual is amended or supplemented from time to time, or any successor manual
thereto.
Required Project In-Service Date shall mean the In-Service Date by which the Transmission
Project must be constructed and operating to satisfy the Reliability Need, as specified in the
Development Schedule set forth in Appendix C to this Agreement.
Services Tariff shall mean the NYISO’s Market Administration and Control Area Services Tariff,
as filed with the Commission, and as amended or supplemented from time to time, or any
successor tariff thereto.
Significant Modification shall mean a Developer’s proposed modification to its Transmission
Project that: (i) could impair the Transmission Project’s ability to meet the identified Reliability
Need, (ii) could delay the In-Service Date of the Transmission Project beyond the Required
Project In-Service Date, or (iii) would constitute a material change to the project information
submitted by the Developer under Attachment Y of the OATT for use by the NYISO in
evaluating the Transmission Project for purposes of selecting the more efficient or cost-effective
transmission solution to meet the identified Reliability Need.
Scope of Work shall mean the description of the work required to implement the Transmission
Project as set forth in Appendix B to this Agreement. The Scope of Work shall be drawn from
the Developer’s submission of the Required Data Submission for Solutions to Reliability Needs,
which is set forth in Attachment C of the NYISO Reliability Planning Manual, as may be
updated as agreed upon by the Parties, and shall include, but not be limited to, a description of:
the acquisition of required rights-of-ways, the work associated with the licensing, design,
financing, environmental and regulatory approvals, engineering, procurement of equipment,
construction, installation, testing, and commissioning of the Transmission Project; the relevant
technical requirements, standards, and guidelines pursuant to which the work will be performed;
the major equipment and facilities to be constructed and/or installed in connection with the
Transmission Project, and the cost estimates for the work associated with the Transmission
Project.
Transmission Owner Technical Standards shall mean the technical requirements and
standards (e.g, equipment or facilities electrical and physical capabilities, design characteristics,
or construction requirements), as those requirements and standards are amended and modified and
in effect from time to time, of: (i) the Connecting Transmission Owner(s), (ii) [to insert the name(s)
of any other Transmission Owners or developers whose transmission facilities the NYISO has
determined may be impacted by the Transmission Project], and (iii) any Affected System
Operator.
Transmission Project shall mean the Developer’s regulated transmission solution that is subject
to this Agreement as described in the Project Description set forth in Appendix A to this
Agreement.
ARTICLE 2. EFFECTIVE DATE AND TERM
2.1.
Effective Date
This Agreement shall become effective on the date it has been executed by all Parties;
provided, however, if the Agreement is filed with FERC as a non-conforming or an unexecuted
agreement pursuant to Section 31.2.8.1.6 of Attachment Y of the OATT, the Agreement shall
become effective on the effective date accepted by FERC.
2.2.
Filing
If the Agreement must be filed with FERC pursuant to Section 31.2.8.1.6 of Attachment
Y of the OATT, the NYISO shall file this Agreement for acceptance with FERC within the
timeframe set forth for the filing in Section 31.2.8.1.6 of Attachment Y of the OATT. The
Developer shall cooperate in good faith with the NYISO with respect to such filing and provide
any information requested by the NYISO to comply with Applicable Laws and Regulations.
Any Confidential Information shall be treated in accordance with Article 11.2 of this Agreement.
2.3.
Term of Agreement
Subject to the termination provisions in Article 8 of this Agreement, this Agreement shall
remain in effect from the Effective Date until: (i) the Developer executes an operating agreement
with the NYISO, and (ii) the Transmission Project: (A) has been completed in accordance with
the terms and conditions of this Agreement, and (B) is in-service; provided, however, that the
terms of this Agreement shall continue in effect to the extent provided in Article 14 of this
Agreement.
ARTICLE 3. TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
3.1.
Application for Required Authorizations and Approvals
The Developer shall timely seek and obtain all authorizations and approvals from
Governmental Authorities required to develop, construct, and operate the Transmission Project
by the Required Project In-Service Date. The required authorizations and approvals shall be
listed in the Scope of Work in Appendix B to this Agreement. The Developer shall seek and
obtain the required authorizations and approvals in accordance with the milestones set forth in
the Development Schedule in Appendix C to this Agreement. The milestones for obtaining the
required authorizations and approvals shall be included in the Development Schedule as Critical
Path Milestones and Advisory Milestones, as designated by the Parties under Article 3.3.1. The
Developer shall notify the NYISO in accordance with the notice requirements in Article 3.3 if it
has reason to believe that it may be unable to timely obtain or is denied an approval or
authorization by a Governmental Authority required for the development, construction, or
operation of the Transmission Project, or if such approval or authorization is withdrawn or
modified.
3.2.
Development and Construction of Transmission Project
The Developer shall design, engineer, procure, install, construct, test and commission the
Transmission Project in accordance with: (i) the terms of this Agreement, including, but not
limited to, the Project Description in Appendix A to this Agreement, the Scope of Work in
Appendix B to this Agreement, and the Development Schedule in Appendix C to this
Agreement; (ii) Applicable Reliability Requirements; (iii) Applicable Laws and Regulations; (iv)
Good Utility Practice; (v) the Transmission Owner Technical Standards, and (vi) any
interconnection agreement(s) entered into by and among the NYISO, Developer, and Connecting
Transmission Owner(s) for the Transmission Project to interconnect to the New York State
Transmission System.
3.3.
Milestones
3.3.1.
The NYISO shall provide the Developer with the Required Project In-Service Date that is
set forth in the Comprehensive Reliability Plan report or the updated Comprehensive
Reliability Plan report, as applicable, in accordance with Sections 31.2.7 and 31.2.7.3 of
Attachment Y of the OATT. Prior to executing and/or filing this Agreement with FERC,
the NYISO and the Developer shall agree to the Critical Path Milestones and Advisory
Milestones set forth in the Development Schedule in Appendix C to this Agreement for
the development, construction, and operation of the Transmission Project by the Required
Project In-Service Date in accordance with Section 31.2.8.1.6 of Attachment Y of the
OATT; provided that any such milestone for the Transmission Project that requires action
by a Connecting Transmission Owner or an Affected System Operator to complete must
be included as an Advisory Milestone.
3.3.2.
The Developer shall meet the Critical Path Milestones in accordance with the
Development Schedule set forth in Appendix C to this Agreement. The Developer’s
inability or failure to meet a Critical Path Milestone specified in the Development
Schedule, as such Critical Path Milestone may be amended with the agreement of the
NYISO under this Article 3.3, shall constitute a Breach of this Agreement under Article
7.1.
3.3.3.
The Developer shall notify the NYISO thirty (30) Calendar Days prior to the date of each
Critical Path Milestone specified in the Development Schedule whether, to the best of its
knowledge, it expects to meet the Critical Path Milestone by the specified date; provided,
however, that notwithstanding this requirement:
(i) the Developer shall notify the NYISO as soon as reasonably practicable, and no later
than fifteen (15) Calendar Days, following the Developer’s discovery of a potential delay
in meeting a Critical Path Milestone, including a delay caused by a Force Majeure event;
and
(ii) the NYISO may request in writing at any time, and Developer shall submit to the
NYISO within five (5) Business Days of the request, a written response indicating
whether the Developer will meet, or has met, a Critical Path Milestone and providing all
required supporting documentation for its response.
3.3.4.
The Developer shall not make a change to a Critical Path Milestone without the prior
written consent of the NYISO. To request a change to a Critical Path Milestone, the
Developer must: (i) inform the NYISO in writing of the proposed change to the Critical
Path Milestone and the reason for the change, including the occurrence of a Force
Majeure event in accordance with Section 15.5, (ii) submit to the NYISO a revised
Development Schedule containing any necessary changes to Critical Path Milestones and
Advisory Milestones that provide for the Transmission Project to be completed and
achieve its In-Service Date no later than the Required Project In-Service Date, and (iii)
submit a notarized officer’s certificate certifying the Developer’s capability to complete
the Transmission Project in accordance with the modified schedule. If the Developer: (i)
must notify the NYISO of a potential delay in meeting a Critical Path Milestone in
accordance with one of the notification requirements in Section 3.3.3 or (ii) is requesting
a change to a Critical Path Milestone to cure a Breach in Section 7.2, the Developer shall
submit any request to change the impacted Critical Path Milestone(s) within the relevant
notification timeframe set forth in Section 3.3.3 or the cure period set forth in Section 7.2,
as applicable. The NYISO will promptly review the Developer’s requested change. The
Developer shall provide the NYISO with all required information to assist the NYISO in
making its determination and shall be responsible for the costs of any study work the
NYISO performs in making its determination. If the Developer demonstrates to the
NYISO’s satisfaction that the delay in meeting a Critical Path Milestone will not delay
the Transmission Project’s In-Service Date beyond the Required Project In-Service Date,
then the NYISO’s consent to extending the Critical Path Milestone date will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s written consent to a
revised Development Schedule proposed by the Developer will satisfy the amendment
requirements in Article 15.8, and the NYISO will not be required to file the revised
Development Schedule with FERC.
3.3.5. Within fifteen (15) Calendar Days of the Developer’s discovery of a potential delay in
meeting an Advisory Milestone, the Developer shall inform the NYISO of the potential
delay and describe the impact of the delay on meeting the Critical Path Milestones. The
Developer may extend an Advisory Milestone date upon informing the NYISO of such
change; provided, however, that if the change to the Advisory Milestone will delay a
Critical Path Milestone, the NYISO’s written consent to make such change is required as
described in Article 3.3.4.
3.4.
Modifications to Transmission Project
The Developer shall not make a Significant Modification to the Transmission Project
without the prior written consent of the NYISO, including, but not limited to, modifications
necessary for the Developer to obtain required approvals or authorizations from Governmental
Authorities. The NYISO’s determination regarding a Significant Modification to the
Transmission Project under this Agreement shall be separate from, and shall not replace, the
NYISO’s review and determination of material modifications to the Transmission Project under
Attachment P of the OATT. The Developer may request that the NYISO review whether a
modification to the Transmission Project would constitute a Significant Modification. The
Developer shall provide the NYISO with all required information to assist the NYISO in making
its determination regarding a Significant Modification and shall be responsible for the costs of
any study work the NYISO must perform in making its determination. If the Developer
demonstrates to the NYISO’s satisfaction that its proposed Significant Modification: (i) does not
impair the Transmission Project’s ability to satisfy the identified Reliability Need, (ii) does not
delay the In-Service Date of the Transmission Project beyond the Required Project In-Service
Date, and (iii) does not change the grounds upon which the NYISO selected the Transmission
Project as the more efficient or cost-effective transmission solution to the identified Reliability
Need (if applicable), the NYISO’s consent to the Significant Modification will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s performance of this review shall
not constitute its consent to delay the completion of any Critical Path Milestone.
3.5.
Billing and Payment
The NYISO shall charge, and the Developer shall pay, the actual costs of: (i) any study
work performed by the NYISO or its subcontractor(s) under Articles 3.3 and 3.4, or (ii) any
assessment of the Transmission Project by the NYISO or its subcontractor(s) under Article 3.7.
The NYISO will invoice Developer on a monthly basis for the expenses incurred by the NYISO
each month, including estimated subcontractor costs, computed on a time and material basis.
The Developer shall pay invoiced amounts to the NYISO within thirty (30) Calendar Days of the
NYISO’s issuance of a monthly invoice. In the event the Developer disputes an amount to be
paid, the Developer shall pay the disputed amount to the NYISO, pending resolution of the
dispute. To the extent the dispute is resolved in the Developer’s favor, the NYISO will net the
disputed amount, including interest calculated from Developer’s date of payment at rates
applicable to refunds under FERC regulations, against any current amounts due from the
Developer and pay the balance to the Developer. This Article 3.5 shall survive the termination,
expiration, or cancellation of this Agreement.
3.6.
Project Monitoring
The Developer shall provide regular status reports to the NYISO in accordance with the
monitoring requirements set forth in the Development Schedule, the Reliability Planning Process
Manual and Attachment Y of the OATT.
3.7.
Right to Inspect
Upon reasonable notice, the NYISO or its subcontractor shall have the right to inspect the
Transmission Project for the purpose of assessing the progress of the development and
construction of the Transmission Project and satisfaction of milestones. The exercise or non-
exercise by the NYISO or its subcontractor of this right shall not be construed as an endorsement
or confirmation of any element or condition of the development or construction of the
Transmission Project, or as a warranty as to the fitness, safety, desirability or reliability of the
same. Any such inspection shall take place during normal business hours, shall not interfere
with the construction of the Transmission Project and shall be subject to such reasonable safety
and procedural requirements as the Developer shall specify.
3.8.
Exclusive Responsibility of Developer
As between the Parties, the Developer shall be solely responsible for all planning, design,
engineering, procurement, construction, installation, management, operations, safety, and
compliance with Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards associated with the Transmission Project, including,
but not limited to, scheduling, meeting Critical Path Milestones and Advisory Milestones, timely
requesting review and consent to any project modifications, and obtaining all necessary permits,
siting, and other regulatory approvals. The NYISO shall have no responsibility and shall have
no liability regarding the management or supervision of the Developer’s development of the
Transmission Project or the compliance of the Developer with Applicable Laws and Regulations,
Applicable Reliability Requirements, and Transmission Owner Technical Standards. The
NYISO shall cooperate with the Developer in good faith in providing information to assist the
Developer in obtaining all approvals and authorizations from Governmental Authorities required
to develop, construct, and operate the Transmission Project by the Required Project In-Service
Date, including, if applicable, information describing the NYISO’s basis for selecting the
Transmission Project as the more efficient or cost-effective transmission solution to satisfy an
identified Reliability Need.
3.9.
Subcontractors
3.9.1. Nothing in this Agreement shall prevent a Party from using the services of any
subcontractor as it deems appropriate to perform its obligations under this Agreement;
provided, however, that each Party shall require, and shall provide in its contracts with its
subcontractors, that its subcontractors comply with all applicable terms and conditions of
this Agreement in providing such services; provided, further, that each Party shall remain
primarily liable to the other Party for the performance of such subcontractor.
3.9.2. The creation of any subcontractor relationship shall not relieve the hiring Party of any of
its obligations under this Agreement. The hiring Party shall be fully responsible to the
other Party for the acts or omissions of any subcontractor the hiring Party hires as if no
subcontract had been made.
3.10. No Services or Products Under NYISO Tariffs
This Agreement does not constitute a request for, nor agreement by the NYISO to provide,
Transmission Service, interconnection service, Energy, Ancillary Services, Installed Capacity,
Transmission Congestion Contracts or any other services or products established under the ISO
Tariffs. If Developer wishes to receive or supply such products or services, the Developer must
make application to do so under the applicable provisions of the ISO Tariffs, ISO Related
Agreements, and ISO Procedures.
3.11. Tax Status
Each Party shall cooperate with the other Party to maintain each Party’s tax status to the
extent the Party’s tax status is impacted by this Agreement. Nothing in this agreement is
intended to affect the tax status of any Party.
ARTICLE 4. COORDINATION WITH THIRD PARTIES
4.1.
Interconnection Requirements for Transmission Project
The Developer shall satisfy all requirements set forth in the Transmission Interconnection
Procedures in Attachment P of the OATT applicable to a “Transmission Project” to interconnect
the Transmission Project to the New York State Transmission System by the Required Project
In-Service Date, including, but not limited to, submitting a Transmission Interconnection
Application; participating in all necessary studies; executing, and/or requesting the NYISO to
file for FERC acceptance, a Transmission Project Interconnection Agreement; and constructing,
or arranging for the construction of, all required Network Upgrade Facilities; provided, however,
if the Developer began the interconnection process in Attachment X of the OATT or the
transmission expansion process in Sections 3.7 or 4.5 of the OATT prior to the effective date of
the Transmission Interconnection Procedures, the Developer shall satisfy the requirements of the
Transmission Interconnection Procedures in accordance with the transition rules in Section
22.3.3 of Attachment P of the OATT.
If the NYISO determines that the proposed interconnection of a “Transmission Project”
under Attachment P could affect the Transmission Project under this Agreement, the Developer
shall participate in the Transmission Interconnection Procedures as an Affected System Operator
in accordance with the requirements set forth in Section 22.4.4 of Attachment P. If the NYISO
determines that the proposed interconnection of a “Large Generating Facility,” “Small
Generating Facility,” or “Merchant Transmission Facility” under Attachments X or Z of the
OATT could affect the Transmission Project, the Developer shall participate in the
interconnection process as an Affected System Operator in accordance with the requirements set
forth in Section 30.3.5 of Attachment X of the OATT. If the NYISO determines that a proposed
transmission expansion under Sections 3.7 and 4.5 of the OATT could affect the Transmission
Project, the Developer shall participate in the transmission expansion process as an affected
Transmission Owner in accordance with the requirements set forth in Sections 3.7 and 4.5 of the
OATT.
4.2.
Interconnection with Affected System
If part of the Transmission Project will affect the facilities of an Affected System as
determined in Attachment P of the OATT, the Developer shall satisfy the requirements of the
Affected System Operator for the interconnection of the Transmission Project.
4.3.
Coordination of Interregional Transmission Project
If the Transmission Project is or seeks to become an Interregional Transmission Project
selected by the NYISO and by the transmission provider in one or more neighboring
transmission planning region(s) to address an identified Reliability Need, the Developer shall
coordinate its development and construction of the Transmission Project in New York with its
responsibilities in the relevant neighboring transmission planning region(s) and must satisfy the
applicable planning requirements of the relevant transmission planning region(s).
ARTICLE 5. OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
If the Developer is a Transmission Owner, the Developer shall comply with the operating
requirements set forth in the ISO/TO Agreement. If the Developer is not a Transmission Owner,
the Developer shall: (i) execute, and/or obtain a FERC accepted, interconnection agreement for
the Transmission Project in accordance with the requirements in Attachment P of the OATT; (ii)
satisfy the applicable requirements set forth in the interconnection agreement and ISO
Procedures for the safe and reliable operation of the Transmission Project consistent with the
Project Description set forth in Appendix A by the In-Service Date, including satisfying all
applicable testing, metering, communication, system protection, switching, start-up, and
synchronization requirements; (iii) enter into required operating protocols as determined by the
NYISO; (iv) register with NERC as a Transmission Owner, be certified as a Transmission
Operator unless otherwise agreed by the Parties, and comply with all NERC Reliability
Standards and Applicable Reliability Requirements applicable to Transmission Owners and
Transmission Operators; and (v) prior to energizing the Transmission Project, execute an
operating agreement with the NYISO.
ARTICLE 6. INSURANCE
The Developer shall, at its own expense, maintain in force throughout the period of this
Agreement, and until released by the NYISO, the following minimum insurance coverages, with
insurers authorized to do business in the state of New York and rated “A- (minus) VII” or better
by A.M. Best & Co. (or if not rated by A.M. Best & Co., a rating entity acceptable to the
NYISO):
6.1
Workers’ Compensation and Employers’ Liability Insurance providing statutory benefits
in accordance with the laws and regulations of New York State under NCCI Coverage
Form No. WC 00 00 00, as amended or supplemented from time to time, or an equivalent
form acceptable to the NYISO; provided, however, if the Transmission Project will be
located in part outside of New York State, Developer shall maintain such Employers’
Liability Insurance coverage with a minimum limit of One Million Dollars ($1,000,000).
6.2
Commercial General Liability Insurance - under ISO Coverage Form No. CG 00 01
(04/13), as amended or supplemented from time to time, or an equivalent form acceptable
to the NYISO - with minimum limits of Two Million Dollars ($2,000,000) per
occurrence/Four Million Dollars ($4,000,000) aggregate combined single limit for
personal injury, bodily injury, including death and property damage.
6.3
Commercial Business Automobile Liability Insurance - under ISO Coverage Form No.
CA 00 01 10 13, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO - for coverage of owned and non-owned and hired vehicles,
trailers or semi-trailers designed for travel on public roads, with a minimum, combined
single limit of One Million Dollars ($1,000,000) per occurrence for bodily injury,
including death, and property damage.
6.4
Umbrella/Excess Liability Insurance over and above the Employers’ Liability,
Commercial General Liability, and Commercial Business Automobile Liability Insurance
coverage, with a minimum combined single limit of Twenty-Five Million Dollars
($25,000,000) per occurrence/Twenty-Five Million Dollars ($25,000,000) aggregate.
6.5
Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility
Practice.
6.6
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies of the Developer shall name
the NYISO and its respective directors, officers, agents, servants and employees
(“NYISO Parties”) as additional insureds. For Commercial General Liability Insurance,
the Developer shall name the NYISO Parties as additional insureds under the following
ISO form numbers, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO: (i) ISO Coverage Form No. CG 20 37 04 13 (“Additional
Insured - Owners, Lessees or Contractors - Completed Operations”) and (ii) (A) ISO
Coverage Form No. CG 20 10 04 13 (“Additional Insured - Owner, Lessees or
Contractors - Scheduled Person or Organization”), or (B) ISO Coverage Form No. CG
20 26 04 13 (“Additional Insured - Designated Person or Organization”). For
Commercial Business Automobile Liability Insurance, the Developer shall name the
NYISO Parties as additional insureds under ISO Coverage Form No. CA 20 48 10 13
(“Designated Insured for Covered Autos Liability Coverage”), as amended or
supplemented from time to time, or an equivalent form acceptable to the NYISO.
6.7
All policies shall contain provisions whereby the insurers waive all rights of subrogation
in accordance with the provisions of this Agreement against the NYISO Parties and
provide thirty (30) Calendar days advance written notice to the NYISO Parties prior to
non-renewal, cancellation or any material change in coverage or condition.
6.8
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies shall contain provisions that
specify that the policies are primary and shall apply to such extent without consideration
for other policies separately carried and shall state that each insured is provided coverage
as though a separate policy had been issued to each, except the insurer’s liability shall not
be increased beyond the amount for which the insurer would have been liable had only
one insured been covered. The Developer shall be responsible for its respective
deductibles or retentions.
6.9
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies, if written on a Claims First
Made Basis in a form acceptable to the NYISO, shall be maintained in full force and
effect for two (2) years after termination of this Agreement, which coverage may be in
the form of an extended reporting period (ERP) or a separate policy, if agreed by the
Developer and the NYISO.
6.10
The requirements contained herein as to the types and limits of all insurance to be
maintained by the Developer are not intended to and shall not in any manner, limit or
qualify the liabilities and obligations assumed by the Developer under this Agreement.
6.11
The Developer shall provide certification of all insurance required in this Agreement,
executed by each insurer or by an authorized representative of each insurer: (A) within
ten (10) days following: (i) execution of this Agreement, or (ii) the NYISO’s date of
filing this Agreement if it is filed unexecuted with FERC, and (B) as soon as practicable
after the end of each fiscal year or at the renewal of the insurance policy and in any event
within thirty (30) days thereafter.
6.12
Notwithstanding the foregoing, the Developer may self-insure to meet the minimum
insurance requirements of Articles 6.2 through 6.10 to the extent it maintains a self-
insurance program; provided that, the Developer’s senior debt is rated at investment
grade, or better, by Standard & Poor’s and that its self-insurance program meets the
minimum insurance requirements of Articles 6.2 through 6.10. For any period of time
that the Developer’s senior debt is unrated by Standard & Poor’s or is rated at less than
investment grade by Standard & Poor’s, the Developer shall comply with the insurance
requirements applicable to it under Articles 6.2 through 6.11. In the event that the
Developer is permitted to self-insure pursuant to this Article 6.12, it shall notify the
NYISO that it meets the requirements to self-insure and that its self-insurance program
meets the minimum insurance requirements in a manner consistent with that specified in
Article 6.11.
6.13
The Developer and the NYISO agree to report to each other in writing as soon as
practical all accidents or occurrences resulting in injuries to any person, including death,
and any property damage arising out of this Agreement.
6.14
Notwithstanding the minimum insurance coverage types and amounts described in this
Article 6, the Developer: (i) shall also maintain any additional insurance coverage types
and amounts required under Applicable Laws and Regulations, including New York State
law, and under Good Utility Practice for the work performed by the Developer and its
subcontractors under this Agreement, and (ii) shall satisfy the requirements set forth in
Articles 6.6 through 6.13 with regard to the additional insurance coverages, including
naming the NYISO Parties as additional insureds under these policies.
ARTICLE 7. BREACH AND DEFAULT
7.1.
Breach
A Breach of this Agreement shall occur when: (i) the Developer notifies the NYISO in
writing that it will not proceed to develop the Transmission Project for reasons other than those
set forth in Articles 8.1(i) through (iv); (ii) the Developer fails to meet a Critical Path Milestone,
as the milestone may be extended with the agreement of the NYISO under Article 3.3.4 of this
Agreement, set forth in the Development Schedule in Appendix C to this Agreement; (iii) the
Developer makes a Significant Modification to the Transmission Project without the prior
written consent of the NYISO; (iv) the Developer fails to pay a monthly invoice within the
timeframe set forth in Article 3.5; (v) the Developer misrepresents a material fact of its
representations and warranties set forth in Article 12; (vi) a Party assigns this Agreement in a
manner inconsistent with the terms of Article 10 of this Agreement; (vii) the Developer fails to
comply with any other material term or condition of this Agreement; (viii) a custodian, receiver,
trustee or liquidator of the Developer, or of all or substantially all of the assets of the Developer,
is appointed in any proceeding brought by the Developer; or (ix) any such custodian, receiver,
trustee, or liquidator is appointed in any proceeding brought against the Developer that is not
discharged within ninety (90) Days after such appointment, or if the Developer consents to or
acquiesces in such appointment. A Breach shall not occur as a result of a Force Majeure event in
accordance with Article 15.5. A Breach shall also not occur as a result of a delay caused by a
Connecting Transmission Owner or an Affected System Operator.
7.2.
Default
Upon a Breach, the non-Breaching Party shall give written notice of the Breach to the
Breaching Party describing in reasonable detail the nature of the Breach and, where known and
applicable, the steps necessary to cure such Breach, including whether and what such steps must
be accomplished to complete the Transmission Project by the Required Project In-Service Date.
The Breaching Party shall have thirty (30) Calendar Days from receipt of the Breach notice to
cure the Breach, or such other period of time as may be agreed upon by the Parties, which
agreement the NYISO will not unreasonably withhold, condition, or delay if it determines a
longer cure period will not threaten the Developer’s ability to complete the Transmission Project
by the Required Project In-Service Date; provided, however, that if the Breach is the result of a
Developer’s inability or failure to meet a Critical Path Milestone, the Developer may only cure
the Breach if either: (i) it meets the Critical Path Milestone within the cure period and
demonstrates to the NYISO’s satisfaction that, notwithstanding its failure to timely meet the
Critical Path Milestone, the Transmission Project will achieve its In-Service Date no later than
the Required Project In-Service Date, or (ii) the Developer requests in writing within the cure
period, and the NYISO consents to, a change to the missed Critical Path Milestone in accordance
with Article 3.3.4. If the Breach is cured within such timeframe, the Breach specified in the
notice shall cease to exist. If the Breaching Party does not cure its Breach within this timeframe
or cannot cure the Breach in a manner that provides for the Transmission Project to be completed
by the Required Project In-Service Date, the non-Breaching Party shall have the right to declare
a Default and terminate this Agreement pursuant to Article 8.1.
7.3.
Remedies
Upon the occurrence of an event of Default, the non-defaulting Party shall be entitled: (i)
to commence an action to require the defaulting Party to remedy such Default and specifically
perform its duties and obligations hereunder in accordance with the terms and conditions hereof;
and (ii) to exercise such other rights and remedies as it may have in equity or at law; provided,
however, the defaulting Party’s liability under this Agreement shall be limited to the extent set
forth in Article 9.1. No remedy conferred by any provision of this Agreement is intended to be
exclusive of any other remedy and each and every remedy shall be cumulative and shall be in
addition to every other remedy given hereunder or now or hereafter existing at law or in equity
or by statute or otherwise. The election of any one or more remedies shall not constitute a
waiver of the right to pursue other available remedies. This Article 7.3 shall survive the
termination, expiration, or cancellation of this Agreement.
ARTICLE 8. TERMINATION
8.1.
Termination by the NYISO
The NYISO may terminate this Agreement by providing written notice of termination to
the Developer in the event that: (i) the Transmission Project is not triggered pursuant to Section
31.2.8.1.1 of Attachment Y of the OATT or is halted pursuant to Sections 31.2.8.2.1 or
31.2.8.2.2, as applicable, of Attachment Y of the OATT; (ii) the Developer notifies the NYISO
that it is unable to or has not received the required approvals or authorizations by Governmental
Authorities required to develop, construct, and operate the Transmission Project by the Required
Project In-Service Date; (iii) the Developer notifies the NYISO that its required approvals or
authorizations by Governmental Authorities have been withdrawn by the Governmental
Authorities; (iv) the Developer cannot complete the Transmission Project by the Required
Project In-Service Date for any reason: (A) including the occurrence of a Force Majeure event
that will prevent the Developer from completing the Transmission Project by the Required
Project In-Service Date, but (B) excluding a delay caused by a Connecting Transmission Owner
or an Affected System Operator; or (v) the NYISO declares a default pursuant to Article 7.2 of
this Agreement.
The NYISO will provide the written notice of termination to the Developer within fifteen
(15) Business Days of its determination under Article 8.1(i), which notice will specify the date of
termination. If the NYISO identifies grounds for termination under Articles 8.1(iv) or (v) or
receives notice from the Developer under Articles 8.1(ii) or (iii), the NYISO may, prior to
providing a written notice of termination, take action in accordance with Section 31.2.10.1.3 of
Attachment Y of the OATT to address the Reliability Need and, notwithstanding the
confidentiality provisions in Article 11.2, may disclose information regarding the Transmission
Project to Governmental Authorities as needed to implement such action. If the NYISO decides
to terminate this Agreement under Article 8.1(ii), (iii), (iv), or (v), it will provide written notice
of termination to the Developer, which notice will specify the date of termination. If the
Agreement was filed and accepted by FERC pursuant to Section 31.2.8.1.6 of Attachment Y of
the OATT, the NYISO will, following its provision of a notice of termination to the Developer,
promptly file with FERC for its acceptance a notice of termination of this Agreement.
In the event of termination under Articles 8.1(i), (ii), or (iii), the Developer may be
eligible for cost recovery under the OATT in the manner set forth in Attachment Y and Schedule
10 of the OATT. In the event of termination under Articles 8.1(iv) or (v), cost recovery may be
permitted as determined by FERC; provided, however, that if the Developer is the Responsible
Transmission Owner, it may also recover costs to the extent permitted under the NYISO/TO
Reliability Agreement. In the event of termination for any reason under this Article 8.1, the
Developer shall use commercially reasonable efforts to mitigate the costs, damages, and charges
arising as a consequence of termination and any transfer or winding up of the Transmission
Project.
8.2.
Reporting of Inability to Comply with Provisions of Agreement
Notwithstanding the notification requirements in Article 3 and this Article 8 of this
Agreement, each Party shall notify the other Party promptly upon the notifying Party becoming
aware of its inability to comply with any provision of this Agreement. The Parties agree to
cooperate with each other and provide necessary information regarding such inability to comply,
including the date, duration, reason for inability to comply, and corrective actions taken or
planned to be taken with respect to such inability to comply.
8.3.
Transmission Project Transfer Rights Upon Termination
If the Transmission Project was proposed as an alternative regulated transmission
solution that was selected by the NYISO as the more efficient or cost-effective transmission
solution to a Reliability Need and the NYISO terminates this Agreement pursuant to Article 8.1,
the NYISO shall have the right, but shall not be required, to request an entity other than the
Developer to complete the Transmission Project. The NYISO may exercise this right by
providing the Developer with written notice within sixty (60) days after the date on which this
Agreement is terminated. If the NYISO exercises its right under this Article 8.3 and Section
31.2.10.1.3 of Attachment Y of the OATT, the Developer shall work cooperatively with the
NYISO’s designee pursuant to the requirements set forth in Section 31.2.10.1.4 of Attachment Y
of the OATT to implement the transition, including entering into good faith negotiations with the
NYISO’s designee to transfer the Transmission Project to the NYISO’s designee. All liabilities
under this Agreement existing prior to such transfer shall remain with the Developer, unless
otherwise agreed upon by the Developer and the NYISO’s designee as part of their good faith
negotiations regarding the transfer. This Article 8.3 shall survive the termination, expiration, or
cancellation of this Agreement.
ARTICLE 9. LIABILITY AND INDEMNIFICATION
9.1.
Liability
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, neither Party shall be liable, whether based on contract, indemnification, warranty,
equity, tort, strict liability, or otherwise, to the Other Party or any Transmission Owner, NYISO
Market Participant, third party or any other person for any damages whatsoever, including,
without limitation, direct, incidental, consequential (including, without limitation, attorneys’ fees
and litigation costs), punitive, special, multiple, exemplary, or indirect damages arising or
resulting from any act or omission under this Agreement, except in the event the Party is found
liable for gross negligence or intentional misconduct in the performance of its obligations under
this Agreement, in which case the Party’s liability for damages shall be limited only to direct
actual damages. This Article 9.1 shall survive the termination, expiration, or cancellation of this
Agreement.
9.2.
Indemnity
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, each Party shall at all times indemnify and save harmless, as applicable, the other
Party, its directors, officers, employees, trustees, and agents or each of them from any and all
damages (including, without limitation, any consequential, incidental, direct, special, indirect,
exemplary or punitive damages and economic costs), losses, claims, including claims and actions
relating to injury to or death of any person or damage to property, liabilities, judgments,
demands, suits, recoveries, costs and expenses, court costs, attorney and expert fees, and all other
obligations by or to third parties, arising out of, or in any way resulting from this Agreement,
provided, however, that the Developer shall not have any indemnification obligation under this
Article 9.2 with respect to any loss to the extent the loss results from the negligence or
intentional misconduct of the NYISO; provided, further, that the NYISO shall not have any
indemnification obligation under this Article 9.2 with respect to any loss to the extent the loss
results from the negligence or intentional misconduct of the Developer. This Article 9.2 shall
survive the termination, expiration, or cancellation of this Agreement.
ARTICLE 10.
ASSIGNMENT
This Agreement may be assigned by a Party only with the prior written consent of the
other Party; provided that:
(i) any Change of Control shall be considered an assignment under this Article 10 and
shall require the other Party’s prior written consent;
(ii) an assignment by the Developer shall be contingent upon the Developer or assignee
demonstrating to the satisfaction of the NYISO prior to the effective date of the
assignment that: (A) the assignee has the technical competence, financial ability, and
materials, equipment, and plans to comply with the requirements of this Agreement and
to construct and place in service the Transmission Project by the Required Project In-
Service Date consistent with the assignor’s cost estimates for the Transmission Project;
and (B) the assignee satisfies the requirements for a qualified developer pursuant to
Section 31.2.4.1.1 of Attachment Y of the OATT; and
(iii) the Developer shall have the right to assign this Agreement, without the consent of
the NYISO, for collateral security purposes to aid in providing financing for the
Transmission Project and shall promptly notify the NYISO of any such assignment;
provided, however, that such assignment shall be subject to the following: (i) prior to or
upon the exercise of the secured creditor’s, trustee’s, or mortgagee’s assignment rights
pursuant to said arrangement, the secured creditor, the trustee, or the mortgagee will
notify the NYISO of the date and particulars of any such exercise of assignment right(s),
and (ii) the secured creditor, trustee, or mortgagee must demonstrate to the satisfaction of
the NYISO that any entity that it proposes to complete the Transmission Project meets
the requirements for the assignee of a Developer described in Article 10(ii).
For all assignments by any Party, the assignee must assume in a writing, to be provided to
the other Party, all rights, duties, and obligations of the assignor arising under this Agreement,
including the insurance requirements in Article 6 of this Agreement. Any assignment under this
Agreement shall not relieve a Party of its obligations, nor shall a Party’s obligations be enlarged,
in whole or in part, by reasons thereof, absent the written consent of the other Party. Where
required, consent to assignment will not be unreasonably withheld, conditioned, or delayed. Any
attempted assignment that violates this Article 10 is void and ineffective, is a Breach of this
Agreement under Article 7.1 and may result in the termination of this Agreement under Articles
8.1 and 7.2.
ARTICLE 11.
INFORMATION EXCHANGE AND CONFIDENTIALITY
11.1. Information Access
Subject to Applicable Laws and Regulations, each Party shall make available to the other
Party information necessary to carry out obligations and responsibilities under this Agreement
and Attachment Y of the OATT. The Parties shall not use such information for purposes other
than to carry out their obligations or enforce their rights under this Agreement or Attachment Y
of the OATT.
11.2.
Confidentiality
11.2.1
Confidential Information shall mean: (i) all detailed price information and vendor
contracts; (ii) any confidential and/or proprietary information provided by one Party to
the other Party that is clearly marked or otherwise designated “Confidential Information”;
and (iii) information designated as Confidential Information by the NYISO Code of
Conduct contained in Attachment F of the OATT; provided, however, that Confidential
Information does not include information: (i) in the public domain or that has been
previously publicly disclosed; (ii) required by an order of a Governmental Authority to be
publicly submitted or divulged (after notice to the other Party); or (iii) necessary to be
divulged in an action to enforce this Agreement.
11.2.2
The NYISO shall treat any Confidential Information it receives in accordance with the
requirements of the NYISO Code of Conduct contained in Attachment F of the OATT. If
the Developer receives Confidential Information, it shall hold such information in
confidence, employing at least the same standard of care to protect the Confidential
Information obtained from the NYISO as it employs to protect its own Confidential
Information. Each Party shall not disclose the other Party’s Confidential Information to
any third party or to the public without the prior written authorization of the Party
providing the information, except: (i) to the extent required for the Parties to perform
their obligations under this Agreement, the ISO Tariffs, ISO Related Agreements, or ISO
Procedures, or (ii) to fulfill legal or regulatory requirements, provided that if the Party
must submit the information to a Governmental Authority in response to a request by the
Governmental Authority on a confidential basis, the Party required to disclose the
information shall request under applicable rules and regulations that the information be
treated as confidential and non-public by the Governmental Authority.
ARTICLE 12.
REPRESENTATIONS, WARRANTIES, AND COVENANTS
12.1. General
The Developer makes the following representations, warranties, and covenants, which are
effective as to the Developer during the full time this Agreement is effective:
12.2. Good Standing
The Developer is duly organized, validly existing and in good standing under the laws of
the state in which it is organized, formed, or incorporated, as applicable. The Developer is
qualified to do business in the state or states in which the Transmission Project is located. The
Developer has the corporate power and authority to own its properties, to carry on its business as
now being conducted and to enter into this Agreement and carry out the transactions
contemplated hereby and to perform and carry out covenants and obligations on its part under
and pursuant to this Agreement.
12.3. Authority
The Developer has the right, power, and authority to enter into this Agreement, to
become a Party hereto, and to perform its obligations hereunder. This Agreement is a legal,
valid, and binding obligation of the Developer, enforceable against the Developer in accordance
with its terms, except as the enforceability thereof may be limited by applicable bankruptcy,
insolvency, reorganization, or other similar laws affecting creditors’ rights generally and by
general equitable principles (regardless of whether enforceability is sought in a proceeding in
equity or at law).
12.4. No Conflict
The execution, delivery and performance of this Agreement does not violate or conflict
with the organizational or formation documents, or bylaws or operating agreement, of the
Developer, or any judgment, license, permit, order, material agreement or instrument applicable
to or binding upon the Developer or any of its assets.
12.5. Consent and Approval
The Developer has sought or obtained, or, in accordance with this Agreement will seek or
obtain, such consent, approval, authorization, order, or acceptance by any Governmental
Authority in connection with the execution, delivery and performance of this Agreement, and it
will provide to any Governmental Authority notice of any actions under this Agreement that are
required by Applicable Laws and Regulations.
12.6. Compliance with All Applicable Laws and Regulations
The Developer will comply with all Applicable Laws and Regulations, including all
approvals, authorizations, orders, and permits issued by any Governmental Authority; all
Applicable Reliability Requirements, and all applicable Transmission Owner Technical
Standards in the performance of its obligations under this Agreement.
ARTICLE 13.
DISPUTE RESOLUTION
If a dispute arises under this Agreement, the Parties shall use the dispute resolution
process described in Article 11 of the NYISO’s Services Tariff, as such process may be amended
from time to time. Notwithstanding the process described in Article 11 of the NYISO’s Services
Tariff, the NYISO may terminate this Agreement in accordance with Article 8 of this
Agreement.
ARTICLE 14.
SURVIVAL
The rights and obligations of the Parties in this Agreement shall survive the termination,
expiration, or cancellation of this Agreement to the extent necessary to provide for the
determination and enforcement of said obligations arising from acts or events that occurred while
this Agreement was in effect. The remedies and rights and obligation upon termination
provisions in Articles 7.3 and 8.3 of this Agreement, the liability and indemnity provisions in
Article 9, and the billing and payment provisions in Article 3.5 of this Agreement shall survive
termination, expiration, or cancellation of this Agreement.
ARTICLE 15.
MISCELLANEOUS
15.1. Notices
Any notice or request made to or by any Party regarding this Agreement shall be made to
the Parties, as indicated below:
NYISO:
[Insert contact information.]
Developer:
[Insert contact information.]
15.2. Entire Agreement
Except as described below in this Section 15.2, this Agreement, including all Appendices
attached hereto, constitutes the entire agreement between the Parties with reference to the subject
matter hereof, and supersedes all prior and contemporaneous understandings of agreements, oral
or written, between the Parties with respect to the subject matter of this Agreement. There are no
other agreements, representations, warranties, or covenants that constitute any part of the
consideration for, or any condition to, either Party’s compliance with its obligation under this
Agreement.
Notwithstanding the foregoing, this Agreement is in addition to, and does not supersede
or limit the Developer’s and NYISO’s rights and responsibilities, under any interconnection
agreement(s) entered into by and among the NYISO, Developer, and Connecting Transmission
Owner(s) for the Transmission Project to interconnect to the New York State Transmission
System, as such interconnection agreements may be amended, supplemented, or modified from
time to time.
15.3. Cost Recovery
The Developer may recover the costs of the Transmission Project in accordance with the
cost recovery requirements in the ISO Tariffs and, if the Developer is the Responsible
Transmission Owner, the ISO Tariffs and the NYISO/TO Reliability Agreement.
15.4. Binding Effect
This Agreement, and the rights and obligations hereof, shall be binding upon and shall
inure to the benefit of the successors and permitted assigns of the Parties hereto.
15.5. Force Majeure
A Party that is unable to carry out an obligation imposed on it by this Agreement due to
Force Majeure shall notify the other Party in writing as soon as reasonably practicable after the
occurrence of the Force Majeure event and no later than the timeframe set forth in Article
3.3.3(i) if the Force Majeure event will result in a potential delay for the Developer to meet a
Critical Path Milestone. If the notifying Party is the Developer, it shall indicate in its notice
whether the occurrence of a Force Majeure event has the potential to delay its meeting one or
more Critical Path Milestones and/or completing the Transmission Project by the Required
Project In-Service Date. If the Force Majeure will delay the Developer’s ability to meet one or
more Critical Path Milestones, the Developer shall request with its notice a change to the
impacted milestones in accordance with the requirements in Section 3.3.4 and must satisfy the
requirements in Section 3.3.4 to change any Critical Path Milestones. A Party shall not be
responsible for any non-performance or considered in Breach or Default under this Agreement,
for any failure to perform any obligation under this Agreement to the extent that such failure is
due to Force Majeure and will not delay the Developer’s ability to complete the Transmission
Project by the Required Project In-Service Date. A Party shall be excused from whatever
performance is affected only for the duration of the Force Majeure and while the Party exercises
reasonable efforts to alleviate such situation. As soon as the nonperforming Party is able to
resume performance of its obligations excused because of the occurrence of Force Majeure, such
Party shall resume performance and give prompt notice thereof to the other Party. In the event
that Developer will not be able to complete the Transmission Project by the Required Project In-
Service Date because of the occurrence of Force Majeure, the NYISO may terminate this
Agreement in accordance with Section 8.1 of this Agreement.
15.6. Disclaimer
Except as provided in this Agreement, the Parties make no other representations,
warranties, covenants, guarantees, agreements or promises regarding the subject matter of this
Agreement.
15.7. No NYISO Liability for Review or Approval of Developer Materials
No review or approval by the NYISO or its subcontractor(s) of any agreement, document,
instrument, drawing, specifications, or design proposed by the Developer nor any inspection
carried out by the NYISO or its subcontractor(s) pursuant to this Agreement shall relieve the
Developer from any liability for any negligence in its preparation of such agreement, document,
instrument, drawing, specification, or design, or its carrying out of such works; or for its failure
to comply with the Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards with respect thereto, nor shall the NYISO be liable to
the Developer or any other person by reason of its or its subcontractor’s review or approval of an
agreement, document, instrument, drawing, specification, or design or such inspection.
15.8. Amendment
The Parties may by mutual agreement amend this Agreement, including the Appendices
to this Agreement, by a written instrument duly executed by both of the Parties. If the
Agreement was filed and accepted by FERC pursuant to Section 31.2.8.1.6 of Attachment Y of
the OATT, the NYISO shall promptly file the amended Agreement for acceptance with FERC.
15.9. No Third Party Beneficiaries
With the exception of the indemnification rights of the NYISO’s directors, officers,
employees, trustees, and agents under Article 9.2, this Agreement is not intended to and does not
create rights, remedies, or benefits of any character whatsoever in favor of any persons,
corporations, associations, or entities other than the Parties, and the obligations herein assumed
are solely for the use and benefit of the Parties, their successors in interest and their permitted
assigns.
15.10. Waiver
The failure of a Party to this Agreement to insist, on any occasion, upon strict
performance of any provision of this Agreement will not be considered a waiver of any
obligation, right, or duty of, or imposed upon, such Party. Any waiver at any time by either
Party of its rights with respect to this Agreement shall not be deemed a continuing waiver or a
waiver with respect to any other failure to comply with any other obligation, right, or duty of this
Agreement. Any waiver of this Agreement shall, if requested, be provided in writing.
15.11. Rules of Interpretation
This Agreement, unless a clear contrary intention appears, shall be construed and
interpreted as follows: (1) the singular number includes the plural number and vice versa; (2)
reference to any person includes such person’s successors and assigns but, in the case of a Party,
only if such successors and assigns are permitted by this Agreement, and reference to a person in
a particular capacity excludes such person in any other capacity or individually; (3) reference to
any agreement (including this Agreement), document, instrument or tariff means such
agreement, document, instrument, or tariff as amended or modified and in effect from time to
time in accordance with the terms thereof and, if applicable, the terms hereof; (4) reference to
any Applicable Laws and Regulations means such Applicable Laws and Regulations as
amended, modified, codified, or reenacted, in whole or in part, and in effect from time to time,
including, if applicable, rules and regulations promulgated thereunder; (5) unless expressly stated
otherwise, reference to any Article, Section or Appendix means such Article of this Agreement,
such Appendix to this Agreement, or such Section of this Agreement, as the case may be; (6)
“hereunder”, “hereof’, “herein”, “hereto” and words of similar import shall be deemed references
to this Agreement as a whole and not to any particular Article or other provision hereof or
thereof; (7) “including” (and with correlative meaning “include”) means including without
limiting the generality of any description preceding such term; and (8) relative to the
determination of any period of time, “from” means “from and including”, “to” means “to but
excluding” and “through” means “through and including”.
15.12. Severability
Each provision of this Agreement shall be considered severable and if, for any reason,
any provision is determined by a court or regulatory authority of competent jurisdiction to be
invalid, void, or unenforceable, the remaining provisions of this Agreement shall continue in full
force and effect and shall in no way be affected, impaired, or invalidated, and such invalid, void,
or unenforceable provision should be replaced with valid and enforceable provision or provisions
that otherwise give effect to the original intent of the invalid, void, or unenforceable provision.
15.13. Multiple Counterparts
This Agreement may be executed in two or more counterparts, each of which is deemed
an original, but all constitute one and the same instrument.
15.14. No Partnership
This Agreement shall not be interpreted or construed to create an association, joint
venture, agency relationship, or partnership among the Parties or to impose any partnership
obligation or partnership liability upon any Party. No Party shall have any right, power, or
authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an
agent or representative of, or otherwise bind, any other Party.
15.15. Headings
The descriptive headings of the various Articles and Sections of this Agreement have
been inserted for convenience of reference only and are of no significance in the interpretation or
construction of this Agreement.
15.16. Governing Law
This Agreement shall be governed, as applicable, by: (i) the Federal Power Act, and (ii)
the substantive law of the State of New York, without regard to any conflicts of laws provisions
thereof (except to the extent applicable, Sections 5-1401 and 5-1402 of the New York General
Obligations Law).
15.17. Jurisdiction and Venue
Any legal action or judicial proceeding regarding a dispute arising out of or relating to
this Agreement or any performance by either Party pursuant thereto that: (i) is within the primary
or exclusive jurisdiction of FERC shall be brought in the first instance at FERC, or (ii) is not
within the primary or exclusive jurisdiction of FERC shall be brought in, and fully and finally
resolved in, either, as applicable, the courts of the State of New York situated in Albany County,
New York or the United States District Court of the Northern District of New York situated in
Albany, New York.
IN WITNESS WHEREFORE, the Parties have executed this Agreement in duplicate originals,
each of which shall constitute an original Agreement between the Parties.
NYISO
By: _______________________
Title:______________________
Date:______________________
[Insert name of Developer]
By:_______________________
Title:______________________
Date:______________________
Appendix A
Project Description
Appendix C
Development Schedule
[To be prepared by Developer consistent with the Developer’s project information submission,
pursuant to Attachment C of the Reliability Planning Process Manual, and subject to acceptance
by the NYISO, as required by Article 3.3 of this Agreement.]
The Developer shall demonstrate to the NYISO that it timely meets the following Critical
Path Milestones and Advisory Milestones and that such milestones remain in good standing.
Critical Path Milestones: [To be developed with consideration of each of the work plan
requirements submitted by the Developer pursuant to Attachment C to the Reliability Planning
Process Manual and presented herein according to the sequence of the critical path. The NYISO
anticipates that the Developer’s critical path schedule will include many of the example
milestones set forth below and that most of the other example milestones will be included as
Advisory Milestones. The composition and sequence of the Critical Path Milestones will differ
depending on the Developer’s Transmission Project and schedule.]
Advisory Milestones: [To include in Development Schedule other milestones (e.g., periodic
project review meetings) that are not determined to be on the critical path, but that will be
monitored by the Developer and reported to NYISO.]
[Example Milestones:
Interconnection studies (e.g. Optional Feasibility Study, System Impact Study, Facilities
Study)
Siting activities (e.g. locating line routing, access roads, and substation site location
options)
Environmental impact studies (relative to siting options)
Engineering (initial)
Permitting and regulatory activities (e.g. Certificate of Environmental Compatibility and
Public Need)
Public outreach plan
Initiation of negotiation of key contracts and financing
Acquisition of all necessary approvals and authorizations of Governmental Authorities,
including identification of all required regulatory approvals
Closing of project financing
Completion of key contracts
Engineering (detailed)
Procurement of major equipment and materials
Environmental management & construction plan (for Article VII certification)
Acquisition of [all or %] required rights of way and property / demonstration of site
control
Surveying and geotechnical assessment (relative to line and station layouts)
Execution, or filing of unexecuted version, of interconnection agreement
Engineering (completed)
Delivery of major electrical equipment
Line and substation site work including milestones for foundations, towers, conductor
stringing, equipment delivery and installation, substation controls and communication,
security, etc.
Construction outage and restoration coordination plan
Completion, verification and testing
Operating and maintenance agreements and instructions
In-Service Date
Required Project In-Service Date]
APPENDIX D - PUBLIC POLICY TRANSMISSION PLANNING PROCESS
DEVELOPMENT AGREEMENT
TABLE OF CONTENTS
Page
ARTICLE 1.
DEFINITIONS
2
ARTICLE 2.
EFFECTIVE DATE AND TERM
6
2.1.
Effective Date
6
2.2.
Filing
6
2.3.
Term of Agreement
6
ARTICLE 3.
TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
6
3.1.
Application for Required Authorizations and Approvals
6
3.2.
Development and Construction of Transmission Project
7
3.3.
Milestones
7
3.4.
Modifications to Required Project In-Service Date
8
3.5.
Modifications to Transmission Project
9
3.6.
Billing and Payment
10
3.7.
Project Monitoring
10
3.8.
Right to Inspect
10
3.9.
Exclusive Responsibility of Developer
10
3.10.
Subcontractors
11
3.11.
No Services or Products Under NYISO Tariffs
11
3.12.
Tax Status
11
ARTICLE 4.
COORDINATION WITH THIRD PARTIES
11
4.1.
Interconnection Requirements for Transmission Project
11
4.2.
Interconnection with Affected System
12
4.3.
Coordination of Interregional Transmission Project
12
ARTICLE 5.
OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
12
ARTICLE 6.
INSURANCE
13
ARTICLE 7.
BREACH AND DEFAULT
15
7.1.
Breach
15
7.2.
Default
15
7.3.
Remedies
16
ARTICLE 8.
TERMINATION
16
8.1.
Termination by the NYISO
16
8.2.
Reporting of Inability to Comply with Provisions of Agreement
17
8.3.
Transmission Project Transfer Rights Upon Termination
17
ARTICLE 9.
LIABILITY AND INDEMNIFICATION
18
9.1.
Liability
18
9.2.
Indemnity
18
ARTICLE 10. ASSIGNMENT
18
ARTICLE 11. INFORMATION EXCHANGE AND CONFIDENTIALITY
19
11.1.
Information Access
19
11.2.
Confidentiality
19
ARTICLE 12. REPRESENTATIONS, WARRANTIES AND COVENANTS
20
12.1.
General
20
12.2.
Good Standing
20
12.3.
Authority
20
12.4.
No Conflict
20
12.5.
Consent and Approval
21
12.6.
Compliance with All Applicable Laws and Regulations
21
ARTICLE 13. DISPUTE RESOLUTION
21
ARTICLE 14. SURVIVAL
21
ARTICLE 15. MISCELLANEOUS
21
15.1.
Notices
21
15.2.
Entire Agreement
22
15.3.
Cost Recovery
22
15.4.
Binding Effect
22
15.5.
Force Majeure
22
15.6.
Disclaimer
23
15.7.
No NYISO Liability for Review or Approval of Developer Materials
23
15.8.
Amendment
23
15.9.
No Third Party Beneficiaries
23
15.10.
Waiver
23
15.11.
Rules of Interpretation
24
15.12.
Severability
24
15.13.
Multiple Counterparts
24
15.14.
No Partnership
24
15.15.
Headings
25
15.16.
Governing Law
25
15.17.
Jurisdiction and Venue
25
Appendices
THIS DEVELOPMENT AGREEMENT (“Agreement”) is made and entered into this ___ day
of ______ 20__, by and between _______________, a [corporate description] organized and
existing under the laws of the State/Commonwealth of _________ (“Developer”), and the New
York Independent System Operator, Inc., a not-for-profit corporation organized and existing
under the laws of the State of New York (“NYISO”). Developer or NYISO each may be referred
to as a “Party” or collectively referred to as the “Parties.”
RECITALS
WHEREAS, the NYISO administers the Comprehensive System Planning Process (“CSPP”) in
the New York Control Area pursuant to the terms set forth in Attachment Y of the NYISO’s
Open Access Transmission Tariff (“OATT”), as accepted by the Federal Energy Regulatory
Commission (“FERC”);
WHEREAS, as part of the CSPP, the NYISO administers a Public Policy Transmission
Planning Process pursuant to which Public Policy Transmission Need(s) are identified; proposed
solutions to the identified need(s) are solicited by the NYISO; and the more efficient or cost-
effective transmission solution to satisfy the identified need(s) is selected by the NYISO and
reported in the NYISO’s Public Policy Transmission Planning Report;
WHEREAS, the Developer has proposed a Public Policy Transmission Project to satisfy an
identified Public Policy Transmission Need (“Transmission Project”);
WHEREAS, the NYISO has selected the Developer’s Transmission Project as the more efficient
or cost-effective transmission solution to satisfy an identified Public Policy Transmission Need
and has directed the Developer to proceed with the Transmission Project;
WHEREAS, the Developer has agreed to obtain the required authorizations and approvals from
Governmental Authorities needed for the Transmission Project, to develop and construct the
Transmission Project, and to abide by the related requirements in Attachment Y of the OATT,
the ISO Tariffs, and the ISO Procedures;
WHEREAS, the Developer and the NYISO have agreed to enter into this Agreement pursuant to
Section 31.4.12.2 of Attachment Y of the OATT for the purpose of ensuring that the
Transmission Project will be constructed and in service in time to satisfy the Public Policy
Transmission Need (“Required Project In-Service Date”); and
WHEREAS, the Developer has agreed to construct, and the NYISO has requested that the
Developer proceed with construction of, the Transmission Project to address the identified Public
Policy Transmission Need by the Required Project In-Service Date.
NOW, THEREFORE, in consideration of and subject to the mutual covenants contained herein,
it is agreed:
ARTICLE 1. DEFINITIONS
Whenever used in this Agreement with initial capitalization, the following terms shall have the
meanings specified in this Article 1. Terms used in this Agreement with initial capitalization that
are not defined in this Article 1 shall have the meanings specified in Section 31.1.1 of
Attachment Y of the OATT or, if not therein, in Article 1 of the OATT.
Advisory Milestones shall mean the milestones set forth in the Development Schedule in
Attachment C to this Agreement that are not Critical Path Milestones.
Affected System Operator shall mean any Affected System Operator(s) identified in connection
with the Transmission Project pursuant to Attachment P of the ISO OATT.
Applicable Laws and Regulations shall mean: (i) all duly promulgated applicable federal, state
and local laws, regulations, rules, ordinances, codes, decrees, judgments, directives, or judicial or
administrative orders, permits and other duly authorized actions of any Governmental Authority,
and (ii) all applicable requirements of the ISO Tariffs, ISO Procedures, and ISO Related
Agreements.
Applicable Reliability Organizations shall mean the NERC, the NPCC, and the NYSRC.
Applicable Reliability Requirements shall mean the requirements, criteria, rules, standards,
and guidelines, as they may be amended and modified and in effect from time to time, of: (i) the
Applicable Reliability Organizations, (ii) the Connecting Transmission Owner(s), (iii) [to insert
the name(s) of any other Transmission Owners or developers whose transmission facilities the
NYISO has determined may be impacted by the Transmission Project], and (iv) any Affected
System Operator; provided, however, that no Party shall waive its right to challenge the
applicability or validity of any requirement, criteria, rule, standard, or guideline as applied to it in
the context of this Agreement.
Breach shall have the meaning set forth in Article 7.1 of this Agreement.
Breaching Party shall mean a Party that is in Breach of this Agreement.
Business Day shall mean Monday through Friday, excluding federal holidays.
Calendar Day shall mean any day including Saturday, Sunday, or a federal holiday.
Change of Control shall mean a change in ownership of more than 50% of the membership or
ownership interests or other voting securities of the Developer to a third party in one or more
related transactions, or any other transaction that has the effect of transferring control of the
Developer to a third party.
Confidential Information shall mean any information that is defined as confidential by Article
11.2.
Connecting Transmission Owner shall be the Connecting Transmission Owner(s) identified in
connection with the Transmission Project pursuant to Attachment P of the ISO OATT.
Critical Path Milestones shall mean the milestones identified as such in the Development
Schedule in Attachment C to this Agreement that must be met for the Transmission Project to be
constructed and operating by the Required Project In-Service Date.
Default shall mean the failure of a Party in Breach of this Agreement to cure such Breach in
accordance with Article 7.2 of this Agreement.
Developer shall have the meaning set forth in the introductory paragraph.
Development Schedule shall mean the schedule of Critical Path Milestones and Advisory
Milestones set forth in Appendix C to this Agreement.
Effective Date shall mean the date upon which this Agreement becomes effective as determined
in Article 2.1 of this Agreement.
FERC shall mean the Federal Energy Regulatory Commission or its successor.
Force Majeure shall mean any act of God, labor disturbance, act of the public enemy, war,
insurrection, riot, fire, storm or flood, explosion, breakage or accident to machinery or
equipment, any order, regulation or restriction imposed by governmental, military or lawfully
established civilian authorities, or any other cause beyond a Party’s control. A Force Majeure
event does not include acts of negligence or intentional wrongdoing by the Party claiming Force
Majeure.
Good Utility Practice shall mean any of the practices, methods and acts engaged in or approved
by a significant portion of the electric industry during the relevant time period, or any of the
practices, methods and acts which, in the exercise of reasonable judgment in light of the facts
known at the time the decision was made, could have been expected to accomplish the desired
result at a reasonable cost consistent with good business practice, reliability, safety and
expedition. Good Utility Practice is not intended to be limited to the optimum practice, method,
or act to the exclusion of all others, but rather to delineate acceptable practices, methods, or acts
generally accepted in the region.
Governmental Authority shall mean any federal, state, local or other governmental regulatory
or administrative agency, public authority, court, commission, department, board, or other
governmental subdivision, legislature, rulemaking board, tribunal, or other governmental
authority having jurisdiction over any of the Parties, their respective facilities, or the respective
services they provide, and exercising or entitled to exercise any administrative, executive, police,
or taxing authority or power; provided, however, that such term does not include the NYISO, the
Developer, the Connecting Transmission Owner(s), the Affected System Operator(s), or any
Affiliate thereof.
In-Service Date shall mean the date upon which the Transmission Project is energized
consistent with the provisions of the Transmission Project Interconnection Agreement and
available to provide Transmission Service under the NYISO Tariffs.
ISO/TO Agreement shall mean the Agreement Between the New York Independent System
Operator and Transmission Owners, as filed with and accepted by the Commission in Cent.
Hudson Gas & Elec. Corp., et al., 88 FERC ¶ 61,138 (1999) in Docket Nos. ER97-1523, et al.,
and as amended or supplemented from time to time, or any successor agreement thereto.
New York State Transmission System shall mean the entire New York State electrical
transmission system, which includes: (i) the Transmission Facilities Under ISO Operational
Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining
transmission facilities within the New York Control Area.
NERC shall mean the North American Electric Reliability Corporation or its successor
organization.
NPCC shall mean the Northeast Power Coordinating Council or its successor organization.
NYPSC shall mean the New York State Public Service Commission or its successor.
NYSRC shall mean the New York State Reliability Council or its successor organization.
OATT shall mean the NYISO’s Open Access Transmission Tariff, as filed with the
Commission, and as amended or supplemented from time to time, or any successor tariff thereto.
Party or Parties shall mean the NYISO, the Developer, or both.
Point of Interconnection shall mean the point or points at which the Developer’s Transmission
Project will interconnect to the New York State Transmission System.
Project Description shall mean the description of the Transmission Project set forth in
Appendix A to this Agreement that is consistent with the project proposed and evaluated in the
NYISO’s Public Policy Transmission Planning Process and selected by the NYISO Board of
Directors as the more efficient or cost-effective transmission solution to the identified Public
Policy Transmission Need.
Public Policy Transmission Planning Process Manual shall mean the NYISO’s manual
adopted by the NYISO stakeholder Operating Committee describing the NYISO’s procedures for
implementing the Public Policy Transmission Planning Process component of the NYISO’s
Comprehensive System Planning Process, as the manual is amended or supplemented from time
to time, or any successor manual thereto.
Required Project In-Service Date shall mean the In-Service Date by which the Transmission
Project must be constructed and operating, which date shall be: (i) the date by which the Public
Policy Transmission Need must be satisfied as prescribed by the NYPSC in its order identifying
the need or in a subsequent order, or (ii) if the NYPSC has not prescribed a date, the date
proposed by the Developer and reviewed and accepted by the NYISO, which date may be either:
(A) the In-Service Date specified by the Developer in the project information it submitted under
Attachment Y of the OATT for use by the NYISO in its selection of the Transmission Project as
the more efficient or cost-effective transmission solution to satisfy the Public Policy
Transmission Need, or (B) such other date accepted by the NYISO as reasonable in light of the
Public Policy Transmission Need. The Required Project In-Service Date is set forth in the
Development Schedule contained in Appendix C to this Agreement.
Services Tariff shall mean the NYISO’s Market Administration and Control Area Services Tariff,
as filed with the Commission, and as amended or supplemented from time to time, or any
successor tariff thereto.
Significant Modification shall mean a Developer’s proposed modification to its Transmission
Project that: (i) could impair the Transmission Project’s ability to meet the identified Public
Policy Transmission Need, (ii) could delay the In-Service Date of the Transmission Project
beyond the Required Project In-Service Date, or (iii) would constitute a material change to the
project information submitted by the Developer under Attachment Y of the OATT for use by the
NYISO in evaluating the Transmission Project for purposes of selecting the more efficient or
cost-effective transmission solution to meet the identified Public Policy Transmission Need.
Scope of Work shall mean the description of the work required to implement the Transmission
Project as set forth in Appendix B to this Agreement. The Scope of Work shall be drawn from
the Developer’s submission of the “Information for a Proposed Solution to a Public Policy
Transmission Need” and the “Data Submission for Public Policy Transmission Projects,” which
are set forth in Attachments B and C of the NYISO Public Policy Transmission Planning Process
Manual, as may be updated as agreed upon by the Parties. The Scope of Work shall include, but
not be limited to, a description of: the acquisition of required rights-of-ways, the work associated
with the licensing, design, financing, environmental and regulatory approvals, engineering,
procurement of equipment, construction, installation, testing, and commissioning of the
Transmission Project; the relevant technical requirements, standards, and guidelines pursuant to
which the work will be performed; the major equipment and facilities to be constructed and/or
installed in connection with the Transmission Project, and the cost estimates for the work
associated with the Transmission Project.
Transmission Owner Technical Standards shall mean the technical requirements and
standards (e.g, equipment or facilities electrical and physical capabilities, design characteristics,
or construction requirements), as those requirements and standards are amended and modified and
in effect from time to time, of: (i) the Connecting Transmission Owner(s), (ii) [to insert the name(s)
of any other Transmission Owners or developers whose transmission facilities the NYISO has
determined may be impacted by the Transmission Project], and (iii) any Affected System
Operator.
Transmission Project shall mean the Developer’s proposed Public Policy Transmission Project
selected by the NYISO as the more efficient or cost-effective transmission solution to a Public
Policy Transmission Need that is subject to this Agreement, as described in the Project
Description set forth in Appendix A to this Agreement.
ARTICLE 2. EFFECTIVE DATE AND TERM
2.1.
Effective Date
This Agreement shall become effective on the date it has been executed by all Parties;
provided, however, if the Agreement is filed with FERC as a non-conforming or an unexecuted
agreement pursuant to Section 31.4.12.2 of Attachment Y of the OATT, the Agreement shall
become effective on the effective date accepted by FERC.
2.2.
Filing
If the Agreement must be filed with FERC pursuant to Section 31.4.12.2 of Attachment
Y of the OATT, the NYISO shall file this Agreement for acceptance with FERC within the
timeframe set forth for the filing in Section 31.4.12.2 of Attachment Y of the OATT. The
Developer shall cooperate in good faith with the NYISO with respect to such filing and provide
any information requested by the NYISO to comply with Applicable Laws and Regulations.
Any Confidential Information shall be treated in accordance with Article 11.2 of this Agreement.
2.3.
Term of Agreement
Subject to the termination provisions in Article 8 of this Agreement, this Agreement shall
remain in effect from the Effective Date until: (i) the Developer executes an operating agreement
with the NYISO, and (ii) the Transmission Project: (A) has been completed in accordance with
the terms and conditions of this Agreement, and (B) is in-service; provided, however, that the
terms of this Agreement shall continue in effect to the extent provided in Article 14 of this
Agreement.
ARTICLE 3. TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION
3.1.
Application for Required Authorizations and Approvals
The Developer shall timely seek and obtain all authorizations and approvals from
Governmental Authorities required to develop, construct, and operate the Transmission Project
by the Required Project In-Service Date. The required authorizations and approvals shall be
listed in the Scope of Work in Appendix B to this Agreement. The Developer shall seek and
obtain the required authorizations and approvals in accordance with the milestones set forth in
the Development Schedule in Appendix C to this Agreement. The milestones for obtaining the
required authorizations and approvals shall be included in the Development Schedule as Critical
Path Milestones and Advisory Milestones, as designated by the Parties under Article 3.3.1. The
Developer shall notify the NYISO in accordance with the notice requirements in Article 3.3 if it
has reason to believe that it may be unable to timely obtain or is denied an approval or
authorization by a Governmental Authority required for the development, construction, or
operation of the Transmission Project, or if such approval or authorization is withdrawn or
modified.
3.2.
Development and Construction of Transmission Project
The Developer shall design, engineer, procure, install, construct, test and commission the
Transmission Project in accordance with: (i) the terms of this Agreement, including, but not
limited to, the Project Description in Appendix A to this Agreement, the Scope of Work in
Appendix B to this Agreement, and the Development Schedule in Appendix C to this
Agreement; (ii) Applicable Reliability Requirements; (iii) Applicable Laws and Regulations; (iv)
Good Utility Practice; (v) the Transmission Owner Technical Standards, and (vi) any
interconnection agreement(s) entered into by and among the NYISO, Developer, and Connecting
Transmission Owner(s) for the Transmission Project to interconnect to the New York State
Transmission System.
3.3.
Milestones
3.3.1.
The NYISO shall provide the Developer with the Required Project In-Service Date that
is set forth in the Public Policy Transmission Planning Report in accordance with Section
31.4.11 of Attachment Y of the OATT. Prior to executing and/or filing this Agreement
with FERC, the NYISO and the Developer shall agree to the Critical Path Milestones and
Advisory Milestones set forth in the Development Schedule in Appendix C to this
Agreement for the development, construction, and operation of the Transmission Project
by the Required Project In-Service Date in accordance with Section 31.4.12.2 of
Attachment Y of the OATT; provided that any such milestone for the Transmission
Project that requires action by a Connecting Transmission Owner or Affected System
Operator to complete must be included as an Advisory Milestone.
3.3.2.
The Developer shall meet the Critical Path Milestones in accordance with the
Development Schedule set forth in Appendix C to this Agreement. The Developer’s
inability or failure to meet a Critical Path Milestone specified in the Development
Schedule, as such Critical Path Milestone may be amended with the agreement of the
NYISO under this Article 3.3, shall constitute a Breach of this Agreement under Article
7.1.
3.3.3.
The Developer shall notify the NYISO thirty (30) Calendar Days prior to the date of each
Critical Path Milestone specified in the Development Schedule whether, to the best of its
knowledge, it expects to meet the Critical Path Milestone by the specified date; provided,
however, that notwithstanding this requirement:
(i) the Developer shall notify the NYISO as soon as reasonably practicable, and no later
than fifteen (15) Calendar Days, following the Developer’s discovery of a potential delay
in meeting a Critical Path Milestone, including a delay caused by a Force Majeure event;
and
(ii) the NYISO may request in writing at any time, and Developer shall submit to the
NYISO within five (5) Business Days of the request, a written response indicating
whether the Developer will meet, or has met, a Critical Path Milestone and providing all
required supporting documentation for its response.
3.3.4.
The Developer shall not make a change to a Critical Path Milestone without the prior
written consent of the NYISO. To request a change to a Critical Path Milestone, the
Developer must: (i) inform the NYISO in writing of the proposed change to the Critical
Path Milestone and the reason for the change, including the occurrence of a Force
Majeure event in accordance with Section 15.5, (ii) submit to the NYISO a revised
Development Schedule containing any necessary changes to Critical Path Milestones and
Advisory Milestones that provide for the Transmission Project to be completed and
achieve its In-Service Date no later than the Required Project In-Service Date, and (iii)
submit a notarized officer’s certificate certifying the Developer’s capability to complete
the Transmission Project in accordance with the modified schedule. If the Developer: (i)
must notify the NYISO of a potential delay in meeting a Critical Path Milestone in
accordance with one of the notification requirements in Section 3.3.3 or (ii) is requesting
a change to a Critical Path Milestone to cure a Breach in Section 7.2, the Developer shall
submit any request to change the impacted Critical Path Milestone(s) within the relevant
notification timeframe set forth in Section 3.3.3 or the cure period set forth in Section 7.2,
as applicable. The NYISO will promptly review the Developer’s requested change. The
Developer shall provide the NYISO with all required information to assist the NYISO in
making its determination and shall be responsible for the costs of any study work the
NYISO performs in making its determination. If the Developer demonstrates to the
NYISO’s satisfaction that the delay in meeting a Critical Path Milestone will not delay
the Transmission Project’s In-Service Date beyond the Required Project In-Service Date,
then the NYISO’s consent to extending the Critical Path Milestone date will not be
unreasonably withheld, conditioned, or delayed. The NYISO’s written consent to a
revised Development Schedule proposed by the Developer will satisfy the amendment
requirements in Article 15.8, and the NYISO will not be required to file the revised
Development Schedule with FERC.
3.3.5.
Within fifteen (15) Calendar Days of the Developer’s discovery of a potential delay in
meeting an Advisory Milestone, the Developer shall inform the NYISO of the potential
delay and describe the impact of the delay on meeting the Critical Path Milestones. The
Developer may extend an Advisory Milestone date upon informing the NYISO of such
change; provided, however, that if the change to the Advisory Milestone will delay a
Critical Path Milestone, the NYISO’s written consent to make such change is required as
described in Article 3.3.4.
3.4.
Modifications to Required Project In-Service Date
3.4.1.
The Developer shall not make a change to the Required Project In-Service Date without
the prior written consent of the NYISO. To request a change, the Developer must: (i)
inform the NYISO in writing of the proposed change to the Required Project In-Service
Date and the reason for the change, including the occurrence of a Force Majeure event,
(ii) submit to the NYISO a revised Development Schedule that provides for the
Transmission Project to be completed and achieve its In-Service Date no later than the
proposed, modified Required Project In-Service Date, and (iii) demonstrate that the
Developer has made reasonable progress against the milestones set forth in the
Development Schedule, and is capable of completing the Transmission Project in
accordance with the modified schedule. If the Required Project In-Service Date is the
date prescribed by the NYPSC in its order identifying the Public Policy Transmission
Need or in a subsequent order, the Developer must also demonstrate that the NYPSC has
issued an order modifying its prescribed date.
3.4.2. The NYISO will promptly review Developer’s requested change to the Required Project
In-Service Date. The Developer shall provide the NYISO with all required information
to assist the NYISO in making its determination and shall be responsible for the costs of
any study work the NYISO performs in making its determination. If the Developer fails
to provide the NYISO with the information required to make its determination, the
NYISO shall not be obligated to make this determination. The NYISO’s consent to
extend the Required Project In-Service Date will not be unreasonably withheld,
conditioned, or delayed if the Developer demonstrates to the NYISO’s satisfaction that:
(i) its proposed modified Required Project In-Service Date is reasonable in light of the
Public Policy Transmission Need, (ii) it has made reasonable progress against the
milestones set forth in the Development Schedule, and (iii) its proposed modified date
will not result in a significant adverse impact to the reliability of the New York State
Transmission System. The Parties shall amend this Agreement in accordance with
Article 15.8 to incorporate a revised Required Project In-Service Date and Development
Schedule.
3.5.
Modifications to Transmission Project
The Developer shall not make a Significant Modification to the Transmission Project
without the prior written consent of the NYISO, including, but not limited to, modifications
necessary for the Developer to obtain required approvals or authorizations from Governmental
Authorities; provided, however, that a proposed Significant Modification that is a proposed
modification to the Required Project In-Service Date shall be addressed in accordance with
Article 3.4. The NYISO’s determination regarding a Significant Modification to the
Transmission Project under this Agreement shall be separate from, and shall not replace, the
NYISO’s review and determination of material modifications to the Transmission Project under
Attachment P of the OATT. The Developer may request that the NYISO review whether a
modification to the Transmission Project would constitute a Significant Modification. The
Developer shall provide the NYISO with all required information to assist the NYISO in making
its determination regarding a Significant Modification and shall be responsible for the costs of
any study work the NYISO must perform in making its determination. The NYISO’s consent to
the Significant Modification will not be unreasonably withheld, conditioned, or delayed if the
Developer demonstrates to the NYISO’s satisfaction that its proposed Significant Modification:
(i) does not impair the Transmission Project’s ability to satisfy the identified Public Policy
Transmission Need, (ii) does not delay the In-Service Date of the Transmission Project beyond
the Required Project In-Service Date, (iii) does not change the grounds upon which the NYISO
selected the Transmission Project as the more efficient or cost-effective transmission solution to
the identified Public Policy Transmission Need, and (iv) will not result in a significant adverse
impact to the reliability of the New York State Transmission System. The NYISO’s
performance of this review shall not constitute its consent to delay the completion of any Critical
Path Milestone.
3.6.
Billing and Payment
The NYISO shall charge, and the Developer shall pay, the actual costs of: (i) any study
work performed by the NYISO or its subcontractor(s) under Articles 3.3, 3.4, and 3.5, or (ii) any
assessment of the Transmission Project by the NYISO or its subcontractor(s) under Article 3.8.
The NYISO will invoice Developer on a monthly basis for the expenses incurred by the NYISO
each month, including estimated subcontractor costs, computed on a time and material basis.
The Developer shall pay invoiced amounts to the NYISO within thirty (30) Calendar Days of the
NYISO’s issuance of a monthly invoice. In the event the Developer disputes an amount to be
paid, the Developer shall pay the disputed amount to the NYISO, pending resolution of the
dispute. To the extent the dispute is resolved in the Developer’s favor, the NYISO will net the
disputed amount, including interest calculated from Developer’s date of payment at rates
applicable to refunds under FERC regulations, against any current amounts due from the
Developer and pay the balance to the Developer. This Article 3.6 shall survive the termination,
expiration, or cancellation of this Agreement.
3.7.
Project Monitoring
The Developer shall provide regular status reports to the NYISO in accordance with the
monitoring requirements set forth in the Development Schedule, the Public Policy Transmission
Planning Process Manual and Attachment Y of the OATT.
3.8.
Right to Inspect
Upon reasonable notice, the NYISO or its subcontractor shall have the right to inspect the
Transmission Project for the purpose of assessing the progress of the development and
construction of the Transmission Project and satisfaction of milestones. The exercise or non-
exercise by the NYISO or its subcontractor of this right shall not be construed as an endorsement
or confirmation of any element or condition of the development or construction of the
Transmission Project, or as a warranty as to the fitness, safety, desirability or reliability of the
same. Any such inspection shall take place during normal business hours, shall not interfere
with the construction of the Transmission Project and shall be subject to such reasonable safety
and procedural requirements as the Developer shall specify.
3.9.
Exclusive Responsibility of Developer
As between the Parties, the Developer shall be solely responsible for all planning, design,
engineering, procurement, construction, installation, management, operations, safety, and
compliance with Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards associated with the Transmission Project, including,
but not limited to, scheduling, meeting Critical Path Milestones and Advisory Milestones, timely
requesting review and consent to any project modifications, and obtaining all necessary permits,
siting, and other regulatory approvals. The NYISO shall have no responsibility and shall have
no liability regarding the management or supervision of the Developer’s development of the
Transmission Project or the compliance of the Developer with Applicable Laws and Regulations,
Applicable Reliability Requirements, and Transmission Owner Technical Standards. The
NYISO shall cooperate with the Developer in good faith in providing information to assist the
Developer in obtaining all approvals and authorizations from Governmental Authorities required
to develop, construct, and operate the Transmission Project by the Required Project In-Service
Date, including, if applicable, information describing the NYISO’s basis for selecting the
Transmission Project as the more efficient or cost-effective transmission solution to satisfy an
identified Public Policy Transmission Need.
3.10. Subcontractors
3.10.1. Nothing in this Agreement shall prevent a Party from using the services of any
subcontractor as it deems appropriate to perform its obligations under this Agreement;
provided, however, that each Party shall require, and shall provide in its contracts with its
subcontractors, that its subcontractors comply with all applicable terms and conditions of
this Agreement in providing such services; provided, further, that each Party shall remain
primarily liable to the other Party for the performance of such subcontractor.
3.10.2. The creation of any subcontractor relationship shall not relieve the hiring Party of any of
its obligations under this Agreement. The hiring Party shall be fully responsible to the
other Party for the acts or omissions of any subcontractor the hiring Party hires as if no
subcontract had been made.
3.11. No Services or Products Under NYISO Tariffs
This Agreement does not constitute a request for, nor agreement by the NYISO to provide,
Transmission Service, interconnection service, Energy, Ancillary Services, Installed Capacity,
Transmission Congestion Contracts or any other services or products established under the ISO
Tariffs. If Developer wishes to receive or supply such products or services, the Developer must
make application to do so under the applicable provisions of the ISO Tariffs, ISO Related
Agreements, and ISO Procedures.
3.12. Tax Status
Each Party shall cooperate with the other Party to maintain each Party’s tax status to the
extent the Party’s tax status is impacted by this Agreement. Nothing in this agreement is
intended to affect the tax status of any Party.
ARTICLE 4. COORDINATION WITH THIRD PARTIES
4.1.
Interconnection Requirements for Transmission Project
The Developer shall satisfy all requirements set forth in the Transmission Interconnection
Procedures in Attachment P of the OATT applicable to a “Transmission Project” to interconnect
the Transmission Project to the New York State Transmission System by the Required Project
In-Service Date, including, but not limited to, submitting a Transmission Interconnection
Application; participating in all necessary studies; executing, and/or requesting the NYISO to
file for FERC acceptance, a Transmission Project Interconnection Agreement; and constructing,
or arranging for the construction of, all required Network Upgrade Facilities; provided, however,
if the Developer began the interconnection process in Attachment X of the OATT or the
transmission expansion process in Sections 3.7 or 4.5 of the OATT prior to the effective date of
the Transmission Interconnection Procedures, the Developer shall satisfy the requirements of the
Transmission Interconnection Procedures in accordance with the transition rules in Section
22.3.3 of Attachment P of the OATT..
If the NYISO determines that the proposed interconnection of a “Transmission Project”
under Attachment P could affect the Transmission Project under this Agreement, the Developer
shall participate in the Transmission Interconnection Procedures as an Affected System Operator
in accordance with the requirements set forth in Section 22.4.4 of Attachment P. If the NYISO
determines that the proposed interconnection of a “Large Generating Facility,” “Small
Generating Facility,” or “Merchant Transmission Facility” under Attachments X or Z of the
OATT could affect the Transmission Project, the Developer shall participate in the
interconnection process as an Affected System Operator in accordance with the requirements set
forth in Section 30.3.5 of Attachment X of the OATT. If the NYISO determines that a proposed
transmission expansion under Sections 3.7 and 4.5 of the OATT could affect the Transmission
Project, the Developer shall participate in the transmission expansion process as an affected
Transmission Owner in accordance with the requirements set forth in Sections 3.7 and 4.5 of the
OATT.
4.2.
Interconnection with Affected System
If part of the Transmission Project will affect the facilities of an Affected System as
determined in Attachment P of the OATT, the Developer shall satisfy the requirements of the
Affected System Operator for the interconnection of the Transmission Project.
4.3.
Coordination of Interregional Transmission Project
If the Transmission Project is or seeks to become an Interregional Transmission Project
selected by the NYISO and by the transmission provider in one or more neighboring
transmission planning region(s) to address an identified Public Policy Transmission Need, the
Developer shall coordinate its development and construction of the Transmission Project in New
York with its responsibilities in the relevant neighboring transmission planning region(s) and
must satisfy the applicable planning requirements of the relevant transmission planning
region(s).
ARTICLE 5. OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT
If the Developer is a Transmission Owner, the Developer shall comply with the operating
requirements set forth in the ISO/TO Agreement. If the Developer is not a Transmission Owner,
the Developer shall: (i) execute, and/or obtain a FERC accepted, interconnection agreement for
the Transmission Project in accordance with the requirements in Attachment P of the OATT; (ii)
satisfy the applicable requirements set forth in the interconnection agreement and ISO
Procedures for the safe and reliable operation of the Transmission Project consistent with the
Project Description set forth in Appendix A by the In-Service Date, including satisfying all
applicable testing, metering, communication, system protection, switching, start-up, and
synchronization requirements; (iii) enter into required operating protocols as determined by the
NYISO; (iv) register with NERC as a Transmission Owner, be certified as a Transmission
Operator unless otherwise agreed by the Parties, and comply with all NERC Reliability
Standards and Applicable Reliability Requirements applicable to Transmission Owners and
Transmission Operators; and (v) prior to energizing the Transmission Project, execute an
operating agreement with the NYISO.
ARTICLE 6. INSURANCE
The Developer shall, at its own expense, maintain in force throughout the period of this
Agreement, and until released by the NYISO, the following minimum insurance coverages, with
insurers authorized to do business in the state of New York and rated “A- (minus) VII” or better
by A.M. Best & Co. (or if not rated by A.M. Best & Co., a rating entity acceptable to the
NYISO):
6.1
Workers’ Compensation and Employers’ Liability Insurance providing statutory benefits
in accordance with the laws and regulations of New York State under NCCI Coverage Form No.
WC 00 00 00, as amended or supplemented from time to time, or an equivalent form acceptable
to the NYISO; provided, however, if the Transmission Project will be located in part outside of
New York State, Developer shall maintain such Employers’ Liability Insurance coverage with a
minimum limit of One Million Dollars ($1,000,000).
6.2
Commercial General Liability Insurance - under ISO Coverage Form No. CG 00 01
(04/13), as amended or supplemented from time to time, or an equivalent form acceptable to the
NYISO - with minimum limits of Two Million Dollars ($2,000,000) per occurrence/Four
Million Dollars ($4,000,000) aggregate combined single limit for personal injury, bodily injury,
including death and property damage.
6.3
Commercial Business Automobile Liability Insurance - under ISO Coverage Form No.
CA 00 01 10 13, as amended or supplemented from time to time, or an equivalent form
acceptable to the NYISO - for coverage of owned and non-owned and hired vehicles, trailers or
semi-trailers designed for travel on public roads, with a minimum, combined single limit of One
Million Dollars ($1,000,000) per occurrence for bodily injury, including death, and property
damage.
6.4
Umbrella/Excess Liability Insurance over and above the Employers’ Liability,
Commercial General Liability, and Commercial Business Automobile Liability Insurance
coverage, with a minimum combined single limit of Twenty-Five Million Dollars ($25,000,000)
per occurrence/Twenty-Five Million Dollars ($25,000,000) aggregate.
6.5
Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility
Practice.
6.6
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies of the Developer shall name the
NYISO and its respective directors, officers, agents, servants and employees (“NYISO Parties”)
as additional insureds. For Commercial General Liability Insurance, the Developer shall name
the NYISO Parties as additional insureds under the following ISO form numbers, as amended or
supplemented from time to time, or an equivalent form acceptable to the NYISO: (i) ISO
Coverage Form No. CG 20 37 04 13 (“Additional Insured - Owners, Lessees or Contractors -
Completed Operations”) and (ii) (A) ISO Coverage Form No. CG 20 10 04 13 (“Additional
Insured - Owner, Lessees or Contractors - Scheduled Person or Organization”), or (B) ISO
Coverage Form No. CG 20 26 04 13 (“Additional Insured - Designated Person or
Organization”). For Commercial Business Automobile Liability Insurance, the Developer shall
name the NYISO Parties as additional insureds under ISO Coverage Form No. CA 20 48 10 13
(“Designated Insured for Covered Autos Liability Coverage”), as amended or supplemented
from time to time, or an equivalent form acceptable to the NYISO.
6.7
All policies shall contain provisions whereby the insurers waive all rights of subrogation
in accordance with the provisions of this Agreement against the NYISO Parties and provide
thirty (30) Calendar days advance written notice to the NYISO Parties prior to non-renewal,
cancellation or any material change in coverage or condition.
6.8
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies shall contain provisions that specify
that the policies are primary and shall apply to such extent without consideration for other
policies separately carried and shall state that each insured is provided coverage as though a
separate policy had been issued to each, except the insurer’s liability shall not be increased
beyond the amount for which the insurer would have been liable had only one insured been
covered. The Developer shall be responsible for its respective deductibles or retentions.
6.9
The Commercial General Liability Insurance, Commercial Business Automobile Liability
Insurance and Umbrella/Excess Liability Insurance policies, if written on a Claims First Made
Basis in a form acceptable to the NYISO, shall be maintained in full force and effect for two (2)
years after termination of this Agreement, which coverage may be in the form of an extended
reporting period (ERP) or a separate policy, if agreed by the Developer and the NYISO.
6.10
The requirements contained herein as to the types and limits of all insurance to be
maintained by the Developer are not intended to and shall not in any manner, limit or qualify the
liabilities and obligations assumed by the Developer under this Agreement.
6.11
The Developer shall provide certification of all insurance required in this Agreement,
executed by each insurer or by an authorized representative of each insurer: (A) within ten (10)
days following: (i) execution of this Agreement, or (ii) the NYISO’s date of filing this
Agreement if it is filed unexecuted with FERC, and (B) as soon as practicable after the end of
each fiscal year or at the renewal of the insurance policy and in any event within thirty (30) days
thereafter.
6.12
Notwithstanding the foregoing, the Developer may self-insure to meet the minimum
insurance requirements of Articles 6.2 through 6.10 to the extent it maintains a self-insurance
program; provided that, the Developer’s senior debt is rated at investment grade, or better, by
Standard & Poor’s and that its self-insurance program meets the minimum insurance
requirements of Articles 6.2 through 6.10. For any period of time that the Developer’s senior
debt is unrated by Standard & Poor’s or is rated at less than investment grade by Standard &
Poor’s, the Developer shall comply with the insurance requirements applicable to it under
Articles 6.2 through 6.11. In the event that the Developer is permitted to self-insure pursuant to
this Article 6.12, it shall notify the NYISO that it meets the requirements to self-insure and that
its self-insurance program meets the minimum insurance requirements in a manner consistent
with that specified in Article 6.11.
6.13
The Developer and the NYISO agree to report to each other in writing as soon as
practical all accidents or occurrences resulting in injuries to any person, including death, and any
property damage arising out of this Agreement.
6.14
Notwithstanding the minimum insurance coverage types and amounts described in this
Article 6, the Developer: (i) shall also maintain any additional insurance coverage types and
amounts required under Applicable Laws and Regulations, including New York State law, and
under Good Utility Practice for the work performed by the Developer and its subcontractors
under this Agreement, and (ii) shall satisfy the requirements set forth in Articles 6.6 through 6.13
with regard to the additional insurance coverages, including naming the NYISO Parties as
additional insureds under these policies.
ARTICLE 7. BREACH AND DEFAULT
7.1.
Breach
A Breach of this Agreement shall occur when: (i) the Developer notifies the NYISO in
writing that it will not proceed to develop the Transmission Project for reasons other than those
set forth in Articles 8.1(i) through (iv); (ii) the Developer fails to meet a Critical Path Milestone,
as the milestone may be extended with the agreement of the NYISO under Article 3.3.4 of this
Agreement, set forth in the Development Schedule in Appendix C to this Agreement; (iii) the
Developer makes a Significant Modification to the Transmission Project without the prior
written consent of the NYISO; (iv) the Developer fails to pay a monthly invoice within the
timeframe set forth in Article 3.6; (v) the Developer misrepresents a material fact of its
representations and warranties set forth in Article 12; (vi) a Party assigns this Agreement in a
manner inconsistent with the terms of Article 10 of this Agreement; (vii) the Developer fails to
comply with any other material term or condition of this Agreement; (viii) a custodian, receiver,
trustee or liquidator of the Developer, or of all or substantially all of the assets of the Developer,
is appointed in any proceeding brought by the Developer; or (ix) any such custodian, receiver,
trustee, or liquidator is appointed in any proceeding brought against the Developer that is not
discharged within ninety (90) Days after such appointment, or if the Developer consents to or
acquiesces in such appointment. A Breach shall not occur as a result of a Force Majeure event in
accordance with Article 15.5. A Breach shall also not occur as a result of a delay caused by a
Connecting Transmission Owner or an Affected System Operator.
7.2.
Default
Upon a Breach, the non-Breaching Party shall give written notice of the Breach to the
Breaching Party describing in reasonable detail the nature of the Breach and, where known and
applicable, the steps necessary to cure such Breach, including whether and what such steps must
be accomplished to complete the Transmission Project by the Required Project In-Service Date.
The Breaching Party shall have thirty (30) Calendar Days from receipt of the Breach notice to
cure the Breach, or such other period of time as may be agreed upon by the Parties, which
agreement the NYISO will not unreasonably withhold, condition, or delay if it determines a
longer cure period will not threaten the Developer’s ability to complete the Transmission Project
by the Required Project In-Service Date; provided, however, that if the Breach is the result of a
Developer’s inability or failure to meet a Critical Path Milestone, the Developer may only cure
the Breach if either: (i) it meets the Critical Path Milestone within the cure period and
demonstrates to the NYISO’s satisfaction that, notwithstanding its failure to timely meet the
Critical Path Milestone, the Transmission Project will achieve its In-Service Date no later than
the Required Project In-Service Date, or (ii) the Developer requests in writing within the cure
period, and the NYISO consents to, a change to the missed Critical Path Milestone in accordance
with Article 3.3.4. If the Breach is cured within such timeframe, the Breach specified in the
notice shall cease to exist. If the Breaching Party does not cure its Breach within this timeframe
or cannot cure the Breach in a manner that provides for the Transmission Project to be completed
by the Required Project In-Service Date, the non-Breaching Party shall have the right to declare
a Default and terminate this Agreement pursuant to Article 8.1.
7.3.
Remedies
Upon the occurrence of an event of Default, the non-defaulting Party shall be entitled: (i)
to commence an action to require the defaulting Party to remedy such Default and specifically
perform its duties and obligations hereunder in accordance with the terms and conditions hereof;
and (ii) to exercise such other rights and remedies as it may have in equity or at law; provided,
however, the defaulting Party’s liability under this Agreement shall be limited to the extent set
forth in Article 9.1. No remedy conferred by any provision of this Agreement is intended to be
exclusive of any other remedy and each and every remedy shall be cumulative and shall be in
addition to every other remedy given hereunder or now or hereafter existing at law or in equity
or by statute or otherwise. The election of any one or more remedies shall not constitute a
waiver of the right to pursue other available remedies. This Article 7.3 shall survive the
termination, expiration, or cancellation of this Agreement.
ARTICLE 8. TERMINATION
8.1.
Termination by the NYISO
The NYISO may terminate this Agreement by providing written notice of termination to
the Developer in the event that: (i) the Developer notifies the NYISO that it is unable to or has
not received the required approvals or authorizations by Governmental Authorities required to
develop, construct, and operate the Transmission Project by the Required Project In-Service
Date; (ii) the Developer notifies the NYISO that its required approvals or authorizations by
Governmental Authorities have been withdrawn by the Governmental Authorities; (iii) the
Developer cannot complete the Transmission Project by the Required Project In-Service Date for
any reason: (A) including the occurrence of a Force Majeure event that will prevent the
Developer from completing the Transmission Project by the Required Project In-Service Date,
but (B) excluding a delay caused by a Connecting Transmission Owner or an Affected System
Operator; or (iv) the NYISO declares a default pursuant to Article 7.2 of this Agreement.
If the NYISO identifies grounds for termination under Articles 8.1(iii) or (iv) or receives
notice from the Developer under Articles 8.1(i) or (ii), the NYISO may, prior to providing a
written notice of termination, take action in accordance with Section 31.4.12.3.1.3 of Attachment
Y of the OATT to address the Public Policy Transmission Need and, notwithstanding the
confidentiality provisions in Article 11.2, may disclose information regarding the Transmission
Project to Governmental Authorities as needed to implement such action. If the NYISO decides
to terminate this Agreement under Article 8.1(i), (ii), (iii), or (iv), it will provide written notice of
termination to the Developer, which notice will specify the date of termination. If the
Agreement was filed and accepted by FERC pursuant to Section 31.4.12.2 of Attachment Y of
the OATT, the NYISO will, following its provision of a notice of termination to the Developer,
promptly file with FERC for its acceptance a notice of termination of this Agreement.
In the event of termination under Articles 8.1 (i) or (ii), the Developer may be eligible for
cost recovery under the OATT in the manner set forth in Attachment Y and Schedule 10 of the
OATT. In the event of termination under Articles 8.1(iii) or (iv), cost recovery may be permitted
as determined by FERC. In the event of termination for any reason under this Article 8.1, the
Developer shall use commercially reasonable efforts to mitigate the costs, damages, and charges
arising as a consequence of termination and any transfer or winding up of the Transmission
Project.
8.2.
Reporting of Inability to Comply with Provisions of Agreement
Notwithstanding the notification requirements in Article 3 and this Article 8 of this
Agreement, each Party shall notify the other Party promptly upon the notifying Party becoming
aware of its inability to comply with any provision of this Agreement. The Parties agree to
cooperate with each other and provide necessary information regarding such inability to comply,
including the date, duration, reason for inability to comply, and corrective actions taken or
planned to be taken with respect to such inability to comply.
8.3.
Transmission Project Transfer Rights Upon Termination
If the NYISO terminates this Agreement pursuant to Article 8.1, the NYISO shall have
the right, but shall not be required, to request an entity other than the Developer to complete the
Transmission Project. The NYISO may exercise this right by providing the Developer with
written notice within sixty (60) days after the date on which this Agreement is terminated. If the
NYISO exercises its right under this Article 8.3 and Section 31.4.12.3.1.3 of Attachment Y of
the OATT, the Developer shall work cooperatively with the NYISO’s designee pursuant to the
requirements set forth in Section 31.4.12.3.1.4 of Attachment Y of the OATT to implement the
transition, including entering into good faith negotiations with the NYISO’s designee to transfer
the Transmission Project to the NYISO’s designee. All liabilities under this Agreement existing
prior to such transfer shall remain with the Developer, unless otherwise agreed upon by the
Developer and the NYISO’s designee as part of their good faith negotiations regarding the
transfer. This Article 8.3 shall survive the termination, expiration, or cancellation of this
Agreement.
ARTICLE 9. LIABILITY AND INDEMNIFICATION
9.1.
Liability
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, neither Party shall be liable, whether based on contract, indemnification, warranty,
equity, tort, strict liability, or otherwise, to the Other Party or any Transmission Owner, NYISO
Market Participant, third party or any other person for any damages whatsoever, including,
without limitation, direct, incidental, consequential (including, without limitation, attorneys’ fees
and litigation costs), punitive, special, multiple, exemplary, or indirect damages arising or
resulting from any act or omission under this Agreement, except in the event the Party is found
liable for gross negligence or intentional misconduct in the performance of its obligations under
this Agreement, in which case the Party’s liability for damages shall be limited only to direct
actual damages. This Article 9.1 shall survive the termination, expiration, or cancellation of this
Agreement.
9.2.
Indemnity
Notwithstanding any other provision in the NYISO’s tariffs and agreements to the
contrary, each Party shall at all times indemnify and save harmless, as applicable, the other
Party, its directors, officers, employees, trustees, and agents or each of them from any and all
damages (including, without limitation, any consequential, incidental, direct, special, indirect,
exemplary or punitive damages and economic costs), losses, claims, including claims and actions
relating to injury to or death of any person or damage to property, liabilities, judgments,
demands, suits, recoveries, costs and expenses, court costs, attorney and expert fees, and all other
obligations by or to third parties, arising out of, or in any way resulting from this Agreement,
provided, however, that the Developer shall not have any indemnification obligation under this
Article 9.2 with respect to any loss to the extent the loss results from the negligence or
intentional misconduct of the NYISO; provided, further, that the NYISO shall not have any
indemnification obligation under this Article 9.2 with respect to any loss to the extent the loss
results from the negligence or intentional misconduct of the Developer. This Article 9.2 shall
survive the termination, expiration, or cancellation of this Agreement.
ARTICLE 10.
ASSIGNMENT
This Agreement may be assigned by a Party only with the prior written consent of the
other Party; provided that:
(i) any Change of Control shall be considered an assignment under this Article 10 and
shall require the other Party’s prior written consent;
(ii) an assignment by the Developer shall be contingent upon the Developer or assignee
demonstrating to the satisfaction of the NYISO prior to the effective date of the
assignment that: (A) the assignee has the technical competence, financial ability, and
materials, equipment, and plans to comply with the requirements of this Agreement and
to construct and place in service the Transmission Project by the Required Project In-
Service Date consistent with the assignor’s cost estimates for the Transmission Project;
and (B) the assignee satisfies the requirements for a qualified developer pursuant to
Section 31.4.4 of Attachment Y of the OATT; and
(iii) the Developer shall have the right to assign this Agreement, without the consent of
the NYISO, for collateral security purposes to aid in providing financing for the
Transmission Project and shall promptly notify the NYISO of any such assignment;
provided, however, that such assignment shall be subject to the following: (i) prior to or
upon the exercise of the secured creditor’s, trustee’s, or mortgagee’s assignment rights
pursuant to said arrangement, the secured creditor, the trustee, or the mortgagee will
notify the NYISO of the date and particulars of any such exercise of assignment right(s),
and (ii) the secured creditor, trustee, or mortgagee must demonstrate to the satisfaction of
the NYISO that any entity that it proposes to complete the Transmission Project meets
the requirements for the assignee of a Developer described in Article 10(ii).
For all assignments by any Party, the assignee must assume in a writing, to be provided to
the other Party, all rights, duties, and obligations of the assignor arising under this Agreement,
including the insurance requirements in Article 6 of this Agreement. Any assignment under this
Agreement shall not relieve a Party of its obligations, nor shall a Party’s obligations be enlarged,
in whole or in part, by reasons thereof, absent the written consent of the other Party. Where
required, consent to assignment will not be unreasonably withheld, conditioned, or delayed. Any
attempted assignment that violates this Article 10 is void and ineffective, is a Breach of this
Agreement under Article 7.1 and may result in the termination of this Agreement under Articles
8.1 and 7.2.
ARTICLE 11.
INFORMATION EXCHANGE AND CONFIDENTIALITY
11.1. Information Access
Subject to Applicable Laws and Regulations, each Party shall make available to the other
Party information necessary to carry out obligations and responsibilities under this Agreement
and Attachment Y of the OATT. The Parties shall not use such information for purposes other
than to carry out their obligations or enforce their rights under this Agreement or Attachment Y
of the OATT.
11.2. Confidentiality
11.2.1. Confidential Information shall mean: (i) all detailed price information and vendor
contracts; (ii) any confidential and/or proprietary information provided by one Party to
the other Party that is clearly marked or otherwise designated “Confidential Information”;
and (iii) information designated as Confidential Information by the NYISO Code of
Conduct contained in Attachment F of the OATT; provided, however, that Confidential
Information does not include information: (i) in the public domain or that has been
previously publicly disclosed; (ii) required by an order of a Governmental Authority to be
publicly submitted or divulged (after notice to the other Party); or (iii) necessary to be
divulged in an action to enforce this Agreement.
11.2.2. The NYISO shall treat any Confidential Information it receives in accordance with the
requirements of the NYISO Code of Conduct contained in Attachment F of the OATT. If
the Developer receives Confidential Information, it shall hold such information in
confidence, employing at least the same standard of care to protect the Confidential
Information obtained from the NYISO as it employs to protect its own Confidential
Information. Each Party shall not disclose the other Party’s Confidential Information to
any third party or to the public without the prior written authorization of the Party
providing the information, except: (i) to the extent required for the Parties to perform
their obligations under this Agreement, the ISO Tariffs, ISO Related Agreements, or ISO
Procedures, or (ii) to fulfill legal or regulatory requirements, provided that if the Party
must submit the information to a Governmental Authority in response to a request by the
Governmental Authority on a confidential basis, the Party required to disclose the
information shall request under applicable rules and regulations that the information be
treated as confidential and non-public by the Governmental Authority.
ARTICLE 12.
REPRESENTATIONS, WARRANTIES AND COVENANTS
12.1. General
The Developer makes the following representations, warranties, and covenants, which are
effective as to the Developer during the full time this Agreement is effective:
12.2. Good Standing
The Developer is duly organized, validly existing and in good standing under the laws of
the state in which it is organized, formed, or incorporated, as applicable. The Developer is
qualified to do business in the state or states in which the Transmission Project is located. The
Developer has the corporate power and authority to own its properties, to carry on its business as
now being conducted and to enter into this Agreement and carry out the transactions
contemplated hereby and to perform and carry out covenants and obligations on its part under
and pursuant to this Agreement.
12.3. Authority
The Developer has the right, power, and authority to enter into this Agreement, to
become a Party hereto, and to perform its obligations hereunder. This Agreement is a legal,
valid, and binding obligation of the Developer, enforceable against the Developer in accordance
with its terms, except as the enforceability thereof may be limited by applicable bankruptcy,
insolvency, reorganization, or other similar laws affecting creditors’ rights generally and by
general equitable principles (regardless of whether enforceability is sought in a proceeding in
equity or at law).
12.4. No Conflict
The execution, delivery and performance of this Agreement does not violate or conflict
with the organizational or formation documents, or bylaws or operating agreement, of the
Developer, or any judgment, license, permit, order, material agreement or instrument applicable
to or binding upon the Developer or any of its assets.
12.5. Consent and Approval
The Developer has sought or obtained, or, in accordance with this Agreement will seek or
obtain, such consent, approval, authorization, order, or acceptance by any Governmental
Authority in connection with the execution, delivery and performance of this Agreement, and it
will provide to any Governmental Authority notice of any actions under this Agreement that are
required by Applicable Laws and Regulations.
12.6. Compliance with All Applicable Laws and Regulations
The Developer will comply with all Applicable Laws and Regulations, including all
approvals, authorizations, orders, and permits issued by any Governmental Authority; all
Applicable Reliability Requirements, and all applicable Transmission Owner Technical
Standards in the performance of its obligations under this Agreement.
ARTICLE 13.
DISPUTE RESOLUTION
If a dispute arises under this Agreement, the Parties shall use the dispute resolution
process described in Article 11 of the NYISO’s Services Tariff, as such process may be amended
from time to time. Notwithstanding the process described in Article 11 of the NYISO’s Services
Tariff, the NYISO may terminate this Agreement in accordance with Article 8 of this
Agreement.
ARTICLE 14.
SURVIVAL
The rights and obligations of the Parties in this Agreement shall survive the termination,
expiration, or cancellation of this Agreement to the extent necessary to provide for the
determination and enforcement of said obligations arising from acts or events that occurred while
this Agreement was in effect. The remedies and rights and obligation upon termination
provisions in Articles 7.3 and 8.3 of this Agreement, the liability and indemnity provisions in
Article 9, and the billing and payment provisions in Article 3.6 of this Agreement shall survive
termination, expiration, or cancellation of this Agreement.
ARTICLE 15.
MISCELLANEOUS
15.1. Notices
Any notice or request made to or by any Party regarding this Agreement shall be made to
the Parties, as indicated below:
NYISO:
[Insert contact information.]
Developer:
[Insert contact information.]
15.2. Entire Agreement
Except as described below in this Section 15.2, this Agreement, including all Appendices
attached hereto, constitutes the entire agreement between the Parties with reference to the subject
matter hereof, and supersedes all prior and contemporaneous understandings of agreements, oral
or written, between the Parties with respect to the subject matter of this Agreement. There are no
other agreements, representations, warranties, or covenants that constitute any part of the
consideration for, or any condition to, either Party’s compliance with its obligation under this
Agreement.
Notwithstanding the foregoing, this Agreement is in addition to, and does not supersede
or limit the Developer’s and NYISO’s rights and responsibilities, under any interconnection
agreement(s) entered into by and among the NYISO, Developer, and Connecting Transmission
Owner(s) for the Transmission Project to interconnect to the New York State Transmission
System, as such interconnection agreements may be amended, supplemented, or modified from
time to time.
15.3. Cost Recovery
The Developer may recover the costs of the Transmission Project in accordance with the
cost recovery requirements in the ISO Tariffs.
15.4. Binding Effect
This Agreement, and the rights and obligations hereof, shall be binding upon and shall
inure to the benefit of the successors and permitted assigns of the Parties hereto.
15.5. Force Majeure
A Party that is unable to carry out an obligation imposed on it by this Agreement due to
Force Majeure shall notify the other Party in writing as soon as reasonably practicable after the
occurrence of the Force Majeure event and no later than the timeframe set forth in Article
3.3.3(i) if the Force Majeure event will result in a potential delay for the Developer to meet a
Critical Path Milestone. If the notifying Party is the Developer, it shall indicate in its notice
whether the occurrence of a Force Majeure event has the potential to delay its meeting one or
more Critical Path Milestones and/or completing the Transmission Project by the Required
Project In-Service Date. If the Force Majeure will delay the Developer’s ability to meet one or
more Critical Path Milestones, the Developer shall request with its notice a change to the
impacted milestones in accordance with the requirements in Section 3.3.4 and must satisfy the
requirements in Section 3.3.4 to change any Critical Path Milestones. A Party shall not be
responsible for any non-performance or considered in Breach or Default under this Agreement,
for any failure to perform any obligation under this Agreement to the extent that such failure is
due to Force Majeure and will not delay the Developer’s ability to complete the Transmission
Project by the Required Project In-Service Date. A Party shall be excused from whatever
performance is affected only for the duration of the Force Majeure and while the Party exercises
reasonable efforts to alleviate such situation. As soon as the nonperforming Party is able to
resume performance of its obligations excused because of the occurrence of Force Majeure, such
Party shall resume performance and give prompt notice thereof to the other Party. In the event
that Developer will not be able to complete the Transmission Project by the Required Project In-
Service Date because of the occurrence of Force Majeure, the NYISO may terminate this
Agreement in accordance with Section 8.1 of this Agreement.
15.6. Disclaimer
Except as provided in this Agreement, the Parties make no other representations,
warranties, covenants, guarantees, agreements or promises regarding the subject matter of this
Agreement.
15.7. No NYISO Liability for Review or Approval of Developer Materials
No review or approval by the NYISO or its subcontractor(s) of any agreement, document,
instrument, drawing, specifications, or design proposed by the Developer nor any inspection
carried out by the NYISO or its subcontractor(s) pursuant to this Agreement shall relieve the
Developer from any liability for any negligence in its preparation of such agreement, document,
instrument, drawing, specification, or design, or its carrying out of such works; or for its failure
to comply with the Applicable Laws and Regulations, Applicable Reliability Requirements, and
Transmission Owner Technical Standards with respect thereto, nor shall the NYISO be liable to
the Developer or any other person by reason of its or its subcontractor’s review or approval of an
agreement, document, instrument, drawing, specification, or design or such inspection.
15.8. Amendment
The Parties may by mutual agreement amend this Agreement, including the Appendices
to this Agreement, by a written instrument duly executed by both of the Parties. If the
Agreement was filed and accepted by FERC pursuant to Section 31.4.12.2 of Attachment Y of
the OATT, the NYISO shall promptly file the amended Agreement for acceptance with FERC.
15.9. No Third Party Beneficiaries
With the exception of the indemnification rights of the NYISO’s directors, officers,
employees, trustees, and agents under Article 9.2, this Agreement is not intended to and does not
create rights, remedies, or benefits of any character whatsoever in favor of any persons,
corporations, associations, or entities other than the Parties, and the obligations herein assumed
are solely for the use and benefit of the Parties, their successors in interest and their permitted
assigns.
15.10. Waiver
The failure of a Party to this Agreement to insist, on any occasion, upon strict
performance of any provision of this Agreement will not be considered a waiver of any
obligation, right, or duty of, or imposed upon, such Party. Any waiver at any time by either
Party of its rights with respect to this Agreement shall not be deemed a continuing waiver or a
waiver with respect to any other failure to comply with any other obligation, right, or duty of this
Agreement. Any waiver of this Agreement shall, if requested, be provided in writing.
15.11. Rules of Interpretation
This Agreement, unless a clear contrary intention appears, shall be construed and
interpreted as follows: (1) the singular number includes the plural number and vice versa; (2)
reference to any person includes such person’s successors and assigns but, in the case of a Party,
only if such successors and assigns are permitted by this Agreement, and reference to a person in
a particular capacity excludes such person in any other capacity or individually; (3) reference to
any agreement (including this Agreement), document, instrument or tariff means such
agreement, document, instrument, or tariff as amended or modified and in effect from time to
time in accordance with the terms thereof and, if applicable, the terms hereof; (4) reference to
any Applicable Laws and Regulations means such Applicable Laws and Regulations as
amended, modified, codified, or reenacted, in whole or in part, and in effect from time to time,
including, if applicable, rules and regulations promulgated thereunder; (5) unless expressly stated
otherwise, reference to any Article, Section or Appendix means such Article of this Agreement,
such Appendix to this Agreement, or such Section of this Agreement, as the case may be; (6)
“hereunder”, “hereof’, “herein”, “hereto” and words of similar import shall be deemed references
to this Agreement as a whole and not to any particular Article or other provision hereof or
thereof; (7) “including” (and with correlative meaning “include”) means including without
limiting the generality of any description preceding such term; and (8) relative to the
determination of any period of time, “from” means “from and including”, “to” means “to but
excluding” and “through” means “through and including”.
15.12. Severability
Each provision of this Agreement shall be considered severable and if, for any reason,
any provision is determined by a court or regulatory authority of competent jurisdiction to be
invalid, void, or unenforceable, the remaining provisions of this Agreement shall continue in full
force and effect and shall in no way be affected, impaired, or invalidated, and such invalid, void,
or unenforceable provision should be replaced with valid and enforceable provision or provisions
that otherwise give effect to the original intent of the invalid, void, or unenforceable provision.
15.13. Multiple Counterparts
This Agreement may be executed in two or more counterparts, each of which is deemed
an original, but all constitute one and the same instrument.
15.14. No Partnership
This Agreement shall not be interpreted or construed to create an association, joint
venture, agency relationship, or partnership among the Parties or to impose any partnership
obligation or partnership liability upon any Party. No Party shall have any right, power, or
authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an
agent or representative of, or otherwise bind, any other Party.
15.15. Headings
The descriptive headings of the various Articles and Sections of this Agreement have
been inserted for convenience of reference only and are of no significance in the interpretation or
construction of this Agreement.
15.16. Governing Law
This Agreement shall be governed, as applicable, by: (i) the Federal Power Act, and (ii)
the substantive law of the State of New York, without regard to any conflicts of laws provisions
thereof (except to the extent applicable, Sections 5-1401 and 5-1402 of the New York General
Obligations Law).
15.17. Jurisdiction and Venue
Any legal action or judicial proceeding regarding a dispute arising out of or relating to
this Agreement or any performance by either Party pursuant thereto that: (i) is within the primary
or exclusive jurisdiction of FERC shall be brought in the first instance at FERC, or (ii) is not
within the primary or exclusive jurisdiction of FERC shall be brought in, and fully and finally
resolved in, either, as applicable, the courts of the State of New York situated in Albany County,
New York or the United States District Court of the Northern District of New York situated in
Albany, New York.
IN WITNESS WHEREFORE, the Parties have executed this Agreement in duplicate originals,
each of which shall constitute an original Agreement between the Parties.
NYISO
By: _______________________
Title:______________________
Date:______________________
[Insert name of Developer]
By:_______________________
Title:______________________
Date:______________________
Appendix A
Project Description
Appendix C
Development Schedule
[To be prepared by Developer consistent with the Developer’s project information submission,
pursuant to Attachment C of the Public Policy Transmission Planning Process Manual, and
subject to acceptance by the NYISO, as required by Article 3.3 of this Agreement.]
The Developer shall demonstrate to the NYISO that it timely meets the following Critical
Path Milestones and Advisory Milestones and that such milestones remain in good standing.
Critical Path Milestones: [To be developed with consideration of each of the work plan
requirements submitted by the Developer pursuant to Attachment C to the Public Policy
Transmission Planning Process Manual and presented herein according to the sequence of the
critical path. The NYISO anticipates that the Developer’s critical path schedule will include
many of the example milestones set forth below and that most of the other example milestones
will be included as Advisory Milestones. The composition and sequence of the Critical Path
Milestones will differ depending on the Developer’s Transmission Project and schedule.]
Advisory Milestones: [To include in Development Schedule other milestones (e.g., periodic
project review meetings) that are not determined to be on the critical path, but that will be
monitored by the Developer and reported to NYISO.]
[Example Milestones:
Interconnection studies (e.g. Optional Feasibility Study, System Impact Study, Facilities
Study)
Siting activities (e.g. locating line routing, access roads, and substation site location
options)
Environmental impact studies (relative to siting options)
Engineering (initial)
Permitting and regulatory activities (e.g. Certificate of Environmental Compatibility and
Public Need)
Public outreach plan
Initiation of negotiation of key contracts and financing
Acquisition of all necessary approvals and authorizations of Governmental Authorities,
including identification of all required regulatory approvals
Closing of project financing
Completion of key contracts
Engineering (detailed)
Procurement of major equipment and materials
Environmental management & construction plan (for Article VII certification)
Acquisition of [all or %] required rights of way and property / demonstration of site
control
Surveying and geotechnical assessment (relative to line and station layouts)
Execution, or filing of unexecuted version, of interconnection agreement
Engineering (completed)
Delivery of major electrical equipment
Line and substation site work including milestones for foundations, towers, conductor
stringing, equipment delivery and installation, substation controls and communication,
security, etc.
Construction outage and restoration coordination plan
Completion, verification and testing
Operating and maintenance agreements and instructions
In-Service Date
Required Project In-Service Date]