Skip to content
STOIntelligence
All insights

From first LNG to first major outage

Tom MankowskiFounder & PrincipalJuly 8, 20266 min read

The United States has added LNG export capacity faster than almost anyone forecast, and federal projections have that capacity nearly doubling again by the early 2030s. Most of the attention goes to the build. Far less goes to what happens after startup, when a new facility moves from commissioning into operations and toward its first major outage.

A turnaround is a system, not a purchase

A major outage is not a service you can buy on the day you need it. It is a system: how scope is developed and challenged, how readiness is gated, how the countdown is governed, who is accountable for each deliverable, and how the execution schedule is tested before the baseline locks. Mature refining and petrochemical operators spent decades building that system, usually the hard way, one event at a time. A newly commissioned LNG facility has not run it as an organization even once.

The people are capable and the equipment is world class. What a young operator lacks is the repeatable work process that turns a first turnaround into a governed event rather than an improvised one. In the meantime the owner leans on engineering firms and equipment makers for expertise that does not yet live in house, which is reasonable, but it leaves the operator without a standard of its own.

Why the gap costs more in LNG

Three reasons the gap matters more here than in most settings.

  • Train economics. A single liquefaction train carries a large stream of cargo value. Trade estimates put lost or deferred production from downtime in the millions of dollars per day. Schedule slippage on a planned outage defers that revenue day for day, exactly as unplanned downtime does.
  • Risk profile. Liquefaction is high-hazard cryogenic processing, and startup and restart are among the highest-risk phases of any event. Weak outage governance threatens more than the schedule. It threatens a safe, controlled restart.
  • The portfolio. Many of these operators run multiple trains and multiple sites. The real constraint is rarely one event. It is overlapping events competing for the same scarce people, and that collision needs to be visible years out, not discovered weeks before.

The two default responses both fall short

One response is to wait and learn on the first outage. That treats the most expensive event on the site as a training exercise, and it is precisely where a first turnaround quietly slips.

The other is to hand the problem to a closed system that hides the standard inside a vendor subscription. That does not build the capability of the operator, and when the contract ends, so does the knowledge.

Adopt a standard, then run it live

There is a better path, and it does not require inventing a turnaround program over three painful outage cycles. Adopt a documented, best-practice STO management system, built on public-framework rigor (DCMA, GAO, AACE, PMI) and tailored to how the facility actually works, then run it on real events with named accountability and recorded gate decisions.

Done well, the standard is something the operator owns and edits, not a black box. Every activity has an owner. A key deliverable does not close without evidence and an accountable approval, and a gate closes only through a recorded decision. Every event across every site sits on one long-range plan, so a resource collision surfaces years out rather than weeks before. And an independent read on readiness and schedule quality sits on the same event record, so a first-time team can see whether it is actually ready and whether the schedule will hold.

That is the shape of the STO·CORE management system and the STO·PATH work process platform: own the standard, and run it live.

Build the system before the outage finds the gaps

New LNG operators do not need a turnaround consultant on the day the train comes down. They need a turnaround standard well before that, and a way to run it that builds their own capability rather than renting one from someone else. The best time to put that system in place is while the first major outage is still on the horizon, not once it has arrived.

Want a defensible read on your next event?

Start a conversation