DPP Madera
Proof of concept · results

What we built, and how we checked it works

A small working system with one service for each record (passport, site observations, building logbook) and a simple assembly twin that reads from them. We fed it the full history of an invented building, including five problems planted on purpose, and checked that it kept every part's story straight.

How the pieces fit

Architecture: the passport, site observation and building logbook services each keep their own data; an identity resolver links their identifiers; the assembly twin and the unified view read from them through their public interfaces.
Each service keeps its own data. An identity resolver links the different codes a part carries (QR, batch, model element), so nothing is copied between services.

The eleven tests: all pass

#What we checkedIn plain wordsResult
T1Identity resolutionScan any of a part's codes and you reach all the others.pass
T2No duplicationEach fact lives in one place; the others only point to it.pass
T3Complete historyEvery part's story runs from factory to building without gaps, or the gap is flagged.pass
T4Missing hand-overA part that reached site with no shipping record (planted fault) is caught.pass
T5Conflicting readingsTwo moisture readings that disagree (11.8% and 18.5%) are both kept, with who and when, and sent for review.pass
T6Late recordsAn inspection recorded 48 hours late still lands in the right order.pass
T7Design model clashTwo parts claiming the same element of the design model are caught.pass
T8Assembly pictureThe twin shows the right state for all 20 parts and flags the one installed out of order.pass
T9One view per partOne request returns links to all four records for any part.pass
T10Needs coverageEach of 14 information needs from the literature is either served or honestly marked "not covered yet".pass
T11RepeatableA clean copy and one command reproduce every result.pass

The assembly picture at the end of the replay

18parts inspected
1part installed, awaiting inspection
1part delivered, not yet installed
Chart of the assembly state per level: most parts inspected, one installed, one delivered, with flagged parts outlined.
State of each part by level, with the flagged parts marked. The whole history took 357 requests to feed in.

Questions people actually ask

Five example questions from site and factory staff. With the linked records each one is a single request. The manual look-up counts are our estimate of what it takes today to find the same answer across separate files.

QuestionAnswerRequestsManual look-ups (estimate)
Which level 2 panels are installed but not inspected?P0519
Where is the model element of P06, and is its chain of custody complete?Found on level 2, inspected, custody complete14
Which parts reached site without a complete chain of custody?G02140
Which moisture readings disagree, and who reported them?11.8% and 18.5% on one panel, sent for review140
Which parts were installed out of the planned order?P11140

Where this sits

The project enters at technology readiness level (TRL) 2. This proof of concept is strong evidence for that level and the first step towards TRL 3, planned for month 6 with real data from partner companies. TRL 4 is planned for month 11 and TRL 5 at the end of the project.

The PoC code and the full test report are available to reviewers and partners on request.