Electronics Manufacturing worked example

SMT Line Throughput at 99% smt performance efficiency: a worked example

This scenario runs the smt line throughput calculation on the strong side: 99% smt performance efficiency, with every other input held at its documented default. a planner needs an honest boards-per-hour rate for an SMT family before committing capacity

The inputs for this scenario

  • Good SMT boards completed: 2,400 boards (unchanged)
  • SMT line runtime: 10 hr (unchanged)
  • SMT performance efficiency: 99 % (raised for this scenario; the documented default is 88)

Working through the calculation

  • Applying the documented formula (Observed SMT board rate = good SMT boards completed รท SMT line runtime) to the inputs above produces each figure below.
  • At this operating point the engine returns 238 boards / hr for effective smt board throughput, the number this scenario is built around.
  • At this operating point the engine returns 240 boards / hr for observed smt board rate.
  • At this operating point the engine returns 99 % for smt performance efficiency.
  • At this operating point the engine returns 10 hr for smt line runtime.

How this compares with the baseline

  • Against the tool's baseline example, where smt performance efficiency sits at 88% and the headline result is 211 boards / hr, this scenario comes in 12.5% above the baseline at 238 boards / hr.
  • Use it when projecting how many boards a line can deliver over a shift, validating capacity for a new order, or computing the performance component of OEE. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.

Results at a glance

  • Effective SMT board throughput: 238 boards / hr (headline result)
  • Observed SMT board rate: 240 boards / hr
  • SMT performance efficiency: 99 %
  • SMT line runtime: 10 hr

Run it with your numbers

  • Every input above is editable in the live SMT Line Throughput calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.