The crossing that could not share a method boundary

ISSUE 03 - INTERFACE CONDITION RISK

(Øresund Fixed Link, Denmark–Sweden. Opened 1 July 2000. Contract values: tunnel DKK 3.8 billion, island DKK 1.4 billion, bridge awarded November 1995.)

⚙️ THE ISLAND IS NOT READY — BOTH CONTRACTS STOPPED

The Øresund Fixed Link connects Copenhagen and Malmö across 16 kilometres of strait. It opened on 1 July 2000, ahead of schedule and within budget. It is still the longest combined rail and road bridge in Europe. Those facts are well known. What is less often examined is the structural logic that made delivering it on time so improbable — and what made it possible anyway.

The project was divided into three separate design-build contracts, each awarded to a different consortium, each using a fundamentally different construction method.

Contract 1, the immersed tunnel: awarded to Øresund Tunnel Contractors at DKK 3.8 billion. The method was factory prefabrication — 20 concrete tunnel elements, each cast at a purpose-built yard at Copenhagen's Nordhavn harbour, towed out to Drogden, and lowered one by one into a pre-dredged trench on the seabed. The first element entered the water in August 1997. The tunnel reached its final metre in March 1999.

Contract 2, the artificial island of Peberholm: awarded to Øresund Marine Joint Venture at DKK 1.4 billion. The method was marine reclamation — dredge, deposit, grade. Peberholm is 4 kilometres long and 500 metres wide, constructed from rock and soil extracted during the dredging operations for the tunnel trench itself. It sits south of the natural island of Saltholm. It had to be built, stabilised, and finished to precise geometry before either the tunnel could be terminated or the bridge could begin.

Contract 3, the bridge: awarded to Sundlink Contractors — Skanska, Højgaard & Schultz, Monberg & Thorsen, Hochtief. The method was large-scale marine prefabrication combined with heavy lift placement. Concrete caissons, pier shafts, and railway deck troughs were cast at Malmö North Harbour. The pontoon crane Svanen — 8,700-tonne lift capacity — transported them to the bridge line and placed them in position. The two pylon caissons for the high bridge each weighed 20,000 tonnes, beyond Svanen's capacity; they were produced in a dry dock near the bridge site and transported by a purpose-built pontoon catamaran. The pylon legs were cast in situ at sea, rising at approximately 4 metres every eight days to a final height of 203.5 metres above the water.

Three methods. Three contractors. Three fundamentally different risk profiles and production rhythms — all converging on a single fixed geographical point: the island of Peberholm.

The tunnel had to enter Peberholm from the west. The bridge had to leave it to the east. Both needed the island to be at the right elevation, the right geometry, and structurally stable enough to receive a portal structure and a bridge abutment. The island contractor was responsible for neither the tunnel nor the bridge, but both depended entirely on what the island contractor delivered, and when.

The boundary was not a line on a map. It was a condition.

This is not an engineering coordination problem. It is a commercial exposure that contract structures do not produce by default.

If the island was too low, the tunnel portal flooded. If the island was too high, the bridge deck geometry failed. If the island was not stable, neither structure could be founded on it. If the island was late, both adjacent contracts stopped — with Svanen already mobilised to the bridge line, and 20 prefabricated tunnel elements waiting in sequence at Nordhavn.

Here is what the Øresund Fixed Link reveals about how risk actually distributes on multi-contract infrastructure programmes.

Most project commercial structures are designed to allocate risk within contracts. The contract between the client and the tunnel contractor defines what the tunnel contractor owns. The contract between the client and the bridge contractor defines what the bridge contractor owns. Each scope is bounded, each risk is allocated, and each day rate is established.

What the contract structure does not naturally produce is visibility of the risk that lives between the contracts — the risk at the interface condition.

⚙️ THREE CONTRACTS — THREE METHOD BOUNDARIES — ONE FIXED HANDOVER POINT

⚠️ The Interface Condition Defined

