Polling vs report-by-exception in SCADA systems - Key Differences Explained

Introduction

Imagine trying to keep track of many machines in a factory. You need to know when something changes or goes wrong, but checking every machine all the time can be slow and waste resources. This is where two ways of getting updates come in: polling and report-by-exception.

Explanation

Polling

Polling means the control system regularly asks each device for its current status, even if nothing has changed. This happens at fixed time intervals, like every few seconds. It ensures the system always has up-to-date information but can create a lot of unnecessary communication if changes are rare.

Polling constantly checks devices at set times, whether or not there is new information.

Report-by-exception

Report-by-exception means devices only send updates when something important changes, like a sensor reading crossing a threshold. Instead of asking repeatedly, the system waits for these special messages. This reduces communication and speeds up response to real changes but depends on devices to detect and report exceptions correctly.

Report-by-exception sends updates only when significant changes happen, reducing unnecessary checks.

Real World Analogy

Think of a teacher who either calls on every student every minute to ask if they have questions (polling), or waits for students to raise their hands only when they need help (report-by-exception). The first way uses more time but guarantees no question is missed; the second saves time but relies on students to speak up.

Polling → Teacher asking every student regularly if they have questions

Report-by-exception → Students raising their hands only when they need help

Diagram

Diagram

┌───────────────┐       ┌───────────────┐
│ Control System│──────▶│ Device 1      │
│ (Polls every │       │ (Responds with │
│  fixed time) │       │  current data) │
└───────────────┘       └───────────────┘
       │                      ▲
       │                      │
       │                      │
       │                      │
       │                      │
       ▼                      │
┌───────────────┐             │
│ Control System│◀────────────┘
│ (Waits for    │
│  exception    │
│  reports)     │
└───────────────┘
       ▲
       │
       │
┌───────────────┐
│ Device 2      │
│ (Sends update │
│  only on      │
│  change)      │
└───────────────┘

Diagram showing control system polling devices regularly versus waiting for devices to send updates only on changes.

Key Facts

Polling → A method where the control system regularly requests data from devices at fixed intervals.

Report-by-exception → A method where devices send data only when a significant change or event occurs.

Communication overhead → The amount of data exchanged between devices and control system, which is higher in polling.

Responsiveness → How quickly the system learns about changes; report-by-exception can be faster for important events.

Common Confusions

Polling always provides faster updates than report-by-exception.

Polling always provides faster updates than report-by-exception. Report-by-exception can provide faster updates for important changes because devices send updates immediately when events occur, while polling waits for the next scheduled check.

Report-by-exception means the control system never asks for data.

Report-by-exception means the control system never asks for data. The control system may still poll occasionally to verify status, but report-by-exception reduces the need for constant polling.

Summary

Polling means regularly asking devices for data, which ensures updates but can waste resources.

Report-by-exception means devices send updates only when important changes happen, saving communication.

Choosing between polling and report-by-exception depends on the system's need for timely updates and communication limits.