NYISO Tariffs --> Open Access Transmission Tariff (OATT) --> 31 OATT Att Y New York ISO Comprehensive System Planning Pro --> 31.7 OATT Att Y Appendices A-D

31.7Appendices


APPENDIX A –               REPORTING OF HISTORIC AND PROJECTED CONGESTION

1.0General

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.0Historic Congestion Reporting

The ISO will report historic Day-Ahead Market congestion-related data.  The following elements of historic congestion-related data will be reported: (i) LBMP load costs (energy, congestion and losses) by Load Zone; (ii) LBMP payments to generators (energy, congestion and losses) by Load Zone; (iii) congestion cost by constraint; and (iv) congestion cost of each constraint to load (commonly referred to in the Economic Planning ProcessCARIS as “demand dollar congestion” by constraint). 

3.0Analysis

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 the System & Resource Outlookeconomic 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.0Detailed 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.0Summary Reports

The ISO will prepare various reports of historic and projected congestion costs. Historic congestion reports will be based upon the actual congestion-related data from the Day-Ahead Market, and will include the information required by Section 2.0 of this Appendix A to Attachment Y of the ISO OATT.  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. 

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-EvaluationCARIS Centralized TCC Auction:  The last Centralized TCC Auction that had been completed as of the date the input assumptions were determined for the Economic Transmission Project EvaluationCARIS in which the Project was identified as a candidate for development under the provisions of this Attachment Y.

Project:  The proposed Regulated Economic tTransmission pProject 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-EvaluationCARIS 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-EvaluationCARIS 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-EvaluationCARIS Centralized TCC Auction to

(ii) the total amount of residual auction revenue allocated in the Pre-EvaluationCARIS 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

ARTICLE 1. DEFINITIONS

ARTICLE 2.EFFECTIVE DATE AND TERM

2.1.Effective Date

2.2.Filing

2.3.Term of Agreement

ARTICLE 3.TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION

3.1.Application for Required Authorizations and Approvals

3.2.Development and Construction of Transmission Project

3.3.Milestones

3.4.Modifications to Transmission Project

3.5.Billing and Payment

3.6.Project Monitoring

3.7.Right to Inspect

3.8.Exclusive Responsibility of Developer

3.9.Subcontractors

3.10.No Services or Products Under NYISO Tariffs

3.11.Tax Status

ARTICLE 4.COORDINATION WITH THIRD PARTIES

4.1.Interconnection Requirements for Transmission Project

4.2.Interconnection with Affected System

4.3.Coordination of Interregional Transmission Project

ARTICLE 5.OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT

ARTICLE 6.INSURANCE

ARTICLE 7.BREACH AND DEFAULT

7.1.Breach

7.2.Default

7.3.Remedies

ARTICLE 8.TERMINATION

8.1.Termination by the NYISO

8.2.Reporting of Inability to Comply with Provisions of Agreement

8.3.Transmission Project Transfer Rights Upon Termination

ARTICLE 9.LIABILITY AND INDEMNIFICATION

9.1.Liability

9.2.Indemnity

ARTICLE 10.ASSIGNMENT

ARTICLE 11.INFORMATION EXCHANGE AND CONFIDENTIALITY

11.1.Information Access

11.2.Confidentiality

ARTICLE 12.REPRESENTATIONS, WARRANTIES AND COVENANTS

12.1.General

12.2.Good Standing

12.3.Authority

12.4.No Conflict

12.5.Consent and Approval

12.6.Compliance with All Applicable Laws and Regulations

ARTICLE 13.DISPUTE RESOLUTION

ARTICLE 14.SURVIVAL

ARTICLE 15.MISCELLANEOUS

15.1.Notices

15.2.Entire Agreement

15.3.Cost Recovery

15.4.Binding Effect

15.5.Force Majeure

15.6.Disclaimer

15.7.No NYISO Liability for Review or Approval of Developer Materials

15.8.Amendment

