Latency on the floor
A local question is answered locally rather than across a link.
Edge Computing
Compute where the data is produced.
Edge is not a smaller cloud. It is a placement decision: what has to be answered locally, and what has to be true centrally.
A site that answers locally and reconciles honestly with the centre.
Data and reads close to the source, with one durable record behind them.
Edge workloads need local reads, tolerance for an intermittent link, and a reconciliation story. PLOMID is one system with one storage contract, which makes the shape of a topology describable, but the fabric that distributes it is the least finished part of the platform and it is stated as roadmap here.
A site that answers locally and reconciles honestly with the centre.
Environment
The site
Readings taken where the equipment is, on a link that drops.
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.
Edge Computing · architecture
Workload
The shape of the work itself.
- Acquire
- Decide
- Reconcile
- Retain
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 · Edge Computing acquire · decide · reconcile · retain Select a stage
Stage
Acquire
Readings taken where the equipment is
Time series
01
Acquire
Readings taken where the equipment is
- Time series
02
Decide
Local records needed for a local answer
- SQL
- JSON / documents
03
Reconcile
What moved, when, and what conflicted
- Events
04
Retain
The durable record behind the site
- Time series
- 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.
One schema
The edge and the centre share a data model instead of diverging.
Visible reconciliation
Synchronisation conflicts are recorded events, not silent differences.
Placement as policy
Where a workload runs becomes a decision that can be stated, which is the direction the fabric is being built toward.
What this is built on.
Edge is where the deployment fabric matters most and where it is least finished. Both are stated plainly here rather than implied.
- 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.
- Control over operation → Who runs the system, and where it runs, is part of the first conversation rather than a tier on a pricing page.
- 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.
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.
- Mining → Geological models, fleet telemetry, plant throughput and equipment history.
- Manufacturing → Line telemetry, machine state, work orders and quality records around a plant.
- Automotive → Vehicle telemetry, build records, connected-fleet data and service history.
- Robotics → Robot state, motion traces, task outcomes and fleet coordination.
- Aerospace → Certification documents, test data, flight telemetry and maintenance records.
- Energy → Generation output, plant state, market positions and settlement records.
- Logistics → Shipments, routes, positions, scans and delivery events.
- Supply Chain → Suppliers, orders, inventory, movements and the documents between them.
- Telecom → Network topology, performance counters, subscriber records and incidents.
- IoT → Device fleets, telemetry, device state and the events between them.
- Cybersecurity → Telemetry, identity, asset relationships and the cases that follow.
- Autonomous Systems → Sensor streams, perception output, decisions, interventions and logs.
- Smart Infrastructure → Buildings, transport and civic systems with sensors attached.
- Government → Registers, case files, service events and reporting obligations.
- Sovereign Infrastructure → Systems that must run inside a boundary, under a known operator.
- Edge Infrastructure → Compute and data close to the source, with a central record behind it.