Version Upgrades Sample Clauses

Version Upgrades. ‌ In order to gain access to and rights to use a new Major Release of the Software, Licensee must purchase a Version Upgrade. Highsoft may, at its sole discretion, at any time choose to discontinue the offering of Version Upgrades and the supply of new Major Releases. In order to purchase a Version Upgrade, Licensee must own a valid License to the previous Major Release of the Software (e.g. in order to purchase Version Upgrade to 5.0, Licensee must own a valid License to 4.0). Licensee holding a License authorizing to use a Major Release older than the previous Major Release must thus purchase a new License (not just a Version Upgrade) in order to access the new Major Release. Once Licensee purchases a Version Upgrade, Licensee is authorized to use all Minor Releases to the Major Release to which Licensee holds a valid license.
Sample 1Sample 2
AutoNDA by SimpleDocs
Version Upgrades. This Agreement entitles the Customer to regular version upgrades. The version upgrades including any hot fixes, service packs and version upgrades are supplied free of charge to customers with a valid Agreement.
Sample 1Sample 2
Version Upgrades. Customer can upgrade the currently licensed Software Package to the newly designated point releases of the Software Package that has been released for general commercial distribution. For example, Customer can upgrade from version 5.6 to 5.7, or 5.7 to version 6.0 in the series. The new version may contain additional features, functionalities, and enhancements of the Software Package. Release of the Software Package designed by Edidev to operate on one operating system, or processor, is not the same as one designed for a different operating system, or processor, the latter Software Package requiring a separate XXXX. That being the case, a Software Package designed for one processor is not considered an upgrade to another Software Package having the same or lower version designed for another processor. For example, a 64-bit release of Software Package is not considered an upgrade to the 32-bit release of the Software Package whatever the version may be for both, or Software Package released for Windows 10 is not considered an upgrade to Software Package released for Windows 8 whatever the version may be for both.
Sample 1
Version Upgrades. Cypress shall implement the Version Upgrade into the live, hosted environment at a time mutually-agreed between Cypress and Customer’s primary Designated Representative; provided, however, Customer shall permit Cypress to implement such Version Upgrade not later than three (3) months following Cypress’s determination that the minor release is ready. Schedule B Hosting Services
Sample 1
Version Upgrades. For the term of this Agreement, Licensor shall furnish Licensee with all version upgrades upon completion; however the parties acknowledge that the Licensor is under no obligation to upgrade the Product beyond the version provided to Licensee at the commencement of this Agreement.
Sample 1
Version Upgrades. Service Provider shall maintain the Applications so as to execute without degradation or error as the underlying operating system or database are upgraded by STC Customer from one version to another within the same release, e.g., from 10.X to 10.Y (release version) with capability to rollback to previous steady state.
Sample 1
Version Upgrades. A license will be issued for any new software version(s) of the purchased edition that are released during the period of the paid support.
Sample 1
AutoNDA by SimpleDocs
Version Upgrades. 5.1 Cyres agrees to supply the Client with:
Sample 1
Version Upgrades. Service-Provider shall make available to End-User Version upgrades, all at additional nominal cost (shipping and media - if any). End-User shall be responsible for the installation and testing of any Version Upgrades.
Sample 1

Related to Version Upgrades

  • Upgrades If this copy of the Software is an upgrade from an earlier version of the Software, it is provided to you on a license exchange basis. You agree by your installation and use of such copy of the Software to voluntarily terminate your earlier XXXX and that you will not continue to use the earlier version of the Software or transfer it to another person or entity unless such transfer is pursuant to Section 3.

  • Software Modifications Company may request that BNYM, at Company’s expense, develop modifications to the software constituting a part of the Licensed System that BNYM generally makes available to customers for modification (“Software”) that are required to adapt the Software for Company’s unique business requirements. Such requests, containing the material features and functionalities of all such modifications in reasonable detail, will be submitted by Company in writing to BNYM in accordance with the applicable, commercially reasonable procedures maintained by BNYM at the time of the request. Company shall be solely responsible for preparing, reviewing and verifying the accuracy and completeness of the business specifications and requirements relied upon by BNYM to estimate, design and develop such modifications to the Software. BNYM shall have no obligation to develop modifications to the Licensed System requested by Company, but may in its discretion agree to develop requested modifications which it, in its sole discretion, reasonably determines it can accomplish with existing resources or with readily obtainable resources without disruption of normal business operations provided Company agrees at such time in writing to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification. BNYM shall be obligated to develop modifications under this Section 2.16 only upon the execution of and in accordance with a writing containing, to BNYM’s reasonable satisfaction, all necessary business and technical terms, specifications and requirements for the modification as determined by BNYM in its sole judgment (“Customization Order”) and Company’s agreement to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification (“Customization Fee Agreement”). All modifications developed and incorporated into the Licensed System pursuant to a Customization Order are referred to herein as “Company Modifications”. BNYM may make Company Modifications available to all users of the Licensed System, including BNYM, at any time after implementation of the particular Company Modification and any entitlement of Company to reimbursement on account of such action must be contained in the Customization Fee Agreement.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Integration; Modification This Agreement constitutes the entire understanding and agreement between the Company and the Executive regarding its subject matter and supersedes all prior negotiations and agreements, whether oral or written, between them with respect to its subject matter. This Agreement may not be modified except by a written agreement signed by the Executive and a duly authorized officer of the Company.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

Time is Money Join Law Insider Premium to draft better contracts faster.