Transcript Purpose of Dashboard

Construction Schedule Best
Practices
®
 Overview
• Benefits of a Good Construction Schedule
• Baseline Schedule Development
• Schedule Updating and Maintenance
• Managing Project Changes
• USACE – Specific Schedule Requirements
• Conclusion
1
Benefits of a Construction
Schedule
®
 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
2
Baseline Schedule
Development
®
 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
3
Baseline Schedule
Development (Cont.)
®
 Key Elements
• Milestones
• Design Phase
• Pre-Construction
Submittals/Review
• Construction
Submittals/Review
• Procurement Activities
• Fabrication & Delivery
Activities
• Site Work & Utilities
• Interior Finishes
• Foundations & Structural
• Interior MEP Finishes
• Exterior Finishes
• Testing & Turnover
• Interior MEP Rough-ins
• Project Close-out
4
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
5
Schedule Updating /
Maintenance
®
 Key Considerations
• Contract Requirements
• Backup to Pay Requests
• Submittal Updates
• Procurement Updates
• Subcontractor Updates
• Impacts / Delays
• Contract Changes
• Reporting Requirements
6
Schedule Updating /
Maintenance
®
 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
7
Schedule Updating /
Maintenance
®
 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
8
Managing Project Changes
®
 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.
9
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
10
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.
11
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
12
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
13
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
14
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
15
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
Activity
Field
Code
Length
Description
1
WRKP
3
Workers per day
2
RESP
4
Responsible Patry (e.g. GC, Subcontractor, USACE)
3
AREA
4
Area of Work
4
MODF
6
Modification or REA number
5
BIDI
6
Bid Item (CLIN)
6
PHAS
2
Phase of Work
7
CATW
1
Category of Work
8
FOW1
10
Feature of Work (used up to 10 charactures in length)
9
FOW2
10
Feature of Work (used up to 20 charactures in length)
10
FOW3
10
Feature of Work (used up to 30 charactures in length)
16
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
17
USACE Requirements
®
3.6 - Periodic Schedule Update Meeting
 3.6.1 - Update Submission following Progress Meeting
 3.6.2 - Status of Activities
 Start and Finish Dates
 Remaining Durations
 Activity Percent Complete
 Logic Change
 Other Change
3.7 – Request For Time Extensions
 3.7.1 - Justification of Delay
 3.7.2 - Submission Requirements
 3.7.3 - Additional Submission Requirements
18
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
19
Conclusion
®
 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
20