Unified data infrastructure
GitHub Let's talk

Supply Chain

Every hop of a shipment, recordable and queryable.

A supply chain is a graph of commitments: who owes what, to whom, by when, and what has actually moved.

See Operational Analytics All of Enterprise & Commerce

A supplier disruption traced to the commitments it affects, in one traversal.

The story

A supplier disruption traced to the commitments it affects, in one traversal.

Where it starts

Orders and commitments

Purchase orders, confirmations, schedules and terms. It is the first of 4 workloads running in Supply Chain.

The question it raises

Disruption impact

A supplier problem resolves to the orders and movements it affects in one traversal of relationships.

Why one question is hard

From Source to Deliver

Supply Chain data moves through 5 stages — Source → Order → Move → Clear → Deliver. The shapes in play are SQL, Events, JSON / documents, Objects, Graph, and answering one question means reading across all of them.

What PLOMID contributes

Supply questions are relationship questions with documents attached. These are the parts that hold them.

  • One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
  • Relationships held as data Edges expressed directly remove the reconstruction that happens at query time when relationships live in a join.
  • Documents beside rows Fields that keep changing shape stay queryable instead of being exported into a separate document store.
The environment

Suppliers, orders, inventory, movements and the documents between them.

Purchase orders and inventory are records, movements are events, and contracts, certificates and customs paperwork are documents. PLOMID holds them together, so a disruption question can be answered from the commitments rather than from a reconciliation of partners’ reports.

The data journey

How supply chain 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 supplier disruption traced to the commitments it affects, in one traversal.

Environment

The supplier

Suppliers, sites and qualification status as records with certificates.

SQL · Objects

One environment · many workloads

What runs against supply chain data.

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

Purchase orders, confirmations, schedules and terms.

  • 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.

Disruption impact

A supplier problem resolves to the orders and movements it affects in one traversal of relationships.

  • SQL
  • Objects

Commitment versus reality

Orders and receipts are read from the same layer, so the gap is measured rather than estimated.

  • SQL

Documentation on the record

Certificates and customs papers stay queryable against the shipment they belong to.

  • Events
  • SQL

Qualification evidence

Supplier qualification and inspection documents attach to the partner record.

  • JSON / documents
  • Objects
Workload architecture

From event to record.

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

Supply Chain · workload architecture
Workloads

What runs against this data.

  • Orders and commitments
  • Inventory and movements
  • Partner records
  • Trade documents
Data models

The shapes those workloads read and write.

  • SQL
  • Events
  • JSON / documents
  • Objects
  • Graph
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.

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

PLOMID · Supply Chain source · order · move · clear · deliver Select a stage
Stage

Source

Supplier records and qualification documents

SQL · Objects

Workload map Supply Chain 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
  • Events Operational events as they happen
  • JSON / documents Documents and nested objects
  • Objects Large assets with queryable metadata
  • Graph Relationships and traversal
Deployment & residency

Where this data is allowed to run.

Partners and sites are on different networks, so reads are distributed while the record stays authoritative.

Deployment, residency and control
What you build next

Operational Analytics

Reporting that reads the operational source instead of a copy of it.

If Disruption impact is your question, start here.

See Operational Analytics 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.