How do you calculate machine data capture rate?

Divide the machines with all required tags reporting by the total connected machines in scope and multiply by 100. With 58 of 62 machines fully reporting, the capture rate is 93.55%.

What is a good machine data capture rate?

For analytics you can trust, aim for 95% or higher, with 98%+ on the machines feeding OEE and downtime reporting. The example's 93.55% falls 1.45 points short of a 95% target, so a handful of machines still need attention.

What does the capture gap to target mean?

It is the difference between your target and your actual rate in percentage points. Here a 95% target minus a 93.55% actual leaves a 1.45-point gap, which with 62 machines is roughly one more machine that needs all its tags reporting.

Why use full-reporting instead of counting individual tags?

A machine missing even one required tag can break OEE or traceability calculations, so this metric counts a machine only when every required tag reports. It is stricter than a tag-level percentage and better reflects whether you can trust per-machine analytics.

Capture rate vs connectivity rate?

Connectivity rate just confirms a machine is networked; capture rate confirms it is actually delivering all required data. A machine can be 100% connected yet 0% captured if its tags are misconfigured, which is why capture rate is the metric that matters for analytics.

How do I close the gap to target?

Identify the specific machines not fully reporting, then fix the usual culprits: missing or renamed tags, broken OPC mappings, offline edge gateways and timed-out polls. In the example, getting one or two of the four lagging machines fully reporting closes most of the 1.45-point gap.

IIoT, SCADA & Edge Connectivity calculator

Machine Data Capture Rate Calculator

Machine Data Capture Rate measures what fraction of your connected machines are reliably reporting every required tag to the SCADA, MES or IIoT platform. It is the practical health metric behind any analytics or OEE program, because a dashboard is only as trustworthy as the data feeding it. Controls engineers, MES administrators and digital manufacturing teams track this rate to find machines that are connected on paper but silently dropping tags. The calculator also returns the gap to your target so you can see exactly how far short of the standard you are before stakeholders rely on the numbers.

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 computes the percentage of connected machines that have all required tags reporting, then the point gap between that rate and your 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:
Total connected machines in scope:
Machine data capture target:

How to use the result

Use it during and after an IIoT rollout to verify coverage before trusting OEE, downtime or quality analytics built on the data.
It counts a machine as captured only if all required tags report, so it does not credit partial capture; a machine missing one minor tag scores the same as one that is fully dark.

Current U.S. benchmarks

Global copper trades at $13,484 per tonne (IMF via FRED, May 2026), up 41.5% in a year, and U.S. industrial electricity averages 8.66 cents per kWh. Both feed electrified-hardware unit economics.

Common questions

How do you calculate machine data capture rate? Divide the machines with all required tags reporting by the total connected machines in scope and multiply by 100. With 58 of 62 machines fully reporting, the capture rate is 93.55%.
What is a good machine data capture rate? For analytics you can trust, aim for 95% or higher, with 98%+ on the machines feeding OEE and downtime reporting. The example's 93.55% falls 1.45 points short of a 95% target, so a handful of machines still need attention.
What does the capture gap to target mean? It is the difference between your target and your actual rate in percentage points. Here a 95% target minus a 93.55% actual leaves a 1.45-point gap, which with 62 machines is roughly one more machine that needs all its tags reporting.
Why use full-reporting instead of counting individual tags? A machine missing even one required tag can break OEE or traceability calculations, so this metric counts a machine only when every required tag reports. It is stricter than a tag-level percentage and better reflects whether you can trust per-machine analytics.
Capture rate vs connectivity rate? Connectivity rate just confirms a machine is networked; capture rate confirms it is actually delivering all required data. A machine can be 100% connected yet 0% captured if its tags are misconfigured, which is why capture rate is the metric that matters for analytics.

Last reviewed 2026-05-12.