Licensing Modes. Customer cannot mix the licensing modes for Dashboard Users on the same License Certificate. Access to the Server may either be “Per Named User”, or “Per Server Use”, or “Per Core Use”.
Licensing Modes
Licensing Modes Sample Clauses
Related to Licensing Modes
Sublicensing Rights (a) The license(s) granted to Intellia in Section 2.1 and to Caribou in Section 2.2 may be sublicensed, in full or in part, by Intellia and Caribou, respectively, (each, the “Sublicensing Party”) by a written agreement to its Affiliates and Third Parties (with the further right to sublicense [***] provided that the following shall likewise apply with respect to sublicenses granted by a Sublicensee), provided, that: (i) the Sublicensing Party will provide to the other Party a copy of any sublicense agreement with a Sublicensee within [***] days of execution thereof, which sublicense agreement may be redacted as necessary to protect commercially sensitive information to the extent such information is not reasonably necessary to determine compliance with this Agreement or to determine the rights granted under any of the Caribou IP or Intellia IP, as applicable (together with an accurate English translation of such sublicense, if applicable) provided that if such agreement is with a Related Party the Sublicensing Party shall provide an unredacted copy thereof; (ii) the Sublicensing Party will be responsible for any and all obligations of such Sublicensee as if such Sublicensee were “Intellia” or “Caribou”, as applicable, hereunder; (iii) any such Sublicensee will agree in writing to be bound by identical obligations as the Sublicensing Party hereunder with respect to the activities of such Sublicensee hereunder; (iv) to the extent that the Sublicensing Party or any Sublicensee grants a sublicense under any intellectual property subject to a Caribou In-License or Intellia Included In-License, as applicable, such sublicense (and such further sublicensee) will be subject to the terms of such Caribou In-License or Intellia Included In-License, including such sublicensee’s compliance with the Required In-License Provisions [***].
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.
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.
Software Licensing Contractor represents and warrants that the software, if any, as delivered to City, does not contain any program code, virus, worm, trap door, back door, time or clock that would erase data or programming or otherwise cause the software to become inoperable, inaccessible, or incapable of being used in accordance with its user manuals, either automatically, upon the occurrence of licensor-selected conditions or manually on command. Contractor further represents and warrants that all third party software, delivered to City or used by Contractor in the performance of the Contract, is fully licensed by the appropriate licensor.
Patents, Licenses, Franchises and Formulas The Borrower and its Subsidiaries own or have valid licenses to use all material patents, trademarks, permits, service marks, trade names, copyrights, licenses, franchises and formulas, or rights with respect to the foregoing, and have obtained assignments of all leases and other rights of whatever nature, reasonably necessary for the present conduct of their business, without any known conflict with the rights of others except for such failures and conflicts which have not had, and could not reasonably be expected to have, either individually or in the aggregate, a Material Adverse Effect.
Licence Grant If you use our software as part of using our Services then we and our licensors grant you a licence that is personal to you only, which is limited, non- exclusive, revocable, non-transferable and without the right to sub-licence. A “licence” is legal way in which we are able to grant you the right to use something for a specific and limited – in this context we use to describe how we grant you the right to use the Service (including its software). You are permitted to use the software provided by us for use solely for the purposes of availing of our Services pursuant to this Agreement and for no other purpose whatsoever. Unless expressly granted by us in this Agreement, nothing in this Agreement shall be interpreted as granting you a licence to use any of our software or other intellectual property rights for any other purposes.
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.
Sublicensing Licensee has the right to grant Sublicense Agreements under the Licensed Subject Matter consistent with the terms of the Agreement, subject to the following: (a) A Sublicense Agreement shall not exceed the scope and rights granted to Licensee hereunder. Sublicensee must agree in writing to be bound by the applicable terms and conditions of the Agreement and shall indicate that Licensor is a third party beneficiary of the Sublicense Agreement. In the event of termination of this Agreement, continued sublicense rights shall be governed by Section 7.5(a) (Effect of Termination). Licensee has no right to grant a Sublicensee the right to grant further sub-Sublicense Agreements. (b) Licensee shall deliver to Licensor a true, complete, and correct copy of each Sublicense Agreement granted by Licensee, Affiliate or Sublicensee, and any modification or termination thereof, within thirty (30) days following the applicable execution, modification, or termination of such Sublicense Agreement. All Sublicense Agreements will be in English. (c) Notwithstanding any such Sublicense Agreement, Licensee will remain primarily liable to Licensor for all of the Licensee’s duties and obligations contained in the Agreement, including without limitation the payment of running royalties due under Section 3.2 whether or not paid to Licensee by a Sublicensee. Any act or omission of a Sublicensee that would be a breach of the Agreement if performed by Licensee will be deemed to be a breach by Licensee. Each Sublicense Agreement will contain a right of termination by Licensee in the event that the Sublicensee breaches the payment or reporting obligations affecting Licensor or any other terms and conditions of the Sublicense Agreement that would constitute a breach of the Agreement if such acts were performed by Licensee.
License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.
Third Party Royalties (i) In the event that Amgen, its Affiliates or Sublicensee obtains a license under Patents of a Third Party in any country that Amgen or its Affiliate, on the advice of patent counsel, determines, in the absence of a license thereunder could be considered to be infringed by the manufacture, use, sale, offer for sale or import of the Compound contained in a Product sold by Amgen (or its Affiliate or Sublicensee) in such country (in each case, a “Necessary Third Party License”), then Amgen may deduct […***…]% of the royalties actually paid to such Third Party under such Necessary Third Party License with respect to sales of such Product in such country from the royalty payments owed to Xencor pursuant to Section 6.7 with respect to Net Sales of such Product in such country, provided that the royalties payable to Xencor with respect to such Product in such country may not be reduced by more than […***…]% in any calendar quarter as a result of any and all such offsets in the aggregate. (ii) In the event that Amgen, its Affiliates or Sublicensee obtains a license (other than a Necessary Third Party License) under Patents of a Third Party in any country that Amgen or its Affiliate determines are necessary or reasonably useful to Develop, make, use, sell, offer for sale or import a Compound or Product sold by Amgen (or its Affiliate or Sublicensee) in such country (in each case, a “Useful Third Party License”), then Amgen may deduct […***…]% of the […***…] actually paid to such Third Party under such Useful Third Party License with respect to sales of such Product in such country from the royalty payments owed to Xencor pursuant to Section 6.7 with respect to Net Sales of such Product in such country, provided that the royalties payable to Xencor with respect to such Product in such country may not be reduced by more than […***…]% in any calendar quarter as a result of any and all such offsets in the aggregate. (iii) For the avoidance of doubt, subject to the foregoing, it is understood that a Party shall be solely responsible for payment of any and all royalties and other amounts owed by such Party under its license or other agreements with Third Parties that were entered into prior to the Effective Date; provided, however, that Amgen shall be responsible for payment of all payments that become due after the Option Exercise Date under the Catalent Agreement (defined in Section 10.2(b)) as a result of the Development, manufacture, use, sale, offer for sale or import of any Product by or on behalf of Amgen or any of its Affiliates or Sublicensees.
