In multi-train LNG operations, performance rarely behaves as steadily as it appears.

On the surface, trains within the same complex often look similar – comparable output, comparable efficiency.

But over time, that similarity starts to drift.  Not dramatically.  Not all at once.  Just enough to matter.

Small differences begin to show up:

• a marginal increase in energy consumption
• slightly less stability under changing feed conditions
• incremental losses that are hard to pin down

Individually, none of these raise concern.  Collectively, they start to shape how performance evolves.

What makes this more complex is that LNG trains don’t operate in isolation.

• Feed gas changes.
• Ambient conditions shift.
• Maintenance cycles introduce variation.

• Shared utilities create dependencies that are difficult to untangle.

So what you’re seeing isn’t just train performance – it’s system behaviour.  And this is where things get interesting.

Two trains can sit side by side, deliver similar results, yet behave very differently when conditions change.  Over time, that difference becomes more than noise.  It becomes structural.

Later trains often reflect improvements – design refinements, operational learning, adjustments based on earlier experience.

But those improvements are shaped by what has already been seen.  And just as importantly, what hasn’t.

What works in one context doesn’t always carry across cleanly to another.

This is where benchmarking starts to shift in meaning.  It’s no longer just about comparison.  It’s about understanding what actually holds up.

• Which choices sustain performance under real operating conditions
• Which improvements only work under specific circumstances
• Which behaviours repeat across systems and over time
• And where the next level of performance might still sit beyond what has already been implemented

The reality is, large-scale LNG operations already have data.  They have visibility.  They have highly capable teams.

Benchmarking itself isn’t new.  It happens internally, across joint ventures, and with external providers.

And yet, outcomes vary.  Not because of a lack of effort – but because maintaining comparability as systems evolve is far from straightforward.

What matters is not just what is measured, but how performance is interpreted in context.

• How differences are separated from noise.
• How interactions are preserved rather than simplified.
• How behaviour is tracked over time in a way that still makes sense when conditions change.

When you look across LNG systems in this way, patterns begin to emerge.

• Some trains remain stable under variability.
• Others are more sensitive to disruption.
• Some operating approaches hold up better across interconnected processes.

These differences are rarely visible from within a single system.

What distinguishes more advanced approaches is not access to data, but the ability to observe performance across systems and over time in a way that remains consistent.

At that point, benchmarking becomes something different. 

Not a comparison exercise –

but a discipline through which performance can be understood, tested, and extended…

…beyond the limits of any individual system or organisation.