Change Procedures. Any Change to the general terms and conditions in the Service Modules (including changes to the Schedules and Attachments) will be made in accordance with Exhibit B. Each Party agrees to consider in good faith any Change request of the other Party and will not unreasonably withhold or delay its approval of any such request.
Change Procedures. Any Change to the general terms and conditions herein (including changes to the Schedules and Attachments) will be made in accordance with Exhibit B. Each Party agrees to consider in good faith any Change request of the other Party and will not unreasonably withhold, condition or delay its approval of any such request.
Change Procedures. (a) If either party wishes to propose any amendment or modification to, or variation of, the Services (including the scope or details of the Services) (a “Change”) then it shall notify the other party of that fact by sending a request (a “Change Request”) to the party, specifying in as much detail as is reasonably practicable the nature of the Change. A Change Request, and any related changes to the fees, also may be submitted to document a Change that was previously agreed to or performed by X.X. Xxxxxx. ETF Agency Services Agreement - August 2021
(b) Promptly following the receipt of a Change Request, the parties shall agree whether to implement the Change Request, whether implementation of the Change Request should result in a modification of the fees contemplated by Section 6 of this Agreement, and the basis upon which X.X. Xxxxxx will be compensated for implementing the Change Request.
(c) If a change to Applicable Law requires a Change, the parties shall follow the processes set forth in this Section to initiate a Change Request. If the change in Applicable Law results in a change to the Services, or an increase in X.X. Xxxxxx’x costs or risk associated with provision of the Services, X.X. Xxxxxx shall be entitled to make an appropriate increase in the fees. X.X. Xxxxxx shall bear its own costs with respect to implementing a Change Request based upon a change to Applicable Law, except that:
i. X.X. Xxxxxx shall be entitled to charge the Trust for any changes to software that has been developed or customized for the Trust; and
Change Procedures. A change in scope of any PRA or FRD is any alteration to the PRA or FRD that affects cost, payments, or schedule. Any change in the scope of a PRA or a FRD shall become effective only when a written change request is executed by authorized representatives of both parties in accordance with this subsection 3 d). eFunds has overall responsibility for the change process through its required resolution. Any change requested by either party will be evaluated, resolved and/or negotiated with respect to cost, schedule, resource impact and/or priorities by authorized representatives of eFunds and Client in accordance with the following:
(i) The parties shall mutually agree upon the form of a "Change Order Request" to be used hereunder. The change request shall be described in the Change Order Request form by the party originating the request The Change Order Request form will then be submitted to eFunds' project manager for approval;
(ii) eFunds' project manager will estimate the schedule impact and cost to perform the evaluation, document this on the Change Order Request form, and return the form to the Client project manager for approval. If the Client project manager authorizes the evaluation expenditure in writing, the eFunds project manager will assign the Change Order Request to the appropriate personnel to perform the technical evaluation-,
(iii) Following the technical evaluation, the eFunds project manager will determine the cost to Client of any changes or additions to eFunds Customizations and the impact on the current project scheduleto implement the Change Order Request document this on the Change Order Request form, and return the form to the Client project manager for an implementation decision, which shall not be unreasonably withheld or delayed. Upon receipt of the approved Change Order Request form signed by the Client project manager, the eFunds project manager will schedule the change for implementation. Approved Change Order Requests will be deemed incorporated into and a part of the applicable PRA or FRD; and
(iv) eFunds shall manage the impact Change Order Requests have on project progress and cost, including both the impact of performing the Change Order Request evaluation and the impact of Change Order implementation. The eFunds project manager shall maintain a log to keep track of all changes/issues and the current status of each.
Change Procedures. Any Change to the general terms and conditions herein (including changes to the Schedules and Attachments) will be made in accordance with Schedule 1-A. Each Party agrees to consider in good faith any Change request of the other Party and will not unreasonably withhold, condition or delay its approval of any such request.
Change Procedures. (a) ACSD will notify and consult with Cubist immediately concerning any potential delay in completion or validation of the Facility. ACSD acknowledges that time is of the essence for this Agreement, and that significant delays in the completion of the Facility may cause Cubist material harm. Cubist and ACSD will, from time to time during the construction process, confer regarding the quality standards for materials and layout of operations within the Facility. [*]. Cubist may request amendments to the building, equipment, or Process to:
(i) effect [*] in the Facility,
(ii) to [*], or
(iii) to accommodate [*].
(b) If Cubist wishes to make a change it shall notify ACSD of the requested change in writing, specifying the change with sufficient details to [*] (each, a Change Order Request). Within [*] business days following the date of ACSD’s receipt of a Change Order Request, ACSD shall deliver a document that:
(i) assesses the impact of the change on the total cost of the Timetable and Facility Construction Plan, and
(ii) incorporates a description of the requested change and its proposed cost (a Change Order). If Cubist accepts the Change Order in writing, then the provisions of this Agreement shall be deemed amended to incorporate such Change Order. The cost stated in the Change Order shall be deemed an adjustment to the charges specified in this Agreement. It is the expectation of both parties that the dates and milestones set forth in this Agreement has been defined broadly enough to accomplish both parties’ goals and that no Change Orders will be required.
Change Procedures. 14.1 If the Licensee wishes to increase its number of User Subscriptions or either party requires a change to this Agreement, the requesting party shall submit details of such requested change to the other party in writing specifying the details of the change and its priority ("Change Request").
14.2 If Totalmobile originates a Change Request, it shall provide, with the Change Request, written details of the proposed change including details of the charges, timetables to implement the change and other relevant matters.
14.3 If the Licensee originates a Change Request or requires any enhancements to the Software or the Services as a result of legislative changes, Totalmobile shall within a reasonable period of time provide a written estimate to the Licensee setting out details of the charges, timetables to implement the change and other relevant matters.
14.4 Unless both parties consent to the Change Request, there shall be no change to this Agreement.
14.5 If both parties consent to the Change Request, it shall be signed by the authorised representatives of both parties, upon which the Change Request shall be incorporated into and from part of this Agreement.
Change Procedures. Changes to completed, or partially completed, work products that may require a change to the project scope, schedule or budget, must be brought to the attention of the Department (PM and ROW Lead). · Completion delays beyond the control of the Consultant or delays resulting from the actions of the Department may require a renegotiated due date. The Consultant shall provide prompt written notice of unexpected conditions or other reasons that might cause a delay to the Department (PM and ROW Lead).
Change Procedures. Procedures for preparation and submittal of application for final payment.
Change Procedures. 3.1. Unless otherwise agreed to in a written Change Request, there will be no changes in price, scope of services, performance standards or to any other rights or obligations in the Agreement or any exhibit, attachment or schedule thereto. Either Vendor or Customer may initiate a request for a Change by delivering to the other’s Project Manager or his/her nominated representative a draft Change Request that describes the proposed Change and sets forth the reasons for it.
3.2. Each party’s respective Project Manager or his/her nominated representatives shall be responsible for reviewing and considering any requests for Change, and shall approve it promptly of receipt for further investigation, if deemed necessary. If the parties agree that the request for Change requires further investigation, the Project Managers shall authorize such investigation, which shall be performed as required by Vendor and/or Customer. The Project Managers shall be responsible for keeping the status of each request for Change as such request progresses through the Change Control Procedures.
3.3. No Change will be implemented without Customer’s written approval, except as may be necessary on an emergency basis to maintain the availability of the Services. With respect to any such Change made on an emergency basis to maintain the availability of the Services, Vendor will document and provide to Customer’s Project Manager notification (which may be given by email) of the Change promptly after the Change is made, based on the significance of such Change.
