Failure to Meet the Guaranteed Commercial Operation Date Sample Clauses

Failure to Meet the Guaranteed Commercial Operation Date. Seller shall cause the Project to achieve the Commercial Operation Date by the Guaranteed Commercial Operation Date. If the Commercial Operation Date occurs after the Guaranteed Commercial Operation Date after giving effect to Permitted Extensions, then Buyer shall be entitled to declare an Event of Default and collect the Damage Payment pursuant to Article Five. [The following subsections (d) and (e) shall only apply to a New Project:]
AutoNDA by SimpleDocs

Related to Failure to Meet the Guaranteed Commercial Operation Date

  • Commercial Operation Date (COD) Bus Terminal and Commercial Complex shall be deemed to be complete when the Completion Certificate or the Provisional Certificate, as the case may be, is issued under the provisions of Article 14, and accordingly the commercial operation date of the Project shall be the date on which such Completion Certificate or the Provisional Certificate is issued (the “COD”). The Bus Terminal and Commercial Complex shall enter into commercial service on COD whereupon the Concessionaire shall be entitled to demand and collect Fee in accordance with provisions of Article 27 and that the entry of Bus Terminal or part thereof into commercial service shall always be subject to compliance with the provisions of Clause 18.3 and Clause 26.2.

  • Commercial Operation Date (COD 15.1.1 The Project shall be deemed to be complete when the Completion Certificate or the Provisional Certificate, as the case may be, is issued under the provisions of Article 14, and accordingly the commercial operation date of the Project shall be the date on which such Completion Certificate or the Provisional Certificate is issued (the “COD”). The Project shall enter into commercial service on COD whereupon the Concessionaire shall be entitled to demand and collect Annuity Payments in accordance with the provisions of this Agreement.

  • Failure to Achieve Commercial Operation If the Large Generating Facility fails to achieve Commercial Operation, but it or another generating facility is later constructed and makes use of the Network Upgrades, the Participating TO shall at that time reimburse Interconnection Customer for the amounts advanced for the Network Upgrades. Before any such reimbursement can occur, the Interconnection Customer, or the entity that ultimately constructs the generating facility, if different, is responsible for identifying and demonstrating to the Participating TO the appropriate entity to which reimbursement must be made in order to implement the intent of this reimbursement obligation.

  • Commercial Operation (i) On or before December 31, 2021, Interconnection Customer must demonstrate commercial operation of all generating units. Demonstrating commercial operation includes achieving Initial Operation in accordance with Section 1.4 of Appendix 2 to this ISA and making commercial sales or use of energy, as well as, if applicable, obtaining capacity qualification in accordance with the requirements of the Reliability Assurance Agreement Among Load Serving Entities in the PJM Region.

  • OUTCOME IF GRANTEE CANNOT COMPLETE REQUIRED PERFORMANCE Unless otherwise specified in this Statement of Work, if Grantee cannot complete or otherwise comply with a requirement included in this Statement of Work, HHSC, at its sole discretion, may impose remedies or sanctions outlined under Contract Attachment C, Local Mental Health Authority Special Conditions, Section 7.09 (Remedies and Sanctions).

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Extended Reporting Period If any required insurance coverage is on a claims-made basis (rather than occurrence), Contractor shall maintain such coverage for a period of no less than three (3) years following expiration or termination of the Master Contract.

  • Failure to Maintain Financial Viability The System Agency may terminate the Contract if, in its sole discretion, the System Agency has a good faith belief that Grantee no longer maintains the financial viability required to complete the services and Deliverables, or otherwise fully perform its responsibilities under the Contract.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

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