Unified data infrastructure
GitHub Let's talk

Enterprise

The record of the business, joined to the work around it.

A large organisation accumulates systems of record, and the work of answering a simple question becomes a data-integration project. That is the cost this addresses.

See Data Infrastructure All of Enterprise & Commerce

A cross-department question answered as a query, not an integration project.

The story

A cross-department question answered as a query, not an integration project.

Where it starts

Master and reference data

Customers, suppliers, products, sites and organisational structure. It is the first of 4 workloads running in Enterprise.

The question it raises

One question, one query

A cross-department question reads records, documents and events without a pipeline being commissioned first.

Why one question is hard

From Record to Report

Enterprise data moves through 4 stages — Record → Workflow → Document → Report. The shapes in play are SQL, JSON / documents, Objects, Events, and answering one question means reading across all of them.

What PLOMID contributes

Enterprise value is in fewer moving parts. These are the parts of the layer that replace integrations.

  • One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
  • Every client, one layer Applications, AI clients, services and background jobs reach the same data through the same interfaces.
  • One storage contract Every model inherits the same durability and recovery rules instead of one guarantee per system.
The environment

Systems of record, documents, workflow events and reporting in one organisation.

Master data is structured, correspondence and contracts are documents, workflow produces events, and reporting wants all three. PLOMID holds them in one layer, so an operational question is a query rather than a pipeline, and access is decided per team rather than per system.

The data journey

How enterprise data reaches one layer.

Walk the path the data takes, from the environment that produces it to the questions it answers. Select a station, or a shape, to read each step.

A cross-department question answered as a query, not an integration project.

Environment

The organisation

Departments of record, each with its own system and its own copy.

SQL

One environment · many workloads

What runs against enterprise data.

4 workload families over one set of shapes. Choose one to see what it moves and where it lands.

Customers, suppliers, products, sites and organisational structure.

  • Planned once against the layer, not once per store
  • Read beside the records it shares a key with
  • Persisted under one storage contract
Where the data goes to work

Questions customers force you to answer.

Each one spans the event and the record around it, answered from the same layer rather than joined by hand.

One question, one query

A cross-department question reads records, documents and events without a pipeline being commissioned first.

  • SQL

Documentation stays findable

Documents keep queryable metadata, so finding a contract is a predicate rather than a folder memory.

  • Events
  • SQL

Audit trail

Process events are stored in the same layer as the records they change, which makes a trail reconstructable.

  • JSON / documents
  • Objects

Fewer integration surfaces

Consolidating on one layer removes the point-to-point integrations that multiply with each new system.

  • SQL
Workload architecture

From event to record.

The work, the shapes it names and the path a request takes — from the storefront to the warehouse.

Enterprise · workload architecture
Workloads

What runs against this data.

  • Master and reference data
  • Documents and contracts
  • Process events
  • Reporting aggregates
Data models

The shapes those workloads read and write.

  • SQL
  • JSON / documents
  • Objects
  • Events
The layer

One path from a request to the data it names.

  • Planning Predicates narrow the work before it runs
  • Execution Records, fields and windows answered together
  • Transactions Readers and writers do not block each other
Surfaces

How the work reaches the layer.

  • SQL surface The query language the layer is documented in
  • Applications Services and jobs writing and reading as they run
  • Analytics & AI clients The same layer, the same access path
Data models in play

The shapes, in one layer.

4 shapes carry this domain. Choose a stage to read the operation, or a shape to see every stage that handles it.

PLOMID · Enterprise record · workflow · document · report Select a stage
Stage

Record

Master and reference data in one place

SQL

Workload map Enterprise workload map. Every shape on it is a surface of the layer, and each stage names the part of the operation it carries.
  • SQL Records, keys and joins
  • JSON / documents Documents and nested objects
  • Objects Large assets with queryable metadata
  • Events Operational events as they happen
Deployment & residency

Where this data is allowed to run.

Large organisations operate their own systems, so deployment is a governance decision as much as a technical one.

Deployment, residency and control
What you build next

Data Infrastructure

One layer for records, documents and time-ordered data, instead of one system per shape.

If One question, one query is your question, start here.

See Data Infrastructure Every solution
Next

Where to go next

Solutions The workload answers this industry leans on, with their models and status. Platform The data models in the product today, and the ones extending the layer. Architecture How a request is planned, executed and persisted once it reaches the layer.