Bertha (tunnel boring machine)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:Front of model of tunnel boring machine at Milepost 31.JPG
Front of a model of Bertha at Milepost 31, the tunnel project information center.

Bertha, also known as Big Bertha, is a 57-foot-diameter (17.4 m) tunnel boring machine built specifically for the Washington State Department of Transportation's (WSDOT) Alaskan Way Viaduct replacement tunnel project in Seattle.[1] It was made by Hitachi Zosen Sakai Works in Osaka, Japan, and the machine's assembly was completed in Seattle in June 2013. Tunnel boring began on July 30, 2013, with the machine originally scheduled to complete the tunnel in December 2015.

On December 6, 2013, work was halted approximately 1,083 feet (330 m) into the planned 9,270-foot-long (2,830 m) route because of an unexpected impediment. Investigations a month later revealed that the machine had damaged several of its cutting blades after encountering a steel pipe that was used to measure groundwater in 2002 around the Alaskan Way Viaduct. Over the next two years, a recovery pit was dug from the surface in order to access and lift the machine's cutterhead for repair and partial replacement in 2015.

Bertha resumed tunnel boring on December 22, 2015, but was stopped in early January 2016 after a tethered barge in Elliott Bay damaged nearby piers and a sinkhole opened near the project site. Governor Jay Inslee halted all work on the tunnel on January 14, 2016, citing concern over public safety after the sinkhole incident. Digging resumed on February 23, but was halted again for maintenance and inspections late in March.[2] Bertha resumed tunneling on Friday, April 29, 2016, digging under the Alaskan Way Viaduct.[2]

In December 2015, WSDOT estimated that the tunnel would be completed and open to traffic in early 2018.[3]

As of May 13, 2016, Bertha has excavated 1,995 feet (608 m) of the planned 9,270-foot long (2,830 m) tunnel route.[4]

Name

The name Bertha, after Seattle's only female mayor, Bertha Knight Landes, was chosen by a panel (that included the Governor and Transportation Secretary) from 150 submissions from kindergarten through 12th graders, who were asked to submit female names with Washington state heritage.[5] The winning entry, submitted by two elementary schools in Poulsbo and Hoquiam, was selected in December 2012.[6]

It is also unofficially nicknamed "Big Bertha", owing to the size of the machine.[7][8]

In March 2016, regional transit agency Sound Transit decided to drop names for its own tunnel boring machines, used for smaller light rail tunnels, citing unwanted association and confusion with Bertha, especially the machine "Brenda" used on the Northgate Link Extension and University Link Tunnel.[9][10]

Design and assembly

Freighter Fairpartner carrying the disassembled tunnel boring machine into the Port of Seattle in April 2013.

Bertha was designed and manufactured by Hitachi Zosen Sakai Works of Osaka, Japan, and is the world's largest earth pressure balance tunnel boring machine,[11] at a cutterhead diameter of 57.5 feet (17.5 m) across. The machine is 326 feet (99 m) long and and weighs 6,700 short tons (6,100 t).[12] The machine itself cost $80 million and is owned by Seattle Tunnel Partners, the project contractors.[13]

Hitachi Zosen held a completion ceremony for the machine, performed at the same time as the naming ceremony, in Osaka, Japan, on December 20, 2012.[14] It was shipped three months later to the Port of Seattle in 41 sections, arriving on April 2, 2013.[15][16]

Bertha has a special pre-programmed melody that plays inside the machine for workers inside and monitoring the tunnel-borer.[17]

Excavation

Dedication and first section

The machine began excavation of the 1.7-mile-long (2.7 km) route on July 30, 2013, with completion of the bore scheduled in 14 months' time and the tunnel opening to traffic in December 2015.[18][19][20] Over 5,000 members of the public, along with Governor Jay Inslee, were present for the machine's dedication a week prior to the beginning of excavation.[21][22]

Damage to cutterhead and two-year delay

File:SR 99 Tunnel Bertha stuck December 6, 2013.png
Route map of the Alaskan Way Viaduct replacement tunnel showing location where the tunnel boring machine became stuck on December 6, 2013.

By December 6, 2013, Bertha had tunneled 1,019 ft (311 m), or 11%, of the total 9,270 ft (2,830 m) length of the tunnel,[23] stopping about 60 ft (18 m) below ground between South Jackson Street and South Main Street.[24] The machine's progress was halted on that day by an unexpected impediment.[25] After a month's investigation, WSDOT announced that the machine's cutting blades had encountered an 8-inch-diameter (20 cm), 119-foot-long (36 m) steel pipe, one of several well casings left over from a previous 2002 drilling project that had assessed groundwater conditions and soil stability in the area in case of another earthquake, such as the 2001 Nisqually earthquake, which led to a need for the replacing of the Alaskan Way Viaduct in the first place. Because the machine cannot cut through metal, the pipe damaged several of Bertha's cutting blades, necessitating blade replacement before the machine could proceed. The pipes' locations were known to WSDOT and the agency thought they had been removed. It is unclear whether the state agency or one of its contractors is responsible for the left-behind pipes, as well as who is responsible for allowing the tunneling to proceed without their removal.[26][27][28]

