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").
Sample 1Sample 2
AutoNDA by SimpleDocs
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. Process ● A Passport representative will complete a Scoping Change Order form describing the exchange to be evaluated. ● Passport will perform an impact assessment (cost, schedule, risk, etc) and provide a recommendation for how to achieve the City's objectives in the context of the latest information. ● The City will decide whether or not to proceed with Passport’s recommendation or to suggest an alternative approach. ● If the Change Request is approved by the City and returned back upon full execution, then the Change Request document will be incorporated as part of the Statement of Work. Timeline Effects
Sample 1
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.
Sample 1
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:
Sample 1
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....
Sample 1
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.
Sample 1

Related to Project Change Control

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

  • Exchange Control If at any time legal restrictions prevent the prompt remittance of part or all royalties with respect to any country in the Territory where Licensed Product is sold, payment shall be made through such lawful means or method as the Parties reasonably shall determine.

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

  • Exchange Control Information Exchange control reporting is required for cash transactions exceeding AUD10,000 and for international fund transfers. If an Australian bank is assisting with the transaction, the bank will file the report on your behalf.

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

  • Exchange Controls As a condition to this grant of Units, the Employee agrees to comply with any applicable foreign exchange rules and regulations.

  • Foreign Asset/Account Reporting; Exchange Controls Participant’s country may have certain foreign asset and/or account reporting requirements and/or exchange controls which may affect Participant’s ability to acquire or hold shares of Stock under the Plan or cash received from participating in the Plan (including from any dividends received or sale proceeds arising from the sale of shares of Stock) in a brokerage or bank account outside Participant’s country. Participant may be required to report such accounts, assets or transactions to the tax or other authorities in his or her country. Participant also may be required to repatriate sale proceeds or other funds received as a result of Participant’s participation in the Plan to his or her country through a designated bank or broker and/or within a certain time after receipt. Participant acknowledges that it is his or her responsibility to be compliant with such regulations, and Participant should consult his or her personal legal advisor for any details.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

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

Time is Money Join Law Insider Premium to draft better contracts faster.