Laserfiche WebLink
Western Dam Engineering <br /> <br /> <br /> <br />12 <br />intermediate completion milestones are not met. <br />Contractors generally understand this provision and <br />are willing to work within it if it is reasonable. <br />However, contractors will tend to be leery of <br />liquidated damage provisions if they perceive that they <br />may be unfair or rigidly enforced despite mitigating <br />circumstances. This will inevitably drive up prices bid <br />for the work. <br />To provide the appearance of fairness, completion <br />schedules should allow realistic time frames to <br />complete tasks, and the actual dollar amount of the <br />late penalty should be roughly equivalent to the actual <br />damages incurred by the owner if the task/project is <br />late in being completed. A contractor that is making a <br />good, diligent effort to complete the project according <br />to the schedule should not be subject to financial <br />penalties for things beyond his control, as this will <br />likely raise the overall price of the project. <br />On larger, more complex jobs, or where certain <br />elements of the construction must be completed <br />within a specific time frame, a baseline schedule for <br />the completion of individual project tasks (milestones) <br />should be established. This will help ensure that the <br />contractor completes those items on time and <br />continues to make acceptable progress. The milestone <br />and baseline schedule requirements should be clearly <br />identified within the specifications, and the contractor <br />should be required to develop and submit a detailed <br />construction schedule for the review and approval of <br />the engineer. The schedule should define when each <br />of the critical construction tasks is to be initiated, what <br />the duration of the task is, and when the task is to be <br />completed. <br />Use of Specification Checklists <br />The preparation of a specifications package requires <br />the assembly of a large volume of information and <br />requirements into a single document, making it easy to <br />forget or overlook something. The use of an <br />appropriate checklist prepared in advance can help <br />prevent this problem, by at least requiring the <br />consideration of the items on the list. State regulatory <br />dam safety agencies may have such a checklist <br />suggested and available for use by the engineer. A link <br />to Colorado’s recently completed “Project Review <br />Guide” is provided in the reference section. Also, <br />recent FEMA grant funding has been used to develop a <br />dam specifications review tool, which is scheduled for <br />release in late 2014. Further information will be <br />provided in a future technical note issue. <br />Provisions for Project Construction Meetings <br />and Schedules <br />A schedule that defines a frequency for required <br />meetings should be laid out within the specifications. <br />Each construction project should kick off with a <br />Preconstruction Meeting involving the owner, <br />engineer, contractor, key subcontractors, and <br />regulator. The principal features of work should be <br />reviewed and any questions regarding <br />the Contract and work site should be addressed. If the <br />project is particularly specialized, involves high risk <br />activities for workers or the safety of the dam could be <br />compromised during construction, a construction risk <br />meeting should be a part of the Preconstruction <br />Meeting(s). Topics in the risk meeting should include <br />reviewing approaches to high risk components, <br />mitigating measures, and emergency response <br />procedures. <br /> <br />Encourage effective communication between <br />engineer, owner, and contractor <br />Regular project construction meetings involving the <br />core project team members (owner, contractor, key <br />subcontractors, engineer) are vital to ensure that the <br />project runs smoothly. These will typically be held as <br />often as weekly, at or near the same time each week, <br />so that developing or impending problems are quickly <br />identified and addressed. Input from all participants <br />should be encouraged. Documentation (minutes) of <br />these meetings is important to track the timely <br />resolution of problems. Minutes are also useful in the