Software License Management Sample Clauses

Software License Management. This Section details the obligations and responsibilities of the Parties regarding the management of CoreLogic’s Software licenses. Except where a responsibility is identified as a “P” responsibility for CoreLogic in the matrix below, Supplier shall be responsible for the following activities associated with the management of CoreLogic’s Software licenses: 3.4.1. Implement a process to capture required data of all Software license information for Software introduced into the CoreLogic IT environment by Supplier (e.g., all Software distributed to the CoreLogic IT environment by Supplier). Supplier shall integrate license information (e.g., per-user limits, concurrent licenses, number of processors on which Software is installed, versions, per-seat limits, license type, vendor) provided by CoreLogic into the CMDB in order to assist CoreLogic in tracking usage of Software licenses for Data Centers and Remote Sites. P 3.4.2. Manage and report the Software license data, *** or as requested by CoreLogic, for Systems and advise CoreLogic of any differences from the licensing limits provided by CoreLogic. P Coordinate and collaborate with CoreLogic and proactively advise CoreLogic of capacity issues (e.g., reporting numbers of Software licenses). P 3.4.3. Validate Software licensing, secure approvals and confirm compliance with CoreLogic prior to implementation of additional Software by Supplier. P A 3.4.4. Report availability and existence of Software licenses to CoreLogic. P 3.4.5. Provide updated Software license counts when Equipment is commissioned and decommissioned or Software is installed or de-installed. P 3.4.6. Maintain and report information regarding CoreLogic business approvals for new or additional Software, as required by CoreLogic. P 3.4.7. Maintain contract compliance for CoreLogic-owned Software from Supplier-supplied information. P 3.4.8. Assist CoreLogic with Software license compliance should CoreLogic be audited by a third party, and assist CoreLogic in providing Software license true-up for Software, as requested by CoreLogic. P 3.4.9. Recommend *** Software license management improvement and cost efficiencies related to Services. P A 3.4.10. Provide training to CoreLogic on usage of tools and processes of Software licensing management. P
AutoNDA by SimpleDocs
Software License Management. Develop an on-line key system to automatically manage and control the activation of SolarWinds software licenses • Develop a system to automatically retrieve license key information from a central key servers and transfer it directly to the customers software application for activation • Develop a highly secure 120 bit DES encryption with multiple levels of security 1) SSL secure session 2) Key request/response packet encryption 3) Serial number/Key encryption 4) Machine, software package, and customer information must match serial number/key pair exactly 5) Customer account must be up to date. • Support an unlimited number of software packages with an unlimited number of license levels. • Support hundreds of thousands of concurrent customers. • Automatically issue replacement keys when customers rebuild and/or replace their machines. • Detects licensing “cracks and hacks” schemes in real-time and shows statistics of license violations. • Record details on companies and users that violate licensing.
Software License Management 

Related to Software License Management

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

  • 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 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 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 Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition. 13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management

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