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 Plan. (a) If the SOW requires the development of a Project Plan, the parties must develop and agree the Project Plan prior to the provision of Services.
(b) The Client will pay Oppizi for the development of the Project Plan in accordance with the SOW, unless otherwise agreed in writing.
(c) The Project Plan will describe:
(i) the obligations of each party and the resources and facilities which will be provided by each party as required for the supply of the Products and/or the performance of the Services;
(ii) if applicable, the Milestone Dates applicable to the supply of the Products and/or the performance of the Services; and
(iii) any other the details required by the SOW.
(d) Once the Project Plan has been developed and agreed the parties must comply with its terms, unless varied in writing.
Project Plan. Based on the Project Specifications, Omnicare CR has provided a description of services to be performed for Sponsor’s “A multi-center, randomized, double-blind, double-dummy, vehicle-controlled sequential cohort study to determine the safety of PEP005 0.025% and 0.05% topical gel in patients with actinic keratoses” (hereinafter “the Project”) and associated costs. Changes made in the Project scope, at any time during the Project, will result in a corresponding adjustment to the Project costs.
Project Plan. Within the timeframe specified in the Milestone Schedule, the Recipient must submit a draft Project Plan for the Department’s approval. The draft Project Plan must: be substantially in the form of the template provided by the Department (if any); detail the activities, linked to Project Outcomes, to be undertaken at each stage of the Project; detail, and provide documents (including satellite images, fixed-point photographs, maps, etc.) clearly identifying the proposed location, as relevant; detail how the Recipient will deliver the Project in accordance with this Agreement; and be consistent with all timeframes arising under this Agreement and identify how they will be met. Unless the Recipient is otherwise notified by the Department, the Department will reject or approve the draft Project Plan within 40 Business Days of submission by the Recipient under clause 4.2(a). Where the draft Project Plan is rejected, the Recipient must continue to submit a draft Project Plan, including any necessary amendments until the Department approves a draft Project Plan. Once a draft Project Plan is approved by the Department, it will become the final Project Plan (subject to any agreed changes agreed by the Department in writing). The Recipient must perform the Project in accordance with the Project Plan and must not make any amendments to the Project Plan, unless approved in writing by the Department. For the avoidance of doubt, the Department’s approval of the Project Plan does not in any way limit the Recipient’s responsibility for the performance of its obligations under the Agreement and any consequences of that performance.
Project Plan. (a) If the Statement of Work requires the development of a Project Plan, the parties must develop and agree the Project Plan before Oppizi provides any of the applicable Products and/or Services.
(b) The Client and Oppizi will consult with each other and use reasonable efforts to develop the Project Plan.
(c) The Client will pay Oppizi for the development of the Project Plan in accordance with the Statement of Work, unless otherwise agreed in writing.
(d) The Project Plan will describe:
(i) the obligations of each party and the resources and facilities which will be provided by each party as required for the supply of the Products and/or the performance of the Services;
(ii) if applicable, the Milestone Dates applicable to the supply of the Products and/or the performance of the Services; and
(iii) any other the details required by the Statement of Work.
(e) Once the Project Plan has been developed and agreed the parties must comply with the Project Plan, unless varied in writing.
Project Plan. The Project Plan should contain the sections listed below. Sections A, B, and C together should not exceed 4 pages. Sections D and E combined should not exceed 15 pages. Please refer to the instructions for details.
A. Specific Objectives
B. Anticipated Results and Significance
C. Related Previous Studies
Project Plan. The Project Plan as defined in the Act, for the Inner City TIRZ as approved and amended from time to time by the Board and the City, and incorporated by reference into this document as if set out in its entirety, for all purposes.
Project Plan. 16.1 In close cooperation with the Purchaser and based on the Preliminary Project Plan included in the Supplier’s bid, the Supplier shall develop a Project Plan encompassing the activities specified in the Contract. The contents of the Project Plan shall be as specified in the SCC and/or Technical Requirements.
16.2 The Supplier shall formally present to the Purchaser the Project Plan in accordance with the procedure specified in the SCC.
16.3 The Supplier shall undertake to supply, install, test, and commission the System in accordance with the Agreed and Finalized Project Plan and the Contract.
16.4 The Progress and other reports specified in the SCC shall be prepared by the Supplier and submitted to the Purchaser in the format and frequency specified in the Technical Requirements or as the parties may agree in writing.
Project Plan. Identify the project plan and how it will be managed; or ask Contractor to propose a project plan. Project plan should identify items such as the required contact personnel; the date the project plan must be submitted to the State; project management process; project breakdown identifying sub-projects, tasks, and resources required; expected frequency and mechanisms for updates/progress reviews; process for addressing issues/changes; and individuals responsible for receiving/reacting to the requested information. The Contractor will carry out this project under the direction and control of the Program Manager. Within 30 calendar days of the Effective Date, the Contractor must submit a project plan to the Program Manager for final approval. The plan must include: (a) the Contractor's organizational chart with names and title of personnel assigned to the project, which must align with the staffing stated in accepted proposals; and (b) the project breakdown showing sub-projects, tasks, and resources required.
Project Plan. Property Owner’s application, as approved, is attached and incorporated into this Agreement as Exhibit C. Property Owner agrees to complete the Project in accordance with the approved plans, design drawings, and specifications set forth in Exhibit C and attachments thereto and in accordance with the terms of this Agreement.
