No synchronisation job
Removing the copy removes the job that kept it in step and the staleness it created.
Digital Twins
The model and the data it mirrors, in step.
A twin has two halves: the structure of the thing, and the stream coming off it. Built separately, they diverge, and the twin becomes a diagram that was true last month.
An asset that is modelled once and read live, rather than copied and synchronised.
An asset model that is read from operational data instead of synchronised with it.
The twin is the asset hierarchy plus its live state plus the documents that describe it. PLOMID is designed to hold the hierarchy as relationships and the state as telemetry in one layer, which makes the twin a query over operational data rather than a maintained copy.
An asset that is modelled once and read live, rather than copied and synchronised.
Environment
The asset
Hierarchy, components and connections recorded as structure.
Graph · 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.
- Graph Relationships and traversal
- Time series Measurements and events in time order
- SQL Records, keys and joins
- JSON / documents Documents and nested objects
- Objects Large assets with queryable metadata
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.
Digital Twins · architecture
Workload
The shape of the work itself.
- Model the asset
- Bind the stream
- Attach the records
- Query the twin
Data models
The models this workload names.
- Graph
- Time series
- SQL
- JSON / documents
- Objects
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 · Digital Twins model the asset · bind the stream · attach the records · query the twin Select a stage
Stage
Model the asset
Hierarchy, components and their connections
Graph · SQL
01
Model the asset
Hierarchy, components and their connections
- Graph
- SQL
02
Bind the stream
Telemetry mapped onto model elements
- Time series
03
Attach the records
Manuals, certificates and procedures
- JSON / documents
- Objects
04
Query the twin
Condition and history read per element
- SQL
- Graph
What changes when the data is in one place.
Stated as properties of the system rather than as results we cannot measure for you.
History per element
A component’s measurements, events and documents resolve from one identifier.
Condition as a query
Derived indicators are computed over the same measurements they summarise.
Documents in context
Procedures and certificates attach to the elements they govern.
What this is built on.
A twin is useful exactly as long as it is current. These are the parts that keep it that way.
- Relationships held as data → Edges expressed directly remove the reconstruction that happens at query time when relationships live in a join.
- Time-ordered storage → Measurements and events are stored beside the records and documents they describe, so history and current state agree.
- Objects with queryable metadata → Large assets are found by a query against their metadata rather than by a naming convention.
- One data layer → Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
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.
- Aerospace → Certification documents, test data, flight telemetry and maintenance records.
- Energy → Generation output, plant state, market positions and settlement records.
- Utilities → Grid topology, meter reads, asset condition and customer records.
- Logistics → Shipments, routes, positions, scans and delivery events.
- Supply Chain → Suppliers, orders, inventory, movements and the documents between them.
- Engineering → Drawings, models, bills of materials, test results and project records.
- 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.