Functionality Changes Clause Samples

The Functionality Changes clause defines the process and conditions under which modifications to a product or service's features or capabilities may be made during the term of an agreement. Typically, this clause outlines who has the authority to propose or approve changes, the notice requirements, and any limitations or obligations regarding the scope or timing of such changes. For example, it may allow a software provider to update or enhance features, provided they notify the customer in advance or ensure that core functionalities remain unaffected. The primary purpose of this clause is to provide flexibility for improvements or necessary adjustments while protecting both parties from unexpected or disruptive alterations.
POPULAR SAMPLE Copied 1 times
Functionality Changes. Instinct Innovations reserves the right to add new functionality and modify existing functionality to the Redbook Software as and when it deems fit, and make any such changes available in newer versions of the Redbook Software or native mobile application or all of these at its discretion. The Subscriber will be duly notified upon release of such newer versions and Instinct Innovations reserves the right to automatically Upgrade all its users, including the Subscriber, to the latest version of the Redbook Software as and when Instinct Innovations deems fit.
View SourceView Similar (3)
Functionality Changes. Due to device differences between the VIEVU solution and the Axon’s Axon Evidence solution, there may be functionality gaps that will not allow for all migrated data to be displayed the same way in the user interface after Migration
View SourceView Similar (35)
Functionality Changes. If IAC Global requests functionality to interact with a Material Car Participant in a new way (e.g. selling insurance, gas option etc.) it will request in writing that Worldspan build such functionality within a reasonable specified time period, provided, that if the relevant supplier causes a delay in Worldspan’s delivery of such functionality by unreasonably delaying or withholding development cooperation and implementation, the specified time period will be extended for a period of time equal to such delay. Such functionality changes will be subject to terms and conditions as may be mutually agreed upon.
View SourceView Similar (4)
Functionality Changes. Timing and cost subject to agreement between the parties. While ▇▇▇▇▇▇▇▇▇.▇▇▇’s fee structure provides substantial incentive for delivering an optimal experience to Client and Client Customers, ▇▇▇▇▇▇▇▇▇.▇▇▇ also will meet the following service levels.
View SourceView Similar (2)
Functionality Changes. Hellodoc reserves the right to add new functionality and modify existing functionality to the MyHealthClinic Software as and when it deems fit, and make any such changes available in newer versions of the MyHealthClinic Software at its discretion. The Subscriber will be duly notified upon release of such newer versions and Hellodoc reserves the right to automatically Upgrade all its users, including the
View Source
Functionality Changes. Due to device differences between the VIEVU solution and the Axon’s Axon Evidence solution, there may be functionality gaps that will not allow for all migrated data to be displayed the same way in the user interface after Migration Acceptance. Once the Migration is complete, Axon will notify Customer and an acceptance form. Customer is responsible for verifying that the scope of the project has been completed and all necessary data is migrated correctly and retained per Customer policy. Customer will have 90 days to provide Axon acceptance that the Migration was successful, or Axon will deem the Migration accepted. In the event Customer does not accept the Migration, Customer agrees to notify the Axon within a reasonable time. Customer also agrees to allow Axon a reasonable time to resolve any issue. In the event Customer does not provide the Axon written rejection of the Migration during these 90 days, Customer may be charged for additional monthly storage costs. After Customer provides acceptance of the Migration, the Axon will delete all data from the VIEVU solution 90 days after the Migration.
View Source

Related to Functionality Changes

  • NETWORK CHANGES 3.1. Sprint shall provide notice of network changes and upgrades in accordance with §§ 51.325 through 51.335 of Title 47 of the Code of Federal Regulations. Sprint may discontinue any interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. Sprint agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers, which may result from such discontinuance of service.

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • SCOPE CHANGES The Commissioner reserves the right to require, by written order, changes to the scope of the Contract, by altering, adding to or deducting from the Bid Specifications, such changes to be within the general scope of the Contract. If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under the Contract, whether or not changed by the order, the Commissioner shall, upon notice from Contractor as hereafter stated, make an equitable adjustment in the Contract price, the delivery schedule or both and shall modify the Contract. The Contractor must assert its right to an adjustment under this clause within thirty days from the date of receipt of the written order. However, if the Commissioner decides that the facts justify it, the Commissioner may provide an adjustment without receipt of a proposal. Failure to agree to any adjustment shall be a dispute under the Disputes clause, provided, however, that nothing in this clause shall excuse the Contractor from proceeding with the Contract as changed.

  • Contract Changes 31.1 All changes to the Call-Off Contract which cannot be accommodated informally as described in Clause 30 will require a Contract Change Note. 31.2 Either Party may request a contract change by completing and sending a draft Contract Change Note in the form in Schedule 4 of Part C - The Schedules ('the Contract Change Notice') to the other Party giving sufficient information to enable the other Party to assess the extent of the change and any additional cost that may be incurred. The Party requesting the contract change will bear the costs of preparation of the Contract Change Notice. Neither Party will unreasonably withhold nor delay consent to the other Party’s proposed changes to the Call-Off Contract. 31.3 Due to the agile-based delivery methodology recommended by the Framework Agreement, it may not be possible to exactly define the consumption of Services over the duration of the Call-Off Contract in a static Order Form. The Supplier should state the initial value of all Services that are likely to be consumed under the Call-Off Contract.