DRAFT SCOPE OF WORK FOR INDUSTRY REVIEW: Repair of Existing Bridge Puling In Wet Conditions

Repair of Existing Bridge Piling In Wet Conditions

Project Overview

Over 80% of bridges in Minnesota are supported on steel foundation elements, particularly when the bridge crosses a waterway. These elements are often HP-Piling or steel shells infilled with concrete (C.I.P. Concrete Piling) and are subject to deterioration over the service life of the structure due to a variety of expose conditions. Deterioration often manifests itself in the form of section loss, which can reduce the load capacity of the bridge.

The goal of this project is to develop cost effective solutions that can be used to either preserve or strengthen existing steel bridge piling. To accomplish this, pile investigation criteria, design methodology, construction specifications, product qualification standards, and inspection training materials need to be developed to complete this work using either State-Maintenance forces or Contractors.

For this work to meet state-wide needs, the following considerations apply to all tasks in this scope or work:

Pile Types:

1. CIP Concrete Piling: Steel shells (generally with closed ends) driven to a required bearing resistance, then filled with cast-in-place concrete. These are displacement piles that generally achieve bearing resistance using friction resulting from perimeter contact with soil and bearing on the end plate. Common diameters used in Minnesota are 12-inch, 16-inch, 18-inch, 20-inch, and-24 inch. Wall thicknesses range from 0.25 inch to 0.5 inch.

2. Steel H Piles: H-shaped steel beams driven to a required bearing resistance, which is typically end bearing on rock or very dense soils. These are non-displacement piles that are selected for driving in rough conditions or end-bearing. Common sizes used in Minnesota are HP10x57, HP12x53, HP14x73, and HP14x89.

Repair types:

1. Preservation: maintain the existing condition and capacity of the pile while preventing further deterioration. Service life of this type of repair is considered a minimum of 20 years.

2. Strengthening: restore the pile to the original axial capacity from initial construction. Determine how much lateral capacity can be added to the existing pile. Service life of this type of repair is considered a minimum of 20 years.

3. Both repair types must provide a barrier that will prevent chlorides, sulfates, industrial contaminants, and organics from contacting the existing piling and will be resistant to microbial-induced corrosion (MIC).

4. Both repair types must consider future removal needs for maintenance re-application, inspection of existing piling, or both.

Installation conditions:

1. Wet conditions (portions of the pile are consistently in standing water or a waterway)

2. The emphasis of this project is on wet conditions; however, Contractor should give consideration whether a proposed repair would be applicable for dry conditions (no portion of the pile is consistently in standing water or a waterway)

3. Both dry and wet conditions need to consider low head room; this is defined as less than 8 feet from the low beam to either the ground line or water surface elevation.

Contractor is strongly encouraged to partner with a Construction Contractor(s) to complete this scope of work. This partner must have experience installing pile repairs in wet conditions on a minimum of 3 projects.

1.0 Project Administration and Meetings

State will provide a Project Manager to give direction to Contractor’s activities. It will be the responsibility of State’s Project Manager to receive the work produced by Contractor, review the work for accuracy and compliance with State standards, and to recommend payment for such work.

Contractor will conduct the administration of the project, which will include communication with State, invoicing, preparation of any necessary supplemental agreements, cost and schedule updates, and other non-technical work.

No changes in Contractor’s project management or lead task personnel will be permitted without prior written notice to and written acceptance from State’s Project Manager. State will notify Contractor immediately if there are changes to State’s assigned project management personnel.

1.1 Project Meetings

Kick-Off Meeting: Contractor will participate in a virtual kick-off meeting. The meeting will establish communication protocol for the project, review State deliverables and sample documents, discuss known project issues, and review the project schedule. Assume a 2-hour meeting duration.

Monthly Project Meetings: Contractor will facilitate monthly progress review meetings to coordinate specific tasks and provide project updates with State staff. Assume 1-hour virtual meeting durations. State anticipates a multi-functional group of participants involved with this project through the duration. Representatives from the following State functional groups will participate in the monthly calls on as-needed basis (dependent on Tasks to be discussed):

a) Bridge Office Project Manager

b) Bridge Office Construction

c) Bridge Office Estimating

d) Bridge Office Design

e) Bridge Office Inspection

f) Bridge Office Maintenance

g) Bridge Office State Aid

h) District Bridge Maintenance

i) Office of Environmental Stewardship

