{"schema":"https://ver.cy/schemas/card/1.0.0","id":"EM-MFG-04","code":"em-mfg-04","url":"https://ver.cy/models/em-mfg-04/","name":"As-built record of a serialized unit","alternateNames":[],"kind":"enterprise-contour","status":"published","version":"research-checkpoint","language":"en","classifiers":{"family":"Enterprise profiles","category":"Enterprise subject","entryKind":"subject","plane":"","domain":["Enterprise","MFG"],"industry":["Manufacturing"],"navPath":"","tags":["EM-MFG-04","W-IND","subject","AsBuiltRecord","InstalledComponent","ConfigurationDeviation","ComponentReplacement","SoftwareInstallation"],"facets":{}},"whatItIs":"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.","purpose":"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.","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"built-configuration","name":"Built configuration","description":"This bundle records the original actual configuration of one serialized unit.","layers":[{"id":"installed-components","name":"Installed components","description":"This layer identifies installed content and its relationship to the planned structure.","findings":[{"id":"component-positions","name":"Component positions","description":"This finding identifies the unit's original installed content and position references.","questions":[{"text":"Which component serials, lots and software versions were installed in this unit at its recorded build completion date?","id":"original-installed-content"},{"text":"Which planned bill of materials version was this unit built against?","id":"planned-baseline"},{"text":"What unit item identifier, unit serial number and position identifier identify this installed position, and what planned position or approved addition does it reference?","id":"position-identity"}]},{"id":"build-deviations","name":"Build deviations","description":"This finding records departures from the planned configuration and their approvals.","questions":[{"text":"What departure from the planned bill of materials does this build deviation record, and which approval authorizes it?","id":"deviation-approval"}]}]}]},{"id":"life-after-build","name":"Life after build","description":"This bundle preserves subsequent configurations without overwriting the original build.","layers":[{"id":"changes-in-service","name":"Changes in service","description":"This layer records effective configuration changes and supporting evidence.","findings":[{"id":"replacements","name":"Replacements","description":"This finding preserves component changes and the resulting as-maintained configurations.","questions":[{"text":"Which components were removed and installed in this replacement event, when did it take effect, who performed it and why?","id":"replacement-details"},{"text":"Where does this replacement record reference the history of its removed component?","id":"removed-component-history"},{"text":"What installed content and effective interval does this as-maintained configuration record declare?","id":"configuration-effective-period"}]},{"id":"traceability-queries","name":"Traceability references","description":"This finding links one unit to evidence supporting its configuration.","questions":[{"text":"Which production order and inspection records support this unit's original as-built configuration?","id":"production-inspection-evidence"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["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."]},"ethics":{"considerations":["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."],"affectedParties":["Owners and users of the units","Service technicians","Suppliers of components"]},"owners":{"steward":"The configuration manager who answers for the accuracy of unit structures.","roles":[],"masterSystems":["Manufacturing execution system","Product lifecycle management system","Field service management system"]},"relations":[{"target":"EM-OPS-04","type":"neighbor"},{"target":"EM-OPS-05","type":"neighbor"},{"target":"EM-OPS-03","type":"neighbor"},{"target":"EM-MFG-01","type":"neighbor"},{"target":"EM-MFG-06","type":"neighbor"},{"target":"EM-TEC-01","type":"neighbor"},{"target":"WM-OBJ-012","type":"references","note":"conceptual-candidate"},{"target":"WM-OBJ-019","type":"references","note":"conceptual-candidate"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"required","items":["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":{"applicability":"required","items":["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":{"applicability":"required","items":["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."]},"interfaces":{"applicability":"optional","items":["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":{"applicability":"required","items":["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":[{"title":"IDTA Asset Administration Shell: digital twin of an individual asset"},{"title":"ISO 10303 (STEP): product structure and configuration"},{"title":"Device history record practice in regulated manufacturing"},{"title":"IDTA Asset Administration Shell specifications","url":"https://industrialdigitaltwin.org/en/content-hub/aasspecifications","note":"Checked live (HTTP 200) on 2026-10-21."},{"title":"21 CFR Part 820, medical device quality management system regulation (eCFR)","url":"https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-820","note":"Checked live (HTTP 200) on 2026-10-21."}],"openQuestions":["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."],"resources":{"source":"https://ver.cy/enterprise/models/em-mfg-04/"},"provenance":{"origin":"enterprise research programme","builtFrom":["enterprise/models/em-mfg-04/brief.json","ver-cy/world-models/card-supplements/em-mfg-04.json"],"providers":[],"researchStatus":"published-partial","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Enterprise record contour: physical properties belong to referenced world models.","_supplement":"Sections authored in card supplement 1.1.0 by Claude (Opus 5.5) (2026-10-21, unreviewed). Written from the industry contour brief and established practice in the field; source pages were checked live on 2026-10-21. Unreviewed. Revised against an independent Codex review on 2026-10-21.","_gate":"Published through the contour publication gate 1.0 on 2026-10-21T19:02:23+00:00: completeness 1.00; subject: research brief; 2 live sources; review by codex: pass"},"score":1.0}}