In early February 2014, as Bertha was being prepared to resume operation, workers discovered it was overheating and that a damaged main bearing seal needed to be replaced. Multiple options were discussed to fix the problem, but Bertha was expected to be out of commission until March 2015.[29] In December 2014, workers began digging a 120-foot-deep (37 m) pit in order to lift Bertha's front end up to street level for repairs,[30] but were delayed when groundwater pumping caused visible damage to nearby South King Street and some of its neighboring buildings.[31] The front end of the machine, including the damaged cutter head, was successfully lifted onto the surface on the morning of March 31, 2015.[32] Seattle Tunnel Partners (STP), the contractors overseeing the project, estimated that fixing Bertha would delay the opening of the new tunnel by an additional nine months to August 2017,[33] which was later extended to March 2018 after additional damage was discovered in June 2015.[34][35]

On May 18, 2015, WSDOT reported to the Seattle City Council that the damage to the bearing sand seals was worse than had been previously reported. Further inspection after the cutting head was removed and disassembled showed damage to the cutter head drive gears, so a new estimate of the repair time and cost was being prepared.[36]

The front end of the machine was lowered back into the access pit for reassembly in a four-lift process beginning with the repaired cutter drive on August 24, 2015.[37][38][39]

In June 2015, Seattle Tunnel Partners sued to force insurers to payout on the $85 million insurance policy to cover repairs needed after Bertha's cutting teeth were damaged in a collision with a steel pipe in December 2013. In August 2015, a consortium of eight insurers filed a lawsuit against STP in order to avoid a $143 million payout to cover the cost of repairs to the boring machine. The insurers claimed that the tunnel-boring machine's capabilities were inadequate for the project and should be excluded.[40]

File:Bertha TBM retrieval site.jpg
View of retrieval site for repairs of Bertha's cutter head. The red gantry crane, center, was used to lift the cutter head from a shaft dug in front of the stuck boring machine. The white shed, right, was built to house the head during repairs and upgrades, and then the head was lowered back down the shaft and reinstalled.

Resumption of digging and subsequent stoppages

On December 22, 2015 at 12:30 a.m., the machine resumed digging 1.5 feet (0.46 m) through sand poured into the recovery pit. By January 4, Bertha had traveled 1,098 feet (335 m) of its planned 9,270-foot-long (2,830 m) route from SoDo to South Lake Union.[3] On January 6, 2016, Bertha broke through the concrete access vault and began digging through normal soil.[41][42] Digging was halted once again on January 12, 2016, after a barge carrying excavated dirt tipped over in Elliott Bay, spilling its load and damaging a dock at the Port of Seattle's Terminal 46.[43] The same day, a sinkhole formed within the tunnel's work zone approximately 35 feet (11 m) north of the access pit; the hole was filled with 250 cubic yards (190 m3) of concrete by contractors the following day and is not expected by WSDOT to delay the resumption of digging later in the week.[44][45]

On January 14, 2016, Governor Jay Inslee ordered drilling on the tunnel to stop, invoking a contract clause in the tunnel agreement that allowed the state to suspend work based on unsafe conditions for project personnel or the general public.[46] Before excavation of the tunnel can resume, WSDOT has requested that contractors Seattle Tunnel Partners complete and deliver an analysis of what caused the January 12 sinkhole and what modifications to tunneling operations can be made to prevent further ground-level problems.[47][48]

Digging resumed on February 23, after a WSDOT review determined that new soil monitoring practices were sufficient, allowing the machine conditional permission to bore through 160 feet (49 m) of material and finish the initial testing phase of the machine.[49] By March 14, Bertha had finished its 300-foot (91 m) bore to a "safe haven" located ahead of the Alaskan Way Viaduct;[50] allowing WSDOT and STP to prepare for a two-week closure of the viaduct in late April as the machine passes under the vulnerable structure while closely monitored.[51] Following a month of maintenance and inspections, Bertha resumed tunneling on Friday, April 29, 2016,[2] and crossed 15 feet (4.6 m) under the closed viaduct in a 11-day closure in early May that ended earlier than scheduled.[52]

As of May 13, 2016, Bertha has excavated 1,995 feet (608 m) of the planned 9,270-foot long (2,830 m) tunnel route.[4]

Tunnel boring is scheduled to be complete in January 2017, with the finished tunnel open to traffic in April 2018.[3][53][54]

Controversy

The two-year stoppage of Bertha has been criticized as an example of a political boondoggle by opponents.[55][56]

In January 2015, two Republican state senators introduced a bill in the Washington State Legislature to kill the project, citing Bertha and its delay in particular. The bill was never heard in the state senate and failed to pass the Senate Transportation Committee.[57]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.

External links