Multi-Style Line Changeover Penalty & Recovery Curve

The formula

This is the expression the tool evaluates. Every term is named underneath, with the unit it must be supplied in.

How the result is derived

Step by step, from the values you type to the figure on screen.

1. The 9 inputs are read from the form on every keystroke: Steady Efficiency, Efficiency at Restart, Recovery Half-Life, Units Since Changeover, Target Efficiency, Changeover Downtime, Operators on Line, Labour Cost per Minute and Contribution per Unit.
2. Each value is checked against the accepted range in the input table below. A value outside its range stops the calculation rather than producing a misleading figure — the results blank out and a message appears.
3. The validated values are substituted into the expression above, which resolves Efficiency Now together with every supporting figure in one pass — no value is carried over from a previous entry.
4. The supporting outputs — Units to Reach Target, Production Lost to Ramp, Downtime Cost, Value of Lost Production and Total Changeover Cost — come from the same pass, so they always describe the same case as the headline figure.
5. Results are rounded for display only. The full-precision value is used throughout the chain, so reading a rounded intermediate figure back into the tool by hand can shift the last digit.

What each input means

Where to read each value on the floor, the unit it must be in, and the range the tool accepts.

What the tool returns

The headline figure and every supporting value it is built from.

Worked example

The tool loads with this case already solved — the Efficiency Now shown above is its answer. Change one value and the difference from this baseline is the sensitivity of the result to that variable.

How to use it

1. Work through the input groups in order — Recovery Curve and Cost of the Change. The defaults are a realistic case, so you can change one value at a time and watch what moves.
2. There is no calculate button. Every figure recalculates as you type or drag, which is what makes this usable for a what-if sweep rather than a single answer.
3. Read Efficiency Now in the dark results panel — that is the headline figure, expressed in %.
4. Check the supporting rows underneath (Units to Reach Target, Production Lost to Ramp, Downtime Cost, Value of Lost Production and Total Changeover Cost) before acting on the headline — they are where an implausible input usually shows itself first.
5. Reset to defaults returns every field to the reference case, which is the quickest way to check whether a surprising result came from the tool or from an input you had changed earlier.

Where this is used

• Process planning — establishing Efficiency Now before a trial is booked, so machine time and material in Production Planning & Sequencing are committed against a calculated figure rather than an estimate.
• Costing and quotation — Efficiency Now is an input to the cost sheet, and quoting from a worked number rather than a remembered one is what keeps a margin intact.
• Troubleshooting — when the floor result drifts from plan, entering the measured values (starting with Steady Efficiency) shows how much of the gap in Efficiency Now each variable explains.
• Teaching and study — the accepted ranges bracket normal Production Planning & Sequencing practice, so moving one variable at a time shows the shape of the relationship rather than a single answer.

Assumptions and limits

• A target efficiency at or above the steady rate is unreachable and the units-to-target figure will run to infinity or return no answer — the curve approaches the steady rate asymptotically and never crosses it. The half-life must be fitted from your own hourly output records after real changeovers; it varies enormously with how similar the new style is to the old and with whether the same operators keep the same operations. Production lost is measured against the steady rate as though the line could have run at it from minute one, which is the right comparison for judging changeover frequency and the wrong one for judging the operators.
• Every input is bounded to the range normal practice occupies (Steady Efficiency 20 to 100 %, Efficiency at Restart 5 to 95 % and Recovery Half-Life 10 to 20000 units, and so on for the rest). Those bounds are guard rails against typing errors, not a claim that the formula fails one unit outside them.
• The calculation is deterministic: the same inputs always give the same result. It carries no allowance for machine condition, operator skill, ambient conditions or lot-to-lot material variation unless an input above explicitly represents one.
• Nothing is sent anywhere. The maths runs in your browser, so the numbers you type never leave the page.

Questions people ask