Project Change Control Procedure Sample Clauses

Project Change Control Procedure. If there is a change to the Services as described in Section 2 above, it must be identified by its project number. In the event of such a change, prices and charges shall be adjusted accordingly. Lenovo shall confirm any agreed changes to Customer via a change authorization or equivalent document. Nothing herein shall obligate Lenovo to proceed with a change except as agreed by the parties. Notwithstanding the foregoing, Lenovo will pick up all Products provided to Lenovo by the Customer at the location designated in a Service Request, whether or not such Products were included in the Service Request completed by the Customer. To the extent the Product counts differ from the counts Customer provided in a Service Request in accordance with Section 1 above, Customer authorizes and agrees to obtain authority from End User for Lenovo to provide Services with respect to any such additional or different Products in accordance with the terms of this Agreement and agrees to pay any additional Service and shipping fees for the processing of such Product. If Lenovo determines that any of the additional or different Products can be reconditioned or otherwise have resale value, Lenovo will pay Customer for such Product in accordance with Section 9 below.
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
Project Change Control Procedure. When Tyler and Client agree to a change in the Disaster Recovery Plan, Tyler will prepare a written description of the agreed change which both Tyler and Client must sign. The Change Order will describe the change, the rationale for the change, and specify any change in the charges, estimated schedule, or other terms. When charges are necessary in order for Tyler to analyze a change, Tyler will give Client a written estimate and begin the analysis only after Client’s written authorization.
Sample 1
Project Change Control Procedure. Changes to the Statement of Work may be requested at any time by either party. Since a change could affect the price, schedule or other terms of the Agreement for this Statement of Work, both the TECHALT, INC. Project Manager and the Arias Technology Corporation Project Leader must approve each changx xxxore amending the Statement of Work and implementing the change. This procedure will be used by TECHALT, INC. and Arias Technology Corporation to control changes to the Statement of Xxxx and changes to any previously approved deliverables. o A Project Change Request (PCR) will be the vehicle for communicating change. The PCR must describe the change, the rationale for the change and the effect the change will have on the Statement of Work. o The designated Project Manager/Leader of the requesting party will review the proposed change and determine whether to submit the request to the other party. o The TECHALT, INC. Project Manager and Arias Technology Corporation Project Leader will review txx xxoposed change and approve it for further, if any, investigation or reject it. Arias Technology Corporation will specify any charges for xxxx investigation. If the investigation is authorized, the TECHALT, INC. Project Manager and Arias Technology Corporation Project leader will sign the PCR which will constitute approval for such investigation charges. Arias Technology Corporation will invoice TECHALT, INC. fxx xxy such charges. The investigation will determine the effect that the implementation of the PCR will have on price, schedule and other terms and conditions of the Agreement. The change will then be approved/disapproved by the TECHALT, INC. Project Manager and Arias Technology Corporation Project Leader for implementxxxxx. o Approved changes will be incorporated in to the Statement of Work through written change authorizations (change orders), as appropriate. This procedure will be used by TECHALT, INC. and Arias Technology Corporation to control TECHALT, INC. orally approvxx XX's, necessary to meet Cook County required time sensitive, change, where the above descrixxx change control procedure is not able to be used. o A Project Change Request (PCR) will be the vehicle for communicating change and will be communicated via telephonic (or other reasonably available medium) by Arias Technology Corporation and will identify for TECHALX, XXC. the proposed emergency action required, the estimated time to make such change, and the rationale for such change. o The T...
Sample 1
Project Change Control Procedure. The following process will be followed if a change to this Agreement is required: • A Project Change Request (PCR) will be the vehicle for communicating change. The PCR must describe the change, the rationale for the change, and the effect the change will have on the project. • The Contractor will review the proposed change and determine whether to accept or reject the request. • A written Change Authorization and/or PCR must be signed by both parties to effectuate the change to this Agreement. Failure to have a signed Changed Authorization will preclude the Change Authorization from going into effect.
Sample 1
Project Change Control Procedure. This Agreement may be amended only by a writing signed by authorized representatives of both parties. Requests for such amendment (“Project Change Request” or “PCR”) should be submitted in writing by the requesting party. The PCR should reference this Agreement, describe in a reasonable level of detail the proposed change, the rationale for the change, and the impact the proposed change may have on the Agreement. The parties will review the PCR and will do one of the following: a. authorize the change by signing the PCR; b. agree in writing to submit the PCR for further investigation. In such case, Customer agrees to pay IBM for its reasonable charges, if any, for such investigation. The investigation will determine the technical merits and the effect on the charges, schedule, and other terms and conditions that may result from the implementation of the PCR. The parties will then decide either to accept or to reject the PCR; or c. reject the PCR. If the PCR is rejected, the rejecting party will inform the requesting party of the reason for the rejection. A mutually signed PCR will be deemed an amendment to this Agreement. Any modification of this Agreement requested by Customer as a result of laws applicable to Customer will be considered a PCR covered by this Subsection. Until a change is agreed in writing, both parties will continue to act in accordance with the latest agreed version of the Agreement.
Sample 1
Project Change Control Procedure. The following provides the detailed process to follow if a change to this Statement of Work of this Agreement is required. A Project Change Request (PCR) will be the vehicle for communicating change. The PCR must describe the change, the rationale for the change and the effect the change will have on the project in terms of IBM-provided estimates (scope, hours and schedule). The designated Project Manager of the requesting party will review the proposed change and determine whether to submit the request to the other party. Both Project Managers will review the proposed change and approve it for further investigation or reject it. IBM will specify any charges for such investigation. If the investigation is authorized, the Project Managers will sign the PCR which will constitute approval for the investigation charges. IBM will invoice 2TM for any such charges. The investigation will determine the effect that the implementation of the PCR will have on price, schedule and other terms and conditions of the Agreement. A written Change Authorization and/or Project Change Request (PCR) must be signed by both parties to authorize implementation of the investigated changes.
Sample 1
Project Change Control Procedure. The following process will be followed if a change to a Transaction Document for a Service is required. (i) A project change request (“PCR”) will be the vehicle for communicating change. The PCR must describe the change, the rationale for the change and the effect the change will have on the Services. The designated Project Manager of the requesting Party will review the proposed change and determine whether to submit the request to the other Party. (ii) Both Project Managers will review the proposed change and recommend it for further investigation or reject it. A PCR must be signed by authorized representatives from both Parties to authorize investigation of the recommended changes. (iii) A written change authorization and/or PCR must be signed by authorized representatives from both Parties to authorize implementation of the investigated changes. Until a change is agreed in writing, both Parties will continue to act in accordance with the latest agreed version of the Transaction Document.
Sample 1
AutoNDA by SimpleDocs

