SYSTEM SOFTWARE LICENSE‌ Sample Clauses

SYSTEM SOFTWARE LICENSE‌. If Authorized User is a state agency, board, commission, or other quasi-political entity of the Commonwealth of Virginia or other body referenced in Title 2.2 of the Code of Virginia, the license shall be held by the Commonwealth. If Authorized User is a locality, municipality, school, school system, college, university, local board, local commission, or local quasi-political entity, the license shall be held by that public body. If Authorized User is a private institution of higher education which is listed at xxxx://xxx.xxxx.xxx/Our-Colleges/Profiles.aspx, the license shall be held by that private institution. Software License (for internal embedded software, firmware and unless otherwise provided in the State’s solicitation document, or in an attachment hereto): Products or Deliverables comprising goods, equipment or hardware may contain System Software for internal operation, or as embedded System Software or firmware that is generally not sold or licensed as a severable software product. System Software may be provided on separate media, such as floppy diskettes or CD-ROM, or may be included within the Product or Deliverable at or prior to delivery. Such System Software is proprietary, copyrighted, and may also contain valuable trade secrets and may be protected by patents. Supplier grants the Authorized Users of this Contract a license to use the code (or any replacement provided) on, or in conjunction with, only the Deliverables or Products purchased, or with any system identified in the Contract. Authorized Users may make and install copies of the System Software to support the authorized level of use. Provided, however that if the Product or Deliverable is inoperable, the System Software may be copied for temporary use on other hardware. Authorized Users shall promptly affix to any such copy the same proprietary and copyright notices affixed to the original. Individual Authorized Users may make one copy of the software for archival, back-up or disaster recovery purposes. The license set forth in this paragraph shall terminate immediately upon the Authorized User’s discontinuance of the use of the Product or Deliverable on which the System Software is installed. The System Software may be transferred to another party only with the transfer of the Product or Deliverable. If the Product or Deliverable is transferred by any Authorized User, such Authorized User shall before the transfer takes place l i) destroy all System Software copies made by the A...
Sample 1Sample 2Sample 3See All (13)
AutoNDA by SimpleDocs
SYSTEM SOFTWARE LICENSE‌. Any and all license rights granted pursuant to this Contract will be held pursuant to the terms of the “Licensing within the Commonwealth” section of this Contract below.
Sample 1
SYSTEM SOFTWARE LICENSE‌. Sabre grants to Customer a non- exclusive, non-transferable and limited license to use the System Software provided by Sabre solely in connection with the Customer's access to and use of the Sabre System. Customer will not disclose, lease, sell, export, distribute, copy, transfer or assign the System Software to any third party without Sabre’s prior written consent. One copy of the System Software may be made for back- up purposes only. System software must incorporate all notices and legends appearing on the original media. System Software owned by third parties and sub-licensed or distributed to Customer by Sabre may be subject to further terms and conditions contained in the license agreement for such System Software and Customer agrees to comply with such further terms and conditions. Sabre may audit the presence of System Software at the Site at any time, through manual or automated means. Customer may not modify, create derivative works, reverse compile, decompile, disassemble, reverse assemble, reverse engineer or otherwise use the System Software except as expressly allowed in this Agreement.
Sample 1
SYSTEM SOFTWARE LICENSE‌. If Authorized User is a state agency, board, commission, or other quasi-political entity of the Commonwealth of Virginia or other body referenced in Title 2.2 of the Code of Virginia, the license shall be held by the Commonwealth. If Authorized User is a locality, municipality, school, school system, college, university, local board, local commission, or local quasi-political entity, the license shall be held by that public body. If Authorized User is a private institution of higher education which is listed at xxxx://xxx.xxxx.xxx/Our-Colleges/Profiles.aspx, the license shall be held by that private institution.
Sample 1
SYSTEM SOFTWARE LICENSE‌. Subject to and conditioned upon your compliance with the terms and conditions of this XXXX, Cepton grants to You a limited, non-exclusive, non-transferable, non- sublicensable, license to use the applicable System Software as incorporated in the applicable Hardware Product purchased by You, in unmodified executable code format only, solely as required for the normal operation and maintenance of the Hardware Product and in accordance with Cepton’s published documentation for such Product. Each such license shall be valid until termination.
Sample 1
SYSTEM SOFTWARE LICENSE‌ 
Sample 1Sample 2Sample 3See All (7)

Related to SYSTEM SOFTWARE LICENSE‌

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

  • Software Licence The following licence terms apply whether HP provides software to Customer as part of a managed service or as a separate software transaction.

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

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

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

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

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

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