Unified data infrastructure
GitHub Let's talk

Engineering

Models, revisions and field data in one place.

Engineering data is revision data: what was specified, what changed, what was measured, and which version is current.

See Digital Twins All of Science & Health

A test result that resolves to the exact drawing revision it was run against.

The story

A test result that resolves to the exact drawing revision it was run against.

Where it starts

Drawings and models

CAD output, drawings, simulations and revision history. It is the first of 4 workloads running in Engineering.

The question it raises

Result against revision

A test measurement resolves to the drawing revision it was taken against.

Why one question is hard

From Requirement to Release

Engineering data moves through 4 stages — Requirement → Design → Verify → Release. The shapes in play are Objects, SQL, Time series, JSON / documents, and answering one question means reading across all of them.

What PLOMID contributes

Engineering is revision control with measurements attached. These are the parts that keep the two together.

The environment

Drawings, models, bills of materials, test results and project records.

Drawings and models are large objects, bills of materials and test plans are structured, and test results are measurements. PLOMID holds the revision chain with the measurements taken against it, so a test result is readable against the exact specification it was run on.

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 · Engineering requirement · design · verify · release Select a stage
Stage

Requirement

Requirements and change requests

JSON / documents · SQL

Workload map Engineering workload map. Every shape on it is a surface of the layer, and each stage names the part of the operation it carries.
  • Objects Large assets with queryable metadata
  • SQL Records, keys and joins
  • Time series Measurements and events in time order
  • JSON / documents Documents and nested objects
The data journey

How engineering 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 test result that resolves to the exact drawing revision it was run against.

Environment

The revision

Drawings, models and their revision history as large objects.

Objects

Where the data goes to work

Questions evidence has to answer.

Each one keeps the measurement with what qualifies it, read from the same layer rather than reconciled later.

Result against revision

A test measurement resolves to the drawing revision it was taken against.

  • JSON / documents
  • SQL

Configuration questions

Assemblies, components and suppliers are read from one layer rather than from exports.

  • Objects
  • JSON / documents

Documentation retrieval

Drawing sets and specifications are found by metadata rather than by folder structure.

  • Time series
  • SQL

Change impact

Change requests are read against the records they affect.

  • SQL
  • Objects
One environment · many workloads

What runs against engineering data.

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

CAD output, drawings, simulations and revision history.

  • Planned once against the layer, not once per store
  • Read beside the records it shares a key with
  • Persisted under one storage contract
Workload architecture

From measurement to evidence.

The work, the shapes it names and the path a request takes — with the protocol beside the measurement.

Engineering · workload architecture
Workloads

What runs against this data.

  • Drawings and models
  • Bills of materials
  • Test and compliance results
  • Project records
Data models

The shapes those workloads read and write.

  • Objects
  • SQL
  • Time series
  • 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
Deployment & residency

Where this data is allowed to run.

Engineering work is often done on isolated networks, so placement and operation are part of the deployment design.

Deployment, residency and control
What you build next

Digital Twins

An asset model that is read from operational data instead of synchronised with it.

If Result against revision is your question, start here.

See Digital Twins 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.