Project Baseline Schedule Update Narrative. Developer shall provide a narrative with each schedule update Submittal. In developing the narrative for the schedule update, Developer shall: a) Describe the Work performed during the progress period. Describe progress for each segment/section and the Project as a whole, including all phases of Work and interim milestones organized and reported by the defined WBS; b) Provide a summary of QA/QC issues that can potentially affect the Critical Path of the CPM model; c) Explain deviations between the Work planned and the Work performed for the period; d) Describe the Work to be accomplished during the next period; e) Describe the current Critical Path of the Project, explaining any changes since the previous update as well as potential issues and proposed resolutions; f) Explain significant changes to the schedule since the previous update; • Provide the reason or justification for the changes, and • Describe any resulting affects or impacts to the Project Schedule. Particular focus should be on any changes that affect Critical Path or near-Critical Paths. • Explain changes to: - Calendar - Activity unit/budget allocations - Planned resource (crew) allocations that deviate from the baseline work plan - Critical Path g) Identify requested and/or required TxDOT actions, if applicable, for the next month; h) Provide the status on pending items applicable to the schedule such as: • Permits, easements, agreements • Contract changes or time adjustments • Change Orders that were executed during the period from the submission of the previous month’s Progress Report to the submission of the current Progress Report • Time impact analyses i) Describe current and anticipated problems or delays including: • List current/anticipated problems and/or delays with cause and effect on Work, milestones and completion dates. A summary of the resolutions (status) to the problems and/or delays listed above (resolved, ongoing or anticipated). • Plans for mitigating or resolving ongoing and/or anticipated problems and/or delays. • Actions TxDOT needs to take and required timeline for actions to avoid or mitigate the problem. A discussion of problems or delay in the schedule update narrative does not relieve Developer of complying with contractual requirements regarding notification and documentation of claims. If any actual dates are changed or corrected in any subsequent month, Developer shall submit a separate narrative with the schedule update providing an explanation of the change. Along with the schedule update narrative, Developer shall include layouts, in PDF format, generated from the scheduling software to illustrate the following: a) Layout to demonstrate ▇▇▇▇▇▇▇▇▇’s approach and progress of work based on WBS or other applicable coding. At a minimum include columns for activity ID, activity name, start, finish, original duration, remaining duration, total Float, budgeted cost, and ▇▇▇▇▇ chart. The ▇▇▇▇▇ chart shall contain current planned bars and baseline /target bars that represent the previous period’s progress forecast; b) Longest path (i.e., Critical Path) layout organized by WBS and sorted by early start; c) A 90-day look ahead ▇▇▇▇▇ chart showing all upcoming Submittals from Developer and Approvals required by TxDOT or other Governmental Entities; d) A 90-day look ahead ▇▇▇▇▇ chart grouped by WBS and sorted by early start date; e) Graphical report which compares Developer’s actual monthly progress to the previous month’s planned progress, organized by WBS; f) A 90-day look ahead ▇▇▇▇▇ chart of Design document Submittals for the forthcoming period; g) Monthly expenditure projections and cash expenditure curves by WBS or as requested by TxDOT, if applicable; and h) Other layouts or reports as agreed upon or requested by TxDOT. Progress payment requests, if applicable, shall accompany the schedule update narrative. In addition to the schedule update narrative, Developer shall provide a separate report on the Completion Deadlines showing the schedule dates for the immediate prior month and the current month. For variances greater than 30 Days, Developer shall include a narrative to explain why the dates have changed.
Appears in 2 contracts
Sources: Comprehensive Development Agreement, Comprehensive Development Agreement
Project Baseline Schedule Update Narrative. Developer shall provide a narrative with each schedule update Submittal. In developing the narrative for the schedule update, Developer shall:
a) Describe the Work performed during the progress period. Describe progress for each segment/section and the Project as a whole, including all phases of Work and interim milestones organized and reported by the defined WBS;
b) Provide a summary of QA/QC issues that can potentially affect the Critical Path of the CPM model;
c) Explain deviations between the Work planned and the Work performed for the period;
d) Describe the Work to be accomplished during the next period;
e) Describe the current Critical Path of the Project, explaining any changes since the previous update as well as potential issues and proposed resolutions;
f) Explain significant changes to the schedule since the previous update; • Provide the reason or justification for the changes, and • Describe any resulting affects or impacts to the Project Schedule. Particular focus should be on any changes that affect Critical Path or near-Critical Paths. • Explain changes to: - Calendar - Activity unit/budget allocations - Planned resource (crew) allocations that deviate from the baseline work plan - Critical Path
g) Identify requested and/or required TxDOT actions, if applicable, for the next month;
h) Provide the status on pending items applicable to the schedule such as: • Permits, easements, agreements • Contract changes or time adjustments • Change Orders that were executed during the period from the submission of the previous month’s Progress Report to the submission of the current Progress Report • Time impact analyses
i) Describe current and anticipated problems or delays including: • List current/anticipated problems and/or delays with cause and effect on Work, milestones and completion dates. A summary of the resolutions (status) to the problems and/or delays listed above (resolved, ongoing or anticipated). • Plans for mitigating or resolving ongoing and/or anticipated problems and/or delays. • Actions TxDOT needs to take and required timeline for actions to avoid or mitigate the problem. A discussion of problems or delay in the schedule update narrative does not relieve Developer of complying with contractual requirements regarding notification and documentation of claims. If any actual dates are changed or corrected in any subsequent month, Developer shall submit a separate narrative with the schedule update providing an explanation of the change. Along with the schedule update narrative, Developer shall include layouts, in PDF format, generated from the scheduling software to illustrate the following:
a) Layout to demonstrate ▇▇▇▇▇▇▇▇▇’s approach and progress of work based on WBS or other applicable coding. At a minimum include columns for activity ID, activity name, start, finish, original duration, remaining duration, total Float, budgeted cost, and ▇▇▇▇▇ chart. The ▇▇▇▇▇ chart shall contain current planned bars and baseline /target bars that represent the previous period’s progress forecast;
b) Longest path (i.e., Critical Path) layout organized by WBS and sorted by early start;
c) A 90-day look ahead ▇▇▇▇▇ chart showing all upcoming Submittals from Developer and Approvals required by TxDOT or other Governmental Entities;
d) A 90-day look ahead ▇▇▇▇▇ chart grouped by WBS and sorted by early start date;
e) Graphical report which compares Developer’s actual monthly progress to the previous month’s planned progress, organized by WBS;
f) A 90-day look ahead ▇▇▇▇▇ chart of Design document Submittals for the forthcoming period;
g) Monthly expenditure projections and cash expenditure curves by WBS or as requested by TxDOT, if applicable; and
h) Other layouts or reports as agreed upon or requested by TxDOT. Progress payment requests, if applicable, shall accompany the schedule update narrative. In addition to the schedule update narrative, Developer shall provide a separate report on the Completion Deadlines showing the schedule dates for the immediate prior month and the current month. For variances greater than 30 Days, Developer shall include a narrative to explain why the dates have changed.
Appears in 1 contract
Sources: Comprehensive Development Agreement