Tolerance Stack-Up Analysis¶
Analysis method — instantiates Robustness Margin Design
Adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share.
Tolerance Stack-Up Analysis reasons about accumulation. Every part in a chain is allowed to wander a little; each is fine alone; but the deviations add along the assembly, and the question is whether the sum still fits. The mechanism sums the per-part tolerances along the dimension that matters, compares the total against the point where the assembly stops working, and — crucially — allocates the available slack back onto each contributor so no single part is asked for impossible precision and no chain is left too loose. That is what makes it THIS mechanism rather than a sibling: it lives entirely at the interfaces, on paper, treating robustness as a budgeting problem across a chain, not a factor on one part and not a trial on a real one.
Example¶
A weatherproof outdoor sensor stacks a battery pack, a circuit board, a foam gasket, and a snap-fit lid, and a spring contact on the board must press a battery terminal with the lid closed. Each part carries its own tolerance: the battery height ±0.3 mm, the board mount ±0.2 mm, the gasket compression ±0.4 mm, the lid depth ±0.3 mm. Any one is acceptable. Stacked, though, the worst-case sum is 1.2 mm of possible play — and the contact only has 0.9 mm of travel. On paper, before a single unit is built, the analysis shows the contact can miss. The fix is a budgeting decision: tighten the gasket's share, add contact travel, or accept a small statistical risk. The stack-up is what turns four locally-fine tolerances into a visible system-level margin problem.
How it works¶
Its distinguishing move is combination. Define the dimensional chain (or loop) that must close; list each contributor's nominal and tolerance; then combine them two ways. Worst-case sums the extremes arithmetically — every part at its worst, simultaneously — which is safe but pessimistic. Statistical combination (root-sum-square) adds the tolerances in quadrature, assuming they vary independently and rarely all hit the limit together, which is realistic but assumption-laden.[n1] The combined spread is compared to the assembly requirement; where it overruns, the total budget is re-split across contributors by tightening the cheapest ones to tighten. The output is not a tested part but a decision about where the tolerance should live.
Tuning parameters¶
- Worst-case vs. statistical combination — arithmetic sum versus root-sum-square. Worst-case never fails but demands tighter (costlier) parts; statistical loosens them but bets on independence.
- Contributors included — how many links in the chain enter the sum; leaving out a hidden contributor (thermal growth, assembly shift) is the usual way a stack-up lies.
- Budget split rule — equal shares versus allocation by process capability; giving the loosest process the widest band and the precise process the narrowest minimizes total cost.
- Directional handling — whether contributors add or partly cancel along the chain; getting the signs right is what separates a real stack from a scary-looking one.
When it helps, and when it misleads¶
Its strength is that it catches the failures that hide between parts — the ones no single-part inspection can see, because each part passed. It makes the interface budget explicit and lets a team spend precision where it buys the most fit. Its failure mode is the assumption underneath the statistical method: root-sum-square assumes the contributors vary independently and roughly normally, and when they do not — parts from the same worn tool, the same hot batch, the same supplier drifting together — the deviations correlate, the real spread balloons toward worst-case, and an assembly that "passed on paper" jams in the field. The classic misuse is quoting the comfortable statistical number for a safety-critical mate that deserves worst-case. The guard is to check the independence assumption honestly, reserve worst-case for the mates that cannot be allowed to fail, and never omit a contributor because it is inconvenient to model.
How it implements the components¶
margin_budget— its signature act: it divides the total allowable variation into a share for each part along the chain, and reallocates when the stack runs tight.operating_variation_envelope— it works over the full range each contributor may occupy, combining those ranges rather than a single nominal value.degradation_boundary— the assembly requirement (the contact's 0.9 mm of travel) is the boundary the accumulated stack must not cross; the analysis measures distance to it.
It does not choose any single part's band from a multiplier (safety_factor — Safety Factor Application) or physically test the assembled stack (robustness_test — Ruggedization Testing); it reasons about accumulation on paper and hands the result to those mechanisms.
Related¶
- Instantiates: Robustness Margin Design — this analysis places margin at the interfaces, where robustness most often fails.
- Consumes: Engineering Tolerance Specification — it sums the per-part bands those specifications declare.
- Sibling mechanisms: Safety Factor Application · Stress Margin Simulation · Ruggedization Testing · Usability Tolerance Testing · Defensive Design Review · Robust Statistics Method · Policy Slack Allowance · Sensitivity Analysis Protocol
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Tolerance Stack-Up Analysis operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share.
Independent corroboration: The frozen evidence defines Tolerance Stack-Up Analysis as 'Adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: NASA, System Engineering Tools and Techniques defines tolerance stack-up analysis as combining manufacturing tolerances, by worst-case or statistical models, to test finished form, fit, and function. This directly supports engineering design as the best-evidenced historical home of the operation—Adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share.—while the alternates record adjacent lineages rather than mere domains of later use.
Related originating lineages:
- Organizational & Management Science — Organizational management supplies a historically relevant adjacent lineage or formative practice for the operation—Adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share.—but the researched evidence more directly locates the defining lineage in engineering design.
- Statistics & Experimental Design — Statistics, experimental design, and measurement theory supplies a parallel or contributing lineage for the mechanism's defining operation: adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each….
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each….
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus engineering_design). The defining operation is: Adds up the individually acceptable deviations of every part along an assembly chain to check whether their accumulation still stays inside the failure boundary — and budgets each part's share. The researched NASA, System Engineering Tools and Techniques defines tolerance stack-up analysis as combining manufacturing tolerances, by worst-case or statistical models, to test finished form, fit, and function. That is mechanism-specific evidence for engineering design as the historical origin. Organizational management remains represented among the uncapped alternates where it contributes a genuine formative practice, but broad deployment or governance of the operation is not by itself evidence that the mechanism originated there. origin_mode=single_lineage records lineage; domain_reach=specialized separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The root-sum-square (RSS) method combines independent tolerances by taking the square root of the sum of their squares rather than their arithmetic total, on the statistical premise that the contributors rarely reach their extremes at once. It yields a tighter, cheaper stack than worst-case — and silently fails when the contributors are correlated instead of independent. ↩