Project Change Control Sample Clauses

Project Change Control. Either Party may request a change to a project subject to the following procedure: All requests for a project change must be submitted via a Project Change Request ("PCR"). The PCR must describe the change in detail, the rationale for the change and the effect the change will have, if accepted, or the impact it will have if rejected, on the project. The Project Manager of the requesting Party will review the PCR and determine whether to submit the request to the other Party. If submitted, both Project Managers will review the proposed change and approve it for further investigation, if required, or reject it. If the Parties agree that the proposed change requires further investigation, the Project Managers will authorize such investigation, and any charges by IBM that IBM specifies for such investigation, by signing the PCR. The investigation to be conducted will determine the technical merits and the effect on price, schedule, and other terms and conditions that may result from the implementation of the proposed change. The requesting Party's Project Manager may then approve or reject the change. If rejected, the PCR will be returned to the requesting Party along with the reason for rejection. If approved, the change will be implemented by providing written authorization signed by authorized representatives of both Parties ("Change Authorization").
View SourceView Similar (2)
Project Change Control. In the event that either party requires changes to the scope originally identified in the Order Form or SOW, shall be made only with the written agreement of both parties (the “Change Order”). Onapsis will provide a Change Order for You to review and sign before additional work is performed or additional fees are invoiced to You. Onapsis shall have no obligation to comply with any change until the parties have agreed in writing to the scope of the change and any adjustment in the fee and/or time for performance. The Change Order will specifically address any variance from the original Order Form or SOW and the requirements and associated costs.
View Source
Project Change Control. Process Deviations that arise during the proposed Project will be managed using the Project Change Control Process outlined below. Changes could include, but are not limited to, changes in costs, timing, scope, or deliverables. The Change Control Process will be invoked before any unplanned or out of scope work is executed or any work is completed outside Licensee’s regular business hours. Any additional effort/costs as a result of such work would be subject to the following Change Control Process. If either party believes that a change to this Work Order is necessary, such party shall issue to the other party a written change request (“Change Request”). In the case of a Licensee initiated Change Request, Infor will evaluate the feasibility of the Change Request as soon as practical following receipt and determine the impact to the Project cost and timelines. In instances where specialized resources are requested, but not contained within the original Project scope, the quoted rate will be established at Infor’s then current rate for such services. Infor shall provide Licensee a written Agreement (a “Change Response”) describing in detail: • Any additional Services to be performed as a result of the Change Request • The estimated cost associated with such additional Services; and • Any other information relating to the Change Request that may reasonably be requested by Licensee. Licensee shall respond promptly to any Infor-initiated Change Request. If Licensee approves an Infor-initiated Change Request or a Change Response, with such approval to be in writing, such Change Request or Change Response shall be deemed to be a “Change Order.” Any duly executed Change Order shall be attached to this Work Order. The Infor Project Manager and the Licensee Project Manager shall be authorized to administer any Change Order. The estimated Project schedule shall be adjusted accordingly for each Change Order. If Licensee rejects an Infor-initiated Change Request, or any Change Response, Infor and Licensee shall proceed to fulfill their obligations as originally agreed under this Work Order.
View Source
Project Change Control. ▪ If either party requests a change to this SOW or in the performance of Services for any reason including: − A change to the agreed upon project timeline, schedule, or duration, or − An absence of or delay in approvals or access to facilities, equipment, or materials necessary to perform the Services, or − Change in the performance of work onsite or remotely, or − Identification of onsite hazards and related safety and risk mitigation measures, or − Non-compliance or delayed compliance with a condition, responsibility, or assumption set out herein, or − A deficiency in fulfillment or delayed fulfillment in Product delivery, or − Any other circumstances outside of WWT’s control Texas A&M University System Phase 1 Project Management Services | January 2025 Then the requesting party will promptly notify the other party, and WWT will prepare and submit to TAMU a proposed Change Order (CO). The CO will describe the proposed change(s) and the impact on schedule and cost. A&M System will promptly review and either approve or reject a proposed CO in writing within five (5) business days. WWT reserves the right to stop performing the Services pending the resolution of a proposed CO without liability for subsequent delays. A proposed change is not binding on either party until a CO is signed by both WWT and A&M System and accompanied by a Purchase Order (if applicable). ▪ If a proposed change results from a cancellation, delay, or change to an agreed upon project schedule and less than fourteen (14) days’ notice has been provided, the CO will include up to two (2) weeks’ charges for the scheduled personnel and non- refundable travel expenses (if any) ▪ If the project is delayed for more than fourteen (14) calendar days, then the project will be rescheduled. WWT will staff the rescheduled project with qualified personnel available at that time ▪ If the project is delayed for thirty (30) calendar days or more for reasons outside of WWT’s direct control, WWT may invoice A&M System for work performed, and A&M System shall pay such invoice per the payment terms Texas A&M University System Phase 1 Project Management Services | January 2025 Appendix 1: Approval to Proceed with Project
View Source
Project Change Control. Either Party may request a change to a project subject to the following procedure: All requests for a project change must be submitted via a Project Change Request ("PCR"). The PCR must describe the change in detail, the rationale for the change and the effect the change will have, if accepted, or the impact it will have if rejected, on the project. The Project Manager of the requesting Party will review the PCR and determine whether to submit the request to the other Party. If submitted, both Project Managers will review the proposed change and approve it for further investigation, if required, or reject it. If the Parties agree that the proposed change requires further investigation, the Project Managers will authorize such investigation, and any charges by IBM that IBM specifies for such investigation; by signing the PCR. The investigation to be conducted will determine the technical merits and the effect on price, schedule, and other terms and conditions that may result from the implementation of the proposed change. The requesting Party's Project Manager may then approve or reject the change. If rejected, the PCR will be returned to the requesting Party along with the reason for rejection. If approved, the change will be implemented by providing written authorization signed by an authorized representative of both Parties ("Change Authorization"). - COMPLETION IBM will notify Certegy, in writing, when the Completion Criteria for a Deliverable has been met. Certegy must inform IBM, in writing, within ten (10) business days following receipt of IBM's notification if Certegy believes IBM has not met the Completion Criteria, together with reasonable detail as to the reasons for such belief. If IBM does not receive written notice within such period, then the Deliverable(s) will be deemed Accepted. MAINFRAME TOWER PROJECT PLANS THERE ARE NO MAINFRAME TOWER PROJECTS APPROVED AS OF THE EXECUTION DATE OF THE TRANSACTION DOCUMENT SCHEDULE S OF TRANSACTION DOCUMENT # ______ MAINFRAME TOWER PERFORMANCE STANDARDS, MINIMUM SERVICE LEVELS AND SERVICE CREDITS - INTRODUCTION - This Schedule S describes: - certain duties, obligations and responsibilities of IBM, including the Performance Standards and Minimum Service Levels for defined Services which IBM is required to meet during the term of the Transaction Document; - the Performance Standards and Minimum Service Levels for the defined Services which IBM is required to meet during the term of the Transaction Document....
View Source
Project Change Control. A Project may be changed only by a writing signed by authorized representatives of WSI and IBM. Either WSI or IBM may request a change to a Project subject to the following Project change control process: a. All requests for a change to a Project will be submitted in writing by the requesting Project Manager (a
View Source
Project Change Control. Changes may be required to manage unanticipated or new information that may arise during the course of the implementation and delivery of this solution that impacts an existing (or creates a new) deliverable, restriction, milestone, or dependency. This Project Change Control process is meant to enforce a process to ensure changes are tracked and approved appropriately throughout the project.
View Source

Related to Project Change Control

  • Project Changes Project changes prior to bid opening shall be made by addendum to plans and specifications. Changes after bid opening shall be made by change order. The Local Government shall submit all addenda and all change orders to the Department for an eligibility determination. After execution of all construction, equipment and materials contracts, the Project contingency may be reduced.

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

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

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.