Documents become data
Fields are queried as columns rather than read by a person.
Document Intelligence
Documents that stay queryable where they live.
Documents are where organisations keep their most consequential information and their least queryable information at the same time.
A document that stops being a file and becomes a row with a payload.
Documents, their fields and their attachments treated as queryable data.
Contracts, reports, submissions and correspondence are read for specific fields, kept for evidence, and searched for meaning. PLOMID stores documents and their extracted fields in the same layer as the records they describe, so a document is a row with a payload rather than a file in a directory.
A document that stops being a file and becomes a row with a payload.
Environment
The document
Contracts, reports, submissions and correspondence arriving as files.
Objects · 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.
- JSON / documents Documents and nested objects
- Objects Large assets with queryable metadata
- Vector Similarity and semantic retrieval
- SQL Records, keys and joins
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.
Document Intelligence · architecture
Workload
The shape of the work itself.
- Capture
- Structure
- Retrieve
- Attach
Data models
The models this workload names.
- JSON / documents
- Objects
- Vector
- SQL
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 · Document Intelligence capture · structure · retrieve · attach Select a stage
Stage
Capture
Documents and attachments with metadata
Objects · JSON / documents
01
Capture
Documents and attachments with metadata
- Objects
- JSON / documents
02
Structure
Fields that matter made queryable
- JSON / documents
- SQL
03
Retrieve
Similarity for what structure misses
- Vector
04
Attach
Documents held against the record they concern
- 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.
Evidence stays attached
The paper trail sits beside the record it supports.
Search that reaches inside
Similarity retrieval covers the parts a schema cannot describe.
One lifecycle
Retention and access apply to documents and records in one place.
What this is built on.
Document workloads are decided by how much structure you can bring to the payload. These are the parts that help.
- Documents beside rows → Fields that keep changing shape stay queryable instead of being exported into a separate document store.
- Objects with queryable metadata → Large assets are found by a query against their metadata rather than by a naming convention.
- 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 storage contract → Every model inherits the same durability and recovery rules instead of one guarantee per system.
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.
- Aerospace → Certification documents, test data, flight telemetry and maintenance records.
- Insurance → Policies, claims, risk factors and the documents behind every decision.
- 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.
- Scientific Research → Instrument output, simulation results, reference material and datasets.
- Engineering → Drawings, models, bills of materials, test results and project records.
- Government → Registers, case files, service events and reporting obligations.