We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Specifically negotiated license rights Sample Clauses

Specifically negotiated license rights. The standard license rights granted to the Gov- ernment under paragraphs (b)(1) through (b)(3) of this clause, including the period dur- ing which the Government shall have gov- ernment purpose rights in technical data, may be modified by mutual agreement to provide such rights as the parties consider appropriate but shall not provide the Gov- ernment lesser rights than are enumerated in paragraph (a)(14) of this clause. Any rights so negotiated shall be identified in a license agreement made part of this contract.
Sample 1Sample 2Sample 3See All (14)
Specifically negotiated license rights. (i) The standard license rights granted to the Government under paragraphs (b)(1) through (b)(3) of this clause, including the period dur- ing which the Government shall have gov- ernment purpose rights in computer soft- ware, may be modified by mutual agreement to provide such rights as the parties consider appropriate but shall not provide the Gov- ernment lesser rights in computer software than are enumerated in paragraph (a)(15) of this clause or lesser rights in computer soft- ware documentation than are enumerated in paragraph (a)(14)of the Rights in Technical Data—Noncommercial Items clause of this contract. (ii) Any rights so negotiated shall be iden- tified in a license agreement made part of this contract.
Sample 1Sample 2Sample 3See All (9)
Specifically negotiated license rights. (1) Negotiate specific licenses when the parties agree to modify the standard license rights granted to the government or when the government wants to obtain rights in data in which it does not have rights. When negoti- ating to obtain, relinquish, or increase the Government’s rights in technical data, consider the acquisition strategy for the item, component, or process, in- cluding logistics support and other fac- tors which may have relevance for a particular procurement. The Govern- ment may accept lesser rights when it has unlimited or government purpose rights in data but may not accept less than limited rights in such data. The negotiated license rights must stipu- late what rights the Government has to release or disclose the data to other persons or to authorize others to use the data. Identify all negotiated rights in a license agreement made part of the contract. (2) When the Government needs addi- tional rights in data acquired with gov- ernment purpose or limited rights, the contracting officer must negotiate with the contractor to determine whether there are acceptable terms for transferring such rights. Generally, such negotiations should be conducted only when there is a need to disclose the data outside the Government or if the additional rights are required for competitive reprocurement and the an- ticipated savings expected to be ob- tained through competition are esti- mated to exceed the acquisition cost of the additional rights. Prior to negoti- ating for additional rights in limited rights data, consider alternatives such as— (i) Using performance specifications and form, fit, and function data to ac- quire or develop functionally equiva- lent items, components, or processes; (ii) Obtaining a contractor’s contrac- tual commitment to qualify additional sources and maintain adequate com- petition among the sources; or (iii) Reverse engineering, or pro- viding items from Government inven- tories to contractors who request the items to facilitate the development of equivalent items through reverse engi- neering. [56 FR 36389, July 31, 1991, as amended at 76 FR 11367, Mar. 2, 2011] (a) Use the clause at 252.227–7013, Rights in Technical Data–Noncommer- cial Items, in solicitations and con- tracts when the successful offeror(s) will be required to deliver to the Gov- ernment technical data pertaining to noncommercial items, or pertaining to commercial items for which the Gov- ernment will have paid for any portion of the development costs ...
Sample 1Sample 2See All (5)
Specifically negotiated license rights. (i) The standard license rights granted to the Government under paragraphs (b)(1) through (b)(3) of this clause, including the period dur-
Sample 1Sample 2
Specifically negotiated license rights. Negotiate specific licenses when the parties agree to modify the standard license rights granted to the Government or when the Government wants to obtain rights in computer software in which it does not have rights. When negotiating to obtain, relinquish, or increase the Government's rights in computer software, consider the planned software maintenance philosophy, anticipated time or user sharing requirements, and other factors which may have relevance for a particular procurement. If negotiating to relinquish rights in computer software documentation, consider the administrative burden associated with protecting documentation subject to restrictions from unauthorized release or disclosure. The negotiated license rights must stipulate the rights granted the Government to use, modify, reproduce, release, perform, display, or disclose the software or documentation and the extent to which the Government may authorize others to do so. Identify all negotiated rights in a license agreement made part of the contract.
Sample 1Sample 2
Specifically negotiated license rights. (1) Negotiate specific licenses when the parties agree to modify the standard license rights granted to the Government or when the Government wants to obtain rights in data in which it does not have rights. When negotiating to obtain, relinquish, or increase the Government's rights in technical data, consider the acquisition strategy for the item, component, or process, including logistics support and other factors which may have relevance for a particular procurement. The Government may accept lesser rights when it has unlimited or government purpose rights in data but may not accept less than limited rights in such data. The negotiated license rights must stipulate what rights the Government has to release or disclose the data to other persons or to authorize others to use the data. Identify all negotiated rights in a license agreement made part of the contract. (2) When the Government needs additional rights in data acquired with government purpose or limited rights, the contracting officer must negotiate with the contractor to determine whether there are acceptable terms for transferring such rights. Generally, such negotiations should be conducted only when there is a need to disclose the data outside the Government or if the additional rights are required for competitive reprocurement and the anticipated savings expected to be obtained through competition are estimated to exceed the acquisition cost of the additional rights. Prior to negotiating for additional rights in limited rights data, consider alternatives such as— (i) Using performance specifications and form, fit, and function data to acquire or develop functionally equivalent items, components, or processes; (ii) Obtaining a contractor's contractual commitment to qualify additional sources and maintain adequate competition among the sources; or (iii) Reverse engineering, or providing items from Government inventories to contractors who request the items to facilitate the development of equivalent items through reverse engineering.
Sample 1Sample 2
Specifically negotiated license rights. The above standard license rights (a. – d.), including the period of Government Purpose Rights, may be modified by mutual agreement but may not provide the Government with fewer rights than limited rights or restricted rights. The Recipient, its Subrecipients and its suppliers are not required to provide the Government with greater rights, but the Recipient does agree to promptly enter into negotiations with the Agreements Officer after a request to negotiate for greater rights. All technical data and noncommercial computer software in which the Recipient has granted greater rights shall be listed in a license that enumerates or describes the greater rights and is made part of the Agreement.
Sample 1
Specifically negotiated license rights. Negotiate specific licenses when the parties agree to modify the stand- ard license rights granted to the Gov- ernment or when the Government wants to obtain rights in computer software in which it does not have rights. When negotiating to obtain, re- linquish, or increase the Government’s rights in computer software, consider the planned software maintenance phi- losophy, anticipated time or user shar- ing requirements, and other factors which may have relevance for a par- ticular procurement. If negotiating to relinquish rights in computer software documentation, consider the adminis- trative burden associated with pro- tecting documentation subject to re- strictions from unauthorized release or disclosure. The negotiated license rights must stipulate the rights xxxxx- xx the Government to use, modify, re- produce, release, perform, display, or disclose the software or documentation and the extent to which the Govern- ment may authorize others to do so. Identify all negotiated rights in a li- cense agreement made part of the con- tract.
Sample 1

