Component Type / Engineering BOM

BOM identity, view and baseline record

Proposed engineering-composition record for bom identity, view and baseline. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which issuer-qualified BOM identity, immutable revision and engineering view define the composition being read? identity
2. Which parent product type and controlled design revision does this baseline describe, and which representations are authoritative? authority
3. Which required members or referenced revisions are missing, unresolved or intentionally withheld from this baseline? quality

Component types and occurrences record

Proposed engineering-composition record for component types and occurrences. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which component type and exact revision is referenced by each occurrence, independently of its displayed item number? relationship
2. How are repeated occurrences, hierarchical reference designators and merged display rows distinguished and reversibly mapped? composition
3. Which occurrence-specific placement, footprint or interface binding identifies its intended position without asserting an actual item's location? spatial

Quantity basis and dimensional meaning record

Proposed engineering-composition record for quantity basis and dimensional meaning. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. What component quantity and unit apply per declared parent base quantity, rather than per an assumed single finished item? measurement
2. Which item-count, per-occurrence amount, conversion, rounding and override rules produce a reported total, and what evidence supports them? provenance
3. Which quantities are unknown, variable or outside the engineering view, including manufacturing scrap, yield and actual consumption? exception

Subassembly reuse and traversal integrity record

Proposed engineering-composition record for subassembly reuse and traversal integrity. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which subordinate BOM revisions are reused, and which occurrence paths must remain distinct when the same subassembly appears more than once? composition
2. Is a detected cycle in the unfiltered family graph or the selected effective graph, and where must traversal stop safely? validation
3. Which unresolved references, depth limits, access-denied branches or intentional recursive-process boundaries make an expansion incomplete? quality

Effectivity and revision resolution record

Proposed engineering-composition record for effectivity and revision resolution. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Under which time, variant, site or other explicitly declared context predicates does a BOM revision or line apply? temporal
2. Which resolver and pinned context selected each component revision, and how are overlapping or missing applicable revisions reported? decision
3. How are approval time, recording time and effective boundaries preserved when a retrospective correction changes applicability? lifecycle

Options, alternates and substitutes record

Proposed engineering-composition record for options, alternates and substitutes. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which optional or alternative component groups are available, and what cardinality and compatibility conditions constrain selection? constraint
2. Which approved substitution is directional, context-limited or conditional on interface and capability evidence rather than universal interchangeability? evidence
3. Which selected option set and explicit exclusions belong to the configured engineering composition, without treating every candidate as installed? state

Component properties and recognition references record

Proposed engineering-composition record for component properties and recognition references. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which versioned material, nominal size, mass and other physical-property definitions belong to each component type, with units and conditions? definition
2. Which distinguishing features, markings, footprints or interface references help identify the intended component class, and what recognition uncertainty remains? classification
3. Which aggregate property is derived from the selected composition, using what method and exclusions, instead of being mistaken for a measured assembly property? measurement

Functional contribution and assembly constraints record

Proposed engineering-composition record for functional contribution and assembly constraints. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. What intended functional role does an occurrence contribute, and which design or requirement master defines that role? relationship
2. Which mating, material, load or environmental constraints must hold for components to function together in this composition? constraint
3. Which unverified capability, prohibited use or unresolved compatibility issue prevents an agent from claiming the assembly is fit for a requested action? evidence

Approval, change and where-used impact record

Proposed engineering-composition record for approval, change and where-used impact. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Who may approve or retire this engineering baseline, and which open findings prevent release under the owning Dimension's policy? authority
2. Which changed occurrence, quantity or revision affects which parent baselines and configured variants according to a context-qualified where-used query? relationship
3. What expected-base check, decision and history preserve concurrent edits and approved deviations without silently rewriting released composition? lifecycle

Engineering-to-manufacturing handoff record

Proposed engineering-composition record for engineering-to-manufacturing handoff. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which engineering occurrences map to which manufacturing BOM or process-master records, including split, merged, phantom or omitted representations? interoperability
2. Which make-or-buy intention or manufacturing-only addition is recorded as a qualified handoff assumption rather than an engineering component fact? decision
3. What receiving-system acknowledgement and discrepancy disposition preserve the original engineering baseline when the production or as-built view differs? event

Mastership, disclosure and preservation record

Proposed engineering-composition record for mastership, disclosure and preservation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which Dimension and engineering authority own the baseline while external component masters retain their own stewardship? ownership
2. Which occurrence details and artifacts may each recipient read or export, and how is a withheld branch distinguished from an empty assembly? access
3. Which retention triggers, holds and preserved dependency references keep retired BOM revisions interpretable without retaining unnecessary protected content? retention

Exchange fidelity and semantic validation record

Proposed engineering-composition record for exchange fidelity and semantic validation. Preserve declared view, exact revisions and evidence; no as-built or certification inference.

1. Which source and target profile versions, exact-byte digests and transformation provenance bind an exported composition? provenance
2. Which occurrence identity, unit, effectivity, selection or reference-designator semantics are lost or changed by flattening or row merging? interoperability
3. Which declared acceptance fixtures and rejection rules establish a usable mapping while keeping unsupported constructs visible? validation