26.12.2013 Views

Report - Oregon State Library: State Employee Information Center ...

Report - Oregon State Library: State Employee Information Center ...

Report - Oregon State Library: State Employee Information Center ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Flow Chart for Evaluation and Mitigation of Liquefaction Hazards<br />

to Bridge Approach Fills<br />

(page 2)<br />

STEP 6<br />

Is remedial ground treatment warranted?<br />

(ODOT Liquefaction Mitigation Policy)<br />

STEP 7A<br />

Develop Liquefaction Mitigation Program including:<br />

1. Select method(s) of remedial soil improvement (Chapter 5)<br />

2. Evaluate constructability issues pertaining to soil<br />

improvement methods (e.g., access, construction vibrations,<br />

noise, project duration) Develop preliminary cost estimates<br />

for various soil improvement schemes.<br />

STEP 7B<br />

Establish the Extent of Soil Improvement<br />

1. Determine the volume of soil to be treated (iterative seismic<br />

performance analysis outlined in Chapter 7)<br />

2. Limit equilibrium methods (static, pseudostatic, sliding-block)<br />

a. Effective stress analysis<br />

b. Total stress analysis using residual strengths<br />

Has the minimum allowable factor of safety been exceeded?<br />

3. Numerical dynamic effective stress modeling (Chapter 6)<br />

Have soil deformations been reduced to an allowable extent?<br />

Limit states for foundation and bridge elements have not been exceeded?<br />

4. Estimate cost for the preferred soil improvement application.<br />

STEP 8<br />

Proceed with Seismic Design of<br />

Approach Embankments, Abutments and Foundations<br />

Apply established methods of<br />

analysis and design for competent soils<br />

Figure 8.1 (continued): Flow Chart for Evaluating and Mitigating Liquefaction Hazard<br />

142

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!