State plus history
What the machine is doing and what was done to it are read together.
Equipment Intelligence
Each asset with its history attached.
Equipment questions are always the same three: what is it doing, what has been done to it, and what is it made of.
One machine, three questions — what is it doing, what was done to it, what is it made of.
Machine state, component history and maintenance action in one place.
Machine state is telemetry, maintenance history is records and documents, and composition is a hierarchy. PLOMID stores all three against one equipment identifier, so a reliability question does not start with a spreadsheet join. Available over records, documents and time-ordered data.
One machine, three questions — what is it doing, what was done to it, what is it made of.
Environment
The identifier
Asset and component records, the key everything else hangs from.
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
- 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.
Equipment Intelligence · architecture
Workload
The shape of the work itself.
- Identify
- Monitor
- Act
- Review
Data models
The models this workload names.
- 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 · Equipment Intelligence identify · monitor · act · review Select a stage
Stage
Identify
Asset and component records
SQL
01
Identify
Asset and component records
- SQL
02
Monitor
State, vibration and process measurements
- Time series
03
Act
Interventions, parts used and findings
- SQL
- JSON / documents
04
Review
History read per machine and component
- SQL
- Objects
What changes when the data is in one place.
Stated as properties of the system rather than as results we cannot measure for you.
Component-level truth
Parts fitted and their lot records attach to the machine that received them.
Fewer manual joins
The identifier is a key in the layer rather than a convention between systems.
Comparable machines
Aggregates compare assets using the same definitions their history uses.
What this is built on.
Equipment questions are identity questions before they are analytics questions. These are the parts that hold identity.
- 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.
- Predicates narrow the work → Indexes and access paths decide what a query touches before a page is read, so operational reads stay bounded.
- Documents beside rows → Fields that keep changing shape stay queryable instead of being exported into a separate document 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.
- Mining → Geological models, fleet telemetry, plant throughput and equipment history.
- Robotics → Robot state, motion traces, task outcomes and fleet coordination.
- Engineering → Drawings, models, bills of materials, test results and project records.
- Digital Twins → Asset models, live telemetry, relationships and the queries run against them.
- Autonomous Systems → Sensor streams, perception output, decisions, interventions and logs.