A42 · Reference edition 2026.11
Component stacks — Layout and sequence
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
Place the relevant elements in a visible order before completing the record. A diagram should distinguish position from sequence and should preserve the orientation used in the written notes. Review the example for a practical way to make the relationship explicit.
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 |
|---|---|
| A42 | 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
Identify the starting condition; mark the order or orientation; check that labels in the figure match the accompanying table.