Project Roadmap Sample Clauses

Project Roadmap. Currently embedded in the Eduuni workspace, D8 needs to be resubmitted as a self-sustained document. Specifically, it should clearly present the operative and realistic plan of activities for the remaining next 12 months of the project, measurements (KPIs – Key Performance Indicators) for monitoring project progress, major problems expected and a detailed proposal for an amendment and internal reallocation of the budget. This deliverable should also be considered as a living document that the consortium should periodically update.  Deliverable D14 - Risk Management Plan. D14 should be resubmitted and include a contingency plan to mitigate the delays in WP3 and reach the stated project objectives. This plan should be prepared as soon as possible.  Deliverable D15 - Desk research. D15 needs to be resubmitted; it only provides a table summarizing main services/products emerged from the desk research being undertaken. This deliverable needs to have more structure and look into the specific requirements, components and how they have been addressed in the literature. It is important to provide more details on current developments and make sure that the deliverable is useful on its own. Clarifications are also needed concerning which services among those listed in D15 have been considered for the architecture, what criteria were used to identify/select services in the list.  Deliverable D18. Detailed description of the user scenarios with guidelines and advice for developers in WP3. D18 needs to be resubmitted and to include a well-structured presentation of how the framework architecture came up, why the selected components are part of it, how they link together, what are the basic elements of each component, which use cases they can facilitate and how the ESCO ontology has been integrated in the architecture. Information on the “Architecture bank” (mentioned in D17 p.4) should also be provided.  Deliverable D35. Stakeholder management plan. D35 needs to be resubmitted since it does not present stakeholder engagement, but the generic dissemination and communication plan as described in D34. Clarifications are also needed concerning how stakeholders have been identified /selected; which/how many stakeholders for each category (among those listed in D34 and D35) are represented/involved in project task forces; which/how many stakeholders for each category (particularly NEETs and immigrants) attended the stakeholders (kick-off and midterm) seminars.
Sample 1
AutoNDA by SimpleDocs
Project Roadmap. The Project Roadmap sets out the estimated timelines and key milestones in the Project. The Parties will review and refine the Project Roadmap as the Project progresses, provided that amendments to the Project Roadmap must be approved by the Executive Steering Committee. The Supplier acknowledges and agrees that the target date for the implementation and deployment of the System is  and the Parties agree to use commercially reasonable efforts to achieve such date.
Sample 1
Project Roadmap. The Hosting Supplier’s project roadmap is incorporated into schedule 4.1 (Hosting Supplier Solution). The project roadmap identifies the portfolio of Projects and their anticipated sequence required to deliver the Hosting Services and to achieve FMO for each of those Hosting Services. The parties agree that the Project Notification for Project 1 (Capability Build) as identified in the Hosting Supplier’s project roadmap shall be deemed to occur on the Effective Date and the Hosting Supplier shall be the Lead Supplier for Projects 1 – 5 as set out in the project roadmap in schedule 4.1 (Hosting Supplier Solution). Following the Effective Date the Authority shall liaise with the Hosting Supplier and all Other FITS Suppliers and with reference to all their project roadmaps and Supplier Solutions, in order to identify the subsequent Projects to proceed to the initiation phase of the FITS delivery lifecycle as described in the rest of this Part 2. The Authority’s identification of each Project is at the Authority’s sole discretion. The Authority shall thereafter similarly identify further Projects through the Transition Period and thereafter from time to time as required throughout the Term. This process describes how each Project is initiated and how accordingly Milestones, Milestone Dates, Dependencies and Acceptance Criteria become contractually fixed. Having identified a Project, the Authority (at its discretion but acting reasonably) shall nominate and/or provide:
Sample 1
Project Roadmap. = main dependencies between achievements in roadmap M0 M12 M24 M36 Implemented SON using component model (WP1) Design of transaction model and semantics over a SON (WP3) Requirements for self- managing application servers (WP5) Measured effectiveness of self-* services (WP5) Guidelines for building large self-managing applications (WP5)
Sample 1

Related to Project Roadmap

  • 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 Review A. Programmatic Allowances 1. If FEMA determines that the entire scope of an Undertaking conforms to one or more allowances in Appendix B of this Agreement, with determinations for Tier II Allowances being made by SOI-qualified staff, FEMA shall complete the Section 106 review process by documenting this determination in the project file, without SHPO review or notification. 2. If the Undertaking involves a National Historic Landmark (NHL), FEMA shall notify the SHPO, participating Tribe(s), and the NPS NHL Program Manager of the NPS Midwest Regional Office that the Undertaking conforms to one or more allowances. FEMA shall provide information about the proposed scope of work for the Undertaking and the allowance(s) enabling FEMA’s determination. 3. If FEMA determines any portion of an Undertaking’s scope of work does not conform to one or more allowances listed in Appendix B, FEMA shall conduct expedited or standard Section 106 review, as appropriate, for the entire Undertaking in accordance with Stipulation II.B, Expedited Review for Emergency Undertakings, or Stipulation II.C, Standard Project Review. 4. Allowances may be revised and new allowances may be added to this Agreement in accordance with Stipulation IV.A.3, Amendments. B. Expedited Review for Emergency Undertakings

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives. C.1. <Title> Deliverable 1

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

  • Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline:

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

  • Research Project The findings of any research project, which would change the provisions of this Agreement will not be implemented until such changes are negotiated and agreed to by the parties.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones) B. Estimated total development time

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