OEE & Factory Performance worked example

Factory Data Capture Rate at 68% target capture rate: a worked example

Here is what the math looks like when conditions slip. We hold every other input steady and drop target capture rate to 68%, then walk the calculation through step by step. Calculate data capture rate for OEE & Factory Performance: automatically captured transactions as a share of all transactions.

The inputs for this scenario

  • Auto-captured transactions: 880 transactions (held at the documented default)
  • Total transactions: 1,000 transactions (held at the documented default)
  • Target capture rate: 68 % (the input this scenario stresses; the baseline uses 95)

Working through the calculation

  • The calculation starts from the formula this tool documents: Data capture rate = auto-captured transactions ÷ total transactions × 100.
  • Data capture rate works out to 88 % at these inputs, and this is the headline figure for the scenario.
  • Gap to target works out to -20 points at these inputs.
  • Auto-captured transactions works out to 880 count at these inputs.
  • Total transactions works out to 1,000 count at these inputs.

How this compares with the baseline

  • Against the tool's baseline example, where target capture rate sits at 95% and the headline result is 88 %, this scenario lands almost exactly on the baseline at 88 %.
  • The practical read: the gap between this scenario and the baseline is entirely attributable to target capture rate, so recovering it is worth quantifying in dollars before considering equipment or staffing changes. A high capture rate says nothing about data accuracy; a sensor can auto-capture a wrong reading just as a human can mistype one.

Results at a glance

  • Data capture rate: 88 % (headline result)
  • Gap to target: -20 points
  • Auto-captured transactions: 880 count
  • Total transactions: 1,000 count

Run it with your numbers

  • To rerun this with your own numbers, open the live Factory Data Capture Rate calculator, set target capture rate to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.