Skip to content

Main content

Setup Improvement Before After Net Term Tool

Compare explicit setup-time savings after a supplied additional support-time requirement without claiming sustained productivity gains.

Loading tool…

Description

Calculate gross and net setup-time savings after added support work.

Production quantities distinguish planned time, operating time, setup, cycle time, demand, first-pass good units and accepted rework. A local availability term is not complete OEE, and equal time-per-unit arithmetic is not measured capacity. Counts and durations must share one nonoverlapping accounting scope.

Calculate gross and net setup-time savings after added support work.

When to use this tool

Use Setup Improvement Before After Net Term when you already have previousSetupMinutes, newSetupMinutes, addedSupportMinutes and need to calculate gross and net setup-time savings after added support work.

How to use the tool and how it works

  1. Enter previousSetupMinutes, newSetupMinutes, addedSupportMinutes. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read grossSavedMinutes, netSavedMinutes. Use the output convention below.

Require nonnegative previous/new setup and added-support minutes; gross=previous-new, net=gross-support.1

Input fieldMeaning and unitsAccepted input
previousSetupMinutesPrevious Setup MinutesRequired. Finite number; minimum 0.
newSetupMinutesNew Setup MinutesRequired. Finite number; minimum 0.
addedSupportMinutesAdded Support MinutesRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
grossSavedMinutesGross Saved MinutesRequired. Finite number.
netSavedMinutesNet Saved MinutesRequired. Finite number.
json
{
  "input": {
    "previousSetupMinutes": 60,
    "newSetupMinutes": 40,
    "addedSupportMinutes": 5
  },
  "output": {
    "grossSavedMinutes": 20,
    "netSavedMinutes": 15
  }
}

Limitations and assumptions

  • Negative savings are retained; scope and timing must match, and no actual improvement, throughput gain or staffing adequacy is established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the full time study, production ledger and process definition before interpreting performance. Use a complete capacity, OEE or workflow analysis when bottlenecks, quality, concurrency and operating constraints matter beyond one local term.

References

  1. Calculation and input contract: industrial-engineering/setup-improvement-before-after-net-term — tool.io

Similar or alternative tools