IGER Research Rights Sample Clauses

IGER Research Rights. 5.1.1 Through the express grant of such rights in any SCHEDULE, CERES may xxxxx XXXX the right to use CERES INTELLECTUAL PROPERTY to the extent required for, and for the sole purpose of, the performance by IGER (or its SUBCONTRACTORS) of RESEARCH PROJECTS. SCHEDULES may specify that similar rights are granted with respect to defined elements of CERES BACKGROUND INTELLECTUAL PROPERTY. 5.1.2 IGER shall have the right to use JOINT INTELLECTUAL PROPERTY and OTHER RESEARCH RESULTS (a) for the purpose of the implementation of RESEARCH PROJECTS; (b) subject to Article 3 and CERES’ prior written approval, for internal research purposes and research under United Kingdom government or European Union funding in collaboration with academic institutions in the European Union, provided that CERES’ approval may be conditional upon (i) CERES receiving the exclusive right (subject to Articles 5.1.2(a) and 5.2) to use and exploit commercially the results of such research in COLLABORATION CROPS, (ii) adequate safeguards to prevent unauthorized use or disclosure of JOINT INTELLECTUAL PROPERTY, OTHER RESEARCH RESULTS or results directly or indirectly based on any of the foregoing and (iii) CERES reviewing and approving the terms and conditions of any agreement governing such research activities.
AutoNDA by SimpleDocs

Related to IGER Research Rights

  • Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.

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

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

  • Technology License 4.1 Unless any event described in Article 2.2 or 2.3 of this Agreement occurs, all of the technology required to be licensed for any of Party B’s business shall be provided by Party A on an exclusive basis. Party A will try its best to license Party B to use the technology owned by Party A, or re-license Party B to use the technology as approved by the owner. 4.2 The Parties shall negotiate with each other to enter into specific technology license contracts to expressly specify the detail matters such as the technology to be licensed, the method to license the technology, license fees and payment.

  • Development License Subject to the terms and conditions of this XXXX, You are licensed to perform an installation of the SOFTWARE for an unlimited use in designing, testing and creating Developed Software by unlimited Developers on one or more computers.

  • Inventions Retained and Licensed I have attached hereto, as Exhibit A, a list describing all inventions, original works of authorship, developments, improvements, and trade secrets which were made by me prior to my employment with the Company (collectively referred to as “Prior Inventions”), which belong to me, which relate to the Company’s proposed business, products or research and development, and which are not assigned to the Company hereunder; or, if no such list is attached, I represent that there are no such Prior Inventions. If in the course of my employment with the Company, I incorporate into a Company product, process or machine a Prior Invention owned by me or in which I have an interest, the Company is hereby granted and shall have a nonexclusive, royalty-free, irrevocable, perpetual, worldwide license to make, have made, modify, use and sell such Prior Invention as part of or in connection with such product, process or machine.

  • Technology Research Analyst Job# 1810 General Characteristics

  • Manufacturing Technology Transfer Except as the Committee ------------ --------------------------------- may otherwise agree in writing, in order to effectuate an orderly transition of the uninterrupted availability of Product to LILLY for purposes contemplated under this Agreement, MEGABIOS, at least ninety (90) days prior to completion of the Project or completion of Phase I Clinical Trials, whichever is earlier, shall transfer to LILLY all information and instructions concerning the manufacturing process and related matters in MEGABIOS' possession which may be necessary for LILLY to manufacture Product (including information regarding obtaining necessary Lipids related thereto) for clinical trials and commercialization as contemplated hereunder including, but not limited to, analytical and manufacturing methods. MEGABIOS shall also provide assistance (in the form of consultation) to LILLY with respect to manufacturing matters for a period of [ * ] months after completion of the initial transfer of information and instructions as provided below. Such transfer and assistance by MEGABIOS will be referred to herein as the "Manufacturing Transfer." All such information, methods and instructions transferred to LILLY under this Section 4.3 shall be referred to herein as the "Manufacturing Information," and shall be maintained in confidence by LILLY pursuant to Section 7.1, except that LILLY's obligation to maintain in confidence such Manufacturing Information shall survive for ten (10) years following expiration or termination of this Agreement. LILLY agrees that it will use all such transferred Manufacturing Information only for the manufacture of the Products and shall not disclose or transfer such Manufacturing Information to any third party manufacturer except as provided in Section 2.10. MEGABIOS shall provide, and bear its costs for, up to [ * ] FTEs for a period of up to [ * ] months [ * ] in aggregate) to accomplish the Manufacturing Transfer. Such FTEs, at LILLY's request, shall include visits to LILLY's facilities by MEGABIOS personnel including up to [ * ] from MEGABIOS' head of manufacturing. MEGABIOS shall furnish any additional reasonable assistance beyond the assistance described above regarding manufacturing matters that LILLY may request and that MEGABIOS is able to provide, for up to [ * ] after the initial transfer of Manufacturing Information, providing that LILLY [ * ] incurred with respect to such additional assistance.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

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