Related to Specifically negotiated license rights

  • Sublicense Rights Subject to the terms and conditions of this Agreement, Astellas shall have the right to grant sublicenses of the rights granted to it under Section 3.1.1 and 2.5.3(c) through multiple tiers to its Affiliates, provided that Astellas shall be and remain responsible for performance of all its obligations under this Agreement, and any action by an Affiliate shall be deemed an action by Astellas for which it is responsible. Astellas and its Affiliates may grant sublicenses through multiple tiers to Third Parties (a) whose primary business is contract manufacturing, solely for manufacturing and supplying Licensed Compound or Product to Astellas or any Related Party or (b) to a subcontractor to perform Astellas’s assigned responsibilities under this Agreement or any Research Plan, Development Plan or Co-Promotion Plan. All other sublicenses to be granted by Astellas or any Astellas Affiliate in the Joint Development Territory prior to […***…] will require prior written approval from Ambit, which shall not be unreasonably withheld or delayed, provided that in the event such sublicense is to all of Astellas’s rights in the U.S. or the Joint Development Territory to a Person who is not an Astellas Affiliate such approval shall be at Ambit’s sole discretion. In the case of sublicenses pursuant to the immediately preceding sentence above, Astellas shall provide to Ambit, upon Ambit’ written request, a copy of all executed agreements in which rights granted by Ambit under this Agreement are sublicensed (and Astellas shall have the right to make reasonable redactions prior to providing such agreements(s)). Ambit shall treat all such sublicense agreements as Astellas’s Confidential Information. Astellas or its Affiliates may grant sublicenses (i) in the Joint Development Territory at any time after the first NDA Submission in the Joint Development Territory, provided that, with respect to each applicable Product in the U.S., the Required Exercise Date has occurred and Ambit has not exercised the Co-Promotion Option or the Co-Promotion Term has expired or terminated and (ii) outside the Joint Development Territory, in each case ((i) and (ii)) through multiple tiers of Sublicensees without Ambit’s approval. Each sublicense granted by Astellas pursuant to this Section 3.1.2 shall be subject and subordinate to the terms and conditions of this Agreement. Any sublicense granted by Astellas shall impose on the Sublicensee obligations consistent with the terms and conditions of this Agreement, with each Sublicensee being required to comply with the obligations under this Agreement applicable to Sublicensees, and also to comply with the generally-applicable obligations of this Agreement that are appropriate for application to Sublicensees. Astellas shall ensure that all Persons to which it (or its Affiliate) grants sublicenses comply with all applicable terms and conditions of this Agreement, and Astellas shall be responsible for any failure of any such Sublicensee to comply with such terms or conditions, with the further understanding that any action or omission by any such Sublicensee that, if committed by Astellas would be a breach of this Agreement (with respect to those country(ies)) in which such Sublicensee is sublicensed), will be deemed a breach by Astellas of this Agreement (with respect to those country(ies) in which such Sublicensee is sublicensed) for which Astellas is responsible. Without limiting the foregoing, no sublicense shall modify Ambit’s rights or obligations under this Agreement (including Ambit’s Co-Promotion rights). Without limiting the foregoing, any sublicense agreement shall contain the following provisions, as applicable: (i) a requirement that such Sublicensee submit applicable Net Sales or other reports consistent with those required hereunder; (ii) audit requirements similar to those set forth in this Agreement; and (iii) a requirement that such Sublicensee comply with the confidentiality provisions of Article 6 with respect to Ambit’s Confidential Information.

  • License Rights The Recipient must provide a license to its “subject data” to the Federal Government, which license is: (a) Royalty-free, (b) Non-exclusive, and (c) Irrevocable, (2) Uses. The Federal Government’s license must permit the Federal Government to take the following actions provided those actions are taken for Federal Government purposes: (a) Reproduce the subject data, (b) Publish the subject data, (c) Otherwise use the subject data, and (d) Permit other entities or individuals to use the subject data, and

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

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • 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 License The SOFTWARE is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE is licensed, not sold.

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

  • Software Licenses Seller has all necessary licenses to use all material third-party software used in Seller's business, and Seller's use of third-party software does not infringe the rights of any Person.

Most Referenced Clauses

Most Referenced Definitions