Closed loop
An intervention can be checked against the measurements that followed it.
Predictive Maintenance
Signals, service history and decisions in one loop.
Prediction is the easy half. The useful half is knowing whether the last intervention changed anything.
A recommendation that can be checked against what happened last time it was followed.
Condition monitoring read against what maintenance actually did.
Condition data is a time series, interventions are records, and the model used to score them depends on retrieval. PLOMID keeps the series, the work history and the outcome in one layer, so a recommendation can be checked against what happened the last time it was followed.
A recommendation that can be checked against what happened last time it was followed.
Environment
The measurement
Condition and process readings arriving continuously.
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
- Vector Similarity and semantic retrieval
- JSON / documents Documents and nested objects
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.
Predictive Maintenance · architecture
Workload
The shape of the work itself.
- Measure
- Score
- Intervene
- Verify
Data models
The models this workload names.
- Time series
- SQL
- Vector
- JSON / documents
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 · Predictive Maintenance measure · score · intervene · verify Select a stage
Stage
Measure
Condition and process measurements
Time series
01
Measure
Condition and process measurements
- Time series
02
Score
Models and thresholds applied in place
- Vector
- Time series
03
Intervene
Work performed, parts and findings
- SQL
- JSON / documents
04
Verify
The next window checked against the intervention
- 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.
Fewer mystery assets
Work history and condition share an identifier rather than a spreadsheet.
Thresholds with context
Alerts are evaluated against the asset’s own history rather than a global line.
Evidence for decisions
Deferrals and replacements can be justified from stored data.
What this is built on.
Maintenance decisions are judgement calls that need evidence. These are the parts that keep the evidence.
- Time-ordered storage → Measurements and events are stored beside the records and documents they describe, so history and current state agree.
- Retrieval as an access path → Similarity search arrives as another way into the same data rather than a second copy to keep in step.
- 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.
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.