LNG Terminal Marine Works: The Underestimated Interface Risk in Program Delivery

LNG terminal projects are usually planned, resourced, and reviewed around the liquefaction or regasification train — the process heart of the facility. Marine works, by comparison, often get treated as a supporting scope: jetties, breakwaters, mooring and berthing systems, and loading arms. That framing consistently underestimates how much schedule and interface risk actually lives in the marine package.

A Different Engineering Discipline, on the Same Critical Path:

Marine infrastructure design draws on coastal engineering, geotechnical conditions specific to the shoreline, metocean data, and vessel interaction dynamics that are largely independent of the process engineering driving the rest of the project. Yet the marine works sit squarely on the critical path: first cargo cannot happen without a functioning berth, and the loading arm interface has hard dependencies on both the jetty structure and the process train's send-out or receiving specifications. This creates a structural coordination challenge. The teams designing the breakwater and jetty are frequently different specialist contractors from the teams designing the process facility, sometimes engaged on different timelines, occasionally even reporting through separate project management structures within the same owner organization.

Where the Interface Risk Actually Concentrates:

• Loading arm envelope and vessel range — berthing structure geometry must accommodate the full range of vessel sizes and hull types expected to call, agreed early and locked before jetty steel is detailed. • Metocean and geotechnical data timing — marine works are unusually sensitive to site-specific data that can take a full season or more to gather; late or thin data collection is one of the most common causes of marine schedule slip. • Utility and control system tie-ins — fire and gas systems, emergency shutdown, and communications between the jetty and the main process control system are often finalized later than they should be, creating late-stage rework. • Permitting and stakeholder timelines — marine works frequently carry separate environmental and navigational permitting tracks with their own regulatory bodies and timelines, distinct from the onshore facility's permitting path.

What Strong Programs Do Differently:

Terminal projects that manage this well treat marine works as a fully integrated workstream from the earliest planning stage, not a downstream dependency to be picked up once the process design matures. That means involving marine engineering discipline leads in the same interface management forums as process and mechanical leads, from concept select onward, and giving marine permitting and metocean data collection their own critical-path visibility in the master schedule rather than folding them into a generic “infrastructure” bucket.

It also means recognizing that marine works often have the longest lead times in the entire project — metocean data campaigns, geotechnical surveys, and permitting approvals can outlast the process engineering schedule by a wide margin if they are not started early enough.

The Program Delivery Takeaway:

Marine works are not a secondary scope attached to an LNG terminal; they are a parallel critical path with their own engineering discipline, data dependencies, and regulatory timeline. Programs that recognize this early and resource marine coordination accordingly avoid the late surprises that otherwise show up as schedule slip in the final year before first cargo.