The life of a timber part from press to inspection, drawn as a BPMN process the way it would sit in a workflow engine such as Camunda. Pick a part to see the path it actually took, then click any step to see how its data is captured and which record it lands in.
DPPProduct passportIdentity and custody: made, shipped, received.
EPMSite observationsObservations: QA, moisture, lift, survey, fixings, inspection. Parts only, never people.
DBLBuilding logbookAs-built: which model element and where.
DTwAssembly twinReads the three records through the link service to show progress.
asset-path.bpmn · process "CLT component, factory to as-built"
Tools and techniques: how each step is captured and shown
The "capture" column is the intended set-up for the funded project. In this proof of concept every input is simulated by a seeded generator, so the same tests can be re-run anywhere.
Step
Captured with
Identifier and format
Lands in
Shown in
DTwAssembly twin
How the records are joined
The QR code holds one ID per part, in GS1 Digital Link style: product code plus serial.
A link service keeps a graph of IDs: part serial, batch, model element (IFC GUID) and building location, each with dates of validity.
When two sources contradict each other (P07 and P08 claiming one model element), the link is kept as disputed, never overwritten.
The twin and the web views ask the link service, then fetch from each record. No record copies another.
What has been tested
Proof of concept, synthetic data
One invented building, 20 parts, 179 records, 5 planted problems.
11 automated tests (T1 to T11) check that each problem is found and each stakeholder question is answered. All 11 pass.
Re-run with one command; reproduced on a second machine.
This supports TRL 2. Re-running it with associates' real data at month 6 is the step towards TRL 3.