1. 1 ®  Overview Benefits of a Good Construction Schedule Baseline Schedule Development Schedule Updating and Maintenance Managing Project Changes USACE – Specific Schedule Requirements Conclusion Construction Schedule Best Practices

2. 2 ®  Requires thinking the project through prior to starting the work  Provides a structured approach to executing the project  Provides a means of communicating Scope and planned work sequence to stakeholders  Identification of problems before they arise  Identification of long-lead procurement/fabrication items  Assessment of resource requirements  Forecasting of cash flow requirements  Serves as primary documentation for modeling delay impacts Benefits of a Construction Schedule

3. 3 ®  Key Considerations Scheduling Software Project WBS (Work Breakdown Structure) Contract Milestones Submittal Requirements Activity Coding Requirements Project Stakeholders Cost & Resources Loading Requirements Updating & Reporting Requirements Testing & Startup Requirements Project Closeout Requirements Baseline Schedule Development

4. 4 ® Interior Finishes Interior MEP Finishes Testing & Turnover Project Close-out Baseline Schedule Development (Cont.)  Key Elements Milestones Design Phase Pre-Construction Submittals/Review Construction Submittals/Review Procurement Activities Fabrication & Delivery Activities Site Work & Utilities Foundations & Structural Exterior Finishes Interior MEP Rough-ins

5. 5 ® Baseline Schedule Development (Cont.)  Key Configuration/Control CPM with “Retained Logic” No open ended activities (Pred/Succ) Activity Durations <20 days Activity Calendars (Work Days vs. Calendar Days, Weather Days) Total Float based on “Longest Path” Limited use of Constraints Supports contract required completion date

6. 6 ®  Key Considerations Contract Requirements Backup to Pay Requests Submittal Updates Procurement Updates Subcontractor Updates Impacts / Delays Contract Changes Reporting Requirements Schedule Updating / Maintenance

7. 7 ®  Key Elements Schedule Update “Data Date” Update to reflect actual period progress / status »Actual Start Dates »Actual Finish Dates »% Complete (Physical) »Remaining Duration Activity Relationship Changes Activities Added / Deleted Update Narrative Report Schedule Updating / Maintenance

8. 8 ®  Key Configuration/Control Schedule “Data Date” Correct “Out of Sequence” Progress No open ended activities (Pred/Succ) Total Float based on “Longest Path” Incorporates all known Impacts and Delays Incorporates Contract Changes Updated/Revised Critical Path Includes Update Narrative Report Schedule Updating / Maintenance

9. 9 ®  Key Elements Add Changes to the schedule as they occur. Change activities need to be tied to activities that are or will be impacted. Changes and projected impacts need to be discussed in the Update Narrative report. Change Notification needs to be made early and in accordance with Contract requirements. Impact analysis should be performed as early as possible. Managing Project Changes

10. 10 ® USACE Requirements USACE – Project Schedule Requirements  Unified Facility Guide Specification UFGS – 01 32 01.00 10, Project Schedule  Contract Specification Section 01 32 01.00 ??, Project Schedule  USACE Regulation ER 1-1-11, Progress, Schedules, and Network Analysis Systems

11. 11 ® USACE Requirements 3.1 - General Requirements  Contractors proposed sequencing of the project work scope.  Forward planning and project monitoring tool.  Includes dates on which the Contractor contemplates starting and completing all scheduled activities.  Represents entire project including design, procurement, construction, and turnover.  Includes participation by contractor management, designers, subcontractors, suppliers.

12. 12 ® USACE Requirements 3.1 - General Requirements (continued)  3.1.1 - Approved Project Schedule Must be Cost Loaded Must have all required activity coding Used to measure work progress Forms basis for progress payments Aids in evaluating time impacts and extensions Approval of Progress Payments may be withheld without schedule submission

13. 13 ® USACE Requirements 3.2 - Basis for Payment and Cost Loading  Activity cost loading shall be reasonable  Activity cost loading must balance with contract CLIN values  Basis for determining period contract earnings/progress payments  Lack of approved schedule will impact processing of progress payments  Retainage may be withheld if changes/revisions have not been incorporated into the updated schedule

14. 14 ® USACE Requirements 3.3 - Project Schedule Detail Requirements  3.3.1 - Critical Path Method  3.3.2 - Level of Detail Required  3.3.3 - Scheduled Project Completion and Activity Calendars  3.3.4 - Interim Completion Dates  3.3.5 - Default Progress Data – Not Allowed  3.3.6 - Out-of-Sequence Progress – Not Allowed  3.3.7 - Negative Lags and Start to Finish Relationships – Not Allowed  3.3.8 - Calculation Mode – Retained Logic  3.3.9 - Milestones

15. 15 ® USACE Requirements 3.4 - Project Schedule Submissions  3.4.1 - Preliminary Project Schedule Submission »Submit within 15 calendar days of NTP »Used for basis of Progress Payments during first 90 days after NTP  3.4.2 - Initial Project Schedule Submission »Submit within 42 calendar days of NTP »Used for basis of all remaining Progress Payments »Once approved, becomes the Baseline Schedule  3.4.3 – Design Package Schedule Submission »Extracted from the then current Preliminary, Initial, or Updated schedule  3.4.4 - Periodic Schedule Updates »Required to support estimate upon which progress payments may be made

16. 16 ® Project Schedule 3.4 - Project Schedule Submissions (continued)  3.4.5 - Standard Activity Coding Dictionary SDEF (ER 1-1-11, Appendix A) Exact structure is mandatory

17. 17 ® USACE Requirements 3.5 - Submission Requirements  3.5.1 - Data CD’s  3.5.2 - Narrative Report  Description of activities on Critical Path  Description of current/anticipated problem areas  Description of delay factors and their impacts  Explanation of corrective actions taken  Communicate Contractors analysis of the schedule and its plans to compensate for any problems  3.5.3 - Approved Change Verification  3.5.4 - Schedule Report  3.5.5 - Network Diagram

18. 18 ® USACE Requirements 3.6 - Periodic Schedule Update Meeting  3.6.1 - Update Submission following Progress Meeting  3.6.2 - Status of Activities 3.7 – Request For Time Extensions  3.7.1 - Justification of Delay  3.7.2 - Submission Requirements  3.7.3 - Additional Submission Requirements  Start and Finish Dates  Remaining Durations  Activity Percent Complete  Logic Change  Other Change

19. 19 ® Project Schedule 3.8 - Directed Changes 3.9 - Weekly Progress Meetings 3.10 - Ownership of Float 3.11 - Transfer of Schedule Data into RMS/QCS

20. 20 ®  The schedule communicates the Scope and Work Plan of the project  It all starts with the project Baseline schedule  Periodic (monthly) updating is a must  Minimum configuration control must be followed to retain validity of the schedule  The schedule documents what actually happened through-out the life cycle of the project  The schedule is the primary tool used for documenting and modeling time related impacts/delays Conclusion