Skip to content
Terreaux

Mfg / Provena

Every part can show
where it came from.

Provenance and traceability for aerospace and advanced manufacturing. For any part, Provena records who did what, under which procedure revision, with what evidence, and what else is affected.

ACT-0002Actuator assembly
  1. H-0142HousingNCR-0001 · reworked
    AL-24-0412Al 7075 · heat NA-55120 · Northline AluminumCoC · mill cert
  2. S-0302Shaft
    HS-8821317-4PH heatMill cert
  3. R-0202Rod end
    CT-4471Ti-6Al-4V heatMill cert
  4. BRG ×2Bearings
    BRG-24-0425Purchased lotCoC
GENEALOGY · ACT-0002
Demo data · Meridian Aerostructures

Six questions an auditor asks, answered from one record.

Today they are split across travellers, spreadsheets, certificate folders and someone’s memory.

Where did it come from?
Supplier lots, heats and certificates.
What happened to it?
Every operation, inspection and rework, in order.
Who did it?
Sign-offs tied to a named person and role.
Under which revision?
The procedure revision pinned at the moment of work.
With what evidence?
CoCs, mill certs, CMM results and photos, attached.
What else is affected?
Everything downstream of a suspect lot.

Upstream, through a quality event, and downstream.

01

Trace upstream

Open a finished assembly and follow its genealogy to the material heat, through every operation, machine, tool and sign-off.

02

Keep the failures

A failed inspection opens an NCR. Rework and reinspection are added; the original result is never overwritten.

03

Contain downstream

Mark a lot suspect and Provena lists every affected part and assembly, shipped or not, and raises containment on the rest.

One suspect lot. Every part it reached.

A supplier flags stainless lot SS-24-0418. Provena follows it through a lot split into six shafts, then into three actuators — one already delivered.

Suspect lot

SS-24-0418split → SS-24-0418-B

Shafts

S-0301S-0302S-0303S-0304S-0305S-0306

Assemblies

ACT-0001 shipped · Aurelian AircraftACT-0002 containment raisedACT-0003 containment raised
Demo data · the failed CMM result on H-0142 stays on record alongside its rework

Built for regulated shop floors.

Ledger

Hash-chained history

Custody and quality events are append-only. Recompute the chain and confirm nothing was edited after the fact.

Procedures

Pinned revisions

Operations record the work instruction revision in force when the work was done, not the one current today.

Sign-off

Separation of duties

Operators record work; only quality roles can disposition it. The API enforces it, not just the screen.

Shop floor

Offline iOS and Android

Scan a part tag, record an operation and attach a photo without signal. Records sync on reconnect.

Isolation

One tenant per organization

Row-level security keeps each organization’s parts out of another’s search, graph and downloads.

Integration

An open API contract

Every request and response is described in OpenAPI 3.1, so ERP, MES and inspection systems feed the same record.

Questions

What to expect.

Are sign-offs legal electronic signatures?

No. They are attributable confirmations by a named, authenticated user with a PIN, not qualified electronic signatures.

Do operators need a connection on the floor?

No. The mobile apps queue work locally and sync it when the device reconnects.

Can we start with one programme?

Yes. A single part family or assembly line is a good first scope, set up with your real lot and part numbering.

Bring a part number you can’t trace today.

Discuss a programme
We’ll walk through how its genealogy, quality events and impact would look in Provena.