Identity that holds
Device records are keys in the layer rather than strings in a message.
IoT
Device fleets and their events in one layer.
An IoT estate is an identity problem wearing a telemetry costume. Devices are replaced, re-keyed, re-provisioned, and the history has to survive it.
A device that is provisioned once and writes for years — across replacements and re-keyings.
Device fleets: identity, telemetry, current state and lifecycle events.
The workload combines device records, a continuous stream of readings, current state read by key, and lifecycle events. PLOMID holds the device identity and the data it produced in one layer, so a fleet question does not begin with a device-management API.
A device that is provisioned once and writes for years — across replacements and re-keyings.
Environment
The device
Identity, model and firmware recorded at provisioning.
SQL
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
- Key-value Direct access by key
- 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.
IoT · architecture
Workload
The shape of the work itself.
- Provision
- Stream
- Resolve
- Maintain
Data models
The models this workload names.
- Time series
- SQL
- Key-value
- 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 · IoT provision · stream · resolve · maintain Select a stage
Stage
Provision
Device identity, model and firmware records
SQL
01
Provision
Device identity, model and firmware records
- SQL
02
Stream
Readings with identity attached
- Time series
- JSON / documents
03
Resolve
Current state read directly by key
- Key-value
04
Maintain
Firmware, fault and lifecycle events
- Events
- SQL
What changes when the data is in one place.
Stated as properties of the system rather than as results we cannot measure for you.
State without a scan
Current state is addressed directly instead of by ordering the stream.
History across replacements
A hardware swap is an event, so the fleet’s history stays continuous.
Fewer systems in the path
Removing the metadata store removes an ingestion dependency.
What this is built on.
Fleet workloads are decided by identity continuity. These are the parts of the layer that carry it.
- 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.
- Every client, one layer → Applications, AI clients, services and background jobs reach the same data through the same interfaces.
- Deployment is a decision → Self-hosted, edge and managed topologies are design destinations of the deployment fabric, and the fabric is specified as its own part of the platform.
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.
- Manufacturing → Line telemetry, machine state, work orders and quality records around a plant.
- Automotive → Vehicle telemetry, build records, connected-fleet data and service history.
- Utilities → Grid topology, meter reads, asset condition and customer records.
- Retail → Transactions, stock, stores, promotions and customer behaviour.
- Logistics → Shipments, routes, positions, scans and delivery events.
- Telecom → Network topology, performance counters, subscriber records and incidents.
- IoT → Device fleets, telemetry, device state and the events between them.
- 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.