History and state agree
The measurement and the record it belongs to are read from one place, so they cannot drift.
Time-series Workloads
Measurements stored beside the records they describe.
Time-ordered data is usually kept in its own system, which is why a question about what happened and a question about what is configured are answered in different places.
A measurement that must still be readable against the record it belongs to, years later.
Measurements and events stored beside the records they describe.
Time series carries telemetry, events and history. PLOMID stores it with the records and documents it belongs to, so history and current state agree by construction. Partitioning, windows and downsampling are part of the query surface.
A measurement that must still be readable against the record it belongs to, years later.
Environment
The source
Equipment, services or devices producing measurements on the clock.
Time series
Two estates, drawn.
The same shapes, held two ways. The difference is not the storage, it is where the agreement between them lives.
Separate systems Copies kept in step
One layer One plan · one contract
What this workload moves.
Every shape below is a surface of the layer, not a format to be converted into one. They are read and written together.
- Time series Measurements and events in time order
- SQL Records, keys and joins
- JSON / documents Documents and nested objects
- Events Operational events as they happen
How the workload reaches the data.
The models this workload names, the path a request takes through them, and the surfaces that speak to the layer.
Time-series Workloads · architecture
Workload
The shape of the work itself.
- Ingest
- Store
- Window
- Compare
Data models
The models this workload names.
- Time series
- SQL
- JSON / documents
- Events
The layer
One path from a request to the data it names.
- Planning Predicates narrow the work before it runs
- Execution Rows, fields and windows answered together
- Transactions Readers and writers do not block each other
Surfaces
How the workload reaches the layer.
- SQL surface The query language the layer is documented in
- Applications Services and jobs reading and writing as they run
- Analytics & AI clients The same layer, the same access path
The work, stage by stage.
Choose a stage to read what happens there, or a shape to see every stage that handles it. Nothing on the map is a private interface.
PLOMID · Time-series Workloads ingest · store · window · compare Select a stage
Stage
Ingest
Measurements and events with identity and timestamps
Time series
01
Ingest
Measurements and events with identity and timestamps
- Time series
02
Store
Time-ordered layout with the records they describe
- Time series
- SQL
03
Window
Ranges, resampling and downsampling
- Time series
04
Compare
History read against current configuration
- SQL
- JSON / documents
What changes when the data is in one place.
Stated as properties of the system rather than as results we cannot measure for you.
One retention policy
How long telemetry is kept is a property of the layer, not of three separate systems.
Shapes that answer together
A window read returns values with the asset fields attached, without a join outside the database.
Ingestion that tolerates reality
Out-of-order and late-arriving writes are the normal case rather than an incident.
What this is built on.
Time-ordered workloads are decided by how writes and windows behave. These are the parts that carry them.
- Time-ordered storage → Measurements and events are stored beside the records and documents they describe, so history and current state agree.
- One data layer → Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- 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.
- Predicates narrow the work → Indexes and access paths decide what a query touches before a page is read, so operational reads stay bounded.
Workloads that sit beside this one.
Where this shows up.
Derived from the industry pages that reference this solution, so the two directions of the relationship always agree.
- Oil & Gas → Seismic records, drilling telemetry, production flow and the documents around them.
- Energy → Generation output, plant state, market positions and settlement records.
- Utilities → Grid topology, meter reads, asset condition and customer records.
- Telecom → Network topology, performance counters, subscriber records and incidents.
- Scientific Research → Instrument output, simulation results, reference material and datasets.
- IoT → Device fleets, telemetry, device state and the events between them.
- Observability → Metrics, logs, traces and the service records they describe.
- Digital Twins → Asset models, live telemetry, relationships and the queries run against them.
- Smart Infrastructure → Buildings, transport and civic systems with sensors attached.
- Edge Infrastructure → Compute and data close to the source, with a central record behind it.