Skip to content

Main content

Assembly Operator Cycle Share

Normalize explicit nonoverlapping operator busy time to one assembly cycle duration.

Loading tool…

Description

Calculate an operator's supplied busy fraction within an assembly cycle.

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 an operator's supplied busy fraction within an assembly cycle.

When to use this tool

Use Assembly Operator Cycle Share when you already have operatorBusySeconds, cycleSeconds and need to calculate an operator's supplied busy fraction within an assembly cycle.

How to use the tool and how it works

  1. Enter operatorBusySeconds, cycleSeconds. 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 busyFraction, idleSeconds. Use the output convention below.

Require cycleSeconds>0 and busy seconds within cycle; return busy/cycle and cycle-busy as idleSeconds.1

Input fieldMeaning and unitsAccepted input
operatorBusySecondsOperator Busy SecondsRequired. Finite number; minimum 0.
cycleSecondsCycle SecondsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
busyFractionBusy FractionRequired. Finite number.
idleSecondsIdle SecondsRequired. Finite number.
json
{
  "input": {
    "operatorBusySeconds": 42,
    "cycleSeconds": 60
  },
  "output": {
    "busyFraction": 0.7,
    "idleSeconds": 18
  }
}

Limitations and assumptions

  • Remaining time is an arithmetic remainder, not verified idle capacity, labor effectiveness or an appropriate workload.
  • 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/assembly-operator-cycle-share — tool.io

Similar or alternative tools