Comment Resolution Meetings: Contractor will plan on one comment resolution meeting for each task. Assume 1-hour virtual meeting durations. When possible, combine these meetings with Monthly Project Meetings.

1.2 Project Schedule

Contractor will develop a baseline schedule based on the Task descriptions and tentative due dates listed throughout. The Contractor’s schedule will include the following assumptions:

• 24-month maximum project duration

• Draft submittals: 12-week review and response period, assuming a 4-week review period by State for each submission (multiple iterations may occur within this period)

• Final submittals: 2-week review period by State for each submission

• Include all State Holidays

A draft schedule will be presented at the kick-off meeting and finalized as discussed in Task 7.0, Deliverables & Schedule.

2.0 Quality Management Plan (QMP) and Quality Control/Quality Assurance Procedures

Contractor will develop a project specific QMP for the project. Contractor will update the QMP as necessary at State’s request. The QMP will specify how Contractor will perform Quality Assurance (QA) and Quality Control (QC) activities throughout the duration of the project to ensure delivery of a quality product in a timely manner that conforms to established contract requirements. The QMP will be provided to State within 5 days of NTP.

2.1 Quality Control of Deliverables Check

Contractor is responsible for the completeness and accuracy of its work. All deliverables must be independently checked and reconciled prior to submittal to State. Review comments from State on Contractor’s various plan review submittals does not relieve Contractor of liability for an inaccurate or incomplete work.

With each submittal, Contractor must supply a comment log documenting resolution of all State plan review comments. Contractor is encouraged to facilitate submittal reviews in Revu Bluebeam sessions whenever possible (comment responses in Bluebeam may serve as a comment log where applicable). Response to all State comments must be well documented and provided with each resubmission of a deliverable.

At the request of State, Contractor must supply electronic copies of completed QA/QC “check prints” of various documents.

2.2 Software Programs

Software programs and/or spreadsheets utilized by Contractor must be verified by Contractor’s in-house Quality Assurance Program.

2.3 Quality Assurance Verification

Contractor’s Project Manager or Quality Assurance Manager must review the entire deliverable development and production process to ensure the completeness and accuracy of Contractor’s work and conformance with Contractor’s QA procedures.

3.0 Review Tasks

3.1 Design manuals, standards, and plans review

State will provide results of a previous literature review completed along with a list of bridge owners who participated in a survey to support previous pile strengthening research at MnDOT.

Contractor will perform a review of available design manuals and standard details to determine if preservation and strengthening details are available for typical Minnesota pile types in wet conditions. These documents do not need to be limited to highway transportation structures.

Deliverable: To be populated with final version Provide draft and final memos that summarize the findings and make recommendations of specific details or portions of details that could be used in development of a Minnesota-specific pile preservation or strengthening strategy. Attach all findings as an appendix to this memo.

3.2 Review of available supplier systems

Contractor will gather product literature of commercially available product systems that can be used in wet conditions and summarize the findings. This information will be necessary to ensure performance characteristics required by the design assumptions are readily available. Additionally, the information will be used to develop the evaluation process and criteria needed for the Schedule of Materials control.

In addition to the considerations listed in the Project Overview, the following criteria must also be considered:

A. Preservation or strengthening repair type

B. Ease of installation

C. Adaptability for differing site conditions

D. Durability against stream/ice flow and cold weather

E. Resistance to:

a. UV degradation

b. Chlorides, sulfates, industrial contaminants, and organics

c. Microbial-induced corrosion (MIC)

F. Availability

G. Climate requirements for installation

H. Maintenance requirements

I. Anticipated service life

J. Advantages & Disadvantages

K. Cost

Deliverable: To be populated with final version Provide draft and final memos that summarize the findings and make recommendations of specific details or product systems that could be used in development of a Minnesota-specific pile preservation or strengthening strategy. Attach all findings as an appendix to this memo.

3.3 In-service pile repair site visits

Contractor will coordinate site visits to observe the performance of in-service pile repairs. These site visits will be within approximately 200 miles of Oakdale, MN: https://www.mapdevelopers.com/draw-circle-tool.php?circles=%5B%5B321868%2C44.9994013%2C-92.9634902%2C%22%23AAAAAA%22%2C%22%23000000%22%2C0.4%5D%5D

State will provide a KANN Boat for access to in-water repairs based on the following conditions:

• Request MnDOT staff be present and operate the boat.

• All aboard need to complete boat safety training (BRDG00073 in learning center).

