How do you calculate machine connectivity rate?

Divide machines reporting live data in the last polling window by total connectable machines and multiply by 100. With 118 of 125 machines reporting, the rate is 118 / 125 x 100 = 94.4%.

What is a good live machine connectivity rate?

Production-grade data collection usually targets 97% or higher so OEE and downtime data stay trustworthy. The example sits at 94.4% against a 97% target, a 2.6-point gap that equals roughly 3 machines currently not reporting.

What does the connectivity gap to target mean?

It is the target rate minus the actual rate in points. Here 97% minus 94.4% is a 2.6-point gap, signaling a handful of machines, about 3 of 125, that need attention before the next shift review.

Why measure per polling window instead of cumulatively?

A live, windowed measure catches machines that have gone dark right now, which is what threatens real-time dashboards and alerts. A cumulative figure would mask a machine that connected last week but stopped reporting this morning.

Machine connectivity rate vs edge gateway coverage?

Connectivity rate is an uptime view of whether expected machines are reporting live, while edge gateway coverage is a rollout view of whether assets are connected at all. A line can be 100% covered yet drop to 90% live if a switch fails.

What causes a low connectivity rate?

Common culprits are an offline edge gateway, a dropped network segment, a powered-down machine, a stalled OPC server, or a polling timeout set too tight. Start by checking whether the missing machines cluster on one gateway or subnet.

IIoT, SCADA & Edge Connectivity calculator

Machine Connectivity Rate Calculator

Live machine connectivity rate is the share of connectable machines that actually reported data in the most recent polling window, a real-time health metric for your shop-floor data collection. Manufacturing IT and OT teams watch it to catch dropped connections, offline gateways, and stale data sources before they corrupt OEE dashboards or starve predictive models. Unlike a one-time rollout metric, it answers a daily operational question: of the machines we expect to hear from right now, how many are we actually hearing from? A small gap to target often points at one rack of machines on a flaky network segment rather than a systemic failure.

What this calculator does

Estimate the share of plant machines that are publishing live data right now from the count of machines actively reporting against the total connectable machines, against the program target.
Use it when an OT manager or plant manager needs a clean live-connectivity number for the morning meeting board, separate from the slower edge gateway deployment view.
It computes the percentage of connectable machines reporting live in the latest polling window and the point gap to your live connectivity target.

Formula used

Live machine connectivity rate = machines reporting ÷ total connectable machines × 100
Connectivity gap to target = target rate - actual rate (negative gap means below target)

Inputs explained

Machines reporting live data in the last polling window:
Total connectable machines:
Live connectivity target:

How to use the result

Use it as a daily or shift operational check on data-collection health, not just during initial rollout.
It reflects the latest polling window only, so a transient network blip can dip the number even when the underlying integration is sound.

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 connectivity rate? Divide machines reporting live data in the last polling window by total connectable machines and multiply by 100. With 118 of 125 machines reporting, the rate is 118 / 125 x 100 = 94.4%.
What is a good live machine connectivity rate? Production-grade data collection usually targets 97% or higher so OEE and downtime data stay trustworthy. The example sits at 94.4% against a 97% target, a 2.6-point gap that equals roughly 3 machines currently not reporting.
What does the connectivity gap to target mean? It is the target rate minus the actual rate in points. Here 97% minus 94.4% is a 2.6-point gap, signaling a handful of machines, about 3 of 125, that need attention before the next shift review.
Why measure per polling window instead of cumulatively? A live, windowed measure catches machines that have gone dark right now, which is what threatens real-time dashboards and alerts. A cumulative figure would mask a machine that connected last week but stopped reporting this morning.
Machine connectivity rate vs edge gateway coverage? Connectivity rate is an uptime view of whether expected machines are reporting live, while edge gateway coverage is a rollout view of whether assets are connected at all. A line can be 100% covered yet drop to 90% live if a switch fails.

Last reviewed 2026-05-12.