Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.
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.
Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.
Project Completion Part 1 – Material Completion
Projects The Annexes attached hereto describe the specific projects and the policy reforms and other activities related thereto (each, a “Project”) that the Government will carry out, or cause to be carried out, in furtherance of this Compact to achieve the Objectives and the Compact Goal.
Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.
Development of the Project 4.1 TSP's obligations in development of the Project: Subject to the terms and conditions of this Agreement, the TSP at its own cost and expense shall observe, comply with, perform, undertake and be responsible:
Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.
Project Budget A Project Budget shall be prepared and maintained by Grantee. The Project Budget shall detail all costs for which the Grant will be used during each calendar month of the Term. The Project Budget must be approved in writing by the Project Monitor. Grantee shall carry out the Project and shall incur costs and make disbursements of funds provided hereunder by the Sponsor only in conformity with the Project Budget. The current approved Project Budget is contained in Attachment B. Said Project Budget may be revised from time to time, but no Project Budget or revision thereof shall be effective unless and until the same is approved in writing by Project Monitor. The funds granted under this Grant Contract cannot be used to supplant (replace) other existing funds.
Production Work The Company may use Outside Entities to perform production work outside the plant and its environs provided the Company demonstrates that it is utilizing plant equipment to the maximum extent consistent with equipment capability and customer requirements and the Company is making necessary capital investments to remain competitive in the steel business and is in compliance with Article Eleven, Section B (Investment Commitment).
