Event Tasks Sample Clauses

Event Tasks 
AutoNDA by SimpleDocs

Related to Event Tasks

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

  • Termination Event; Notice The Purchase Contracts and all obligations and rights of the Company and the Holders thereunder, including, without limitation, the rights of the Holders to receive and the obligation of the Company to pay any Purchase Contract Payments (including any deferred or accrued and unpaid Purchase Contract Payments), if the Company shall have such obligation, and the rights and obligations of Holders to purchase Common Stock, shall immediately and automatically terminate, without the necessity of any notice or action by any Holder, the Purchase Contract Agent or the Company, if, prior to or on the Purchase Contract Settlement Date, a Termination Event shall have occurred.

  • Force Majeure Event After giving effect to any applicable provision, disruption fallback or remedy specified in, or pursuant to, the relevant Confirmation or elsewhere in this Agreement, by reason of force majeure or act of state occurring after a Transaction is entered into, on any day:—

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

  • Development Milestones Subject to the terms and conditions of this Agreement, no later than [**] following the first occurrence of each event described below (each, a “Development Milestone”), on Product-by-Product basis Moderna shall pay Carisma the non-refundable and non-creditable amounts set forth below for each Product to achieve such event (each, a “Development Milestone Payment”): ​ Development MilestoneDevelopment Milestone Payment (in US$ millions) [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] ​ Moderna shall provide written notice to Carisma of the achievement of each Development Milestone within [**] after such achievement. If a Development Milestone for a Product is achieved without the preceding Development Milestone(s) having been achieved for such Product, then the Development Milestone Payment for such preceding Development Milestone(s) shall be paid by Moderna to Carisma together with ​ ​ the Development Milestone Payment for the Development Milestone that was achieved. For example, if the [**] Development Milestone [**] in the table above is achieved for a Product but the [**] Development Milestone [**] in the table above had not been achieved for such Product, then Moderna would pay the Development Milestone Payment for both such [**] Development Milestone and [**] Development Milestone upon achievement of the [**] Development Milestone. Each of the Development Milestone Payments set forth above shall be payable one time only per Product. If Moderna or its Affiliates or Sublicensees Develops a Product that has achieved at least one Development Milestone and subsequently discontinues Development of such Product and Develops a different Product incorporating or directed to the same combination of Collaboration Targets (whether one Collaboration Target or multiple Collaboration Targets), then Moderna shall be required to pay Development Milestone Payments for such different Product only for Development Milestones that had not been achieved by such discontinued Product.

  • Additional Termination Events The following Additional Termination Events will apply:

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

  • Additional Termination Event If any "Additional Termination Event" is specified in the Schedule or any Confirmation as applying, the occurrence of such event (and, in such event, the Affected Party or Affected Parties shall be as specified for such Additional Termination Event in the Schedule or such Confirmation).

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

  • Force Majeure Events The Parties shall be excused from any failure to perform any obligation hereunder to the extent such failure is caused by a Force Majeure Event. A Force Majeure Event shall operate to excuse a failure to perform an obligation hereunder only for the period of time during which the Force Majeure Event renders performance impossible or infeasible and only if the Party asserting Force Majeure as an excuse for its failure to perform has provided written notice to the other Party specifying the obligation to be excused and describing the events or conditions constituting the Force Majeure Event. As used herein, “Force Majeure Event” means the occurrence of an event or circumstance beyond the reasonable control of the party failing to perform, including, without limitation, (a) explosions, fires, flood, earthquakes, catastrophic weather conditions, or other elements of nature or acts of God; (b) acts of war (declared or undeclared), acts of terrorism, insurrection, riots, civil disorders, rebellion or sabotage; (c) acts of federal, state, local or foreign governmental authorities or courts; (d) labor disputes, lockouts, strikes or other industrial action, whether direct or indirect and whether lawful or unlawful; (e) failures or fluctuations in electrical power or telecommunications service or equipment; and (f) delays caused by the other Party’s nonperformance hereunder.

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