One number
Served and reported values come from one source, so disagreements become bugs.
Operational Analytics
Plant data answered without making a copy of it.
Operational reporting is the least glamorous workload and the one that decides whether a platform is trusted: the number served and the number reported have to be the same number.
One number: what the application serves and what the report says.
Reporting that reads the operational source instead of a copy of it.
Aggregates run over the live tables, with document fields filterable beside them. Because there is no extract, a report describes the state of the system at the moment it ran, and the operational view agrees.
One number: what the application serves and what the report says.
Environment
The system of record
The application writes rows and documents all day, every day.
SQL · JSON / documents
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.
- SQL Records, keys and joins
- JSON / documents Documents and nested objects
- Time series Measurements and events in time order
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.
Operational Analytics · architecture
Workload
The shape of the work itself.
- Operate
- Aggregate
- Segment
- Publish
Data models
The models this workload names.
- SQL
- JSON / documents
- Time series
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 · Operational Analytics operate · aggregate · segment · publish Select a stage
Stage
Operate
The application writes records and documents
SQL · JSON / documents
01
Operate
The application writes records and documents
- SQL
- JSON / documents
02
Aggregate
Reporting aggregates over the same tables
- SQL
03
Segment
Document fields used as filters, not decoration
- JSON / documents
04
Publish
The same numbers serve every consumer
- 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.
No nightly dependency
Reporting availability stops being tied to a batch window.
Fields that filter
Document fields are part of the query surface rather than opaque payload.
Fewer copies
Each copy removed is both a cost and a place where the truth could diverge.
What this is built on.
Operational reporting is a trust problem before it is a performance problem. These are the parts that address it.
- One data layer → Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- One plan per request → A request is planned once against the layer rather than per system, which is where cross-system glue usually accumulates.
- 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.
- Real-time Analytics → Windows and aggregates over data that is still being written.
- Data Infrastructure → One layer for records, documents and time-ordered data, instead of one system per shape.
- Transactional Systems → Application records with consistent reads and writes while reports run against them.
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.
- 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.
- Payments → Authorisations, clearing, settlement, routing and fraud signals.
- Insurance → Policies, claims, risk factors and the documents behind every decision.
- Risk & Fraud → Signals, relationships, cases and decisions across an institution’s data.
- Enterprise → Systems of record, documents, workflow events and reporting in one organisation.
- Retail → Transactions, stock, stores, promotions and customer behaviour.
- E-commerce → Orders, catalogues, inventory, sessions and fulfilment events.
- 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.
- Healthcare → Clinical records, encounters, observations, orders and results.
- Life Sciences → Experiment records, instrument data, sample lineage and publications.
- Pharmaceuticals → Trial data, batch records, regulatory submissions and pharmacovigilance.
- Engineering → Drawings, models, bills of materials, test results and project records.
- Cybersecurity → Telemetry, identity, asset relationships and the cases that follow.
- Observability → Metrics, logs, traces and the service records they describe.
- 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.