Ramp Calculations

How to Calculate Production Ramp Rate, Yield Curve, and Ramp Staffing Hours

The core ramp and launch-readiness formulas worked through with real inputs, units, and where each number comes from, so you can run the math yourself.

Five formulas carry most of a launch: ramp rate, yield ramp curve, staffing workload hours, capacity-gap risk, and pilot build cost. Start with ramp rate, which is units past the ramp checkpoint divided by total units scheduled in the ramp window, times 100. If 8 of 250 scheduled units have cleared the gate, that is 8 / 250 x 100 = 3.2%. Subtract your target to get gap in points: 3.2% against a 95% exit target leaves a 91.8-point gap. Use the full scheduled window as the denominator, not units run so far, or the rate reads falsely high. The Production Ramp Rate calculator runs this each shift.

Yield ramp curve uses the same ratio form but a different denominator: good first-pass units divided by units started at a checkpoint, times 100. With 8 good units from 250 started, first-pass yield is 3.2%; against a 95% stage target the gap is 91.8 points. Two rules keep it honest. Count only units that passed the first time, never reworked units, and put every started unit in the denominator including scrap and rework. Pilot builds routinely start below 50%, so read the slope build over build, not one point. The Yield Ramp Curve calculator plots each gate from EVT to PVT toward steady state.

Staffing ramp workload converts a build target into schedulable labor hours. Base time equals units divided by output rate: 120 units at 12 units per minute is 10 minutes... check your units. At 12 units per hour it is 10 hours; keep the time base consistent between quantity and rate or the answer is garbage. Then inflate for reality: required time equals base time times one plus the allowance. A 10% setup, handling, and delay allowance turns 10 hours into 11. To reach headcount, divide required hours by paid hours per person, so 11 hours over an 8-hour operator needs roughly 1.4 people. The Staffing Ramp Workload calculator adds the allowance step for you.

Capacity-gap risk uses FMEA-style multiplication, not a ratio. Ramp capacity gap risk equals severity times occurrence times detection, each on the same anchored scale. Severity 6, occurrence 4, detection 3 multiplies to a composite the tool normalizes to 4.55. Because the three multiply, one high dimension dominates: a shortfall you only catch at full rate scores its detection high and pushes the whole number up. This ranks constraints, it does not size the gap in units per hour, so back the top scores with a takt or line-balance calculation. The Ramp Capacity Gap calculator and Launch Readiness Score share this severity-occurrence-detection math.

Pilot build cost splits into a volume-scaled variable part and a fixed adder. The formula is pilot units times steady-state unit cost times premium factor, plus setup cost. Take 250 units at a $180 steady-state cost, a 140% premium, and $85,000 of soft tooling: 250 x 180 x 1.40 = $63,000 of variable premium-loaded cost, plus $85,000 fixed, for $148,000 total. Divide by 250 units and the loaded pilot cost is $592 per unit, about 3.3 times the $180 steady-state figure. Apply the premium only to the variable cost, never to the setup adder, or you double-count. The Pilot Build Cost calculator separates the two lines.

Where do the inputs come from? Ramp rate and yield counts come off inspection records and production reports at a fixed checkpoint definition, so week-over-week numbers stay comparable. Output rate for staffing comes from a time study at current ramp maturity, not the ideal spec rate, because operators are still climbing the learning curve. The allowance percentage comes from your own downtime logs; early ramps commonly run 10% to 20% versus 5% to 10% on mature lines. Severity, occurrence, and detection ratings come from an FMEA worksheet with anchored level definitions, calibrated across raters before you score the full punch list.

Chain the formulas and the ramp becomes a system you can steer. A 3.2% ramp rate is fine on day one but must climb each cycle; a yield curve stuck at 3.2% three builds later is a design or fixture problem, not a learning-curve dip. Feed the current, real output rate into staffing so crew hours track the volume steps, and re-run the pilot build cost as yield improves, watching the loaded-to-steady-state ratio fall toward the premium factor. If that ratio will not drop toward 1.4 over successive builds, the ramp is not converging and the scale-up decision should wait, whatever the calendar says.

One unit-discipline checklist prevents most calculation errors. Keep the ramp checkpoint definition frozen so counts compare across builds. Keep the yield denominator as started units, not shipped units. Match time bases in the staffing division to the exact minute or hour. Use one anchored 1-to-10 scale across every risk you compare, or two identical composites will not mean the same thing. And treat pilot per-unit cost as a launch-phase figure only; the $592 here will not persist at rate, and quoting production parts off it will bury the program in margin it never had.

Published 2026-07-01.