15.9.No Third Party Beneficiaries

15.10.Waiver

15.11.Rules of Interpretation

15.12.Severability

15.13.Multiple Counterparts

15.14.No Partnership

15.15.Headings

15.16.Governing Law

15.17.Jurisdiction and Venue

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.

ISO/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.

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.

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 “Class Year Transmission Project” 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.1Workers’ 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.2Commercial 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.3Commercial 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.4Umbrella/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.5Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility Practice.

6.6The 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.7All 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.8The 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.9The 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.10The 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.11The 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.12Notwithstanding 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.13The 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.14Notwithstanding 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.  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 gross negligence or intentional misconduct of the NYISO; provided, further, that the NYISO shall only have an indemnification obligation under this Article 9.2 with respect to any loss resulting from its gross negligence or intentional misconduct to the same extent as provided in Section 2.11.3(b) of the ISO OATT.  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.1Confidential 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.2The 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 ISO/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 B – Scope of Work


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

ARTICLE 1.DEFINITIONS

ARTICLE 2.EFFECTIVE DATE AND TERM

2.1.Effective Date

2.2.Filing

2.3.Term of Agreement

ARTICLE 3.TRANSMISSION PROJECT DEVELOPMENT AND CONSTRUCTION

3.1.Application for Required Authorizations and Approvals

3.2.Development and Construction of Transmission Project

3.3.Milestones

3.4.Modifications to Required Project In-Service Date

3.5.Modifications to Transmission Project

3.6.Billing and Payment

3.7.Project Monitoring

3.8.Right to Inspect

3.9.Exclusive Responsibility of Developer

3.10.Subcontractors

3.11.No Services or Products Under NYISO Tariffs

3.12.Tax Status

ARTICLE 4.COORDINATION WITH THIRD PARTIES

4.1.Interconnection Requirements for Transmission Project

4.2.Interconnection with Affected System

4.3.Coordination of Interregional Transmission Project

ARTICLE 5.OPERATION REQUIREMENTS FOR THE TRANSMISSION PROJECT

ARTICLE 6.INSURANCE

ARTICLE 7.BREACH AND DEFAULT

7.1.Breach

7.2.Default

7.3.Remedies

ARTICLE 8.TERMINATION

8.1.Termination by the NYISO

8.2.Reporting of Inability to Comply with Provisions of Agreement

8.3.Transmission Project Transfer Rights Upon Termination

ARTICLE 9.LIABILITY AND INDEMNIFICATION

9.1.Liability

9.2.Indemnity

ARTICLE 10.ASSIGNMENT

ARTICLE 11.INFORMATION EXCHANGE AND CONFIDENTIALITY

11.1.Information Access

11.2.Confidentiality

ARTICLE 12.REPRESENTATIONS, WARRANTIES AND COVENANTS

12.1.General

12.2.Good Standing

12.3.Authority

12.4.No Conflict

12.5.Consent and Approval

12.6.Compliance with All Applicable Laws and Regulations

ARTICLE 13.DISPUTE RESOLUTION

ARTICLE 14.SURVIVAL

ARTICLE 15.MISCELLANEOUS

15.1.Notices

15.2.Entire Agreement

15.3.Cost Recovery

15.4.Binding Effect

15.5.Force Majeure

15.6.Disclaimer

15.7.No NYISO Liability for Review or Approval of Developer Materials

15.8.Amendment

15.9.No Third Party Beneficiaries

15.10.Waiver

15.11.Rules of Interpretation

15.12.Severability

15.13.Multiple Counterparts

15.14.No Partnership

15.15.Headings

15.16.Governing Law

15.17.Jurisdiction and Venue

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 “Class Year Transmission Project” 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.1Workers’ 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.2Commercial 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.3Commercial 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.4Umbrella/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.5Builder’s Risk Insurance in a reasonably prudent amount consistent with Good Utility Practice.

