EM-MFG-04 · Subject model · W-IND
As-built record of a serialized unit
The actual structure of one serialized unit: which component serials, lots and software versions were installed, deviations from the planned bill of materials, and later replacements. Lot genealogy and the planned bill of materials belong to neighboring contours.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- AsBuiltRecord
- InstalledComponent
- ConfigurationDeviation
- ComponentReplacement
- SoftwareInstallation
Deep research questions
- How is the as-built structure linked to the planned bill of materials version without copying it?
- How are later replacements in service recorded without rewriting the original build?
- Which deviations need an approved concession before shipment?
Verifiable invariants
- Each installed position is held by at most one component at a time
- A replacement keeps the history of the removed component
- A deviation from the planned bill of materials references an approval
End-to-end acceptance scenario
For a synthetic serialized device, record the build with one approved substitute, replace a module in service, and answer which delivered units contain a given component lot.
Negative case
The planned bill of materials is shown as the structure of a delivered unit, so a recall misses units built with a substitute component.
Approaches to compare
- IDTA Asset Administration Shell: digital twin of an individual asset
- ISO 10303 (STEP): product structure and configuration
- Device history record practice in regulated manufacturing
Candidates in the live catalogue
- WM-OBJ-012 · Assembly Instance / As-built BOM · 1.0.0 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-OBJ-019 · Component Type / Engineering BOM · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.