One view of a well
A single request reads the asset record, its telemetry window and the events recorded against it, instead of three systems joined by a timestamp convention.
- Objects
- JSON / documents
From downhole sensor to control-room query, in one path.
Where it starts
Production telemetry
Pressure, flow, temperature and equipment state written as measurements. It is the first of 4 workloads running in Oil & Gas.
The question it raises
One view of a well
A single request reads the asset record, its telemetry window and the events recorded against it, instead of three systems joined by a timestamp convention.
Why one question is hard
From Exploration to Pipelines
Oil & Gas data moves through 5 stages — Exploration → Drilling → Production → Refining → Pipelines. The shapes in play are Time series, SQL, Events, JSON / documents, Objects, and answering one question means reading across all of them.
What PLOMID contributes
Telemetry writes never stop and the reads have to stay consistent while they land. These are the parts of the layer that carry that.
- One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- Time-ordered storage Measurements and events are stored beside the records and documents they describe, so history and current state agree.
- Snapshot reads under continuous writes Readers and writers do not block each other, which is what makes a telemetry feed and an application share one system.