Common use of Deficiencies in Interconnection Request Clause in Contracts

Deficiencies in Interconnection Request. An Interconnection Request will not be considered to be a valid request until all items in Section 30.3.3.1 have been received by the ISO and the applicable solicitation window has closed for any Interconnection Request that is submitted for a proposed project subject to the ISO’s competitive selection process in the ISO’s Comprehensive System Planning Process in Attachment Y to the ISO OATT. If an Interconnection Request fails to meet the requirements set forth in Section 30.3.3.1, the ISO shall notify the Developer and Connecting Transmission Owner within ten (10) Business Days of receipt of the initial Interconnection Request of the reasons for such failure and that the Interconnection Request does not constitute a valid request. However, for any Interconnection Request that is submitted for a proposed project subject to the ISO’s competitive selection process in the ISO’s Comprehensive System Planning Process in Attachment Y to the ISO OATT and that fails to meet the requirements set forth in Section 22.4.2.1, the ISO shall notify the Developer and the Connecting Transmission Owner(s) no later than ten (10) Business Days following the close of the applicable solicitation window. The Developer shall provide the ISO the additional requested information needed to constitute a valid request within ten (10) Business Days after receipt of such notice. The ISO shall promptly forward such information to the Connecting Transmission Owner; provided, however, for any Interconnection Request that is submitted for a proposed project subject to the ISO’s competitive selection process in the ISO’s Comprehensive System Planning Process in Attachment Y of the ISO OATT, such information will not be forwarded to the Connecting Transmission Owner(s) until the close of the applicable solicitation window. Failure by Developer to comply with this Section 30.3.3.3 shall be treated in accordance with Section 30.3.6.