Recipient-Requested Changes to Existing Services Sample Clauses

Recipient-Requested Changes to Existing Services. If Kenvue requests that the level or volume of any Service be increased in scope beyond that provided to the Kenvue Business during the twelve (12) month period prior to the Separation or that the manner in which any Service is provided be changed from that provided to the Kenvue Business during the twelve (12) month period prior to the Separation, J&J will use commercially reasonable efforts to increase the level or volume of such Service or change the manner in which such Service is provided to extent commercially practicable; provided, that in no event shall J&J be required to materially increase the level or volume of any Service or, unless required for such Service to be in compliance with applicable Law, materially change the manner in which any Service is provided. If J&J increases the level or volume of such Service or changes the manner in which such Service is provided pursuant to this Section 2.02(d), any and all fees associated with such increase or change shall be negotiated in good faith and agreed upon between Kenvue and J&J.
AutoNDA by SimpleDocs
Recipient-Requested Changes to Existing Services. If Concentra requests that the level or volume of any Service be increased in scope beyond that provided to the Concentra Business during the twelve (12) month period prior to the Separation or that the manner in which any Service is provided be changed from that provided to the Concentra Business during the twelve (12) month period prior to the Separation, Select will use commercially reasonable efforts to increase the level or volume of such Service or change the manner in which such Service is provided to extent commercially practicable; provided, that in no event shall Select be required to materially increase the level or volume of any Service or, unless required for such Service to be in compliance with applicable Law, materially change the manner in which any Service is provided. If Select increases the level or volume of such Service or changes the manner in which such Service is provided pursuant to this Section 2.02(d), any and all fees associated with such increase or change shall be negotiated in good faith and agreed upon between Concentra and Select.

Related to Recipient-Requested Changes to Existing Services

  • Changes to the Services We provide Services in a multi- user environment and must therefore reserve the right to modify and discontinue Services. We may modify a Service at any time without degrading its functionality or security features For current subscriptions, we may degrade the functionality of a Service or discontinue a Service only in case of (i) legal requirements; (ii) changes in the Services imposed by Siemens’ subcontractors; (iii) the termination of our relationship with a provider of software and/or services used by us which are material for the provision of such Service; (iv) lack of customer acceptance; and/or (v) security risks. We will notify you of any material degradation of functionality or the discontinuation of a Service and the effective date at least 80 days prior to such change, and you may terminate the modified Service 30 days prior to the change effective date. In the event of such termination or discontinuation of a Service, we will refund any prepaid amounts for the applicable Service on a pro-rata basis for the remaining Subscription Term. We do not maintain prior versions of a Service.

  • Changes to Services The Parties acknowledge and agree that there will be changes to the scope of the Services during the Contract Period. The Customer may amend the Stories that are comprised within the Minimum Marketable Features of a Release at any time during the Release at no additional charge and without adopting the Change Control Procedure set out in Clause 28 above provided that: the Customer shall not be entitled to make any changes to the Stories that form the subject of a Sprint following the mutual agreement by the Parties of the Sprint Plan for that Sprint; new Stories and/or changes to existing Stories may only be introduced if: existing Stories with an equivalent number of Story Points are removed; or existing Stories are reduced in size by the equivalent number of Story Points, such that the total number of Story Points for the Release remains constant throughout the Release. The Supplier shall consider any request by the Customer to increase the number of Story Points for a Release, and may, subject to the Change Control Procedure set out at Clause 28, agree to such request.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • 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

  • Attachment A, Scope of Services The scope of services is amended as follows:

  • CHANGES TO PRODUCT OR SERVICE OFFERINGS a. Product or Service Discontinuance Where Contractor is the Product Manufacturer/Developer, and Contractor publicly announces to all U.S. customers (“date of notice”) that a Product is being withdrawn from the U.S. market or that maintenance service or technical support provided by Contractor (“withdrawn support”) is no longer going to be offered, Contractor shall be required to: (i) notify the Commissioner, each Licensee and each Authorized User then under contract for maintenance or technical support in writing of the intended discontinuance; and (ii) continue to offer Product or withdrawn support upon the Contract terms previously offered for the greater of: a) the best terms offered by Contractor to any other customer, or b) not less than twelve (12) months from the date of notice; and (iii) at Authorized User’s option, provided that the Authorized User is under contract for maintenance on the date of notice, either: provide the Authorized User with a Product replacement or migration path with at least equivalent functionality at no additional charge to enable Authorized User to continue use and maintenance of the Product. In the event that the Contractor is not the Product Manufacturer, Contractor shall be required to: (i) provide the notice required under the paragraph above, to the entities described within five (5) business days of Contractor receiving notice from the Product Manufacturer, and (ii) include in such notice the period of time from the date of notice that the Product Manufacturer will continue to provide Product or withdraw support. The provisions of this subdivision (a) shall not apply or eliminate Contractor’s obligations where withdrawn support is being provided by an independent Subcontractor. In the event that such Subcontractor ceases to provide service, Contractor shall be responsible for subcontracting such service, subject to state approval, to an alternate Subcontractor.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Changes to Service We may, from time to time, modify the Service to reflect improvements and other changes and modifications to our network. In addition, we reserve the right to discontinue or limit Service as required to comply with or satisfy our obligations under applicable laws or regulations, including when changes to or interpretations of such laws and regulations have a material, adverse effect on the business, technical or economic feasibility of providing Service, as determined by us in our reasonable judgment.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

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