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 (8)
AutoNDA by SimpleDocs
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. 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. Exhibit F Appendix A
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.
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.
Sample 1
Project Change Control Procedure. The following process will be followed if a change to a Transaction Document for a Service is required.
Sample 1

Related to Project Change Control Procedure

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

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

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

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

  • Internal Control Over Financial Reporting The Company and each of its Subsidiaries maintain a system of internal control over financial reporting (as such term is defined in Rule 13a-15(f) of the Exchange Act Regulations) that complies with the requirements of the Exchange Act and the Exchange Act Regulations and has been designed by the Company’s principal executive officer and principal financial officer and is sufficient to provide reasonable assurance regarding the reliability of financial reporting and the preparation of financial statements for external purposes in accordance with GAAP, including that (A) transactions are executed in accordance with management’s general or specific authorizations; (B) transactions are recorded as necessary to permit preparation of financial statements in conformity with GAAP and to maintain asset accountability; (C) access to assets is permitted only in accordance with management’s general or specific authorization; (D) the recorded accountability for assets is compared with the existing assets at reasonable intervals and appropriate action is taken with respect to any differences; and (E) the interactive data in eXtensible Business Reporting Language included or incorporated by reference in the Registration Statement is accurate and fairly presents the information called for in all material respects and has been prepared in accordance with the Commission’s rules and guidelines applicable thereto. The systems of internal control over financial reporting of the Company and its Subsidiaries are overseen by the Audit Committee of the Board of Directors of the Company in accordance with Nasdaq rules and regulations. Except as described in the Registration Statement, the Pricing Disclosure Package and the Prospectus, since the end of the Company’s most recent audited fiscal year, (i) there has been no material weakness in the Company’s internal control over financial reporting (whether or not remediated), (ii) there has been no change in the Company’s internal control over financial reporting that has materially affected, or is reasonably likely to materially affect, the Company’s internal control over financial reporting and (iii) the Company has not been advised of (a) any significant deficiencies in the design or operation of internal controls that could adversely affect the ability of the Company or any Subsidiary to record, process, summarize and report financial data, or any material weakness in internal controls, or (b) any fraud, whether or not material, that involves management or other employees who have a significant role in the internal controls of the Company and each of the Subsidiaries.

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