Podmínky specifické pro Licenční systém Sample Clauses

Podmínky specifické pro Licenční systém. Pokud Zákazník získá licenci na Software v rámci licenčního systému MSC MasterKey Plus, licenčního systému, nebo jiného podobného tokenového licenčního systému společnosti MSC (všechny nazývané licenční systémy), potom platí kromě výše uvedených podmínek v části 4.3 také následující licenční Podmínky specifické pro Licenční systém: V rámci licenčního systému Zákazník získává „licenční jednotky“ (např. jednotky „Masterkey Plus Tokens“ v rámci licenčního systému MSC.MasterKey Plus). Ke spuštění každé instance každého Softwaru licencovaného v rámci daného Licenčního systému je nutný určitý počet licenčních jednotek. Licenční jednotky získané v rámci jednoho Licenčního systému nelze použít ke spuštění Softwaru licencovaného v rámci jiného Licenčního systému (např. jednotky MSC.MasterKey Plus Tokens nelze použít ke spuštění Softwaru poskytovaného v rámci Licenčního systému Enterprise Advantage). Software licencovaný v rámci určitého Licenčního systému je omezen výhradně na software stanovený v příslušné produktové příloze k Licenčnímu systému (někdy označované jako „Přehled“ nebo „Tabulka“), která je přiložena nebo je součástí Rozpisu objednávky nebo této Smlouvy. Zákazník není oprávněn k použití žádného jiného softwarového programu v rámci tohoto Licenčního systému bez ohledu na to, zda jsou tyto softwarové programy nabízeny společností MSC v rámci stejného Licenčního programu.
AutoNDA by SimpleDocs

Related to Podmínky specifické pro Licenční systém

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

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Manufacturing Technology Transfer Except as the Committee ------------ --------------------------------- may otherwise agree in writing, in order to effectuate an orderly transition of the uninterrupted availability of Product to LILLY for purposes contemplated under this Agreement, MEGABIOS, at least ninety (90) days prior to completion of the Project or completion of Phase I Clinical Trials, whichever is earlier, shall transfer to LILLY all information and instructions concerning the manufacturing process and related matters in MEGABIOS' possession which may be necessary for LILLY to manufacture Product (including information regarding obtaining necessary Lipids related thereto) for clinical trials and commercialization as contemplated hereunder including, but not limited to, analytical and manufacturing methods. MEGABIOS shall also provide assistance (in the form of consultation) to LILLY with respect to manufacturing matters for a period of [ * ] months after completion of the initial transfer of information and instructions as provided below. Such transfer and assistance by MEGABIOS will be referred to herein as the "Manufacturing Transfer." All such information, methods and instructions transferred to LILLY under this Section 4.3 shall be referred to herein as the "Manufacturing Information," and shall be maintained in confidence by LILLY pursuant to Section 7.1, except that LILLY's obligation to maintain in confidence such Manufacturing Information shall survive for ten (10) years following expiration or termination of this Agreement. LILLY agrees that it will use all such transferred Manufacturing Information only for the manufacture of the Products and shall not disclose or transfer such Manufacturing Information to any third party manufacturer except as provided in Section 2.10. MEGABIOS shall provide, and bear its costs for, up to [ * ] FTEs for a period of up to [ * ] months [ * ] in aggregate) to accomplish the Manufacturing Transfer. Such FTEs, at LILLY's request, shall include visits to LILLY's facilities by MEGABIOS personnel including up to [ * ] from MEGABIOS' head of manufacturing. MEGABIOS shall furnish any additional reasonable assistance beyond the assistance described above regarding manufacturing matters that LILLY may request and that MEGABIOS is able to provide, for up to [ * ] after the initial transfer of Manufacturing Information, providing that LILLY [ * ] incurred with respect to such additional assistance.

  • Manufacturing License Subject to the terms of this Agreement, including without limitation Section 2.2, Theravance grants to GSK an exclusive license under the Theravance Patents and Theravance Know-How to make and have made API Compound or formulated Alliance Product in the Territory.

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • PRODUCT MANUFACTURER'S SUPPLIERS Only those dealers/distributors listed by the manufacturer will be considered authorized to act on behalf of the Product Manufacturer.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Product Specific Terms these terms apply to specific Products referenced in this section.

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