Turning readings into information.
WHAT PROCESSING TYPICALLY DOES
Converts raw values to meaningful units Applies calibration Filters noise Detects thresholds and anomalies Aggregates across devices Triggers actions
WHAT TO DO AT THE DEVICE
Whatever reduces transmission meaningfully.
WHAT TO DO AT THE PLATFORM
Anything requiring data from several devices, or history.
WHY THAT DIVISION
Devices cannot see beyond themselves.
WHAT RULE ENGINES PROVIDE
Conditions and actions configured rather than programmed.
WHAT THEY SUIT
Threshold alerts and simple routing.
WHAT THEY DO NOT SUIT
Complex logic, which becomes unmanageable as rules multiply.
WHAT STREAM PROCESSING PROVIDES
Windowed aggregation, joins between streams, and stateful detection.
WHAT TO BE CAREFUL WITH
Readings arriving late, after their window closed Duplicate messages Out-of-order arrival
WHY THAT MATTERS MORE HERE THAN ELSEWHERE
Devices buffer during outages and then transmit history, so late data is normal.
WHAT TO PROCESS BY
Event time, not arrival time.
WHAT TO VALIDATE
That derived values remain plausible.
WHAT TO ALERT ON
Processing falling behind ingestion.
