IIoT, SCADA & Edge Connectivity calculator

Machine Data Capture Rate Calculator

Estimate the share of machines fully captured. Enter the count of machines reporting all required tags to the historian or MES, the total connected machines in scope, and the capture target. The calculator returns capture rate and the gap to target.

What this calculator does

  • Estimate the share of machines whose data is fully captured to the historian or MES from the count of machines with full capture against the total connected machines, against a capture target.
  • Use it when an OEE or analytics lead needs to know how many machines are reporting all required tags (not just one heartbeat), before publishing a plant-wide OEE or scrap dashboard.
  • It returns the share of connected machines reporting their full required tag set and the gap to the OEE program target.

Formula used

  • Machine data capture rate = machines fully reporting ÷ total connected machines × 100
  • Capture gap to target = target rate - actual rate

Inputs explained

  • Machines with all required tags reporting: Use the count of machines whose required tag set (state, cycle, reject, downtime reason) is all reporting fresh in the historian or MES.
  • Total connected machines in scope: Use the count of connected machines in OEE or MES scope from the asset register.
  • Machine data capture target: Use the program target (typical 95 to 99 percent for mature OEE programs; below 90 percent triggers a tag fix sprint).

How to use the result

  • Use it on the OEE program board, before publishing a plant-wide OEE roll-up, or when a downtime reason dashboard has too many empty cells.
  • It treats capture as binary per machine. A machine missing one downtime reason tag still counts as not-fully-reporting; if you need partial credit, build a per-tag completeness view with the OT data completeness calculator.

Common questions

  • What is the required tag set? Whatever the OEE or MES program defined: state, cycle, reject, planned vs. unplanned downtime reason, operator ID, and recipe. The set is plant-specific; use the agreed list.
  • Why binary? An OEE roll-up needs every required tag to compute. A machine missing one tag breaks the calc, so binary capture is the operational truth.
  • What target is realistic? 95 to 99 percent for mature OEE programs. Below 90 percent usually means tags are mis-mapped, the PLC is missing the logic, or operators are not entering downtime reasons.
  • How is this different from machine connectivity rate? Connectivity rate asks did the machine report at all. Capture rate asks did the machine report everything required. Capture is always equal to or lower than connectivity.

Last reviewed 2026-05-12.