Polling vs report-by-exception in SCADA systems - When to Use Which

The Big Idea

What if your system could tell you only when something really matters, saving you hours of useless waiting?

The Scenario

Imagine you are monitoring a factory's machines by constantly checking each one every few seconds to see if it is working fine or if something went wrong.

The Problem

This constant checking, called polling, wastes time and computer power because you keep asking even when nothing has changed. It can also miss quick problems if the checks are too far apart.

The Solution

Report-by-exception means machines only send a message when something important happens, like a warning or failure. This saves time and lets you focus on real problems immediately.

Before vs After

✗ Before

while True:
  check_all_machines()
  sleep(5)

✓ After

def on_machine_event(event):
  handle_event(event)

What It Enables

This approach lets you get instant alerts only when needed, making monitoring faster, smarter, and less tiring for your system.

Real Life Example

In a power plant, instead of checking every sensor all the time, sensors send alerts only if temperature or pressure goes beyond safe limits, so operators can act quickly.

Key Takeaways

Polling checks everything repeatedly, wasting resources.

Report-by-exception sends updates only on important changes.

This makes monitoring efficient and responsive.