• Coordinate with State for scheduling use of boat a minimum of 4 weeks in advance of the desired trip date(s). Flood response will take priority and may result in rescheduling needs with minimal or no advance notice.

• Recommend launch sites with sufficient length of concrete ‘platform’ for launching,

o 5’ minimum depth for launch the boat.

o Boat length is 20’ and the weight of boat, trailer and motors is about 4,000 lbs.

• KANN Boat specs for capacity:

o 8 persons or 1330 lbs (typically, this boat becomes too crowded at 5 or 6 people).

o 1910 lbs persons, motor, gear (motors are about 520 lbs).

Site visits must not require snooper access or traffic control to observe pile repairs. It is encouraged that the Construction Contract that installed the pile repairs be present for the site visits when possible.

For hours estimating, assume 2 trips where the site visit duration is 4 hours. Travel time is not included in the site visit duration. Transportation for State employees will be provided by State.

Following the site visit(s), provide a memo summarizing the project site, project consideration and limitation, repair strategy details, and observations made by participants.

Deliverable: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

4.0 Design Tasks

4.1 Develop repair details

Develop conceptual repair details for the assumed pile types in wet conditions. Assume up to 5 details will be developed for each pile type (10 total). Consider strategies such as wraps, encapsulation, plating (both welded and bolted connections), and others.

Collaborate with State to select and refine conceptual repairs to be developed as plan details. Assume 2 strengthening and 1 preservation detail will be developed for each pile type (6 details total). Additional details will be developed as authorized by State.

Details will be developed on 11x17 sheets formatted in accordance with MnDOT CADD Standards. Detail sheets must be fully customizable to be meet project-specific needs and include ‘Designer Notes’ to assist with plan development.

Contractor will either work in conjunction with or facilitate reviews of proposed details with Construction Contractor(s) to ensure the proposed repairs are clear, concise, and constructable.

A sample plan that can be used as a starting reference can be found here:
Bridge 9462 Pier Repair Plan: https://edocs-public.dot.state.mn.us/edocs_public/DMResultSet/download?docId=13188088

Deliverable: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

4.2 Develop design guidance

Using the strengthening details developed in other tasks, develop design methodology for determining the capacity that each strengthening repair detail adds to an existing pile. State will provide guidance on basic assumptions for determining capacity of deteriorated piling and load demands for repair scenarios.

Provide step-by-step design examples and calculation tools in MathCAD or Microsoft Excel that can be used by Engineers to develop project-specific designs. Methodologies and design examples will be formatted like the MnDOT Bridge Design Manual (BDM) such that these documents can be added to that manual in the future.

These deliverables will be developed by a Professional Engineer and thoroughly checked by another Professional Engineer. One of these Professional Engineers must be licensed in the State of Minnesota. One of these Professional Engineers must have experience designing pile strengthening repairs for a minimum of 3 projects.

Deliverables: To be populated with final version. Draft and final electronic versions of the information required above.

4.3 Develop inspection criteria for planning projects

Develop inspection procedures to collect information necessary for:

A. analysis of existing pile capacity

B. design and detailing of each pile repair option

Include supporting documents such as inspection checklists, standardized forms, template drawings, and lists of equipment needed to collect this data. Designate if data requires special access considerations (i.e. underwater, snooper, ropes etc.).

Contractor will collaborate with underwater bridge inspection diver(s) who has the following credentials:

1. Completed a FHWA-approved underwater bridge inspection training course or is an ADCI certified diver

2. Has at least two years of experience in underwater bridge inspections.

3. Familiar with underwater inspection in Minnesota.

This effort is necessary to ensure the assumed access and equipment is readily available and that underwater inspections will be able to collect the data required to complete analysis of existing pile and design of pile strengthening repairs. Document this collaboration in a memo.

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of inspection collaboration memos and inspection procedures. Include supporting documents as an appendix.

5.0 Construction Tasks

5.1 Develop construction specifications and special provisions

Develop construction specifications which include description of work, material requirements, submittal requirements, construction/installation requirements, method of measurement, and basis of payment. These will be formatted as Division SB special provisions and will include “Designer Notes” to assist specification writers in modifying the document to meet project-specific needs.

During development, Contractor will collaborate with Construction Contractor(s) with experience installing repairs in wet conditions. The goal of this collaboration is to describe material, technique, equipment, access considerations. This collaboration will be used to ensure the specifications are thorough and acknowledge construction risks, time, and cost. These interactions will be summarized in a memo.

Contractor will also facilitate specification reviews with Construction Contractor(s) to collect comments from the industry.