Related to Project Change Control Procedure

  • Change Control Procedure 34.1 In the event that either Party desires any change the terms of this Agreement or any Contract which may materially impact on the timings, scope, Specification or Charges of the Goods or Services, or the scope of either parties’ obligations under this Agreement or the relevant Contract, or which the relevant Party otherwise reasonably determines warrants the use of this change control procedure, the following procedures will apply: (a) the Party requesting the change will deliver a “Change Request” (in the form (or substantially in the same form) contained in Schedule 5 to this Agreement) which describes: (i) the nature of the change; (ii) the reason for the change; (iii) the effect that the requested change will have on the scope or Specification for the Goods or Services; and (iv) any change to the Charges and the Term. (b) Upon receipt of a Change Request, the receiving Party’s authorised representative will contact his/ her counterpart within 5 working days to discuss and agree the Change Request. The parties will negotiate the proposed changes to the Agreement and/or affected Contract in good faith and agree a timeline in which to finalise the Change Notice. (c) Neither party is obliged to agree to a Change Request, but if the parties do agree to implement such a Change Request, the appropriate authorised representatives of both parties will sign the Change Request which will be effective from the date set out in the Change Request. (d) If there is any conflict between the terms and conditions set out in the Agreement or any Contract and the Change Request, then the terms and conditions set out in the most recent fully executed Change Request will apply. (e) The Supplier shall neither be relieved of its obligations to supply the Goods and/or Services in accordance with the terms and conditions of this Agreement or any Contract, nor be entitled to an increase in the Charges as the result of: (i) a General Change in Law; or (ii) a Specific Change in Law where the effect of that Specific Change in Law on the Goods and/or Services is reasonably foreseeable at the Commencement Date of this Agreement, or, where the Change Request relates to a Contract, the applicable Contract Commencement Date. 34.2 The Parties agree that any variations to the Agreement or any Contract to reflect non- material changes (including for example a change to the name/contact details of a Party’s representative) may be agreed in writing and shall not be required to be made in accordance with the procedure in this clause 34, provided always that UKRI shall, in their absolute discretion, decide whether a proposed change is non-material for these purposes.

  • Change Control Procedures (a) No changes or additions may be made to any Work Order without the written agreement of LAUSD as evidenced by a duly executed Change Order. (b) Contractor will not take an action or make a decision which may have a material effect on LAUSD or which adversely affects the function or performance of, or decreases the resource efficiency of, the Services, including implementing changes in technology or equipment and software configuration, without first obtaining LAUSD’s written approval, which approval LAUSD may withhold in its sole discretion as respects any change which may have an adverse effect on LAUSD or the Services.

  • Project Changes 1.8.1. All changes shall be administered per the UGC. 1.8.2. Upon authorization by the Owner, the Owner or Architect/Engineer will prepare and issue all changes to the Contract affecting cost, scope and/or time as a formal Change Order to the Contract on the standard University of Texas MD Xxxxxxxx Cancer Center Change Order form. The Change Order may include separate change issues, identified as Change Proposals and field orders. 1.8.3. Upon authorization by the Owner, Change Proposals may be issued to the Architect/Engineer for pricing by the Contractor. Contractor shall submit pricing to the Owner within twenty-one (21) days and pricing shall be indicated on the standard Owner "Change in Work Cost Analysis" ("Cost Analysis") form provided in the Pre-Construction Conference Brochure. Contractor may not include a Change Proposal within a Change Order unless the Owner has accepted the Change Proposal. 1.8.3.1. The Contractor shall summarize all costs for each change at each level of subcontractor and supplier by preparing the "Cost Analysis" form, and shall provide each subcontractor's cost summary on separate "Cost Analysis" forms as backup. Additional support documentation from both the Contractor and Contractor’s subcontractors is encouraged, but such will not replace use of the standard form. 1.8.3.2. When the Contractor believes it is entitled to a time extension, Contractor shall so state as part of Contractor’s response to the Change Proposal, including a justifica- tion for a time extension. Owner may grant time extensions only if a Change Proposal affects the activities on the Longest Path of an Owner approved Work Progress Schedule; i.e., when the Work impacts the "Contract Substantial Completion Date". 1.8.3.3. If the Owner’s Project Manager and Contractor cannot mutually agree upon a fair and reasonable cost and time settlement, the Owner’s Project Manager may: 1) Reject the quotation and void the Change Proposal, 2) Issue instructions to the Contractor to proceed on a time and material basis for a price to be determined later not to exceed a fixed maximum dollar and time, or 3) Issue a Unilateral Change Order. 1.8.3.4. The Owner’s Construction Inspector and/or Owner’s Project Manager may issue field orders directly to the Contractor for minor changes to the Contract, which can be negotiated in the field. Pricing backup is at the discretion of the Owner’s Construction Inspector, but pricing backup is required for any field order, the pricing backup is to be outlined on the "Cost Analysis" form. When the Owner and Contractor have signed the field order, the Work is authorized and the field order may be included in the next Change Order. 1.8.4. Request for payment for Change Order work may be submitted only after the Change Order has been fully executed.

  • AMENDMENT AND CHANGE CONTROL Any amendment or change of any nature made to this Agreement and the Schedule of Requirements thereof shall only be valid if it is in writing, signed by both Parties and added to this Agreement as an addendum hereto. In this regard a Change Notice must first be defined and issued by the requesting Party. A Change Notice Response must then be issued by responding Party. A formal approval of the Change Request will then trigger the issue of the addendum to this Agreement.

  • Quality Control Procedures The Seller shall have an internal quality control program that verifies, on a regular basis, the existence and accuracy of the legal documents, credit documents, property appraisals, and underwriting decisions. The program shall include evaluating and monitoring the overall quality of the Seller's loan production and the servicing activities of the Seller. The program is to ensure that the Mortgage Loans are originated and serviced in accordance with Accepted Servicing Standards and the Underwriting Guidelines; guard against dishonest, fraudulent, or negligent acts; and guard against errors and omissions by officers, employees, or other authorized persons.

  • Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2

  • Exchange Control Notification Exchange control reporting is required for cash transactions exceeding A$10,000 and international fund transfers. If there is an Australian bank assisting with the transaction, the Australian bank will file the report for the Participant. If there is no Australian bank involved in the transaction, the Participant must file the report.

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