Capability · for QA head, owner
The birth certificate for every unit you ship
Genealogy is the structure underneath both trace directions. Walk down from a finished unit to every component inside it, or up from a component to every unit it ended up in.
Serialised children and lot consumption, modelled separately
A serialised sub-assembly contributes its own identity and its own history. A material lot contributes a lot code and a quantity. These are different things and Trace stores them as different things, which is what lets both be indexed.
Multi-level, not one level deep
A sub-assembly built on your line carries its own genealogy, and the finished unit inherits the whole tree. The trace page shows depth, so an auditor can see how far down the record goes.
Bound to the BOM, checked at the station
Each link references the BOM line it satisfies. A component that is not on the BOM for that revision does not get quietly recorded, it gets refused.
Constraints that keep the graph honest
Exactly one of serial or lot is populated. A lot link must carry a quantity. A unit can never be its own component. These are database constraints, so no amount of bad input creates a nonsense tree.
Book a 20-minute line walkthrough
We walk one line, list what each operation should capture, and tell you plainly which of your machines can be read. You get that list whether or not you buy anything.
Where this matters
- Switchgear and electricalsElectrical assemblies fail on components you did not make. When a contactor batch turns out to be bad, the question is which panels have it inside them.
- What a part genealogy record must containThe structure of a genealogy record that answers both trace directions, and the one modelling mistake that quietly breaks your recall query.
- Recall and forward traceGive Trace a component lot code and it returns every finished unit that consumed it, where each one went, and when. An indexed lookup, not an overnight report.