Inventions Based on Pfizer Compounds Sample Clauses

Inventions Based on Pfizer Compounds. As provided for more specifically in Article 7 of this Agreement, Pfizer shall own all Inventions made in the course of conducting the Research Program that are either compounds Owned By Pfizer, or compositions containing one or more such compounds, or methods of administering, making or using one or more such compounds.
AutoNDA by SimpleDocs

Related to Inventions Based on Pfizer Compounds

  • Know-How The term “

  • Background Technology List here prior contracts to assign Inventions that are now in existence between any other person or entity and you.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • Research Program The term “Research Program” shall mean the research program to be undertaken by TSRI under the direction and control of the Principal Investigator as expressly set forth on Exhibit A hereto.

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

  • Background IP As between the Parties, each Party will retain all right, title and interest in and to all of its Background IP.

  • Joint Inventions For Subject Inventions conceived or first actually reduced to practice under this Agreement that are joint Subject Inventions made by CONTRACTOR and USER, each Party shall have the option to elect and retain title to its undivided rights in such joint Subject Inventions.

  • Patent Rights The State and the U. S. Department of Transportation shall have the royalty free, nonexclusive and irrevocable right to use and to authorize others to use any patents developed by the Engineer under this contract.

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

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