Deliverables: To be populated with final version. Draft and final electronic documents of the information required above.

5.2 Develop a material evaluation process

Before a new product can be added to MnDOT’s Approved/Qualified Products List (APL), it must be thoroughly evaluated. Refer to MnDOT Policy #OE005, Approved/Qualified Products, https://www.dot.state.mn.us/policy/operations/oe005.html. Note that these systems are considered “Qualified” products as material testing will be included in the Schedule of Material Controls.

Develop the evaluation process for product qualification based on the “APL Master Template”, https://edocs/edocs_employee/DMResultSet/download?docId=14561358. Note that intent of this work is to only develop the framework/document for evaluation process. The State does not intend for Contractor to participate in the evaluation process for future product submittals nor complete any of the testing or environmental review tasks.

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

5.3 Develop cost estimation tools

Develop list of considerations that may influence the estimated cost for performing this work. Include consideration to person-hours, labor, equipment, permanent material, construction material, access, mobilization, and indirect costs. This list will include detailed descriptions of each item that a Contractor would consider in developing a bid price that would roll-up into unit price pay item(s).

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

5.4 Develop construction inspection checklist list

Develop a construction inspection checklist to be used as a supplement to the specifications for construction inspectors to follow during this work. This checklist will not be included in construction contracts, but rather, as a one- or two-page job aid for State construction inspectors.

Sample checklist for other bridge construction activities can be found here:
MnDOT Bridges and Structures – Bridge Construction – During Bridge Construction
https://www.dot.state.mn.us/bridge/construction.html

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

5.5 Develop construction inspection training video / learning module

Develop a short video to be used as just-in-time training for construction inspectors. The video will include an overview of the installation process, required QA/QC duties, and general observations to be made during installation. This video will be published on the MnDOT website to supplement the Inspection Checklist and will not be considered part of the construction contract. It is anticipated that the video duration will be less than 15 minutes and can include a mixture of content such as photos, videos, and presentation slides.

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

6.0 Operations Tasks

6.1 Develop in-service inspection criteria

Develop inspection guidance and condition state definitions for in-service inspection of the repair details developed under separate sub-tasks. Include photos and detailed descriptions such that bridge safety inspectors can easily collect data and rate these elements. If necessary, develop forms to be used in the field to record this data.

Deliverables: To be populated with final version. Draft and final pdf and electronic versions of the information required above.

6.2 Develop maintenance criteria

Develop maintenance strategies to perpetuate the service life of repair details developed under separate sub-tasks. Include diagrams, procedures, and frequencies of maintenance work to be performed to meet or exceed the targeted service life of the repair details. Provide observation/inspection criteria that would require the need to re-apply or replace the repair detail.

Deliverables: To be populated with final version. Draft and final MS word files of the information required above.

7.0 Deliverables

7.1 State deliverables

a) To be populated with final version.

b)

c)

7.2 Contractor deliverables

The detailed requirements of each deliverable are described in the above sub-tasks. A tentative schedule of deliverables shown in the table below. The “Due Dates” are considered a guideline and is provided to assist Contractor with the workflow envisioned by State.

At the conclusion of the project, Contractor will provide State with final versions of all submittals in as completed package (i.e. Jump Drive, SharePoint site, etc.). Final versions will be delivered as PDF and in the electronic file format that was used to generate the content. Non-PDF files must be fully editable by State to make future updates.

The Balance Of This Page Has Been Intentionally Left Blank

TASK	DELIVERABLE	DRAFT SUBMITTAL
1.0	Project Management
1.1	Meeting Meetings	5 days after each meeting
1.2	Project Schedule	5 days after kick-off meeting
2.0	Quality Management
2.0	QMP	5 days after NTP
3.0	Review Tasks
3.1		# weeks after Task # Draft
3.2		# weeks after Task # Draft
3.3		# weeks after Task # Draft
4.0	Design Tasks
4.1		# weeks after Task # Draft
4.2		# weeks after Task # Draft
4.3		# weeks after Task # Draft
5.0	Construction Tasks
5.1		# weeks after Task # Draft
5.2		# weeks after Task # Draft
5.3		# weeks after Task # Draft
5.4		# weeks after Task # Draft
5.5		# weeks after Task # Draft
6.0	Operations Task
6.0		# weeks after Task # Draft
6.1		# weeks after Task # Draft
7.0	Deliverables
	Final deliverables package	1 week after all tasks have been finalized

To be populated with final version.