Project/Milestones Taxpayer is a cosmetics manufacturer. Taxpayer has certified in its application that absent award of the California Competes Tax Credit, its project may occur in another state. In consideration for the Credit, Taxpayer agrees to hire full-time employees and invest in a facility, furniture and fixtures, manufacturing equipment, and computer equipment, as part of its expansion in San Bernardino, California (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit A (“Milestones”). In addition, Taxpayer must maintain the three (3) employee based Milestones (“Total California Full-Time Employees,” “Minimum Annual Wage of California Full-Time Employees Hired,” and “Cumulative Average Annual Wage of California Full-Time Employees Hired”) 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 Wage of California Full-time Employees Hired” and the “Cumulative Average Annual Wage of California Full-time Employees Hired,” Taxpayer may use the wages of any of the full-time employees hired within the required time period. For purposes of calculating the “Minimum Annual Wage of California Full-time Employees Hired” and the “Cumulative Average Annual Wage of California Full-time Employees Hired,” the wage of any full-time employee that is not employed by Taxpayer for the entire taxable year shall be annualized. In addition, the wage 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 (either itself or through the acts of a SUBLICENSEE) the following development milestones in its diligence activities under this AGREEMENT: (a) (b).
Milestone schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.
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.
Product Specific Terms these terms apply to specific Products referenced in this section.
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.
Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.
SCHEDULE AND MILESTONES The planned major milestones for the activities for this Annex defined in the "Responsibilities" Article are as follows:
