ACCELERATED LAUNCH SERVICE Sample Clauses

ACCELERATED LAUNCH SERVICE. In the event that the Launch Service is accelerated as described in Article 7 entitled "Launch Schedule Adjustments," the next payment due for such Launch Service following such acceleration shall be increased to include the balance of the payments that would have been made had the Contract payments been scheduled on the basis of the accelerated Launch Period.
AutoNDA by SimpleDocs

Related to ACCELERATED LAUNCH SERVICE

  • Launch Customer shall use commercially reasonable efforts to begin distribution of the Google Desktop Applications promptly following the launch of the Desktop Portal.

  • Exercise Schedule This Option shall vest and become exercisable as to the number of Shares and on the dates specified in the exercise schedule at the beginning of this Agreement. The exercise schedule shall be cumulative; thus, to the extent this Option has not already been exercised and has not expired, terminated or been cancelled, the Optionee or the person otherwise entitled to exercise this Option as provided herein may at any time, and from time to time, purchase all or any portion of the Shares then purchasable under the exercise schedule. This Option may also be exercised in full (notwithstanding the exercise schedule) under the circumstances described in Section 8 of this Agreement if it has not expired prior thereto.

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

  • Termination for Force Majeure In the event of a force majeure that lasts longer than thirty (30) days from the date that a Party claiming relief due to the force majeure event gives notice to the other Party, the Party not claiming relief under the force majeure event may terminate this Agreement upon written notice to the other Party. For the avoidance of doubt, the COVID-19 pandemic does not constitute a force majeure event.

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

  • Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.

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

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

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

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