Reciprocal Non-Exclusive Research Program Licenses Sample Clauses

Reciprocal Non-Exclusive Research Program Licenses. During the Research Term, effective as of the Effective Date:
Sample 1
AutoNDA by SimpleDocs

Related to Reciprocal Non-Exclusive Research Program Licenses

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

  • Sublicense Agreements Sublicenses under this Section 2.3 shall be granted only pursuant to written agreements, which shall be subject to and consistent with the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect: 2.3.2.1 all provisions necessary to ensure Licensee’s ability to comply with Licensee’s obligation under or not violate the provisions of Sections 4.4, 4.5, 4.6, 5.1, 5.3, 5.4, 8.1 and 11.1; 2.3.2.2 a section substantially the same as Article 9 (Indemnification), which also shall state that the Indemnitees (as defined in Section 9.1) are intended third party beneficiaries of such Sublicense agreement for the purpose of enforcing such indemnification; 2.3.2.3 in the event of termination of the license set forth in Section 2.1.1 above (in whole or in part (e.g., termination of the license as to a Licensed Product or in a particular country)), any existing Sublicense shall terminate to the extent of such terminated license; provided, however, that, for each Sublicensee, upon termination of the license, if the Sublicensee is not then in breach of the Sublicense agreement such that Licensee would have the right to terminate such Sublicense agreement, such Sublicensee shall have the right to obtain a license from Harvard on the same terms and conditions as set forth herein, which shall not impose any representations, warranties, obligations or liabilities on Harvard that are not included in this Agreement, provided that (a) the scope of the license granted directly by Harvard to such Sublicensee shall be coextensive with the scope of the license granted by Licensee to such Sublicensee, (b) if the Sublicense granted to such Sublicensee was non-exclusive, such Sublicensee shall not have the right to participate in the prosecution or enforcement of the Patent Rights under the license granted to it directly by Harvard and (c) if there are more than one Sublicensee, each Sublicensee that is granted a direct license shall be responsible for a pro rata share of the reimbursement due under Section 6.2.3 of this Agreement (based on the number of direct licenses under the Patent Rights in effect on the date of reimbursement); 2.3.2.4 the Sublicensee shall only be entitled to sublicense its rights under such Sublicense agreement on the terms set forth in this Section 2.3; and 2.3.2.5 the Sublicensee shall not be entitled to assign the Sublicense agreement without the prior written consent of Harvard, except that Sublicensee may assign the Sublicense agreement to a successor in connection with the merger, consolidation or sale of all or substantially all of its assets or that portion of its business to which the Sublicense agreement relates; provided, however, that any permitted assignee agrees in writing in a manner reasonably satisfactory to Harvard to be bound by the terms of such Sublicense agreement.

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

  • Exclusive Negotiations The State will not bargain collectively or meet with any employee organization other than MSEA-SEIU with reference to terms and conditions of employment of employees covered by this Agreement. If any such organizations request meetings they will be advised by the State to transmit their requests concerning terms and conditions of employment to MSEA-SEIU.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

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

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

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

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

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