Scheduled Commercial Operation Date ( SCOD) as defined in PPA
Scheduled Commercial Operation Date ( SCOD) Sample Clauses
Related to Scheduled Commercial Operation Date ( SCOD)
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.
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.
Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.
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.
Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.
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.
Project Completion Date It is agreed between the Parties that the Project Completion Date is <END DATE, YEAR>. If the Project is not completed by such date then, subject to an amendment agreed to between the Parties, Alberta Innovates may elect to terminate this Investment Agreement. In such event, Alberta Innovates will notify the Applicant of its decision to terminate as soon as reasonably practical and shall advise the Applicant of the effective date of termination. Alberta Innovates will have no liability or obligation to reimburse the Applicant for any Project Costs incurred after the effective date of termination and may require the Applicant to return any portions of the Investment which were spent on Ineligible Expenses. Additionally, any portion of the Investment not used and accounted for in accordance with this Agreement as of the Project Completion Date or earlier termination is repayable by the Applicant to AI at AI’s request.
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.
