Schedule Narrative. 27 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 28 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 29 to ADOT. The Schedule Narrative must describe the activities, including how the activities 30 interrelate. Developer shall ensure that the Schedule Narrative includes the following 31 information:
32 A. A list of the activities on each Critical Path and a comparison of early dates and late 33 dates for activities designating times;
34 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 35 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 36 resources, (c) basis and assumptions for critical activity durations and logic, (d) 37 compliance with winter weather requirements, (e) any shifts, non-Business Days, and 38 multiple calendars applied to the activities, (f) the construction philosophy supporting the 39 approach to the Work outlined in the submitted Project Schedule, and (g) the reasons for 40 the sequencing of Work, including a description of any limited resources, potential 41 conflicts, and other salient items that may affect the schedule and how they may be 42 resolved;
43 C. For all subsequent schedule Submittals, the Schedule Narrative must recap progress 44 and days gained or lost versus the previous Progress Schedule, problems and delays 1 that have been experienced to date, the party responsible for the problems or delays, 2 and Developer’s plan to resolve the problems or bring the delayed activities back on 3 schedule, potential problems that may be encountered during the next period and the 4 proposed solutions (identify all potential problems and explain what action ADOT needs 5 to take and the date by which the action needs to be taken to avoid the problem), 6 describe changes in resources to be used on remaining Work and identify delays, their 7 extent, and causes. Each Schedule Narrative must also itemize changes in activities and 8 logic ties caused by each Supplemental Agreement, schedule recovery plans and 9 grouping of related Developer-initiated revisions;
10 D. The justification for any activity with a duration exceeding 20 Business Days;
11 E. The justification for any constraints used;
12 F. Developer’s approach used to apply relationships between activities, including a list of 13 activity relationships with lags and the justification for the use of each lag (e.g., all...
Schedule Narrative. 14 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 15 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 16 to ADOT. The Schedule Narrative must describe the activities, including how the activities 17 interrelate. Developer shall ensure that the Schedule Narrative includes the following 18 information:
Schedule Narrative. 8 At each Project Schedule Submittal, Developer shall prepare and submit a stand-alone 9 Schedule Narrative with sufficient detail to explain the basis of the submitted Project Schedule 10 to ADOT. The Schedule Narrative must describe the activities, including how the activities 11 interrelate. Developer shall ensure that the Schedule Narrative includes the following 12 information:
13 A. A list of the activities on each Critical Path and a comparison of early dates and late 14 dates for activities designating contract times
15 B. For the Project Schedule Submittals, include (a) Developer’s site management plan 16 (e.g., lay down, staging, traffic, and parking), (b) the use of construction equipment and 18 compliance with winter weather requirements, (e) any shifts, non-Business Days, and
