Case Study

LNG Operations.
Same platform. Different commodity.

Same facility. Same Constellation patterns. Different commodity primitives. The direct proof that the model works beyond helium.


01 — The Operation

Trucked LNG at the same plant

Liquefied natural gas (LNG) moves by truck from production facilities to end customers — industrial users, backup power sites, remote operations. The logistics are different from pipeline gas: every delivery is a discrete transaction with its own measurement, its own chain of custody, its own billing.

This LNG operation runs at the same facility as the helium operation. Same plant. Same operators. Different commodity, different measurement units, different pricing structures, different compliance requirements. If Cosmos can handle both from the same platform instance, the platform claim is not marketing — it is engineering fact.


02 — The Problem

Two commodities, one team, zero shared tooling

What happens when the same person tracks two commodities in two systems? They make the same mistake twice — and reconcile it twice.

The operations team managed helium and LNG from the same facility but with completely separate systems. Different spreadsheets, different tracking methods, different reconciliation processes. The same person would track a helium ISO container in one system and an LNG delivery in another — duplicating effort, duplicating errors, duplicating the pain of manual reconciliation.

The question was not whether a unified system would be better. Everyone knew it would. The question was whether any system could model both commodities without becoming so generic it modeled neither one well. Generic ERP systems abstract away the domain specifics that make each commodity unique — purity grades for helium, BTU content for LNG, different custody transfer protocols, different regulatory frameworks.


03 — The Constellations

Same patterns, different primitives

01

Asset Tracking

LNG trailers modeled alongside helium ISO containers. Different asset types, different measurement profiles, same tracking pattern — location, custody state, capacity, maintenance schedule.

02

Transaction Management

LNG deliveries structured with BTU-based pricing, volumetric measurement, and temperature-compensated calculations. The transaction pattern is the same — the commodity primitives are different.

03

Data Modeling

LNG-specific domain models layered onto the same Cosmos instance. Commodity type, measurement units, pricing formulas, and regulatory requirements defined as configuration — not as code changes.

04

API & Integration

Connections to the plant's existing metering and accounting systems. The same integration layer that serves helium data serves LNG data — different endpoints, same pattern.


04 — The Result

One system, two commodities, zero duplication

Both commodities now run on the same Cosmos instance. The operations team uses one system instead of two. Container tracking, delivery management, invoicing, and reconciliation work the same way for both commodities — with domain-specific primitives handling the differences in measurement, pricing, and compliance.

This is the generalization proof. Not a theoretical claim that the platform could handle multiple commodities, but a production deployment that does. Same facility, same operators, same Cosmos instance, different commodity primitives. If it generalizes across helium and LNG, it generalizes.

“We used to run two separate systems for the same facility. Now one system handles both commodities and the operators don't have to think about which tool they're in.”

— Operations Director, Fortune 10 energy company

Industrial facility

See how this applies to your commodity.

If you operate across multiple commodities or product lines, the same Constellation patterns can model each one — without building separate systems.

Start a ConversationSee the Helium case study →