Transition to Subscription License Model Sample Clauses

Transition to Subscription License Model. If the Parties mutually agree that any on- premises Subscription Software purchased under this SPA as part of an on-premises Software System as a service will be replaced with or upgraded to Subscription Software hosted in a data center, then upon such time which the Parties execute the applicable Ordering Document, (a) the licenses granted to such on-premises Subscription Software under the applicable Ordering Document will automatically terminate, (b) DIR Customer and its Authorized Users will cease use of the applicable on-premises copies of Subscription Software, and (c) the replacement hosted Subscription Software provided hereunder will be governed by the terms of the SSA and this SPA.
AutoNDA by SimpleDocs

Related to Transition to Subscription License Model

  • Subscription License A Subscription license will commence on the date specified in the Notification Form and continue in force for the fixed initial term specified therein. The license is firm and cannot be cancelled or otherwise reduced or terminated by Customer during the license term. On expiry of the initial term, the subscription license will terminate unless renewed. Unless otherwise stated in the applicable Notification Form, each subscription license will include the provision of Support Services.

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

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

  • Software Subscription Lifecycle During the life cycle of Red Hat Software, the scope of Software Maintenance and Support evolves and, after a number of years, we discontinue Software Maintenance and Support for older versions of Software. The details of the Software Maintenance and Production Support life cycle are set forth at xxxxx://xxxxxx.xxxxxx.xxx/support/policy/update_policies.html. If available, you may purchase Extended Update Support and/or Extended Life Cycle Support, as described in Exhibit 1.G, to extend your Subscription Services for certain versions of Software.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy It is NIH’s intent to promote the dissemination of research findings from use of controlled-access dataset(s) subject to the NIH GDS Policy as widely as possible through scientific publication or other appropriate public dissemination mechanisms. Approved Users are strongly encouraged to publish their results in peer-reviewed journals and to present research findings at scientific meetings.

  • License Model The software is licensed under two models: • Perpetual License Model – Under this model, you have licensed the software under perpetual license terms, as code that is installed on your premises or hosted for you by a third party acting as your agent (“Perpetual License Model”).

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

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

  • License Key 2.5. The Application Software may include an embedded security system which if provided must be used together with a license key. The license key may limit the use of the Application Software to the applicable Use Level and prevent a single User from using more than one workstation at the same time and is valid for a certain period of time following which the license key must be renewed. Customer is solely responsible for any cost or loss arising out of Customer’s failure or delay to renew the license key.

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