Common use of Baseline Schedule Clause in Contracts

Baseline Schedule. Developer shall use the preliminary schedule submitted with the Proposal as a foundation to prepare a Project Baseline Schedule and shall submit it to TxDOT for review and approval. Approval of the Project Baseline Schedule shall be a condition of NTP2. Developer shall submit a single hard copy of the Project Baseline Schedule in full-size color plot sheets, along with a backup disk of the schedule in electronic format. Scheduling software shall be as outlined in Book 2, and the Developer shall be responsible for updating scheduling software to maintain compatibility with current TxDOT-supported scheduling software. The Project Baseline Schedule shall include a separate narrative report which describes, in general fashion, the Developer’s proposed methods of operation for designing and constructing the major portions of the Work required by the CDA Documents. The schedule narrative shall describe the general sequence of design and construction, the proposed Critical Path of the Project, and all Milestone Schedule Deadlines. The Project Baseline Schedule shall include all major activities of Work required under the CDA Documents, in sufficient detail to monitor and evaluate design and construction progress, from commencement of the Work to Final Acceptance of the Work. The Project Baseline Schedule shall also include activities for property acquisition, Utility Adjustments, permit acquisitions, and interfaces with other projects, localities, municipalities and other Governmental Entities. For each major activity, Developer shall indicate the duration (in Days) required to perform the activity and the anticipated beginning and completion date of each activity. In addition, the Project Baseline Schedule shall indicate the sequence of performing each major activity and the logical dependencies and inter-relationships among the activities. The Project Baseline Schedule shall include a listing of all submittals as called out in the CDA Documents. Submittal activity durations shall include specific durations for TxDOT review and/or approval of the Developer’s submittals as called out elsewhere in the Agreement and these Technical Provisions. With the exception of activities relating to Environmental Approvals by Governmental Entities, each activity depicting the Developer’s operations shall have duration of not more than 20 Days, and not less than one Day, except as otherwise approved by TxDOT. All activities shown in the schedule, with the exception of the first and last activities, shall have a minimum of one predecessor and a minimum of one successor activity. Float shall not be considered as time for the exclusive use of or benefit of either TxDOT or the Developer but shall be considered as a jointly owned, expiring resource available to the Project and shall not be used to the financial detriment of either party. Any method utilized to sequester Float calculations will be prohibited without prior approval of TxDOT. Any schedule, including the Project Baseline Schedule and all updates thereto, showing an early completion date shall show the time between the scheduled completion date and the applicable Milestone Schedule Deadline as "Project Float."

Baseline Schedule. Developer shall use the preliminary schedule submitted with the Proposal as a foundation to prepare a Project Baseline Schedule and shall submit it a draft of the Project Baseline Schedule to TxDOT for review and approval. Approval of the Project Baseline Schedule shall be a condition of NTP2. Developer shall submit a single hard copy hardcopy of the Project Baseline Schedule in on full-size (24” x 36”) color plot sheets, along with a backup disk an electronic version of the schedule in electronic its native format. Scheduling software shall be as outlined in Book 2, and the Developer shall be responsible for updating scheduling software to maintain compatibility with current TxDOT-supported scheduling software. The Project Baseline Schedule shall include a separate narrative report which describes, in general fashion, the Developer▇▇▇▇▇▇▇▇▇’s proposed methods of operation for designing and constructing the major portions of the Work required by the CDA Documents. The schedule narrative shall describe the general sequence of design and construction, the proposed Critical Path of the Project, and all Milestone Schedule Deadlines. The Project Baseline Schedule shall include all major Work activities of Work required under the CDA Documents, in sufficient detail to monitor and evaluate design and construction progress, from commencement of the Work to Final Acceptance of the Work. The Project Baseline Schedule shall also include activities for property acquisition, Utility Adjustments, permit acquisitions, and interfaces with other projects, localities, municipalities and other Governmental Entities. For each major activity, Developer shall indicate the duration (in Days) required to perform the activity and the anticipated beginning and completion date of each activity. In addition, the Project Baseline Schedule shall indicate the sequence of performing each major activity and the logical dependencies and inter-relationships among the activities. The Project Baseline Schedule shall include a listing of all submittals as called out in the CDA Documents. Submittal activity durations shall include specific durations for TxDOT review and/or approval of the Developer’s submittals as called out elsewhere in the Agreement and these Technical Provisions. With the exception of activities relating to Environmental Approvals by Governmental Entities, each activity depicting the Developer’s operations shall have duration of not more than 20 Days, and not less than one Day, except as otherwise approved by TxDOT. All activities shown in the schedule, with the exception of the first and last activities, shall have a minimum of one predecessor and a minimum of one successor activity. Float shall not be considered as time for the exclusive use of or benefit of either TxDOT or the Developer but shall be considered as a jointly owned, expiring resource available to the Project and shall not be used to the financial detriment of either party. Any method utilized to sequester Float calculations will be prohibited without prior approval of TxDOT. Any schedule, including the Project Baseline Schedule and all updates thereto, showing an early completion date shall show the time between the scheduled completion date and the applicable Milestone Schedule Deadline as "“Project Float."” Developer shall allocate the total contract price and quantities throughout the Project activities in the Project Schedule. Such allocation shall accurately reflect Developer's cost for each Project activity and shall not artificially inflate, imbalance, or front-load line items. The price of each Project activity shall be all-inclusive and shall include all direct and indirect costs, overhead, risks, and profit. Note that cost information will be suppressed on the Proposal submission, but shall be included with Developer’s first monthly Project Schedule Update(s) and submitted with Developer's first Draw Request. Percent complete shall be used to show activity progress as of the status date. The definition of percent complete for activities shall be made in consultation with TxDOT prior to beginning of scheduled Work. It should only be altered with TxDOT’s consent. Developer shall establish a WBS in line with the WBS shown in Attachment 2-2 with clearly identifiable linkage between the Price Proposal and Developer- designated Project activities, and phases represented in the Project Schedule. The WBS for each Work element shall indicate the duration, timing, and logical relationship to other Work Elements, including relationships to Project activities other than the parent Project activity of the particular Work Element. The WBS for each Project activity shall be defined in terms of Work Elements reflecting the types of Work shown in the Price Elements (see Book 2). Project activities shall be broken down at a minimum to Work Elements (e.g., bridges may be broken down into foundations, substructure, superstructure, and decks). All Work shall be broken down to similar manageable Work Elements. For Utility Adjustment Work, if Work is not shown as a Project activity itself, such Work shall be shown as a Work Element, where applicable. For mobilization, Developer shall provide a list of Work items that are included in each Project activity or Work Element.