Visual walkthrough — Verification methods — analysis, test, inspection, demonstration
This page answers ONE question, drawn all the way from the ground up:
When we shake a spacecraft to prove it survives launch, why do we shake it 25% harder than launch actually shakes it? Where does the number 1.25 come from?
The parent note stated the rule. Here we earn it — every symbol, every bell curve, every square root, drawn as a picture before it is used. A smart 12-year-old who has never seen a "sigma" should be able to follow from line one.
We will build to this one final statement:
but only after we understand what each piece is.
Step 1 — What "the load" actually is: a single number on a ruler
WHAT. Every spacecraft that flies gets rattled by its rocket. We compress "how hard it gets rattled" into a single number. For vibration we call it the shaking strength, measured in g (multiples of Earth's gravity). Call it .
- = shaking strength (in g). Bigger = a rougher ride.
A word on "RMS." The parent note says "8 g RMS random vibration." Random shaking is not a steady push — it jitters up and down thousands of times a second, so its plain average is zero (it pushes up as often as down). To get a single honest "size" for something that averages to zero, we square every wiggle (squaring makes both up and down positive), average those squares, then take the square root to get back to g. That three-word recipe — Root of the Mean of the Squares — is RMS. So "8 g RMS" is the typical effective strength of the jitter. Our is this RMS number.
WHY start here. Before we can talk about margins and safety factors, we need a thing to measure. Everything downstream is just "where does land, and where do we test?" So we draw a ruler.
PICTURE. Look at the orange tick. The rocket engineers tell us the Flight Limit — the roughest ride any launch is expected to give. That is one fixed point on the ruler, one particular value of .
Step 2 — Reality is not one number: it is a cloud
WHAT. Here is the twist that forces the whole derivation. No two flights are identical, and no two spacecraft are identical. Build the same satellite twice and one will be slightly stiffer than the other (a weld a hair thicker, a bolt a touch tighter). Fly the same rocket twice and one launch shakes a little harder than the other (weather, fuel, wind).
So the real value of a given unit feels is not the single tick . It is a whole spread of possible -values scattered around .
WHY this matters. If reality were one exact number, we would test at exactly that number and be done. We do NOT test harder for fun — we test harder because we cannot see which side of any particular flight or unit will land on. The margin exists purely to cover this scatter.
PICTURE. The single orange tick blooms into a cloud of possible -values — a pile of little dots, densest near the middle, thinning out as you move away. Most flights land near ; a few unlucky ones land noticeably higher.
Step 3 — Naming the cloud: the bell curve and its width
WHAT. Smooth that pile of -dots into a curve and you get the famous bell curve (the normal distribution). Two numbers completely describe it:
- (Greek "mu") — the center: the -value where the peak sits. This is our Flight Limit tick.
- (Greek "sigma") — the width: how far the cloud spreads sideways in . Small = a tight, confident pile. Large = a fat, uncertain smear.
WHY a bell and not something lopsided. Strictly, can never be negative — you cannot shake something with less than zero strength. A perfect bell curve does leak a tiny sliver of probability below zero, so it is only ever an approximation. It is a good one here because our scatter is small: is about 10% of , so "zero" sits a full below the center — so far out on the tail that the leaked probability is utterly negligible (well under one in a trillion trillion). For small scatter around a comfortably-positive mean, the tidy symmetric bell is the honest, standard choice. (If were comparable to we would switch to a one-sided model like the log-normal — but we are nowhere near that regime.)
WHY we need . The margin is going to be measured in widths. "How far past the center must I go to be safe?" only has an answer once we know how wide one step of uncertainty is. That step is exactly .
PICTURE. The bell, centered on . The teal double-arrow is one — one standard step of uncertainty out from the middle. Notice the shaded areas: 68% of all outcomes land within , and 99.7% within . Those percentages are baked into this exact shape.
is the tick, is the step, is...
Step 4 — Two clouds, not one: manufacturing scatter AND environment scatter
WHAT. Our uncertainty comes from two independent sources, and the parent note gave both:
- Manufacturing scatter — units come out different from each other.
- Environment scatter — launches shake differently from each other.
(The means "10% of the Flight Limit," so we're working in units where and one of means 10%.)
WHY two separate numbers. A stiff unit on a rough launch is worse than either effect alone. To size the margin we need the combined scatter, not each piece separately. So the question of Step 5 is: how do two clouds add?
PICTURE. Two narrower bells side by side — the plum one for manufacturing, the teal one for the environment — each with its own width . We must fuse them into one.
Step 5 — Why we ADD THE SQUARES (variances add; Pythagoras hiding in statistics)
WHAT. To combine two independent scatters we do not simply add the 's ( is wrong). Instead we add their variances (, the squared widths from Step 3) and take the square root:
Term by term:
- — the manufacturing variance (one leg of a right triangle).
- — the environment variance (the other leg).
- — undoes the squaring to get back to a plain width (the hypotenuse).
WHY squares and not a plain sum? This is the deep fact from Step 3: for independent sources, it is the variances (the 's, the squared distances) that add up, not the 's themselves. Geometrically that means the two effects point in "different directions" — like walking East then North. Walk 0.1 East and 0.1 North and you are NOT 0.2 from home; you are from home. Independent uncertainties combine exactly like perpendicular distances: by Pythagoras. Adding the 's straight would pretend the worst of both always happen together, which is too pessimistic (and too expensive).
PICTURE. A right triangle. The horizontal leg is , the vertical leg is , and the slanted hypotenuse — the real combined uncertainty — is .
Now plug in the numbers:
- each — the two variances (squared legs).
- — the total variance (squared hypotenuse).
- — the combined width: 14%, not 20%.
Step 6 — Covering almost everything: the reach
WHAT. We now decide how much of the cloud we insist on covering. Industry chooses — reaching three widths above the center captures 99.7% of all cases (recall Step 3's shaded bell). The test level is:
Plug in:
Term by term:
- — the Flight Limit itself (working in units where the limit is 1).
- — three standard steps of combined scatter, our safety reach.
- Sum — test 40% above the flight limit to swallow 99.7% of all real flights.
WHY and not or . covers only 68% — one in three flights would exceed our test, unacceptable. covers 99.9999% but demands a monstrous, hardware-destroying shake for vanishing extra safety. is the sweet spot: near-total coverage at survivable cost.
PICTURE. The full bell with the orange test-level tick planted at , far out on the right tail. Everything left of that tick — 99.7% of reality — is covered by our test.
Step 7 — From 1.4 down to the real-world 1.25 (the degenerate & practical cases)
WHAT. The clean statistics, fed our illustrative inputs, give . The published industry standard (e.g. NASA-STD-7001 / GEVS and MIL-STD-1540 heritage) is 1.25 — historically expressed as a +3 dB qualification margin on the vibration spectrum, which multiplies the RMS level by ... in energy, but the flat-level factor customarily applied and quoted is . The gap from our 1.4 to 1.25 is not a fudge: it reflects that the figures were worst-case teaching numbers, and that decades of flight data show mature, well-characterised hardware and launch environments scatter less than that.
WHY 1.25 is chosen. Three edge/degenerate cases pin it down:
- Less scatter than assumed — the pair is deliberately conservative. When flight-heritage data give a tighter, empirically-measured scatter (roughly for characterised hardware), then , and . So the standard's 1.25 factor is the answer once you plug in measured rather than assumed-worst scatter — which is exactly why standards bodies settled there.
- Zero scatter (perfect world) — if , then and Test Level . No uncertainty ⇒ no margin. This is the sanity check: the whole margin exists only because of scatter.
- Acceptance vs qualification. The design is proven once at on a qualification unit. Each flight unit then gets an acceptance test at — just enough to catch a manufacturing defect, without overstressing a good unit you actually intend to fly.
PICTURE. A number line from to with the three landmarks: (acceptance / zero-scatter), (qualification, the standard, from measured scatter), and (the result for the pessimistic teaching inputs). The chosen band sits at 1.25.
The one-picture summary
Everything above, in a single frame: the Flight Limit tick blooms into a cloud of -values, the cloud gets a width , two variances combine by Pythagoras into , three of those widths reach out to cover 99.7%, and using measured rather than worst-case scatter pulls the standard factor to 1.25.
Recall Feynman retelling — say it like a story
Imagine the rocket promises to shake your satellite exactly "8 g RMS" — where "RMS" just means: since random shaking wiggles up and down and averages to nothing, we square all the wiggles, average them, and square-root back to get one fair "size" for the jitter. But nature never hands you an exact 8. Build the satellite twice and they come out a little different; fly the rocket twice and it shakes a little different. So "8" is really a fuzzy blob of possible values — a pile of dots, tall in the middle, thin at the edges: a bell curve (a fine approximation here because our fuzz is tiny next to the 8, so it never dips near zero). The blob has a width; call one step of that width "sigma," and its square "variance." Two things make it fuzzy — the factory and the weather — and because they don't know about each other, their variances add, which by Pythagoras means a tenth East and a tenth North leaves you not two-tenths but about fourteen-hundredths from home. To be almost totally safe we walk out three of those steps from the center, which scoops up 99.7% of everything that could happen — landing near "test at 1.4× the promise" if we use gloomy worst-case fuzz. But decades of real flight data show mature hardware wobbles less than that gloomy guess, so the standards settle on 1.25× for proving the design, and just 1.0× to give each finished unit a quick honest once-over. And the punchline hiding underneath: if nothing were ever fuzzy — zero scatter — the margin would vanish and you'd test at exactly the promise. The margin is the uncertainty, made into a number.
See also: Verification Methods — Analysis, Test, Inspection, Demonstration · Vibration Testing · Acceptance Testing · Margin Philosophy · Requirements Development · Traceability Matrix · Model Validation