X hits on this document

14 views

0 shares

0 downloads

0 comments

3 / 6

Bridge Falsework Forum October 15, 2007 Page 3 of 6

4.

2. Communication/Partnering/ Falsework Design Plans

4.

2. 1

. Require meetings at critical benchmarks

4.

2. 1. 1.Erection

4.

2. 1. 2.Grading

4.

2. 1. 3.Removal

4.

2. 1. 4.Prior to opening to traffic (for falsework over traffic)

The extent of the meeting would be relative to the size of the job. Tailgate meetings might suffice for a small simple span bridge not over live traffic.

4.

3. Communication/Partnering/ Falsework Design Plans

4. 3. 1. Erection and Removal Plans – Discussion questioned why the erection and removal plans needed to be a part of the design plan? This is a construction issue, not a design issue. Sometimes the falsework needs to be designed with erection and removal in mind.

4.

3. 2. General at time of falsework plan submittal - The thoughts were that the Designer is able to provide a general plan of removal but it is up to the construction crew that is aware of their capabilities and available equipment to develop the site specific plan. As previously mentioned, this is not always practical. There are instances where falsework must be designed for specific erection and removal restrictions.

4.

3. 3. Detailed at pre-activity meeting – The idea is that the more detailed plan for erection and/or removal could be submitted, reviewed and approved during a meeting prior to the contractor performing the work.

4.

3. 4. Implementation – Implementation of these “requirements” could be initiated via the falsework manual or made part of the Contract Standard Specifications or the Special Provisions.

4.

  • 4.

    Falsework Engineer of Record Presence and Approvals

      • 4. 4. 1.

        At Critical benchmarks

4.

4. 1. 1.Certify prior to traffic opening (for falsework over traffic)

Meeting notes

11/21/07

Document info
Document views14
Page views14
Page last viewedFri Dec 09 21:25:51 UTC 2016
Pages6
Paragraphs180
Words1913

Comments