Purchase of Machines Royalties and Licenses
Purchase of Machines Royalties and Licenses Sample Clauses
Related to Purchase of Machines Royalties and Licenses
Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.
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.
Ownership and License in Deliverables Unless otherwise specified in a specific Purchase Order concerning procurement of a SaaS product:
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.
GRANT OF LICENSE AND LIMITATIONS License to Use the Licensed Software. In accordance with the terms and conditions hereof, the Licensor agrees to grant to Bianfeng Networking a license to install and operate the Licensed Software on the Designated Computers and to grant to its customers the right to use such software system.
Xxxxx of License Georgia Institute of Technology shall grant the Student a limited, nonexclusive, nontransferable and revocable license to use and occupy an assigned space in a Georgia Institute of Technology facility in accordance with the terms and conditions of this Contract (the “License”). The parties to this Contract do not intend that an estate, a tenancy or any other interest in property should pass from Georgia Institute of Technology to Student. Instead, it is the intention of the parties that the relationship between Georgia Institute of Technology and Student be that of licensor and licensee and the sole right of Student to use the assigned space as a living unit shall be based upon the License granted in this Contract.
Xxxxx of License; Limitations The Engineer is granted a limited revocable non-exclusive license to use the registered TxDOT trademark logo (TxDOT Flying “T”) on any deliverables prepared under this contract that are the property of the State. The Engineer may not make any use of the registered TxDOT trademark logo on any other materials or documents unless it first submits that request in writing to the State and receives approval for the proposed use. The Engineer agrees that it shall not alter, modify, dilute, or otherwise misuse the registered TxDOT trademark logo or bring it into disrepute.
License of Data; Warranty; Termination of Rights A. The valuation information and evaluations being provided to the Trust by USBFS pursuant hereto (collectively, the “Data”) are being licensed, not sold, to the Trust. The Trust has a limited license to use the Data only for purposes necessary to valuing the Trust’s assets and reporting to regulatory bodies (the “License”). The Trust does not have any license nor right to use the Data for purposes beyond the intentions of this Agreement including, but not limited to, resale to other users or use to create any type of historical database. The License is non-transferable and not sub-licensable. The Trust’s right to use the Data cannot be passed to or shared with any other entity. The Trust acknowledges the proprietary rights that USBFS and its suppliers have in the Data. B. THE TRUST HEREBY ACCEPTS THE DATA AS IS, WHERE IS, WITH NO WARRANTIES, EXPRESS OR IMPLIED, AS TO MERCHANTABILITY OR FITNESS FOR ANY PURPOSE OR ANY OTHER MATTER. C. USBFS may stop supplying some or all Data to the Trust if USBFS’s suppliers terminate any agreement to provide Data to USBFS. Also, USBFS may stop supplying some or all Data to the Trust if USBFS reasonably believes that the Trust is using the Data in violation of the License, or breaching its duties of confidentiality provided for hereunder, or if any of USBFS’s suppliers demand that the Data be withheld from the Trust. USBFS will provide notice to the Trust of any termination of provision of Data as soon as reasonably possible.
Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.
Outbound Licenses Part 2.7(d) of the Disclosure Schedule accurately identifies each Contract pursuant to which any Person has been granted any license under, or otherwise has received or acquired any right (whether or not currently exercisable) or interest in, any Seller IP. The Seller is not bound by, and no Seller IP is subject to, any Contract containing any covenant or other provision that in any way limits or restricts the ability of the Seller to use, exploit, assert, or enforce any Seller IP anywhere in the world.
