Milestone Log Sample Clauses

Milestone Log. Provide milestones for each budget period (or phase) of the project. Each milestone should include a title and planned completion date. Milestones should be quantitative (e.g., a date, a decision to be made, a key event) and show progress toward budget period and/or project goals. Milestones should also be important and few. Higher TRL projects (Demonstration and Deployment) typically have the most detailed milestone logs compared to lower TRL level projects (Research and Development). If applicable, milestones chosen should clearly reflect progress through various TRL stages. Note: The Milestone Status must present actual performance in comparison with the Milestone Log, and include:
AutoNDA by SimpleDocs
Milestone Log. Provide milestones for each budget period (or phase) of the project. Each milestone should include a title and planned completion date. Milestones should be quantitative and show progress toward budget period and/or project goals. [Note: During project performance, the Recipient will report the Milestone Status as part of the required quarterly Research Performance Progress Report (RPPR) as prescribed under Attachment b2, Reporting Requirements Checklist. The Milestone Status will present actual performance in comparison with Milestone Log, and include: ​
Milestone Log. Provide milestones for each budget period (or phase) of the project. Each milestone should include a title and planned completion date. Milestones should be quantitative and show progress toward budget period and/or project goals. The following are examples of the type of milestones that should be included in the Project Management Plan. These should be tailored to meet the specific work tasks of the project (some may be deleted if not applicable): · Initial Simulation and Modeling Complete · Initial (Material, Component, or Process) Specifications Complete · Initial (Material, Component, or Process) Design Complete · Commercialization Plan Complete · Initial (Material, Component, or Process) Development & Testing Complete · (Material, Component, or Process) Downselection Complete · Test Cell (Material, Component, or Process) and Systems Demonstrations Initiated · Test Cell (Material, Component, or Process) and Systems Demonstrations Completed · Delivery of Technology or Material for Government Confirmatory Testing Completed (AOIs 4 and 5 only) · Systems Integration Design Complete · Vehicle Integration and Demonstration Initiated · Vehicle Integration and Demonstration 50% Completed · Vehicle Integration and Demonstration 100% Completed [Note: During project performance, the Recipient will report the Milestone Status as part of the required quarterly Progress Report as prescribed in the award document under Attachment 4, Reporting Requirements Checklist. The Milestone Status will present actual performance in comparison with Milestone Log, and include:

Related to Milestone Log

  • Milestone Event Milestone Payment [***] [***]

  • Milestone A principal event specified in the Contract Documents including the Material Completion and Occupancy Date and other events relating to an intermediate completion date or time.

  • Development Milestone Payments In partial consideration for the rights and licenses granted to Coya hereunder, within ten days after the first achievement of each milestone event in a given Indication set forth in this Section 5.2 (Development Milestone Payments) with respect to a Product (each, a “Development Milestone Event”) by or on behalf of Coya or any of its Affiliates or Sublicensees, Coya shall provide ARScience Bio written notice to ARScience Bio identifying the Development Milestone Event achieved. Upon receipt of any such notice of first achievement of a Development Milestone Event by Coya or its Affiliates or Sublicensees, ARScience Bio will promptly invoice Coya for the applicable Development Milestone Event and Coya will make a milestone payment to ARScience Bio in the amount set forth in this Section 5.2 (Development Milestone Payments) corresponding to such Development Milestone Event (each, a “Development Milestone Payment”) within 45 days of receipt of such invoice. On an Indication-by-Indication basis, each Development Milestone Payment shall be payable only upon the first achievement of the corresponding Development Milestone Event by a Product, in any given Indication for which the Development Milestone Events have not been previously achieved (each such Indication, a “New Indication”). No amounts shall be due for subsequent or repeated achievements of such Development Milestone Event with respect to the same or different Mono Product or Combination Product, as applicable, in such Indication. Accordingly and for clarity, the Development Milestone Payment shall be paid only once, when first achieved by Coya, an Affiliate or a Sublicensee, but no payment shall be due if the same milestone is subsequently achieved by one of Coya, an Affiliate or a Sublicensee. For clarity, the amounts owed in Column (a) below shall be due for the first Combination Product to achieve the Development Milestone Events in a New Indication and the amounts owned in Column (c) below shall be due for the first Mono Product to achieve the Development Milestone Events in a New Indication. Any Combination Product or Mono Product to achieve the Development Milestone Events in a New Indication after the first achievement of the Development Milestone Events as described in the foregoing sentence will cause the amounts in Column (b) with respect to a Combination Product and Column (d) with respect to a Mono Product to be due and payable by Coya upon each such occurrence. If the first Product to achieve a Development Milestone Event in any Indication is a Combination Product, the amounts in Column (a) below shall be due and payable by Coya. If the next Product to achieve a Development Milestone Event in a New Indication is a Mono Product, the amounts in Column (c) below would be due and payable by Coya; provided, that if such next Product to achieve a Development Milestone Event in a New Indication is a Combination Product, the amounts in Column (b) would be due and payable by Coya. By way of example, if a Combination Product achieves IND Acceptance in ALS, and is the first Product to achieve a Development Milestone Event under this Agreement, [***] will be due and payable by Coya. If subsequently a Mono Product achieves IND Acceptance in ALS, no Development Milestone Payments will be due and payable by Coya under this Agreement. However, if subsequently any Combination Product achieves IND Acceptance in Alzheimer’s disease, [***] would be due and payable by Coya.

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

  • Milestone Payment Within thirty (30) days following the first Patent Issuance, Eton shall give written notice to Imprimis and shall pay to Imprimis a non-refundable and noncreditable payment of fifty thousand dollars ($50,000).

  • Commercial Milestone Payments For each Licensed Product, Licensee shall pay Arvinas the following one-time milestone event payments when the aggregate Net Sales of such Licensed Product in one or more particular country(ies) for a given calendar year (“Annual Net Sales”), where such Licensed Product is a Valid Claim Licensed Product at the time of sale in each of such country(ies), first achieves the corresponding threshold as set forth in this Section 6.3.2 below, subject to the terms of this Section 6.3 and the payment provisions in Article 7 below: Commercial Milestone Event Milestone Event Payment (US$)

  • Milestone Fees Licensee will pay Milestone Fees indicated in Section 3.1(b) of the Patent & Technology License Agreement by the Quarterly Payment Deadline for the Contract Quarter in which the milestone events set forth in Section 3.1(b) of the Patent & Technology License Agreement are achieved.

  • Sales Milestone Payments As further consideration for Daiichi Sankyo’s grant of the rights and licenses to Rain hereunder, Rain will pay to Daiichi Sankyo the following payments upon the first achievement of the following levels of aggregate annual Net Sales of all Products by Rain, its Affiliates, and its Sublicensees. If two or more sales milestone events are achieved in the same [***], then Rain shall pay to Daiichi Sankyo all of the applicable milestone payments achieved in such [***]. Rain shall deliver written notice to Daiichi Sankyo within [***] after the end of the [***] in which a sales milestone threshold described in this Section 5.3 is achieved for the first time. Aggregate annual Net Sales of all Products shall be calculated based on Net Sales for each Calendar Year. After receipt of such notice from Rain, Daiichi Sankyo shall issue Rain an invoice for the amount corresponding to the applicable sales milestones event. Rain shall pay Daiichi Sankyo within [***] after receipt of an invoice therefor from Daiichi Sankyo. Milestone Event Payment Amount Aggregate Annual Net Sales of all Products combined in the Territory in a Calendar Year equals or exceeds [***] [*** ] Aggregate Annual Net Sales of all Products combined in the Territory in a Calendar Year equals or exceeds [***] [*** ] [***] = CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY BRACKETS, HAS BEEN OMITTED BECAUSE THE INFORMATION (I) IS NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED. EXECUTION VERSION Aggregate Annual Net Sales of all Products combined in the Territory in a Calendar Year equals or exceeds [***] [*** ] Aggregate Annual Net Sales of all Products combined in the Territory in a Calendar Year equals or exceeds [***] [*** ]

  • Regulatory Milestones Celgene shall make the following approval milestone payments to Jounce that are set forth below upon the first achievement by or on behalf of Celgene, its Affiliates or Sublicensees of the Regulatory Milestone Events set forth below with respect to the first Co-Co Product that achieves such event. For clarity, each milestone set forth below shall be due and payable one time only (regardless of the number of Co-Co Products to achieve any such Regulatory Milestone Event). CERTAIN CONFIDENTIAL PORTIONS OF THIS EXHIBIT WERE OMITTED AND REPLACED WITH “[***]”. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECRETARY OF THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO AN APPLICATION REQUESTING CONFIDENTIAL TREATMENT PURSUANT TO RULE 406 PROMULGATED UNDER THE SECURITIES ACT OF 1933, AS AMENDED. Regulatory Milestone Event (For the first Co-Co Product that achieves such event) Milestone Payments (in $ millions) [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] For each of Paragraphs (1) - (3) of this Exhibit C-2, the Parties understand and agree that in no event will more than one (1) milestone payment be paid with respect to any specific event triggering a payment under this Jounce Lead Co-Co Agreement.

  • Sales Milestones Subject to the terms and conditions set forth in the Agreement, in the event that the Annual Net Sales made by or on behalf of a Selling Entity for all Licensed Products in a given calendar year first exceeds a threshold set forth in the table immediately below, Pyxis shall pay to LCB the following one-time, non-refundable, non-creditable milestone payments. Annual Net Sales Milestone Threshold Payment (US Dollars) [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] In the event that in a given calendar year more than one (1) Annual Net Sales milestone threshold is achieved, Pyxis shall pay to LCB each separate Annual Net Sales milestone payment with respect to each Annual Net Sales milestone threshold that is achieved in such calendar year. Pyxis shall notify LCB in writing upon the first achievement, in respect of a Licensed Product, by or on behalf of Pyxis or its Affiliate or Sublicensee, of each of the Milestones set forth in Section 5.2 (Development Milestones), Section 5.3 (Regulatory Milestones) and Section 5.4 (Sales Milestones) no later than [***] of Pyxis’s knowledge of achievement thereof, and in any event, each of the Milestones set forth in Section 5.4 (Sales Milestones) no later than [***] after the end of the applicable calendar year in which such Milestone is achieved. No later than [***] of receipt of an appropriate invoice from LCB, Pyxis shall pay the applicable payment due upon achievement of the corresponding Milestone Event. Each Milestone Event shall be deemed to be achieved once for all Licensed Products and shall be payable only once.

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