City Infrastructure Milestones Sample Clauses

City Infrastructure Milestones. Based on the Developer’s targeted milestones described in Section 3.2.6, attached hereto as Exhibit 3.2.7 is a proposed sequencing plan for the Construction of the City Infrastructure. The Parties recognize and acknowledge that Construction of the City Infrastructure is a complex undertaking and the timing and sequencing of which is based, in part, on the City’s timely receipt of preliminary and final GF Plant Development Plans and the Developer’s timing and progress for the Construction of the GF Plant, and may be subject to delays based on many reasons, including but not limited to changes in the GF Plant Development Plans, the City Infrastructure or the City Infrastructure Plans and/or delays in the Developer’s preparation of preliminary and final GF Plant Development Plans, the Developer’s Construction timing and progress of the GF Plant, receipt of information described in Exhibit 3.2.3 and/or receipt of Government Requirements for either the GF Plant or any part of the City Infrastructure. The City may amend its proposed sequencing plan from time to time in Good Faith to reflect such changes or delays and will promptly advise Developer and Developer’s Engineer and Architect of such changes.
Sample 1
AutoNDA by SimpleDocs

Related to City Infrastructure Milestones

  • Project/Milestones Taxpayer develops and manufactures various products for use in the defense, aerospace and security industries. In consideration for the Credit, Taxpayer agrees to expand its operations at various locations throughout California, including El Segundo, Redondo Beach, Palmdale, Sunnyvale, Woodland Hills, Azusa and Rancho Xxxxxxxx. As part of its expansion, Taxpayer will invest in manufacturing equipment, computer and electrical equipment and make tenant improvements to the above facilities. Additionally, Taxpayer will hire full-time employees as part of its expansion (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit “A” (“Milestones”) and must maintain Milestones for a minimum of three (3) taxable years thereafter. In the event Taxpayer employs more than the number of Full- time employees, determined on an annual full-time equivalent basis, than required in Exhibit A, for purposes of satisfying the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” Taxpayer may use the salaries of any of the Full-time employees hired and retained within the required time period. For purposes of calculating the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” the salary of any full-time employee that is not employed by the taxpayer for the entire taxable year shall be annualized. In addition, Xxxxxxxx agrees that any full-time employee hired after the effective date of this agreement that is a “qualified full-time employee” (as defined in RTC section 23636) shall be excluded from the calculation of the net increase of full-time employees required by this Agreement if Taxpayer claims the credit allowed by RTC section 23636.

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • Milestones Subject to the provisions of the SGIP, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party’s obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Force Majeure event, it shall immediately notify the other Parties of the reason(s) for not meeting the milestone and (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless it will suffer significant uncompensated economic or operational harm from the delay, (1) attainment of the same milestone has previously been delayed, or (2) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.

  • 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.

  • 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.

  • PROGRESS AND COMPLETION 8.2.1 All time limits stated in the Contract Documents are material terms and time is the essence of the Contract. A failure by Contractor to do what is required by the time specified in the Contract Documents is a breach of the contract.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!