IIoT, SCADA & Edge Connectivity worked example

Dashboard Refresh Latency at 110% analytics and historian server uptime: a worked example

Push analytics and historian server uptime up to 110% and the picture changes. This example computes every intermediate figure at that operating point. Use it when an OT data ops or analytics platform lead is sizing how many dashboards an analytics server (PI Vision, AVEVA Insight, Grafana, Power BI gateway) can keep refreshed cleanly.

The inputs for this scenario

  • Dashboards refreshed per polling thread per minute: 10 dashboards / min (unchanged)
  • Planned refresh window in the period: 480 min (unchanged)
  • Analytics / historian server uptime: 110 % (raised for this scenario; the documented default is 99)
  • Refreshes completing inside SLA: 95 % (unchanged)

Working through the calculation

  • Applying the documented formula (Gross dashboard refresh capacity = dashboards per minute × planned minutes) to the inputs above produces each figure below.
  • At this operating point the engine returns 5,016 dashboards for dashboards delivered inside sla, the number this scenario is built around.
  • At this operating point the engine returns 4,800 dashboards for gross dashboard refresh capacity.
  • At this operating point the engine returns -480 dashboards for server downtime loss.
  • At this operating point the engine returns 264 dashboards for sla miss loss.

How this compares with the baseline

  • Against the tool's baseline example, where analytics and historian server uptime sits at 99% and the headline result is 4,514 dashboards, this scenario comes in 11.11% above the baseline at 5,016 dashboards.
  • It computes how many dashboard refreshes are delivered inside SLA from a thread refresh rate, the planned refresh window, server uptime and the share of refreshes meeting the latency target. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Dashboards delivered inside SLA: 5,016 dashboards (headline result)
  • Gross dashboard refresh capacity: 4,800 dashboards
  • Server downtime loss: -480 dashboards
  • SLA miss loss: 264 dashboards

Run it with your numbers

  • Every input above is editable in the live Dashboard Refresh Latency calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.