Case Study
LNG Operations.
Same platform. Different commodity.
Same facility, same Constellation patterns, different commodity primitives — proof 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 industrial users, backup power sites, and remote operations. Unlike pipeline gas, every delivery is a discrete transaction with its own measurement, chain of custody, and billing.
It runs at the same plant as the helium operation, with the same operators — but different measurement units, pricing structures, and compliance requirements. If one Cosmos can model both, and Command can build from it, the platform claim is engineering fact, not marketing.
02 — The Problem
Two commodities, one team, zero shared tooling
The team ran helium and LNG from the same facility on completely separate spreadsheets, tracking methods, and reconciliation processes. The same person tracked a helium ISO container in one system and an LNG delivery in another — duplicating effort, errors, and manual reconciliation.
Everyone knew a unified system would be better. The question was whether any system could model both without becoming so generic it modeled neither well. Generic ERP abstracts away what makes each commodity distinct — purity grades for helium, BTU content for LNG, different custody transfer protocols and regulatory frameworks.
03 — The Constellations
Same patterns, different primitives
01
Asset Tracking
LNG trailers modeled alongside helium ISO containers. Different asset types and measurement profiles; same tracking pattern — location, custody state, capacity, maintenance schedule.
02
Transaction Management
LNG deliveries with BTU-based pricing, volumetric measurement, and temperature-compensated calculations. Same transaction pattern, different primitives.
03
Data Modeling
LNG domain models layered onto the same Cosmos. Commodity type, units, pricing formulas, and regulatory requirements defined as configuration, not code changes.
04
API & Integration
Connections to the plant's existing metering and accounting systems. The integration layer that serves helium serves LNG — different endpoints, same pattern.
04 — The Result
One system, two commodities, zero duplication
Both commodities now live in one Cosmos, and the team uses one system instead of two. Container tracking, delivery management, invoicing, and reconciliation work the same way for both, with domain-specific primitives handling measurement, pricing, and compliance.
This is the generalization proof — not a theoretical claim, but a production deployment.
See how this applies to your commodity.
If you run multiple commodities or product lines, the same Constellation patterns can model each one — without separate systems.