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).
Development and Regulatory Milestones With respect to each of the following milestones, Ikaria shall pay BioLineRx the corresponding payment set forth below within [**] days after the achievement by Ikaria, its Affiliates or Licensees of such milestone: MILESTONE PAYMENT
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.
New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.
Licensed Product “Licensed Product” shall mean any article, composition, apparatus, substance, chemical material, method, process or service whose manufacture, use, or sale is covered or claimed by a Valid Claim within the Patent Rights. For clarity, a “Licensed Product” shall not include other product or material that (a) is used in combination with Licensed Product, and (b) does not constitute an article, composition, apparatus, substance, chemical material, method, process or service whose manufacture, use, or sale is covered or claimed by a Valid Claim within the Patent Rights.
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.
Product ACCEPTANCE Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User(s) shall have thirty (30) days from the date of delivery to accept hardware products and sixty (60) days from the date of delivery to accept all other Product. Where the Contractor is responsible for installation, acceptance shall be from completion of installation. Failure to provide notice of acceptance or rejection or a deficiency statement to the Contractor by the end of the period provided for under this clause constitutes acceptance by the Authorized User(s) as of the expiration of that period. The License Term shall be extended by the time periods allowed for trial use, testing and acceptance unless the Commissioner or Authorized User agrees to accept the Product at completion of trial use. Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User shall have the option to run testing on the Product prior to acceptance, such tests and data sets to be specified by User. Where using its own data or tests, Authorized User must have the tests or representative set of data available upon delivery. This demonstration will take the form of a documented installation test, capable of observation by the Authorized User, and shall be made part of the Contractor’s standard documentation. The test data shall remain accessible to the Authorized User after completion of the test. In the event that the documented installation test cannot be completed successfully within the specified acceptance period, and the Contractor or Product is responsible for the delay, Authorized User shall have the option to cancel the order in whole or in part, or to extend the testing period for an additional thirty (30) day increment. Authorized User shall notify Contractor of acceptance upon successful completion of the documented installation test. Such cancellation shall not give rise to any cause of action against the Authorized User for damages, loss of profits, expenses, or other remuneration of any kind. If the Authorized User elects to provide a deficiency statement specifying how the Product fails to meet the specifications within the testing period, Contractor shall have thirty (30) days to correct the deficiency, and the Authorized User shall have an additional sixty (60) days to evaluate the Product as provided herein. If the Product does not meet the specifications at the end of the extended testing period, Authorized User, upon prior written notice to Contractor, may then reject the Product and return all defective Product to Contractor, and Contractor shall refund any monies paid by the Authorized User to Contractor therefor. Costs and liabilities associated with a failure of the Product to perform in accordance with the functionality tests or product specifications during the acceptance period shall be borne fully by Contractor to the extent that said costs or liabilities shall not have been caused by negligent or willful acts or omissions of the Authorized User’s agents or employees. Said costs shall be limited to the amounts set forth in the Limitation of Liability Clause for any liability for costs incurred at the direction or recommendation of Contractor.
Commercial Milestones In partial consideration of the rights granted by AstraZeneca to Licensee hereunder, Licensee shall pay to AstraZeneca the following payments, which shall be non-refundable, non-creditable and fully earned upon the first achievement of the applicable milestone event:
Launch Customer shall use commercially reasonable efforts to begin distribution of the Google Desktop Applications promptly following the launch of the Desktop Portal.
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.
