Published
As-built record of a serialized unit
EM-MFG-04 · em-mfg-04
Identify a serialized unit's original and subsequent configurations at a stated effective date so that recall, service and warranty decisions use the applicable actual configuration.
Enterprise profiles Enterprise subject EnterpriseMFG
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Built configuration This bundle records the original actual configuration of one serialized unit.
Installed components
This layer identifies installed content and its relationship to the planned structure.
Component positions
This finding identifies the unit's original installed content and position references.
- Which component serials, lots and software versions were installed in this unit at its recorded build completion date?
- Which planned bill of materials version was this unit built against?
- What unit item identifier, unit serial number and position identifier identify this installed position, and what planned position or approved addition does it reference?
Build deviations
This finding records departures from the planned configuration and their approvals.
- What departure from the planned bill of materials does this build deviation record, and which approval authorizes it?
Life after build This bundle preserves subsequent configurations without overwriting the original build.
Changes in service
This layer records effective configuration changes and supporting evidence.
Replacements
This finding preserves component changes and the resulting as-maintained configurations.
- Which components were removed and installed in this replacement event, when did it take effect, who performed it and why?
- Where does this replacement record reference the history of its removed component?
- What installed content and effective interval does this as-maintained configuration record declare?
Traceability references
This finding links one unit to evidence supporting its configuration.
- Which production order and inspection records support this unit's original as-built configuration?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseMFG
- Industry
- Manufacturing
- Tags
- EM-MFG-04W-INDsubjectAsBuiltRecordInstalledComponentConfigurationDeviationComponentReplacementSoftwareInstallation
What it is Filled
The original built configuration of one serialized unit and its subsequent as-maintained configurations, recording installed component serials, lots, software versions, approved deviations and replacements with effective dates.
Why it exists Filled
Identify a serialized unit's original and subsequent configurations at a stated effective date so that recall, service and warranty decisions use the applicable actual configuration.
Distinguishing features Filled
- The record describes one physical unit, not the product design.
- It references the planned bill of materials version instead of copying it.
- The original as-built configuration remains distinguishable from subsequent as-maintained configurations by effective dates.
- Replacements preserve removed component history and the configurations in which those components were installed.
- Lot-level genealogy is held by the inventory contour, and this contour holds the per-unit structure.
- Approved additions may have unit-specific position identifiers without a corresponding planned position.
What robots and AI may and may not do Filled
Must not
- Edit the original build record to hide a later replacement.
- Approve a configuration deviation.
- Present the planned bill of materials as the as-built structure.
Only with a human decision
- A responsible quality or engineering person must approve configuration deviations.
- A recall scope based on as-built data must be approved by a responsible person.
May
- Answer which units contain a given component lot or serial.
- Compare a unit's structure with its planned bill of materials.
- Draft a replacement record for technician confirmation.
Moral aspects Filled
- Incomplete as-built records can leave affected units in use after a recall.
- Service records may reveal where and how a customer uses a product.
Who is affected
- Owners and users of the units
- Service technicians
- Suppliers of components
Owners Filled
Steward
The configuration manager who answers for the accuracy of unit structures.
Master systems
- Manufacturing execution system
- Product lifecycle management system
- Field service management system
Links to other meta-models Filled
neighbor
- EM-OPS-04
- EM-OPS-05
- EM-OPS-03
- EM-MFG-01
- EM-MFG-06
- EM-TEC-01
references
- WM-OBJ-012 - conceptual-candidate
- WM-OBJ-019 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A unit is identified by its item identifier and serial number.
- Each installed position is identified by the unit item identifier, unit serial number and a position identifier.
- A position references either a planned position or an approved addition without a planned counterpart.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- Records distinguish the original as-built configuration from subsequent as-maintained configurations using effective dates.
- An actual unit configuration must be distinguished from a design bill of materials and a lot genealogy record.
Capabilities and actions required Filled
- The contour supports recall targeting, warranty analysis and service planning per unit.
- Retrieval can identify delivered units containing a specified component lot or serial at a stated effective date.
- Retrieval can identify units with a specified software version installed at a stated effective date.
Hazards and failure modes required Filled
- A missing replacement record can leave a defective component in a unit believed to be safe.
- Copying the planned structure into the record creates false traceability.
- Confusing original and subsequent configurations can misidentify affected units.
Standards and interfaces optional Filled
- The Industrial Digital Twin Association publishes the Asset Administration Shell specifications for individual assets.
- The International Organization for Standardization publishes ISO 10303 for exchanging product data, including product structure and configuration data.
Context of use required Filled
- The contour is used for serialized products such as machines, vehicles, devices and medical equipment.
- Applicable sector and jurisdiction requirements determine the configuration evidence that must be retained.
Sources Filled
- IDTA Asset Administration Shell: digital twin of an individual asset
- ISO 10303 (STEP): product structure and configuration
- Device history record practice in regulated manufacturing
- IDTA Asset Administration Shell specifications - Checked live (HTTP 200) on 2026-10-21.
- 21 CFR Part 820, medical device quality management system regulation (eCFR) - Checked live (HTTP 200) on 2026-10-21.
Open 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?
- Settle the boundary and the reuse, extend or new decision against the current specifications.
- Confirm the semantic crosswalk, rights and source mastership.
- Choose immutable references and run fixture checks before claiming publication readiness.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-mfg-04/brief.json, ver-cy/world-models/card-supplements/em-mfg-04.json