{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-obj-019","code":"wm-obj-019-component-type-engineering-bom","url":"https://ver.cy/models/wm-obj-019-component-type-engineering-bom/","name":"Component Type / Engineering BOM","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"aggregate","plane":"","domain":["PHY.OBJ.ASM"],"industry":["Cross-industry"],"navPath":"NAV.PHY.OBJ.ASM","tags":["component","type","engineering","bom","phy.obj.asm"],"facets":{}},"whatItIs":"An engineering BOM revision owns occurrence relationships, quantities, applicability, selection, intended-property references and controlled exchange. Product types, designs, configured variants and physical items retain independent masters.","purpose":"Describe reusable type-level engineering composition distinctly from as-built assembly.","scope":{"in":["Versioned engineering baseline and component occurrences","Quantities, graph integrity, effectivity and selection","Qualified nominal properties, functional contributions and governed change"],"out":["As-built item state, actual material consumption and inventory","Production routes, procurement execution and software BOM","Automatic physical action or certification from information validity"],"boundaries":[{"neighbor":"WM-OBJ-002 Product Type / Catalog Item","distinction":"Frozen COMPOSE relation: occurrences reference reusable component types, not copied product masters."},{"neighbor":"WM-OBJ-018 Engineering Design / Product Definition","distinction":"Design geometry and functional intent stay referenced, not remastered in the BOM."},{"neighbor":"WM-OBJ-017 Product Configuration / Variant","distinction":"Selection binds applicability; candidate lines do not imply installed components."},{"neighbor":"Physical items and manufacturing masters","distinction":"Engineering occurrence is not serialized item; manufacturing additions and process recursion require a separate view."}]},"distinguishingFeatures":["Describes type-level composition, which components and how many, not the as-built structure of a serial unit.","Records occurrences with quantities, units, effectivity and alternates, which a design record does not.","Differs from a manufacturing BOM and routing, which add production steps, scrap and plant-specific items.","Differs from a software BOM, which lists software components and licences."],"structure":{"bundles":[{"id":"bom-composition-authority","name":"Composition authority","description":"Engineering composition concerns: composition authority.","layers":[{"id":"bom-baseline","name":"BOM identity, view and baseline","description":"Proposed engineering-composition record for bom identity, view and baseline. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"bom-baseline-record","name":"BOM identity, view and baseline record","description":"Proposed engineering-composition record for bom identity, view and baseline. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which issuer-qualified BOM identity, immutable revision and engineering view define the composition being read?","id":"bom-baseline-q01","kind":"identity"},{"text":"Which parent product type and controlled design revision does this baseline describe, and which representations are authoritative?","id":"bom-baseline-q02","kind":"authority"},{"text":"Which required members or referenced revisions are missing, unresolved or intentionally withheld from this baseline?","id":"bom-baseline-q03","kind":"quality"}]}]},{"id":"component-occurrence","name":"Component types and occurrences","description":"Proposed engineering-composition record for component types and occurrences. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"component-occurrence-record","name":"Component types and occurrences record","description":"Proposed engineering-composition record for component types and occurrences. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which component type and exact revision is referenced by each occurrence, independently of its displayed item number?","id":"component-occurrence-q01","kind":"relationship"},{"text":"How are repeated occurrences, hierarchical reference designators and merged display rows distinguished and reversibly mapped?","id":"component-occurrence-q02","kind":"composition"},{"text":"Which occurrence-specific placement, footprint or interface binding identifies its intended position without asserting an actual item's location?","id":"component-occurrence-q03","kind":"spatial"}]}]}]},{"id":"bom-quantified-assembly-graph","name":"Quantified assembly graph","description":"Engineering composition concerns: quantified assembly graph.","layers":[{"id":"quantity-basis","name":"Quantity basis and dimensional meaning","description":"Proposed engineering-composition record for quantity basis and dimensional meaning. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"quantity-basis-record","name":"Quantity basis and dimensional meaning record","description":"Proposed engineering-composition record for quantity basis and dimensional meaning. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"What component quantity and unit apply per declared parent base quantity, rather than per an assumed single finished item?","id":"quantity-basis-q01","kind":"measurement"},{"text":"Which item-count, per-occurrence amount, conversion, rounding and override rules produce a reported total, and what evidence supports them?","id":"quantity-basis-q02","kind":"provenance"},{"text":"Which quantities are unknown, variable or outside the engineering view, including manufacturing scrap, yield and actual consumption?","id":"quantity-basis-q03","kind":"exception"}]}]},{"id":"assembly-graph","name":"Subassembly reuse and traversal integrity","description":"Proposed engineering-composition record for subassembly reuse and traversal integrity. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"assembly-graph-record","name":"Subassembly reuse and traversal integrity record","description":"Proposed engineering-composition record for subassembly reuse and traversal integrity. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which subordinate BOM revisions are reused, and which occurrence paths must remain distinct when the same subassembly appears more than once?","id":"assembly-graph-q01","kind":"composition"},{"text":"Is a detected cycle in the unfiltered family graph or the selected effective graph, and where must traversal stop safely?","id":"assembly-graph-q02","kind":"validation"},{"text":"Which unresolved references, depth limits, access-denied branches or intentional recursive-process boundaries make an expansion incomplete?","id":"assembly-graph-q03","kind":"quality"}]}]}]},{"id":"bom-applicability-and-selection","name":"Applicability and selection","description":"Engineering composition concerns: applicability and selection.","layers":[{"id":"line-effectivity","name":"Effectivity and revision resolution","description":"Proposed engineering-composition record for effectivity and revision resolution. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"line-effectivity-record","name":"Effectivity and revision resolution record","description":"Proposed engineering-composition record for effectivity and revision resolution. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Under which time, variant, site or other explicitly declared context predicates does a BOM revision or line apply?","id":"line-effectivity-q01","kind":"temporal"},{"text":"Which resolver and pinned context selected each component revision, and how are overlapping or missing applicable revisions reported?","id":"line-effectivity-q02","kind":"decision"},{"text":"How are approval time, recording time and effective boundaries preserved when a retrospective correction changes applicability?","id":"line-effectivity-q03","kind":"lifecycle"}]}]},{"id":"component-selection","name":"Options, alternates and substitutes","description":"Proposed engineering-composition record for options, alternates and substitutes. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"component-selection-record","name":"Options, alternates and substitutes record","description":"Proposed engineering-composition record for options, alternates and substitutes. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which optional or alternative component groups are available, and what cardinality and compatibility conditions constrain selection?","id":"component-selection-q01","kind":"constraint"},{"text":"Which approved substitution is directional, context-limited or conditional on interface and capability evidence rather than universal interchangeability?","id":"component-selection-q02","kind":"evidence"},{"text":"Which selected option set and explicit exclusions belong to the configured engineering composition, without treating every candidate as installed?","id":"component-selection-q03","kind":"state"}]}]}]},{"id":"bom-intended-characteristics","name":"Intended characteristics","description":"Engineering composition concerns: intended characteristics.","layers":[{"id":"nominal-properties","name":"Component properties and recognition references","description":"Proposed engineering-composition record for component properties and recognition references. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"nominal-properties-record","name":"Component properties and recognition references record","description":"Proposed engineering-composition record for component properties and recognition references. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which versioned material, nominal size, mass and other physical-property definitions belong to each component type, with units and conditions?","id":"nominal-properties-q01","kind":"definition"},{"text":"Which distinguishing features, markings, footprints or interface references help identify the intended component class, and what recognition uncertainty remains?","id":"nominal-properties-q02","kind":"classification"},{"text":"Which aggregate property is derived from the selected composition, using what method and exclusions, instead of being mistaken for a measured assembly property?","id":"nominal-properties-q03","kind":"measurement"}]}]},{"id":"functional-contribution","name":"Functional contribution and assembly constraints","description":"Proposed engineering-composition record for functional contribution and assembly constraints. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"functional-contribution-record","name":"Functional contribution and assembly constraints record","description":"Proposed engineering-composition record for functional contribution and assembly constraints. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"What intended functional role does an occurrence contribute, and which design or requirement master defines that role?","id":"functional-contribution-q01","kind":"relationship"},{"text":"Which mating, material, load or environmental constraints must hold for components to function together in this composition?","id":"functional-contribution-q02","kind":"constraint"},{"text":"Which unverified capability, prohibited use or unresolved compatibility issue prevents an agent from claiming the assembly is fit for a requested action?","id":"functional-contribution-q03","kind":"evidence"}]}]}]},{"id":"bom-change-and-realization-boundary","name":"Change and realization boundary","description":"Engineering composition concerns: change and realization boundary.","layers":[{"id":"composition-change","name":"Approval, change and where-used impact","description":"Proposed engineering-composition record for approval, change and where-used impact. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"composition-change-record","name":"Approval, change and where-used impact record","description":"Proposed engineering-composition record for approval, change and where-used impact. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Who may approve or retire this engineering baseline, and which open findings prevent release under the owning Dimension's policy?","id":"composition-change-q01","kind":"authority"},{"text":"Which changed occurrence, quantity or revision affects which parent baselines and configured variants according to a context-qualified where-used query?","id":"composition-change-q02","kind":"relationship"},{"text":"What expected-base check, decision and history preserve concurrent edits and approved deviations without silently rewriting released composition?","id":"composition-change-q03","kind":"lifecycle"}]}]},{"id":"realization-handoff","name":"Engineering-to-manufacturing handoff","description":"Proposed engineering-composition record for engineering-to-manufacturing handoff. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"realization-handoff-record","name":"Engineering-to-manufacturing handoff record","description":"Proposed engineering-composition record for engineering-to-manufacturing handoff. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which engineering occurrences map to which manufacturing BOM or process-master records, including split, merged, phantom or omitted representations?","id":"realization-handoff-q01","kind":"interoperability"},{"text":"Which make-or-buy intention or manufacturing-only addition is recorded as a qualified handoff assumption rather than an engineering component fact?","id":"realization-handoff-q02","kind":"decision"},{"text":"What receiving-system acknowledgement and discrepancy disposition preserve the original engineering baseline when the production or as-built view differs?","id":"realization-handoff-q03","kind":"event"}]}]}]},{"id":"bom-governed-composition-exchange","name":"Governed composition exchange","description":"Engineering composition concerns: governed composition exchange.","layers":[{"id":"composition-stewardship","name":"Mastership, disclosure and preservation","description":"Proposed engineering-composition record for mastership, disclosure and preservation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"composition-stewardship-record","name":"Mastership, disclosure and preservation record","description":"Proposed engineering-composition record for mastership, disclosure and preservation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which Dimension and engineering authority own the baseline while external component masters retain their own stewardship?","id":"composition-stewardship-q01","kind":"ownership"},{"text":"Which occurrence details and artifacts may each recipient read or export, and how is a withheld branch distinguished from an empty assembly?","id":"composition-stewardship-q02","kind":"access"},{"text":"Which retention triggers, holds and preserved dependency references keep retired BOM revisions interpretable without retaining unnecessary protected content?","id":"composition-stewardship-q03","kind":"retention"}]}]},{"id":"exchange-fidelity","name":"Exchange fidelity and semantic validation","description":"Proposed engineering-composition record for exchange fidelity and semantic validation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","findings":[{"id":"exchange-fidelity-record","name":"Exchange fidelity and semantic validation record","description":"Proposed engineering-composition record for exchange fidelity and semantic validation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.","questions":[{"text":"Which source and target profile versions, exact-byte digests and transformation provenance bind an exported composition?","id":"exchange-fidelity-q01","kind":"provenance"},{"text":"Which occurrence identity, unit, effectivity, selection or reference-designator semantics are lost or changed by flattening or row merging?","id":"exchange-fidelity-q02","kind":"interoperability"},{"text":"Which declared acceptance fixtures and rejection rules establish a usable mapping while keeping unsupported constructs visible?","id":"exchange-fidelity-q03","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Resolve one applicable baseline for a given effectivity and configuration.","Expand the composition tree with loop protection and report withheld branches.","Compute rolled-up quantities when units are compatible and alternates are excluded.","Draft change proposals and where-used reports."],"mustNot":["Sum alternates or mix incompatible units in a roll-up.","Edit a released BOM revision in place.","Treat the BOM as authority to order material or start manufacturing.","Flatten distinct occurrences into one line when their identity matters for traceability.","Disclose supplier-confidential parts lists beyond the declared scope."],"requiresHuman":["Releasing a BOM revision or engineering change.","Approving substitutes or alternates for safety-relevant components."]},"ethics":{"considerations":["BOM errors can introduce unsafe or counterfeit components into products people rely on.","Composition data supports material disclosure duties, such as restricted substances, and should stay accurate.","Supplier part data can be commercially sensitive."],"affectedParties":["Users of the finished product","Production and service staff","Suppliers whose parts are listed"]},"owners":{"steward":"Identify Dimension owner and composition authority.","roles":[{"name":"Dimension owner","responsibilities":["Defines namespace, storage and delegated access."]},{"name":"Composition authority","responsibilities":["Owns baseline and approves applicability and change."]},{"name":"Engineering author","responsibilities":["Maintains component bindings, quantities and evidence."]},{"name":"Reviewer","responsibilities":["Checks selection, units, cycles and unresolved assertions."]},{"name":"Custodian","responsibilities":["Preserves authorized readable dependencies without becoming owner."]}],"masterSystems":[]},"relations":[{"target":"WM-OBJ-002","type":"composes","note":"Frozen type-level component composition relation."},{"target":"WM-OBJ-018","type":"references","note":"Resolve controlled geometry and intended definition."},{"target":"WM-OBJ-017","type":"references","note":"Bind selected variants without merging lifecycles."},{"target":"WM-OBJ-001","type":"references","note":"Link as-built discrepancies without treating intent as observation."},{"target":"Manufacturing BOM, routing and procurement masters","type":"references","note":"Preserve independent realization views and permissions."},{"target":"ISO 10303-242:2025 public scope","type":"aligned","note":"Candidate exchange alignment only; licensed clauses and crosswalk deferred."},{"target":"WM-OBJ-002 Product Type / Catalog Item","type":"neighbor","note":"Frozen COMPOSE relation: occurrences reference reusable component types, not copied product masters."},{"target":"WM-OBJ-018 Engineering Design / Product Definition","type":"neighbor","note":"Design geometry and functional intent stay referenced, not remastered in the BOM."},{"target":"WM-OBJ-017 Product Configuration / Variant","type":"neighbor","note":"Selection binds applicability; candidate lines do not imply installed components."},{"target":"Physical items and manufacturing masters","type":"neighbor","note":"Engineering occurrence is not serialized item; manufacturing additions and process recursion require a separate view."},{"target":"WM-OBJ-002","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system ID","Governed issuer-qualified UUID","Dimension UUID with revision and digest"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"required","items":["An engineering BOM is identified by parent part number, revision and BOM view.","Each line shows child part, quantity, unit and find number or reference designator.","Confused with the manufacturing BOM, the as-built record, a parts catalog and a software BOM."]},"capabilities":{"applicability":"required","items":["Resolve applicable baseline: Resolve one engineering baseline under explicit context, preserving ambiguity.","Expand bounded composition: Traverse occurrences without flattening identity or looping.","Qualify engineering quantities: Describe dimensional calculation and override provenance; this contract supplies no calculation engine.","Bind configured selection: Record constrained choices and qualified substitutions.","Review and release composition change: Assess where-used impact and baseline authority.","Exchange composition with loss report: Preserve source identity through target-view mappings."]},"hazards":{"applicability":"required","items":["Wrong quantity or unit causing shortages or wrong assembly.","Superseded part used because effectivity was misread.","Infinite recursion or duplicate counting in poorly formed trees.","Undeclared restricted substances through unlisted components."]},"interfaces":{"applicability":"required","items":["ISO 10303-242 (STEP AP242) product structure.","ISO 10303-239 (PLCS) for configured structures.","IPC-2581 for printed circuit assembly data.","IEC 62474 for material declaration.","IEC 62264 (ISA-95) for exchange with manufacturing.","UN/CEFACT Recommendation 20 unit codes."]},"context":{"applicability":"required","items":["Owning Dimension must declare contract, sector and jurisdiction requirements; no legal or manufacturing authorization inferred."]}},"sources":[{"title":"Bills of materials and formulas","url":"https://learn.microsoft.com/en-us/dynamics365/supply-chain/production-control/bill-of-material-bom","note":"Microsoft"},{"title":"About BOM Quantity","url":"https://help.autodesk.com/cloudhelp/2023/ENU/Inventor-Help/files/GUID-37BA8DB6-E39C-4C96-AAF1-E7B342F20D0E.htm","note":"Autodesk"},{"title":"BOMRow Object","url":"https://help.autodesk.com/cloudhelp/2023/ENU/Inventor-API/files/BOMRow.htm","note":"Autodesk"},{"title":"Electronics Bill of materials","url":"https://help.autodesk.com/cloudhelp/ENU/Fusion-ECAD/files/ECD-BOM-CPT.htm","note":"Autodesk"},{"title":"Recursiveness Check","url":"https://help.sap.com/docs/SAP_ERP/43fa3cddb00348beb3ed12212a94448f/dd05c453f57eb44ce10000000a174cb4.html","note":"SAP"},{"title":"Managed model-based 3D engineering","url":"https://www.iso.org/standard/84300.html","note":"ISO"},{"title":"Configuration Management","url":"https://www.nasa.gov/reference/6-5-configuration-management/","note":"NASA"},{"title":"PROV-DM","url":"https://www.w3.org/TR/prov-dm/","note":"W3C"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"}],"openQuestions":["Independent external review.","Executable field-level schemas and negative fixtures for units, cycles, alternatives and concurrent revisions.","Licensed standards and sector-specific alternate/substitution qualification.","Real multi-level mechanical and electronics examples with loss-aware round trips.","No independent external research/review: Claude and Grok each timed out once. Codex-only owner waiver requires reviewable-draft assurance.","SAP support is indexed text only; licensed ISO clauses unread. Source-to-field normative compliance is not established.","Vendor documentation is selected and domain-specific, not exhaustive industry coverage. Alternate/substitute rules are proposed Vercy design needing specialist review.","Nested field groups are not an executable instance schema. No BOM solver, unit engine, CAD adapter or real-product round-trip fixtures delivered.","Actual physical properties and capability require design/component evidence; safety and certification are outside this contract.","Adopters must instantiate actual authority, retention, access, effectivity predicates and acceptance criteria."],"resources":{"spec":"/models/wm-obj-019-component-type-engineering-bom/spec.yaml","agents":"/models/wm-obj-019-component-type-engineering-bom/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-019"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-obj-019-component-type-engineering-bom/spec.yaml","ver-cy/world-models/card-supplements/wm-obj-019-component-type-engineering-bom.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-09T19:01:50Z","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":"A bill of materials is a structure record; component types and parts carry the physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}