| OTIA III State Bridge Delivery Program |
|
|
 |
| Web Brief (Oct 06) |
|
Collaboration on I-5
Bridge Delivery Unit and Region 2 team up to make bridge work a success
When ODOT began planning to repair and replace eight bridges and expand Interstate 5 from four to six lanes on a busy stretch of interstate in south Salem, the Bridge Delivery Unit knew it needed the help of a few friends.
After a statewide survey of bridge conditions revealed cracks in the bridges between the I-5/Highway 22 interchange and the I-5/Kuebler Boulevard interchange, BDU was tasked with replacing seven bridges and repairing one through the OTIA III State Bridge Delivery Program. The project, Bundle 212, I-5: North Santiam to Kuebler Boulevard, was going to be huge.
Construction on Bundle 212 let in October 2005, and scheduling issues presented challenges right away. In addition, in-water work periods at Mill Creek were threatening to delay the project by an entire year.
“If you don’t hit the in-water work periods, you could lose an entire construction season,” said Ron Reisdorf, ODOT construction project manager.
BDU and Region 2 together came up with a solution. The project was “decoupled,” or split, so that work could start at the south end, where the in-water work periods were not a factor.
“Through some creative thinking and collaboration with region, we created a less linear project so that we could start work on the south end and postpone work on the portion affected by the in-water work period,” Reisdorf said.
Region 2 Project Delivery Manager Mike Long said keeping mobility delays to a minimum has also been a challenge—and a significant priority—on Bundle 212.
“With eight bridges within just a few miles, it’s a very complex project,” said Long. “It’s like choreographing a ballet with vehicles moving 50 miles per hour.”
Despite the challenges, freight and commuter traffic is flowing smoothly, albeit slightly more slowly, to accommodate the 50-mile-per-hour reduced speed limit through the work zone.
Adding to the complexity of the project are cultural and environmental concerns. Region 2 Area Manager Tim Potter said that ODOT worked with local Indian tribes because parts of the work area are culturally sensitive. In addition, Bundle 212 crosses Mill Creek, which is a critical flood way for the City of Salem and provides habitat for two salmon species.
“We worked closely with the Oregon Department of Fish and Wildlife, the City of Salem, Marion County, and the National Oceanic and Atmospheric Administration to minimize the impacts on fish in Mill Creek and ensure the project did not increase downstream flooding,” said Potter.
Salem Municipal Airport’s runway 31.
Salem Municipal Airport to make sure our cranes were lighted and did not pose a threat to aircraft. Overall, this is a very strictly controlled work zone,” Potter said.
BDU’s Regional Liaison Mike McMillen said the challenges on Bundle 212 have been an exemplary example of teamwork in action. In early October, the contractor identified an emerging safety issue: the pavement above a utility vault beneath a lane on I-5 was disintegrating, exposing a large metal plate that could have collapsed into a six-foot-deep hole or flown up and into traffic.
ODOT’s program management consultants called for an emergency lane closure to make the repair, and District 3 teams showed up to help. Region 2 District 3 Manager Don Jordan and Transportation Maintenance Manager Jeff Sorenson pitched in with equipment and materials—even manning some shovels—to get the vault filled, the surface repaved and traffic flowing smoothly again as quickly as possible.
“It was an example of everyone coming together to get the problem solved as safely and quickly as possible,” said McMillen.
Despite the complexity of Bundle 212, work is progressing well and is on time, thanks to great collaboration between BDU and Region 2.
“This project has allowed us to find out how to work together to manage such a large project,” said McMillen. “In 2007 to 2009, we’re going to have huge numbers of projects going on through the bridge program, and Bundle 212 has served as a laboratory, allowing us to figure out how to continue to work together to manage upcoming projects.”
###
|
|
|
|