REQUESTED EFFECTIVE DATE AND WAIVERS Sample Clauses

REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept this Interconnection Agreement, without modifications or conditions, with an effective date of June 22, 2015, to coincide with the date the parties executed the agreement. The Filing Parties request any waivers of the Commission’s regulations, including but not limited to, 18 C.F.R. §§ 35.3 and 35.11, that may be necessary so as to permit the requested effective date.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the Interconnection Agreement, as submitted, with an effective date of February 12, 2024 to coincide with the date the Filing Parties and the Interconnection Customer executed the Interconnection Agreement. In order to permit this effective date, the Filing Parties respectfully request a waiver of the Commission’s 60-day notice requirement set forth in 18 C.F.R. § 35.3. Such waiver is appropriate because this filing is being made prior to the commencement of service, and the Commission has indicated that waiver is appropriate if a service agreement is filed within 30 days after the commencement of service.15
Sample 1See All (4)
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the Berkshire Wind SGIA, without modifications or conditions, effective June 23, 2014, to coincide with the date the parties executed the agreement. The Filing Parties request any waivers of the Commission’s regulations, including but not limited to, 18 C.F.R. §§ 35.3, 35.11, and 35.15, that may be necessary so as to permit the requested effective date.
Sample 1Sample 2
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the Xxxx LGIA, effective August 31, 2012. Pursuant to section 35.11 of the Commission’s regulations, 18 C.F.R. § 35.11, the Filing Parties request waiver of the Commission’s sixty-day notice requirement set forth at 18 C.F.R. § 35.3. Such waivers will have no adverse effect on the ISO, CMP, TransCanada, or their customers, and will actually confer substantial benefits on TransCanada to allow it to proceed with the next steps in the interconnection process. Therefore, the Filing Parties respectfully submit that good cause exists to grant waiver of the 60-day prior notice requirement. Further, the Filing Parties submit that the information in this filing substantially complies with the applicable requirements of 18 C.F.R. § 35.12. The Filing Parties respectfully request waivers of any applicable requirements of 18 C.F.R. § 35.12 for which waiver is not specifically requested, if necessary, to permit the Xxxx LGIAs to become effective as proposed.
Sample 1
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the First Revised LGIA as filed, without modifications or conditions, effective November 4, 2022 to coincide with the date the Parties executed the agreement. A November 4, 2022 effective date is appropriate as the First Revised LGIA is being filed within 30 days of execution pursuant to 18 C.F.R. § 35.3(a)(2).
Sample 1
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the Interconnection Agreement, as submitted, with an effective date of June 14, 2016, to coincide with the date the Filing Parties and the Interconnection Customer executed the Interconnection Agreement. To that end, the Filing Parties request any waivers of the Commission’s regulations, including but not limited to 18 C.F.R. §§ 35.3, 35.11, and 35.15, that may be necessary so as to permit the requested effective date. Good cause exists to grant this waiver. Granting the waiver will accord with the Filing Parties’ and Interconnection Customer’s intent to make the new Interconnection Agreement effective as of June 14, 2016, consistent with Article 2.1 of the Interconnection Agreement. The Commission has previously granted waivers when “all affected parties have sufficient notice that [the] change will be incorporated in the [Tariff].”17 In this case, no prejudice will result to any party from granting the waiver. The Commission has previously permitted retroactive dates for interconnection agreements and notices of cancellation under similar circumstances.18 For these reasons, the Commission should find good cause exists to grant the requested effective date. In the alternative, should the Commission reject the requested effective date, the Filing Parties request as early an effective date as the Commission may allow.
Sample 1
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the Interconnection Agreement, as submitted, with an effective date of August 31, 2015, to coincide with the date the Filing Parties executed the Interconnection Agreement. To that end, the Filing Parties request any waivers of the Commission’s regulations, including but not limited to 18 C.F.R. §§ 35.3, 35.11, and 35.15, that may be necessary so as to permit the requested effective date. Good cause exists to grant this waiver. Granting the waiver will accord with the Filing Parties’ intent to make the new Interconnection Agreement effective as of August 31, 2015, consistent with Article 2.2 of the Interconnection Agreement. The Commission has previously granted waivers when “all affected parties have sufficient notice that [the] change will be incorporated in the [Tariff].”13 In this case, no prejudice will result to any party from granting the waiver. The Commission has previously permitted retroactive dates for interconnection agreements and notices of cancellation under similar circumstances.14 For these reasons, the 13 California Independent System Operator Corp., 111 FERC ¶ 61,073 at P 26 (2005). 14 See PacifiCorp, Letter Order, Notice of Cancellation, Docket No. Docket No. ER03-1020-000 (Aug. 13, 2003) (granting effective date requested by customer for cancelling a rate schedule where customer had asked to terminate the agreement effective April 30, 2000, but the filing utility filed the (continued...) The Xxxxxxxxx Xxxxxxxx X. Bose September 30, 2015 Commission should find good cause exists to grant the requested effective date. In the alternative, should the Commission reject the requested effective date, the Filing Parties request as early an effective date as the Commission may allow.
Sample 1
AutoNDA by SimpleDocs
REQUESTED EFFECTIVE DATE AND WAIVERS. The Filing Parties respectfully request that the Commission accept the 2021 SGIA, without modifications or conditions, effective November 23, 2021, to coincide with the date the parties executed the agreement. The Filing Parties request any waivers of the Commission’s regulations, including but not limited to, 18 C.F.R. §§ 35.3, 35.11, and 35.15, that may be necessary so as to permit the requested effective date.
Sample 1

Related to REQUESTED EFFECTIVE DATE AND WAIVERS

  • Amendment and Waivers Any term or provision of this Agreement may be amended, and the observance of any term of this Agreement may be waived (either generally or in a particular instance and either retroactively or prospectively) only by a writing signed by the party to be bound thereby. The waiver by a party of any breach hereof for default in payment of any amount due hereunder or default in the performance hereof shall not be deemed to constitute a waiver of any other default or any succeeding breach or default.

  • Termination Amendment and Waiver 46 7.1 Termination....................................................................................46 7.2

  • Amendment and Waiver The provisions of this Agreement may be amended or waived only with the prior written consent of the Company and Executive, and no course of conduct or failure or delay in enforcing the provisions of this Agreement shall affect the validity, binding effect or enforceability of this Agreement.

  • Amendments and Waiver No modification of or amendment to this Agreement shall be valid or binding unless set forth in writing and duly executed by both of the parties hereto and no waiver of any breach of any term or provision of this Agreement shall be effective or binding unless made in writing and signed by the party purporting to give the same and, unless otherwise provided, shall be limited to the specific breach waived.

  • EFFECTIVE DATE AND NOTICE OF NONLIABILITY This Agreement shall not be effective or enforceable until it is approved and signed by the State Controller or its designee (hereinafter called the “Effective Date”), but shall be effective and enforceable thereafter in accordance with its provisions. The State shall not be liable to pay or reimburse Contractor for any performance hereunder or be bound by any provision hereof prior to the Effective Date.

  • Execution of Agreement and Effective Date The Agreement shall become effective (i.e., final and binding) upon the date of signing of this Agreement and the CAP by the last signatory (Effective Date).

  • WAIVER AND EFFECTIVE DATE PJM requests that the Commission grant any and all waivers of the Commission’s rules and regulations necessary for acceptance of this filing and the enclosed Amended Service Agreements. Additionally, PJM requests a waiver of the Commission’s 60-day prior notice requirement to (i) allow the effective date of the Amended ISA to remain January 28, 2019; and

  • Modifications and Waivers No provision of this Agreement shall be modified, waived or discharged unless the modification, waiver or discharge is agreed to in writing and signed by the Executive and by an authorized officer of the Company (other than the Executive). No waiver by either party of any breach of, or of compliance with, any condition or provision of this Agreement by the other party shall be considered a waiver of any other condition or provision or of the same condition or provision at another time.

  • Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment.

  • EFFECTIVE DATE AND SIGNATURE This MOU shall be effective upon the signature of authorized officials from Party A and Party B. It shall be in force from (Date to be finalized with Lease-Up) to (Date to be finalized with Lease-Up). Parties A and B indicate agreement with this MOU by their signatures below. Party A Party B By: By: Title: Title: Signed: Signed: Date: Date:

Time is Money Join Law Insider Premium to draft better contracts faster.