How do you calculate machine data completeness?

Divide the number of machines sending complete data feeds by the total machines in MES scope, then multiply by 100. With 38 of 45 machines fully connected, that is (38 / 45) x 100 = 84.4%.

What is a good machine data completeness rate?

For production-grade MES reporting, aim for 95%+ before trusting plant-wide OEE. The default here lands at 84.4% against a 95% target, leaving a 10.6-point gap — fine for a pilot, not yet ready for plant KPIs.

Why does the gap to target matter more than the raw rate?

The gap tells you how much connectivity work remains. At 84.4% versus a 95% target you are 10.6 points short, which with 45 machines is about 5 more machines to bring fully online.

Does 100% completeness mean my MES data is reliable?

No. Completeness only confirms each machine has a complete feed at the moment of measurement. It says nothing about tag accuracy, timestamp drift, or mid-shift dropouts, so pair it with a data-quality audit.

Completeness rate vs data quality score — what's the difference?

Completeness asks 'are the machines connected and sending all expected fields?' Quality asks 'is the data they send correct?' You can hit 95% completeness and still have bad cycle-time tags; both metrics are needed.

How many machines do I need to connect to hit my target?

Multiply target rate by total in scope: 0.95 x 45 = 42.75, so 43 machines. You currently have 38 complete, meaning 5 more machines need full feeds to reach 95%.

MES, MOM & Shop-Floor Data Systems calculator

Machine Data Completeness Calculator

Machine data completeness measures the share of machines in your MES scope that are actually streaming complete, usable data — cycle counts, states, alarms, and process tags — versus the total you intended to connect. MES and digital-manufacturing leads use it as the gating metric for any OEE, downtime, or analytics rollout, because dashboards built on partial feeds quietly mislead. A line showing 84% completeness means roughly one in six machines is dark or sending gaps, and every report that aggregates across them is biased. Tracking this rate against an explicit target keeps a connectivity project honest as it scales from a pilot cell to the whole plant.

What this calculator does

Measure what percentage of connected machines have complete data feeds with all required tags reporting, and identify the gap to your completeness target.
Use after initial MES connectivity to audit which machines still have missing or intermittent data tags, so you can prioritize remediation before relying on the data for OEE or analytics.
It computes the percentage of in-scope machines that have complete MES data feeds and the gap in points to your completeness target.

Formula used

Completeness rate = (machines with complete feeds / total machines in scope) x 100
Gap to target = completeness rate - target completeness rate

Inputs explained

Machines with complete data feeds:
Total machines in MES scope:
Target completeness rate:

How to use the result

Use it during an MES or IIoT connectivity rollout and in weekly data-health reviews to decide whether your OEE and downtime numbers are trustworthy yet.
A machine counted as 'complete' here is binary — it does not measure feed quality, sampling rate, or how often a connected machine drops out intra-shift, so a high rate can still hide flaky tags.

Common questions

How do you calculate machine data completeness? Divide the number of machines sending complete data feeds by the total machines in MES scope, then multiply by 100. With 38 of 45 machines fully connected, that is (38 / 45) x 100 = 84.4%.
What is a good machine data completeness rate? For production-grade MES reporting, aim for 95%+ before trusting plant-wide OEE. The default here lands at 84.4% against a 95% target, leaving a 10.6-point gap — fine for a pilot, not yet ready for plant KPIs.
Why does the gap to target matter more than the raw rate? The gap tells you how much connectivity work remains. At 84.4% versus a 95% target you are 10.6 points short, which with 45 machines is about 5 more machines to bring fully online.
Does 100% completeness mean my MES data is reliable? No. Completeness only confirms each machine has a complete feed at the moment of measurement. It says nothing about tag accuracy, timestamp drift, or mid-shift dropouts, so pair it with a data-quality audit.
Completeness rate vs data quality score — what's the difference? Completeness asks 'are the machines connected and sending all expected fields?' Quality asks 'is the data they send correct?' You can hit 95% completeness and still have bad cycle-time tags; both metrics are needed.

Last reviewed 2026-05-12.