A43 · Reference edition 2026.11
Component stacks — Comparison and alternatives
A stack record needs an ordered sequence from the base to the part contact. Component IDs alone do not establish assembled height.
Scope and purpose
Compare alternatives using the same question and context. A difference in wording, layout or scale is not automatically a difference in performance. Keep the original observations available and explain which differences are meaningful for this comparison.
Working notes
This reference collection concerns light, offline dimensional-inspection layouts. It brings locating concepts, component descriptions and revision records together without substituting for an engineered fixture design. The drawings are original explanatory diagrams. Reference IDs identify documents, not commercially tested products. Read the scope and limitations alongside each example, and keep the actual part drawing and inspection requirements available when reviewing a proposed layout.
Practical example
List base interface, riser, support body and contact cap as separate rows.
| Reference record | Interpretation |
|---|---|
| A43 | Component stacks |
| Scope and purpose | A stack record needs an ordered sequence from the base to the part contact. Component IDs alone do not establish assembled height. |
| Limits and interpretation | Do not sum nominal catalogue heights into an unsupported tolerance claim. |
Review checklist
State the comparison question; align context and labels; list common features separately from differences; leave unsupported conclusions open.