Assembly Instance / As-built BOM
One serialized assembly with the record of exactly which components went into it.
Bundle → Layer → Finding → Questions Filled
3 bundles · 4 layers · 5 findings · 10 questions
Unit identity Which built unit this is.
Serialized unit
The unit's identity and the design it was built to.
Unit and design reference
The unit's serial number and the product type, configuration and design revision it was built to.
- Which serial number identifies the unit, and who assigned it?
- Which product type, configuration and design revision was the unit built to?
Built composition What actually went into the unit.
As-built structure
The tree of installed component instances.
Installed components
Each installed component with its position, part number and serial or lot.
- Which part number and serial or lot is installed at each position?
- Does each installed part match the approved design or an approved deviation?
Software and firmware
The software and firmware versions loaded at build.
- Which software and firmware versions were loaded, and are they approved for this configuration?
- Has any version changed since the unit left production?
Build evidence
Records that show how the unit was built and tested.
Deviations and tests
Approved deviations, nonconformances and final test results.
- Which deviations or concessions were approved for this unit, and by whom?
- Which final tests did the unit pass, and where are the results?
Configuration over life How the unit changes after build.
Changes in service
Replacements, upgrades and modifications after delivery.
Part replacement
A component removed and another installed, with the reason.
- Which component was removed, which was installed, and on what date?
- Was the replacement part of an approved type for this unit?
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.OBJ.ASM
- Domain
- PHY.OBJ.ASM
- Industry
- Cross-industry
- Tags
- assemblyinstanceasbuiltbomphy.obj.asm
What it is Filled
An assembly instance with its as-built bill of materials is one physical, serialized product or subassembly together with the record of exactly which component instances, lots and software versions went into it as it was built. It covers the as-built and as-maintained configuration of one unit, not the engineering bill of materials for the product type or the stock of loose parts.
In scope
- Unit-to-master binding and external design baseline reference
- Installed serialized components, lot quantities and incorporation evidence
- As-built snapshots, firmware bindings, discrepancy and test references
- Local configuration change history and time-qualified trace views
Out of scope
- Engineering or manufacturing BOM authoring and product-type lifecycle
- Component master ownership, stock balances, logistics containment and physical assembly or maintenance execution
- Software release authoring, full asset lifecycle, legal title, release authorization or recall decisions
- Universal sector certification, actuation and controlled-subject operational detail
Why it exists Filled
One serialized assembly with the record of exactly which components went into it.
Distinguishing features Filled
- It records one built unit, while the engineering bill of materials describes the design for all units of a type.
- Component identity is by serial or lot of each installed part, not only by part number.
- The as-built record is the starting point for the as-maintained record, which changes with every replacement.
- Distinct from inventory stock, which counts parts not yet installed.
What robots and AI may and may not do Filled
Must not
- Change the as-built record to hide a nonconformance or an unapproved part.
- Record a part as installed without evidence from the build or maintenance record.
- Approve a deviation or concession from the design.
- Disclose a customer's unit configuration to third parties without a grant.
- Delete records of removed components that are needed for traceability.
Only with a human decision
- Approving deviations and concessions from the design.
- Releasing a unit for delivery or return to service after a configuration change.
- Deciding the scope of a recall based on as-built traceability.
May
- Trace which units contain a given component lot for a recall or investigation.
- Compare an as-built structure with its design and flag mismatches.
- Record replacements and upgrades with dates, parts and reasons.
- Report the current configuration of a unit to an entitled requester.
Moral aspects Filled
- Accurate as-built records decide who is reached in a safety recall and who is left exposed.
- Falsified traceability can hide counterfeit or substandard parts in safety-critical products.
- Unit records tied to an owner can reveal personal or commercial information.
Who is affected
- Owners and users of the unit
- Manufacturers and suppliers
- Maintenance organizations
- Regulators and investigators
Owners Filled
Steward
The manufacturer answers for the as-built record at delivery, and the owner or maintenance organization answers for changes during service.
Roles
- Assembly record steward
- Resolve unit identity and own local record quality and profile selection.
- Build or maintenance recorder
- Submit evidenced configuration assertions within assigned scope; no self-granted release authority.
- Configuration reviewer
- Resolve discrepancies and approve local baseline acceptance within a documented mandate.
- Evidence custodian
- Maintain record revisions, access, integrity and governed disposition.
- Entitled consumer
- Use scoped trace reports with their coverage and uncertainty limits.
Master systems
- Manufacturing execution system
- Product lifecycle management system
- Maintenance and configuration management system
Links to other meta-models Filled
composes
- WM-OBJ-001 - Honor the registry candidate: reference independently mastered physical component instances through local installation occurrences. No cascading ownership, lifecycle or deletion; lot quantity may represent nonserialized content. Runtime binding needs a pinned profile.
references
- WM-OBJ-019 - Proposed engineering BOM and component type baseline link; actual installation evidence remains here and design authority remains external.
- WM-OBJ-022 - Proposed asset lifecycle projection consumes configuration history without this model owning work, custody, valuation or asset lifecycle execution.
- wm-obj-019-component-type-engineering-bom - The unit is built to an engineering bill of materials.
aligned
- GS1 EPCIS 2.0 - Optional event mapping distinguishes durable installation association, temporary logistics aggregation and transformed inputs; not implemented conformance.
- CycloneDX 1.7 - Optional hardware/software BOM projection with explicit identity, time and completeness loss report. An external BOM document is not a physical unit.
- W3C PROV-O and SOSA - Optional evidence and observation vocabulary mappings; provenance and observation do not prove installation or product acceptance.
neighbor
- WM-OBJ-001 Physical Item Instance - Local installation edges compose independently mastered items. The unit identity links to its physical master; this record does not own child identity or lifecycle.
- WM-OBJ-019 Component Type / Engineering BOM - Reusable intended composition is external; instance-specific actual membership and deviations are local references and assertions.
- WM-OBJ-022 Asset Lifecycle Record - The wider asset projection consumes configuration evidence. Work execution, ownership and asset-wide lifecycle remain external.
- Logistics containment and inventory - Temporary containment and stock quantity are not installation membership; consumed inputs require a different relation from retained components.
- Software BOM and release - A document identifier or software version does not identify the physical unit or prove that a version was loaded.
extends
- wm-obj-001-physical-item-instance - An assembly instance is a physical item with an installed structure.
related
- wm-obj-022-asset-lifecycle-record - Changes during service continue the configuration record.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A unit is identified by the manufacturer's serial number together with its part number and design revision.
- Installed components are identified by part number and serial number or lot code.
- Positions in the structure can be named by reference designations under IEC 81346.
Direct properties required Filled
- Mass of the assembled unit in kilograms, with the measured configuration.
- Overall dimensions in millimetres or metres, as measured or declared.
- Operating hours or cycles since build, from the unit's counter or log.
- Final test measurements in the units of the test specification, with test conditions.
Recognition required Filled
- A unit is recognized by its nameplate or data plate with serial and part number, and by labels on installed components.
- Easily confused with another unit of the same type when nameplates are missing or replaced.
Capabilities and actions required Filled
- Units can be traced from component lots to finished serials and back.
- Their configuration can be compared with design and updated on every replacement.
Hazards and failure modes required Filled
- Installation of counterfeit or wrong-revision parts that the record does not reveal.
- Missed recall when as-built traceability is incomplete.
- Failure in service after an unrecorded modification.
Standards and interfaces required Filled
- ISO 10303 (STEP), including AP242, for product structure exchange.
- IEC 81346 for reference designations.
- GS1 identifiers such as GTIN with serial number for traded units.
Context of use required Filled
- Used in aerospace, automotive, rail, medical devices, energy equipment and other regulated manufacturing.
- Sector regulation often requires as-built traceability for safety-critical units.
Sources Filled
- EPCIS Standard - GS1
- Systems Engineering Handbook - 6.5 Configuration Management - National Aeronautics and Space Administration
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Semantic Sensor Network Ontology - World Wide Web Consortium
- Hardware Components use case - OWASP Foundation
- EPC Tag Data Standard - GS1
- CycloneDX v1.7 JSON Reference - OWASP Foundation
- ISO 10303-242 Industrial automation systems and integration - Product data representation and exchange - Managed model-based 3D engineering (ISO)
- IEC 81346 Industrial systems, installations and equipment and industrial products - Structuring principles and reference designations (IEC)
- ISO 9001 Quality management systems - Requirements, identification and traceability (ISO)
Open questions
- Complete direct source checks and exact version, licensing and applicability verification, including the full CycloneDX schema.
- Develop adopting profiles and executable fixtures for duplicate serial scopes, installation cycles, conflicting effective intervals, unknown lots, consumed inputs, partial observations, firmware changes, late corrections, rebuild identity and governed disposal.
- Test pinned neighbor bindings and exchange mappings with explicit data-loss and trace-coverage reports.
- Restore independent external review before canonical or publishable-draft promotion.
- Executable nested instance schemas, required-field profiles, quantity/interval constraints and acceptance fixtures are not supplied.
- Pinned neighbor versions and tested EPCIS, CycloneDX, PROV-O and SOSA mappings remain open.
- Sector-specific release, retention, identity continuity and traceability requirements require qualified adoption review.
- No direct HTTP status or body hash measured locally; source version verification incomplete and full CycloneDX JSON page unavailable to browser retrieval.
- Independent external review is absent; Claude and Grok skipped under the owner-authorized waiver.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-obj-012-assembly-instance-as-built-bom/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-012-assembly-instance-as-built-bom.json