Every LNG facility lives with boil-off gas (BOG). Heat leaks through tank walls, loading displaces vapor, and pressure changes flash liquid to gas. The question is how much product value BOG destroys before recovery catches up.
The IEA's assessment of emissions from LNG supply finds that flaring intensity varies more than 100-fold between the best and worst performing LNG plants, with some liquefaction plants flaring up to 3% of their LNG output. As margin pressure grows across LNG export operations, the difference between a facility that recovers BOG well and one that flares the excess is a real driver of margin, and many teams are reviewing how they manage it before committing to new equipment.
BOG generation is far from steady. Storage produces a predictable baseline, but transfer operations generate much more BOG than static storage, and control systems designed around fixed parameters struggle most during exactly those transients.
Where BOG generation creates the largest losses
Transfer and loading create the largest BOG losses, well above the baseline from tank heat leak. Storage BOG depends on insulation performance, ambient conditions and tank design. Modern composite insulation can lower that baseline compared with traditional perlite systems, and storage BOG is manageable with standard compression.
During transfer, several mechanisms add up at once:
- Flash gas forms at pressure drops across the loading arm connections.
- Vapor displacement fills the headspace of the receiving tank as liquid flows in.
- Recirculation, which operators sometimes extend to keep transfer lines cold, generates BOG that keeps climbing instead of leveling off.
How BOG costs compound beyond the flare
BOG losses show up in more places than the flare stack. Even when vapor is recovered, high-BOG events drive up compressor power and cycling, increase driver fuel use, and create knock-on constraints in downstream refrigeration and fuel gas systems. Those costs rise exactly when loading schedules are tight and the plant is already constrained.
Ship tank cool-down and pressure headroom
Ship tank cool-down is often the largest controllable source of waste, because it is procedural, repeatable and sensitive to pacing. When a protocol lets the tanks rewarm between spray sessions, much of the LNG used for cool-down never produces stable, cold tank conditions. A steadier cool-down rate that avoids unnecessary rewarming wastes less LNG redoing work already done.
The highest-loss periods also tend to be when teams hold extra tank pressure headroom as insurance. That headroom lowers the risk of reaching relief limits during a transient, but it can increase flashing and vapor displacement once transfer starts. The best-performing sites manage that headroom as a controllable variable.
When facilities decide where to start, cool-down protocols and energy efficiency usually show returns soonest. Pressure control and flash gas minimization often follow.
BOG recovery methods and their trade-offs
Recovery approaches suit different facility profiles, and no single approach fits every plant. Without active recovery, a high-BOG event forces a choice between flaring the excess and risking a pressure excursion. Both cost money.
Compression
Most facilities anchor their strategy on BOG compression, using reciprocating or centrifugal compressors to capture vapor and send it to fuel gas or back into the process. Each machine type has its own trade-offs in turndown, maintenance burden and surge sensitivity. Either way, BOG variability during loading often exceeds what the compression system was tuned to handle smoothly. Many BOG losses start as a control decision to protect surge margin or limit compressor cycling, before any equipment capacity limit is reached.
Compressor sizing creates a related trade-off. Sizing for peak loading events reduces flaring risk, but it can push day-to-day operation into inefficient part-load regions that raise energy cost, wear and cycling frequency. Sites that track compressor cycling alongside flared volume can see where plant reliability and recovery economics meet.
Reliquefaction and fuel use
Where volumes justify the capital, reliquefaction recovers full product value by returning BOG to liquid. Newer reliquefaction designs reach lower specific power consumption through additional compressor staging and better heat integration. Where BOG volumes are modest or the economics do not work, routing BOG to on-site fuel users still captures its heating value, even though it does not recover LNG product.
Advanced process control on BOG handling
Layering advanced process control onto whichever recovery configuration a facility runs can tighten BOG handling considerably. It can stabilize the flow back to liquefaction and lower the average BOG flow, which reduces load on the refrigeration system. APC layers onto the existing DCS through model-based cascade controls, with little added infrastructure.
Why recovery systems underperform during transitions
Installed recovery capacity rarely equals realized recovery, and the gap widens during the high-BOG events where losses matter most.
One reason is how conventional control logic treats equipment constraints. Anti-surge protection, high discharge temperature limits and suction drum level controls are designed to prevent equipment damage, not to maximize recovery during a transient. When several protections act at the same moment, the system tends to fall back on conservative actions that keep the equipment safe and send BOG to flare. Constraint interactions that operators manage routinely at steady state become harder to balance when BOG generation spikes and several subsystems respond at once.
When independent loops create system-level losses
The deeper limit is coordination. BOG management spans compressors, reliquefaction, fuel gas, storage pressure control and utilities. Even on a common DCS, the control strategies tend to run each loop independently, with each controller tuned for its own objective.
When loading rates change, tank pressure control and vapor return respond on different timescales. Conventional approaches resolve the mismatch by shedding load instead of finding a better operating point.
Multi-train facilities are especially exposed, because transitions stack up across equipment. A loading event on one train can shift BOG flows that change compressor loading across the facility, while each train's control system responds to its own loop variables. The largest losses sit in these handoffs between subsystems.
What changes when a model coordinates BOG handling
The coordination gaps that limit conventional recovery are multivariable problems that span subsystems and timescales. A model trained on the facility's own history can forecast BOG generation from ambient conditions, feed composition, loading schedules and equipment state. When it sees that an upcoming loading event will generate more BOG than current compressor capacity can handle, it can adjust setpoints across several subsystems before the pressure excursion develops.
A shared view of the whole system also changes how planning and maintenance decisions land in operations. A loading schedule change that looks minor on paper can become a high-risk transient when a compressor is down or a tank pressure target is already high. When everyone sees the same forecast of tank pressure, compressor loading and recovery margin, the discussion moves from who owns the problem to which trade-off is acceptable today.
Measuring BOG performance
The metrics that matter most operationally are:
- daily boil-off rate as a percentage of stored volume
- BOG generated per loading event relative to throughput
- compressor utilization and cycling frequency
- the ratio of recovered to flared vapor
The best benchmark is often the facility's own historical envelope under comparable operating modes and seasons. Tracked over time, these show whether broader operational efficiency gains are holding.
Starting in advisory mode
Facilities applying plant automation to BOG systems usually start in advisory mode. The model recommends setpoint changes, and operators weigh them against their own experience. A model does not stand in for the judgment an experienced operator brings to a non-routine event. It handles the number of interacting variables that makes BOG management during transitions hard to do by hand.
Newer operators benefit as well. Comparing what the model recommended with what happened builds intuition about how the control systems interact during high-BOG events. As operators confirm that recommendations match or improve on manual decisions, facilities move to closed-loop control, where the controller writes setpoints to the APC or DCS and operators can take over at any time.
How the Imubit Platform applies
In gas processing and LNG, the Imubit Platform applies Map, Model and Control to loading and storage. Map traces flared and unrecovered BOG to the recurring decisions behind it, such as cool-down pacing, tank pressure targets and compressor staging. Model uses Deep Learning Process Control® (DLPC®) to learn how the tanks, compressors and reliquefaction respond through loading events from the facility's own history. Control takes those decisions to closed loop, inside limits set by plant engineers, writing setpoints through the APC and DCS already in place.
