IIoT, SCADA & Edge Connectivity calculator

Telemetry Event Rate Calculator

Estimate telemetry event delivery rate. Enter the count of events delivered to the broker or historian in the period, the expected event count for the period, and the delivery target. The calculator returns the delivery rate and the gap to target.

What this calculator does

  • Estimate telemetry event delivery rate from events delivered to the broker or historian against events expected for the period, against a delivery target.
  • Use it when an OT data ops or analytics lead is verifying that telemetry events (machine cycle, batch step, alarm) are landing at expected volume before signing off on a model rebuild or cutover.
  • It returns the share of telemetry events that landed on the broker or historian against expected, and the gap to the data ops SLA.

Formula used

  • Telemetry event delivery rate = events delivered ÷ events expected × 100
  • Delivery gap to target = target rate - actual rate (negative gap means below target)

Inputs explained

  • Telemetry events delivered in the period: Use the count of events landed on the broker or historian (machine cycle events, batch step events, alarm events, or vision frame events).
  • Telemetry events expected in the period: Use expected count from machines actually running times their per-machine event rate, or from the production schedule.
  • Telemetry delivery target: Use the delivery target from the data ops SLA (typical 99.5 to 99.99 percent for production telemetry).

How to use the result

  • Use it on the data ops dashboard, before a model rebuild, or any time analytics output looks suspicious because of missing events.
  • It only sees what the broker or historian counter sees. Events lost upstream of the gateway (PLC scan misses, sensor read failures) need a different counter; pair with PLC data availability.

Common questions

  • How do I get expected event count? Multiply machines actually running by the per-machine event rate (cycle events per hour, alarm events per hour). For batch processes, use the recipe step count times batches run.
  • What target is realistic? 99.5 to 99.99 percent on a healthy plant. Below 99 percent usually means broker session drops, store-and-forward backlog, or PLC scan misses.
  • Can the rate exceed 100 percent? Yes, if expected count is wrong (machines ran longer than scheduled or duplicated events). Reset the expected basis before publishing the number above 100 percent.
  • How is this different from OT data completeness? Telemetry event rate counts discrete events (cycles, alarms, frames). OT data completeness counts polled tag samples. Use both for the right architecture.

Last reviewed 2026-05-12.