An interface condition is a physical or geometric state that one contractor must achieve before an adjacent contractor can proceed. It is not a milestone. It is not a programme date. It is a method boundary — the point at which one erection method ends, and another begins. The handover at that boundary is not contractual in the normal sense. It is structural. The second contractor cannot proceed until the condition is met — regardless of what the programme says, and regardless of who is responsible for the delay.

On Øresund, the interface condition was the island of Peberholm. The risk it created was not hidden — it was not held by the parties most exposed to it.

The tunnel contractor, if the island was late, had 20 prefabricated elements sequenced for delivery. Each was towed from Nordhavn. Each required a clear trench, a positioned gravel bed, and a termination point — which was the tunnel portal on Peberholm. If the island was not ready, the towing sequence could not proceed. The cost of a delay — elements holding position at anchor, crane barges on standby, specialist marine teams standing by — was running regardless of whose fault the delay was.

The bridge contractor had Svanen. In 1996, it became clear that Svanen would be available from summer 1997 — a window that fitted the overall programme well enough that the design was reconfigured to take advantage of it, increasing the size of prefabricated elements specifically because Svanen could handle them. That decision produced a more efficient structure. It also created a tighter dependence on the island's timing, because the Svanen programme — and the prefabrication programme it fed — assumed a bridge abutment would be available to receive elements from a specific date.

The island contractor was responsible for meeting a specification. They were not responsible for the costs the tunnel contractor or the bridge contractor would incur if that specification was late.

🔄 The Pattern That Repeats

The Øresund structure is unusual in its scale and its public visibility. But the pattern — three or more contractors converging on a shared interface condition, with the costs of interface failure distributed to the parties least able to control it — repeats on every major infrastructure scope with a method change at a contract boundary.

It repeats on offshore wind foundations meeting transition pieces. It repeats on tunnel boring machines meeting precast lining rings from a different supplier. It repeats on heavy lift marine operations, meeting civil works that were not complete when the vessel mobilised. The method boundary is always the commercial exposure that the contract missed.

On Øresund, the risk was managed — well — through the project governance structure established by Øresundsbro Konsortiet. The consortium's management of parallel works and risk contingency planning was recognised at the time as a significant contributor to the early completion. The risk framework was not a contract fix. It was an owner-level integration function that sat above all three contracts and could see the interface conditions they individually could not.

The project succeeded. But the reason it succeeded is precisely the reason most projects with the same structure do not: there was an owner-level function with the authority, the information, and the commercial visibility to manage the interface. Most projects don't have that. They have a programme. And a programme is not the same thing as interface condition management.

🎯 The Question for Your Next Campaign

"On your current project — where is the interface condition, who owns it contractually, and who bears the cost if it is late?"

Not theoretically. Not programme-theoretically. Commercially — in the room where the day-rate is running, where the vessel is on standby, where the prefabrication sequence has been committed. The party incurring the cost, and the party contractually responsible for the condition. If those are not the same party, you have found the commercial exposure your contract does not see.

Test it against these three scenarios. Each is a recognisable pattern in erection engineering and heavy lift scopes.

In all three scenarios, the structural and erection decisions were technically correct within their own scope. The commercial consequences emerged at the boundary — where two methods met, where two contracts ended, where two programmes were supposed to join.

The scenarios above are composite illustrations of patterns recognisable across erection engineering and heavy lift. They are not drawn from specific projects or clients.

"The boundary was not a line on a map. It was a condition."

Marco Torri

Founder, EE&HL Network  |  Commercial intelligence for erection engineering & heavy lift

eehl.net  |  linkedin.com/in/marco-torri  |  [email protected]

Sources: Øresundsbro Konsortiet, Skanska project record, Ramboll project documentation, GIHUB/TEN-T Fixed Link case study, Ingenia (ICE), PMI Network (Christensen & Rydberg, 2001), Wikipedia (Øresund Bridge), ScienceDirect (sedimentological/environmental record)

Diagrams: Original - EE&HL Network 2026