EM-OPS-04 · Subject model · W3
Product, design and bill of materials
Product class, SKU, engineering revision, EBOM/MBOM, components and allowed substitutions. The software image and the serial instance have separate identities.
Partially published; research continues
Claude: complete-initial-study-plus-single-frozen-audit-remediated; Grok: complete-reconciled-visible-response-hidden-coordination-and-sources-excluded.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- ItemDefinition
- SKU
- EngineeringRevision
- BillOfMaterials
- BOMLine
- SubstitutionRule
Deep research questions
- How to reconcile the engineering and manufacturing composition?
- How to define the applicability of a revision to a batch?
- How to link firmware to a device without mixing types?
Verifiable invariants
- A BOM has a type and a version
- A quantity includes a unit
- A substitution requires an applicability range
End-to-end acceptance scenario
A product with two revisions, an alternative component and a firmware release is traced down to the manufactured instance.
Negative case
A single Product record simultaneously denotes a drawing, a SKU and a serial number.
Approaches to compare
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
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.