6.6The 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.7All 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.8The 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.9The 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.10The 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.11The 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.12Notwithstanding 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.13The 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.14Notwithstanding 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 file with the Commission any Cost Cap the Developer submitted to the NYISO with its Public Policy Transmission Project and agreed to in this Agreement or seeks to recover through its transmission rates for the Transmission Project or through any other means costs for the Included Capital Costs (as defined in Section 31.4.5.1.8.1 of the ISO OATT) above its Cost Cap, except as permitted for excusing conditions in Section 6.10.6.2 of the ISO OATT and Article 15.3 of this Agreement; (viii) the Developer fails to comply with any other material term or condition of this Agreement; (ix) 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 (x) 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 gross negligence or intentional misconduct of the NYISO; provided, further, that the NYISO shall only have an indemnification obligation under this Article 9.2 with respect to any loss resulting from its gross negligence or intentional misconduct to the same extent as provided in Section 2.11.3(b) of the ISO OATT.  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, the cost recovery provisions in Article 15.3 and Appendix D, 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.  If the Developer submitted a Cost Cap for the Included Capital Costs (as defined in Section 31.4.5.1.8.1 of the ISO OATT) of the Transmission Project pursuant to Section 31.4.5.1 of the ISO OATT, the Developer’s Cost Cap for the Included Capital Costs shall be detailed in Appendix D of this Agreement, which description shall include the Cost Cap in the Developer’s project proposal.  Developer agrees to file this Cost Cap for Included Capital Costs with the Commission in accordance with the requirements in Rate Schedule 10 of the ISO OATT.  If the Cost Cap is a soft Cost Cap, Developer agrees to implement the Cost Cap in accordance with Section 6.10.6.3 of Rate Schedule 10.  The Developer further agrees in accordance with Rate Schedule 10 of the OATT that it shall not seek to recover through its transmission rates for the Transmission Project or through any other means costs for the Included Capital Cost above its agreed-upon Cost Cap; provided, however, the Developer may recover costs above its agreed-upon Cost Cap resulting from one of the following excusing conditions, but only to the extent the costs arise from the excusing condition:

A.Transmission Project changes, delays, or additional costs that are due to the actions or omissions of the ISO, Connecting Transmission Owner(s), Interconnecting Transmission Owner(s), or Affected Transmission Owner(s);

B.A Force Majeure event as defined in this Agreement and subject to the Force Majeure requirements in Section 15.5 of this Agreement;

C.Changes in laws or regulations, including but not limited to applicable taxes;

D.Material modifications to scope or routing arising from siting processes under Public Service Law Article VII or applicable local laws as determined by the New York State Public Service Commission or local governments respectively; and

E.Actions or inactions of regulatory or governmental entities, and court orders.

The provisions of this Section 15.3 and the Developer's Cost Cap for the Included Capital Costs detailed in Appendix D shall not be subject to change through application to the Federal Energy Regulatory Commission pursuant to the provisions of Section 205 of the Federal Power Act absent the agreement of all Parties to the Agreement.  In any proceeding conducted pursuant to Section 206 of the Federal Power Act, the standard of review for any change to this Section 15.3 and the Developer’s Cost Cap for the Included Capital Costs detailed in Appendix D shall be the “public interest” application of the just and reasonable standard set forth in United Gas Pipe Line Co. v. Mobile Gas Serv. Corp., 350 U.S. 332 (1956), and Fed. Power Comm'n v. Sierra Pacific Power Co., 350 U.S. 348 (1956), as clarified in Morgan Stanley Capital Grp., Inc. v. Pub. Util. Dist. No. 1 of Snohomish Cnty., Wash., 554 U.S. 527 (2008), and refined in NRG Power Mktg. v. Maine Pub. Utils. Comm'n, 558 U.S. 165 (2010).

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 B – Scope of Work


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]


Appendix D – Cost Cap

 

Effective Date: 4/11/2021 - Docket #: ER21-1074-000 - Page 1