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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 9 questions
Item definitions The product class, SKU and engineering revisions as separate records.
Item and revision
Design identity apart from sales identity.
Separate identities
Drawing, SKU and serial instance kept apart.
- Is this record a design item, a SKU or a serial instance?
- Which engineering revision does this SKU currently ship?
Revision applicability
Which batches or serial ranges a revision applies to.
- To which batches or serial ranges does this revision apply?
- When did the revision take effect?
Composition Bills of materials, lines and substitutions.
Bills of materials
Typed and versioned bills with their lines.
BOM type and version
Engineering and manufacturing bills reconciled.
- Is this an engineering or a manufacturing bill, and which version?
- Where do the engineering and manufacturing compositions differ, and why?
Lines and substitutions
Quantities with units and allowed alternatives.
- Does every line state a quantity with a unit?
- Which substitutions are allowed, and for which range?
- Which firmware release belongs with this revision?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseOPS
- Industry
- Cross-industry
- Tags
- EM-OPS-04W3subjectItemDefinitionSKUEngineeringRevisionBillOfMaterialsBOMLine
What it is Filled
Product class, SKU, engineering revision, EBOM/MBOM, components and allowed substitutions. The software image and the serial instance have separate identities.
Why it exists Filled
Product class, SKU, engineering revision, EBOM/MBOM, components and allowed substitutions. The software image and the serial instance have separate identities.
Distinguishing features Filled
- A design item, a SKU and a serial instance are three records with separate identities.
- Every bill of materials has a type and a version, and every line a quantity with a unit.
- A substitution is allowed only within a stated range of applicability.
- Software images such as firmware are versioned on their own and linked to hardware, not merged with it.
What robots and AI may and may not do Filled
Must not
- Use one Product record to denote a drawing, a SKU and a serial number at once.
- Apply a substitution outside its range of applicability.
- Edit a released bill of materials in place instead of issuing a new version.
- Record a quantity without a unit of measure.
Only with a human decision
- Releasing a new engineering revision.
- Approving a substitution of a safety-relevant component.
May
- Trace a manufactured instance to its revision, bill version and firmware release.
- Compare engineering and manufacturing bills and list differences.
- Flag lines without units and substitutions without a range.
Moral aspects Filled
- Wrong composition records can put unsafe or non-compliant products on the market.
- Traceability to revision and firmware matters for security fixes that protect users.
Who is affected
- Users of the product
- Engineering and manufacturing teams
- Component suppliers
Owners Filled
Steward
The head of operations who answers for physical assets, products and material flows.
Master systems
- Business process management suite
- ERP
- Warehouse management system
- Product lifecycle management system
- Enterprise asset management system
Links to other meta-models Filled
neighbor
- EM-OPS-05
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A design item by item number and revision; a SKU by its GTIN or internal code; an instance by serial number.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record with item number, revision, bill type and versioned lines with units.
- Often confused with a catalogue product page or a single serial record.
Capabilities and actions required Filled
- Instances can be traced to their revision, composition and firmware.
- Engineering changes can be scoped to batches or serial ranges.
Hazards and failure modes required Filled
- Mixed identities that make recalls and fixes impossible to scope.
- Unapproved substitutions in safety-relevant assemblies.
Standards and interfaces required Filled
- ISO 10303 STEP for exchange of product design data.
- ISO 10007 for configuration management.
- GS1 GTIN for trade item identification.
Context of use required Filled
- Used in product engineering, manufacturing and change control.
- Relevant for products that combine hardware revisions with firmware releases.
Sources Filled
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
- IDTA Asset Administration Shell specifications - Checked live (HTTP 200) on 2026-10-07.
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-ops-04/brief.json, ver-cy/world-models/card-supplements/em-ops-04.json
Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.