Project Specific Milestones Sample Clauses

Project Specific Milestones. In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:
AutoNDA by SimpleDocs
Project Specific Milestones. During the term of this WMPA, Wholesale Market Participant shall ensure that it meets each of the following milestones:
Project Specific Milestones. In addition to the milestones stated in GIP, section [to be determined], as applicable, during the term of this GIA, Project Developer shall ensure that it meets each of the following development milestones: [Specify Project Specific Milestones] [As appropriate include the following standard Milestones, with any revisions necessary for the project at hand (sections should be renumbered as appropriate):]
Project Specific Milestones. In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: None. Interconnection Customer shall demonstrate the occurrence of each of the foregoing milestones to Transmission Provider’s reasonable satisfaction. Transmission Provider may reasonably extend any such milestone dates, in the event of delays that Interconnection Customer (i) did not cause and (ii) could not have remedied through the exercise of due diligence. The milestone dates stated in this ISA shall be deemed to be extended coextensively with any suspension of work initiated by Interconnection Customer in accordance with the Interconnection Construction Service Agreement.
Project Specific Milestones. In addition to the milestones stated in Section 36.8.5 or Section 41.7.4 of the J.'ariff, during the teiln of this X.XX, Interconnection Customer shall ensure that its generation project meets each of the following development milestones:

Related to Project Specific Milestones

  • Project/Milestones Taxpayer is a developer, manufacturer, and distributor of dental products for dental laboratories. In consideration for the Credit, Taxpayer agrees to hire full time employees and invest in computer and manufacturing equipment, tenant improvements, software licenses, and furniture and fixtures as part of its expansion in San Diego, California (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 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 Taxpayer for the entire taxable year shall be annualized. In addition, the salary of any full-time employee hired to fill a vacated position in which a full-time employee was employed during Taxpayer’s Base Year shall be disregarded.

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

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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