Unified data infrastructure
GitHub Let's talk

Logistics

Routes, shipments and events on one map.

Logistics is a stream of events attached to a movement: a shipment exists as a record, but it is understood through its scans, its positions and its exceptions.

See Operational Analytics All of Enterprise & Commerce

A shipment understood through its scans, positions and exceptions — in one query.

The story

A shipment understood through its scans, positions and exceptions — in one query.

Where it starts

Shipment records

Consignments, parcels, parties and service levels. It is the first of 4 workloads running in Logistics.

The question it raises

Shipment in one request

The record, its scans and its movement history read together instead of via a tracking cache.

Why one question is hard

From Plan to Deliver

Logistics data moves through 4 stages — Plan → Move → Handle → Deliver. The shapes in play are SQL, Time series, Events, Geo, JSON / documents, and answering one question means reading across all of them.

What PLOMID contributes

A movement is a record and a stream at once. These are the parts that keep the two in step.

  • Time-ordered storage Measurements and events are stored beside the records and documents they describe, so history and current state agree.
  • 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.
The environment

Shipments, routes, positions, scans and delivery events.

Shipments and consignments are records, positions are time-ordered with a location dimension, and pickups, scans and exceptions are events. PLOMID holds all three in one layer, so a customer question resolves against the operational record rather than against a tracking service’s cache.

The data journey

How logistics 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 shipment understood through its scans, positions and exceptions — in one query.

Environment

The consignment

Shipments and parcels as records with parties and service levels.

SQL

One environment · many workloads

What runs against logistics data.

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

Consignments, parcels, parties and service levels.

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

Shipment in one request

The record, its scans and its movement history read together instead of via a tracking cache.

  • SQL
  • JSON / documents

Exception analysis

Delays and damage events are read against routes and capacity rather than in isolation.

  • Time series
  • Geo

Operational reporting

Service-level aggregates compute over the same events that drive the operations view.

  • Events
  • SQL

Proof of delivery as data

Delivery documents keep queryable metadata attached to the shipment record.

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

Logistics · workload architecture
Workloads

What runs against this data.

  • Shipment records
  • Position and telemetry
  • Scan and exception events
  • Route and capacity data
Data models

The shapes those workloads read and write.

  • SQL
  • Time series
  • Events
  • Geo
  • JSON / documents
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 · Logistics plan · move · handle · deliver Select a stage
Stage

Plan

Routes, stops and capacity records

SQL · JSON / documents

Workload map Logistics 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
  • Time series Measurements and events in time order
  • Events Operational events as they happen
  • Geo Location as a queryable dimension
  • JSON / documents Documents and nested objects
Deployment & residency

Where this data is allowed to run.

Vehicles and depots submit events intermittently, so the write path has to tolerate delay and duplication.

Deployment, residency and control
What you build next

Operational Analytics

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

If Shipment in one request 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.