Oil & Gas Midstream
Midstream operations measure custody transfer and allocation across wellheads, pipelines, and compressor stations-figures that feed financial reconciliation between counterparties, not just an operations dashboard. A gap or a misordered reading in that stream is a disputed allocation, not just a blind spot. The same field assets also generate leak-detection, pressure, and emergency-shutdown events that have to be complete and correctly sequenced for incident reconstruction, over satellite and cellular backhaul where every byte transmitted carries a real cost. KŌJŌ Stack acquires DNP3 and Modbus telemetry at the field edge, reduces what crosses backhaul to control connectivity spend, and delivers flow measurement and event data to the historian in order and without gaps-so the numbers reconcile and the sequence of events holds up.
Architecture Highlights
Flow Data That Reconciles to the Number
The Problem
Measurement Gaps Become Financial Disputes
Custody-transfer and allocation figures computed from flow measurement feed financial reconciliation between counterparties. A missing or misordered reading is not just an operational blind spot-it is a number that will not reconcile, and fixing it after the fact means renegotiating a figure counterparties have already relied on.
Safety-Relevant Events Must Reconstruct Cleanly
Leak-detection alarms, pressure excursions, and emergency-shutdown events are exactly the records an incident investigation depends on afterward. If those events arrive incomplete or out of sequence, reconstructing what happened-and in what order-becomes guesswork at the moment it matters most.
Backhaul Bandwidth Is a Real Cost, Not Just a Constraint
Wellheads and compressor stations often connect over satellite or cellular backhaul billed by the byte or the session. Transmitting every raw reading, most of which represents no real change, is a recurring operating cost-not a one-time architectural inconvenience.
What Fails in Traditional Architectures
Without structured, prepared data at the first mile, downstream systems inherit every inconsistency, gap, and limitation of the raw source data.
Allocation Numbers Don't Reconcile
When a flow measurement gap or an out-of-order reading reaches the allocation calculation, the resulting figure does not match what counterparties expect. Resolving the discrepancy after the fact means manually investigating a number that has already been used downstream.
Incident Reconstruction Runs on an Incomplete Timeline
If leak-detection or emergency-shutdown events are dropped or arrive out of sequence, an incident review cannot establish a reliable timeline of what happened and when. The record that should anchor the investigation instead raises questions about its own completeness.
Backhaul Costs Scale with Every Tag Added
Sending every raw reading over metered satellite or cellular backhaul means connectivity spend grows with every new wellhead or sensor added to the field-regardless of whether any of that data represents a real change in the process.
How KŌJŌ Stack Helps
Field Measurement Structured for Reconciliation
Flow, pressure, and volumetric readings from wellhead RTUs and flow computers are acquired natively over DNP3 or Modbus and normalized at the point of measurement, so the figures that feed custody-transfer and allocation calculations are consistent and traceable back to the source reading.
Event Integrity for Incident Reconstruction
Leak-detection, pressure, and emergency-shutdown events are captured and durably buffered at the field asset, then delivered to the historian in the order they occurred-even across a backhaul interruption-so an incident review has a complete, correctly sequenced record to work from.
Edge Reduction as a Backhaul Cost Lever
Report-by-exception with configurable deadband thresholds filters insignificant changes before they consume metered satellite or cellular bandwidth. Reducing what crosses backhaul reduces the recurring connectivity bill, not just the noise in the historian.
Unified Structure Across Wellheads, Pipelines, and Stations
Every field asset publishes to the same ISA-95 compliant namespace, so reconciliation, incident review, and central analytics all query one consistent structure across the entire midstream footprint instead of reconciling formats asset by asset.
Why This Requires First-Mile Data Structuring
Midstream field assets carry two kinds of data that cannot tolerate gaps or reordering, for very different reasons. Flow, pressure, and volumetric readings from wellhead RTUs and flow computers feed custody-transfer and allocation calculations that settle financially between counterparties-a missing or misordered value there is a number someone eventually has to dispute and reconcile. Leak-detection alarms, pressure excursions, and emergency-shutdown events from the same assets are the record an incident investigation depends on afterward-their value is in being complete and correctly sequenced, not just present. Both travel over DNP3 or Modbus from RTUs and flow computers connected by satellite or licensed-radio backhaul billed by volume, where transmitting every raw reading is a recurring cost with no operational upside once report-by-exception has already captured every meaningful change. KŌJŌ Stack addresses this by acquiring and normalizing measurement and event data at the field asset, reducing what crosses backhaul to control connectivity spend, and buffering durably so both the measurement record and the event sequence arrive at the central historian complete and in order-regardless of how the backhaul link behaves in between.
Expected Outcomes
Complete, ordered measurement data traceable back to the source reading
Leak-detection, pressure, and shutdown events arrive complete and in sequence for incident reconstruction
Edge filtering cuts what crosses metered satellite and cellular links
Own the First Mile
Owning the first mile ensures oil & gas midstream data is consistent, contextualized, and usable across the enterprise.