Project Baselines Sample Clauses

Project Baselines illustrating balanced, integrated and coordinated scope, budget, schedule and proforma performance including operational staffing models.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Project Baselines a. Top technical, cost, schedule and safety risks, risk mitigation plans, and associated resources Initial b. Staffing requirements and plans Initial c.i. Infrastructure requirements and plans Business case analysis for infrastructure c.ii Capitalization Determination Form (CDF) Update - Tailored: Infrastructure requirements and plans only. Rationale: Business case analysis and CDF is assumed to be for NASA only and commercial companies will analyze, propose and manage any infrastructure updates or additions internally.
Sample 1
Project Baselines x. Xxx technical, cost, schedule and safety risks, risk mitigation plans, and associated resources Update b. Staffing requirements and plans Update c. i. Infrastructure requirements and plans Business case analysis for infrastructure c.ii Capitalization Determination Form (CDF) Update - Tailored: Infrastructure requirements and plans only. Rationale: Business case analysis and CDF is assumed to be for NASA only and commercial companies will analyze, propose and manage any infrastructure updates or additions internally. d. Schedule Tailored: Risk informed at subsystem level with preliminary Phase D completion ranges and Preliminary Integrated Master Schedule only e. Cost Estimate Risk-informed schedule-adjusted range estimate f. Basis of Estimate (cost and schedule) N/A—It is assumed formal XXXx are not required under a funded SAA to meet the intent of a design review. Any cost and schedule estimates may include justification as applicable to assess the reasonableness of the schedule or any cost estimates provided. g. Confidence Level(s) and supporting documentation N/A for SDR. Since Phase 1 is under a funded SAA and NASA will be formulating requirements for Phase 2 in parallel with Phase 1, a Cost Risk Assessment would be too preliminary without formal technical and Program requirements. h. External Cost and Schedule Commitments Tailored: Preliminary (if applicable), no JCL assumed. i. CADRe N/A for Phase 1. Since Phase 1 is under a funded SAA and NASA will be formulating requirements for Phase 2 in parallel with Phase 1, a Cost Risk Assessment would be too preliminary without formal technical and Program requirements. j. PMB NA—Assume Phase 1 under SAA does not required PMB. Assume intent met by other Plans, Milestone Review status and documentation until Phase 2. 1. Technical, Schedule, and Cost Control Plan N/A—it is assumed that the combination of SEMP, Risk Management Plan and Configuration Management Plan sufficiently describe CLD Program controls and process to meet technical, schedule and cost baselines so a separate plan is unneeded. 2. Safety and Mission Assurance Plan Update 3. Risk Management Plan Update 4. Acquisition Strategy N/A—CLD Program is not responsible for this document. Assume this is developed by NASA if required. 5. Technology Development Plan N/A—It is assumed a formal technology development plan is not required. Intent is my by identifying low Technology Readiness items that pose a cost, schedule or technical risk and these risk...
Sample 1
Project Baselines a. Top technical, cost, schedule and safety risks, risk mitigation plans, and associated resources Update b. Staffing requirements and plans Update c.i. Infrastructure requirements and plans Business case analysis for infrastructure c.ii Capitalization Determination Form (CDF) Update - Tailored: Infrastructure requirements and plans only. Rationale: Business case analysis and CDF is assumed to be for NASA only and commercial companies will analyze, propose and manage any infrastructure updates or additions internally. d. Schedule Tailored: Update - Risk informed at subsystem level with Phase D completion ranges and Update Integrated Master Schedule only. Assume cost-loaded schedule is not required under SAA. Until Phase 2 procurement requirements are in place, a baseline is premature.
Sample 1

Related to Project Baselines

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

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • 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 Goals The schedule, budget, physical, technical and other objectives for the Project shall be defined.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Project Work PURCHASER shall complete the following projects in accordance with the specifications provided in Exhibits B, C, D, E, and F and written instructions from STATE. Project locations are shown on Exhibit A unless otherwise described. PURCHASER shall furnish all material unless otherwise specified.

  • 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 Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • 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 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 “C”. 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.

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