Failure to Agree on New Collaboration Compound Sample Clauses

Failure to Agree on New Collaboration Compound. In the event the Parties do not mutually agree as to whether the Parties should continue activities under the Development Plan with respect to the Collaboration Compound, either Party shall have the right to terminate this Agreement under Section 10.2, and the effects of termination set forth in Section [**] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. 10.4.1 shall apply.
AutoNDA by SimpleDocs

Related to Failure to Agree on New Collaboration Compound

  • Research Collaboration 3.7.1 Aarvik shall carry out the activities of each Work Item and deliver the required Data Package and/or deliverables in accordance with the applicable SOW. Without limiting the generality of the foregoing, Aarvik shall, in accordance with the applicable SOWs and the timeline approved by JRC, apply the Aarvik IP to (i) design and synthesize Collaboration Compounds, and (ii) by itself or through subcontractor(s), [***]. During the Research Term, if any Party identifies any Third Party Patent or Know-How that is necessary or reasonably useful for any activity under the SOWs but has not been included in the Aarvik IP, then such Party shall immediately inform the other Party and the Parties shall discuss in good faith the need of obtaining a license from such Third Party. 3.7.2 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver the Data Packages and all other deliverables required under the [***], as well as the results of the Patentability and FTO Analysis as described in Section 3.2.3, to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.3 If, upon completion of the [***] for the Collaboration Program, AxxxXxxx decides not to advance the Collaboration Program to [***], ArriVent may terminate the Collaboration Program. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.4 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. 3.7.5 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. 3.7.6 Within [***] ([***]) days after completion of the [***], Aarvik shall deliver to ArriVent a full report on all key results and findings of the Collaboration Program, and such other data, results and information as ArriVent may deem necessary for it to determine whether or not to exercise the Option (the “Full Report”).

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

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • For clarity the time allowances provided in clause 2.10 shall operate to reduce the maximum timetabled classroom teaching time specified in clause 4.2 of this agreement.

  • Human Leukocyte Antigen Testing This plan covers human leukocyte antigen testing for A, B, and DR antigens once per member per lifetime to establish a member’s bone marrow transplantation donor suitability in accordance with R.I. General Law §27-20-36. The testing must be performed in a facility that is: • accredited by the American Association of Blood Banks or its successors; and • licensed under the Clinical Laboratory Improvement Act as it may be amended from time to time. At the time of testing, the person being tested must complete and sign an informed consent form that also authorizes the results of the test to be used for participation in the National Marrow Donor program.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • Development Milestone Payments Pfizer shall make the payments set forth below within [**] days (or [**] days after [**] following the first occurrence of each event described below for a Licensed Product Covered by a Valid Claim that achieves such milestone (each event a “Development Milestone” and each payment a “Development Milestone Payment”). Development Milestone Development Milestone Payment [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**]. The Development Milestone Payment in clause (2) of this Section 3.3 may become payable as set forth in Section 4.6. Whether or not the Development Milestone in clause (2) of this Section 3.3 is achieved, the Development Milestone Payment in clause (2) shall, pursuant to Section 4.6, in all cases become payable prior to the time the Development Milestone Payment in clause (3) of this Section 3.3 becomes payable. With respect to the Development Milestone in clause (3) of this Section 3.3, in the case of a [**] that is determined to have become [**], such Development Milestone, if achieved based on such [**], shall be achieved upon [**]; provided, however, if either [**], such Development Milestone shall be deemed to have been met on the date of such determination. With respect to the Development Milestone in clause (8) of this Section 3.3, such Development Milestone will be paid in [**], provided that if such Licensed Product [**]. (For the avoidance of doubt, all payment [**] that became payable prior to such [**] shall continue to be payable and there shall be [**] of the [**] Development Milestone Payment will be deemed to have been achieved and payable on [**], and will be paid by Pfizer within [**] days thereafter, until the earlier of [**]. For example, [**] of such Development Milestone, such Development Milestone Payment would be paid [**] of the Development Milestone [**]. For the avoidance of doubt: (a) except for (i) the Development Milestone Payment set forth in clause (6) of this Section 3.3 [**], (ii) the Development Milestone Payment set forth in clause (8) of this Section 3.3 [**] and (iii) the Development Milestone Payment set forth in clause (9) of this Section 3.3 [**], each Development Milestone Payment shall be payable only once upon achievement of the applicable Development Milestone and only on the first occurrence of the corresponding Development Milestone regardless of the number of Licensed Products and (b) satisfaction of a Development Milestone by an Affiliate or by a sublicensee or assignee of, or Third Party retained by, Pfizer or its Affiliates shall be deemed to have been satisfied by Pfizer for the purposes of this Section 3.3.

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

  • Commercial Milestones (a) Within [*****] calendar days after the end of the first Calendar Year in which aggregate annual Net Sales for that Calendar Year for the Licensed Product in the Territory reach any threshold indicated in the Commercial Milestone Events listed below, EverInsight shall notify VistaGen of the achievement of such Commercial Milestone Event and VistaGen shall invoice EverInsight for the corresponding non-refundable, non-creditable Milestone Payment set forth below and EverInsight shall remit payment to VistaGen within [*****] Business Days after the receipt of the invoice, as described in Section 8.6 (Currency; Exchange Rate; Payments). Annual Net Sales Milestones for Licensed Product Milestone Payments (in Dollars) (each a “Commercial Milestone Event”): (1). [*****] (2). [*****] (3). [*****] (4). [*****] (5). [*****] (b) For the purposes of determining whether a Net Sales Milestone Event has been achieved, Net Sales of Licensed Product(s) in the Territory shall be aggregated. For clarity, the annual Net Sales Milestone Payments set forth in this Section 8.3 (Commercial Milestones) shall be payable only once, upon the first achievement of the applicable Commercial Milestone Event, regardless of how many times such Commercial Milestone Event is achieved. (c) If a Commercial Milestone Event in Section 8.3 (Commercial Milestones) is achieved and payment with respect to any previous Commercial Milestone Event in Section 8.3 has not been made, then such previous Commercial Milestone Event shall be deemed achieved and EverInsight shall notify VistaGen within fifteen (15) calendar days of such achievement. VistaGen shall then invoice EverInsight for such unpaid previous Commercial Milestone Event(s) and EverInsight shall pay VistaGen such unpaid previous milestone payment(s) within thirty (30) Business Days of receipt of such invoice. (d) In the event that, VistaGen believes any Commercial Milestone Event under Section 8.3(a) has occurred but EverInsight has not given VistaGen the notice of the achievement of such Commercial Milestone Event, it shall so notify EverInsight in writing and shall provide to EverInsight data, documentation or other information that supports its belief. Any dispute under this Section 8.3(d) (Commercial Milestones - subsection (d)) that relates to whether or not a Commercial Milestone Event has occurred shall be referred to the JSC to be resolved in accordance with ARTICLE 3 (Governance) and shall be subject to resolution in accordance with Section 14.10 (Dispute Resolution). The Milestone Payments made for each Commercial Milestone Event shall be non-creditable and non-refundable.

  • Joint Patent Rights If not already established under the Research Collaboration Agreement, prior to either Party filing any Patent Right disclosing Joint Program Technology or Joint TAP Platform Improvements, the Parties shall establish a patent committee (the “Patent Committee”) comprised of at least one (1) representative of each Party for the purpose of facilitating the preparation, filing, prosecution, maintenance and defense of Joint Patent Rights. As agreed upon by the Parties, meetings of the Patent Committee may be face-to-face or may be conducted by teleconferences or videoconferences, from time to time as needed. The Patent Committee will be the forum through which the Parties coordinate their respective obligations to each other described in Sections 5.2.2 and 5.2.3 hereof and in this Section. In the event the Parties conceive or generate any Joint Program Technology or Joint TAP Platform Improvements, the Parties shall promptly meet to discuss and determine, based on mutual consent, whether to seek patent protection thereon, which Party will control filing, prosecution and maintenance of such patents and how to pay for the filing, prosecution and maintenance of such patents. It is presumed that CytomX will control filing, prosecution and maintenance of Joint Patent Rights claiming Joint Program Technology or Joint Unconjugated Probody Platform Improvements, and that ImmunoGen will control filing, prosecution and maintenance of Joint Patent Rights claiming Joint TAP Platform Improvements or Joint Conjugation Probody Platform Improvements. Neither Party will file any Joint Patent Right without the prior written consent of the other Party, which consent shall not be unreasonably withheld, conditioned or delayed. The Party controlling filing and prosecution of any such Joint Patent Right (a) shall keep the other Party informed regarding each Patent Right, (b) shall consider in good faith any recommendations made by the other Party in regard to the filing, prosecution or maintenance of any such Patent Right and (c) shall not unreasonably refuse to incorporate any recommendations made by the other Party in regard to such filing, prosecution or maintenance.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!