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
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”).
Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.
Research Program The term “
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.
Licensed Product The term “Licensed Product” shall mean any product (a) the manufacture, use, importation, sale or offer for sale of which would, in the absence of the license granted by this Agreement, infringe a Valid Claim of any of the Licensed Patent Rights, or (b) that is comprised of, utilizes or incorporates Licensed Biological Materials, or (c) that is discovered, developed or made using a Licensed Process.
Licensed Patent Rights The Licensee shall indemnify and hold the IC, its employees, students, fellows, agents, and consultants harmless from and against all liability, demands, damages, expenses, and losses, including but not limited to death, personal injury, illness, or property damage in connection with or arising out of:
Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.
Licensed Technology (a) LICENSOR is not aware of any interference, infringement, misappropriation, or other conflict with any intellectual property rights of third parties, and LICENSOR has never received any charge, complaint, claim, demand, or notice alleging any such interference, infringement, misappropriation, or violation (including any claim that LICENSOR must license or refrain from using any intellectual property rights of any third party). To the knowledge of LICENSOR, no third party has interfered with, infringed upon, misappropriated, or otherwise come into conflict with any of the LICENSED TECHNOLOGY. (b) Exhibit A identifies each patent or registration which has been issued to LICENSOR with respect to any of the LICENSED TECHNOLOGY and identifies each pending patent application or application for registration which LICENSOR has made with respect to any of the LICENSED TECHNOLOGY. LICENSEE acknowledges that LICENSOR has previously made available to LICENSEE correct and complete copies of all such patents, registrations and applications (as amended to-date) in LICENSOR’s possession and has made available to LICENSEE correct and complete copies of all other written documentation in LICENSOR’s possession evidencing ownership and prosecution (if applicable) of each such item. (c) Exhibit A identifies each item of LICENSED TECHNOLOGY that is assigned to LICENSOR or that LICENSOR uses pursuant to license, sublicense, agreement, or permission. LICENSOR has made available to LICENSEE correct and complete copies of all such licenses, sublicenses, agreements, patent prosecution files and permissions (as amended to-date) in LICENSOR’s possession. With respect to each item of LICENSED TECHNOLOGY required to be identified in Exhibit A and to the knowledge of LICENSOR: (i) the license, sublicense, agreement, or permission covering the item is legal, valid, binding, enforceable, and in full force and effect; (ii) the license, sublicense, agreement, or permission will continue to be legal, valid, binding, enforceable, and in full force and effect on identical terms following the consummation of the transactions contemplated hereby; (iii) no Party to the license, sublicense, agreement, or permission is in breach or default, and no event has occurred which with notice or lapse of time would constitute a breach or default or permit termination, modification, or acceleration thereunder; (iv) no party to the license, sublicense, agreement, or permission has repudiated any provision thereof; (v) the underlying item of LICENSED TECHNOLOGY is not subject to any outstanding lien or encumbrance, injunction, judgment, order, decree, ruling, or charge; (vi) no action, suit, proceeding, hearing, investigation, charge, complaint, claim, or demand is pending or is threatened which challenges the legality, validity, or enforceability of the underlying item of LICENSED TECHNOLOGY; and (vii) except as provided in Exhibit A, LICENSOR has not granted any license or similar right to the LICENSED TECHNOLOGY within the GENERAL FIELD or PARTHENOGENESIS FIELD.
Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.
