Additive Manufacturing worked example

Parts Per Build at 99% machine uptime: a worked example

This scenario runs the parts per build calculation on the strong side: 99% machine uptime, with every other input held at its documented default. a production manager needs expected good part output from one machine or process window

The inputs for this scenario

  • Nested parts per build: 38 parts / build (unchanged)
  • Available build runs: 5 builds (unchanged)
  • Machine uptime: 99 % (raised for this scenario; the documented default is 92)
  • Expected print yield: 96 % (unchanged)

Working through the calculation

  • Applying the documented formula (Gross parts = nested parts per build × available builds) to the inputs above produces each figure below.
  • At this operating point the engine returns 181 parts for good parts expected, the number this scenario is built around.
  • At this operating point the engine returns 190 parts for gross nested parts.
  • At this operating point the engine returns 1.9 parts for machine downtime loss.
  • At this operating point the engine returns 7.52 parts for failed or rejected parts.

How this compares with the baseline

  • Against the tool's baseline example, where machine uptime sits at 92% and the headline result is 168 parts, this scenario comes in 7.61% above the baseline at 181 parts.
  • Use it when committing delivery quantities, sizing overbuild, or checking whether available builds can meet an order. 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

  • Good parts expected: 181 parts (headline result)
  • Gross nested parts: 190 parts
  • Machine downtime loss: 1.9 parts
  • Failed or rejected parts: 7.52 parts

Run it with your numbers

  • Every input above is editable in the live Parts Per Build calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.