One query surface
A question is asked of the layer once instead of once per system.
Enterprise Search
Every document under one index, with its structure.
An organisation’s knowledge is held in whatever system happened to be adopted at the time, which is why search becomes a federation problem.
One question, every system, one surface — with access respected on the way through.
One search surface over records, documents, events and their metadata.
Search has to reach records, documents, attachments and events, and it has to respect access. PLOMID keeps the material in one layer, so search is a query rather than a federation across indexes, with similarity retrieval as an additional access path once it lands.
One question, every system, one surface — with access respected on the way through.
Environment
The estate
Records, documents, attachments and events spread across systems by history.
SQL · JSON / documents · Objects
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.
- JSON / documents Documents and nested objects
- SQL Records, keys and joins
- Objects Large assets with queryable metadata
- Vector Similarity and semantic retrieval
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.
Enterprise Search · architecture
Workload
The shape of the work itself.
- Index
- Match
- Rank
- Return
Data models
The models this workload names.
- JSON / documents
- SQL
- Objects
- Vector
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 · Enterprise Search index · match · rank · return Select a stage
Stage
Index
Documents, fields and attachments live in the layer
JSON / documents · Objects
01
Index
Documents, fields and attachments live in the layer
- JSON / documents
- Objects
02
Match
Structured predicates and text narrowed together
- SQL
- JSON / documents
03
Rank
Similarity where the source supports it
- Vector
04
Return
Results carry the record they came from
- 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.
Access respected
Results are scoped by the same rules as the data itself.
Attachments findable
Documents are found by queryable metadata rather than by folder memory.
Fewer places to maintain
Retiring a separate index removes a sync job and a second copy.
What this is built on.
Search is judged on coverage and access. These are the parts of the layer that provide both.
- Documents beside rows → Fields that keep changing shape stay queryable instead of being exported into a separate document store.
- Retrieval as an access path → Similarity search arrives as another way into the same data rather than a second copy to keep in step.
- 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.
- Banking → Accounts, transactions, counterparties and the relationships between them.
- Insurance → Policies, claims, risk factors and the documents behind every decision.
- Enterprise → Systems of record, documents, workflow events and reporting in one organisation.
- Retail → Transactions, stock, stores, promotions and customer behaviour.
- Healthcare → Clinical records, encounters, observations, orders and results.
- Government → Registers, case files, service events and reporting obligations.