Pressure Anomalies

Pressure channel (P, kPa) anomalies in the hourly archive — outage, critical and low levels, sharp drops, baseline drift and instability, with an events table.

A report for a single metering node: it analyzes what happened to the pressure in the pipe (channel P, measured in kilopascals, kPa) over the selected period. Operations and the monitoring service use it to catch data loss, pressure drops, and unstable sensor behavior in time.

The report takes the hourly pressure record from the device archive and checks it for five types of problems, then shows a summary and a table of all detected events, with the option to expand the hourly detail for each.

What it shows

Problem	What it means
Data loss	the device failed to transmit pressure for several hours in a row (empty or zero)
Critical / low level	pressure dropped below a set threshold
Sharp drop	pressure fell quickly over a few hours
Baseline drift	pressure slowly but steadily slides in one direction over the period
Instability	pressure “jitters” heavily, with spread higher than usual

In addition, if the device passport defines pressure limits (Pmax / Pmin for the relevant corrector types), the report separately flags excursions beyond these physical limits — always critical.

Detected events are matched against the device service-event log (tampering, reading substitution, and similar entries). If a pressure drop coincided with such an entry, it is visible in the table.

How it works

The data source is the device’s hourly archive. The pressure channel P is taken from it. Each hour is checked against simple rules:

Problem	Rule (default)
Data loss	empty or zero for ≥ 4 hours in a row
Low level	pressure below 50 kPa
Critical level	pressure below 20 kPa
Sharp drop	drop of ≥ 30 % over 3 hours
Drift	baseline shift of ≥ 10 kPa over a 7-day window
Instability	spread over a 24-hour window three times higher than usual

All thresholds are configurable via run parameters (see below). The method is a set of clear hourly rules, with no complex models; this keeps the result transparent and explainable.

Run parameters

Parameter	Default	What it means
Node #	required	the metering node number
Period from	30 days ago	start of the analysis period
Period to	yesterday	end of the period
Low threshold	50 kPa	”low” pressure threshold
Critical threshold	20 kPa	”critical” pressure threshold
Drop percentage	30 %	what drop counts as sharp
Drop hours	3 h	over how many hours that drop occurs
Outage hours	4 h	how many hours without data count as data loss

How to read the result

Look first at the summary at the top: red counters (critical level, data loss) are grounds for adding the node to the field-visit plan.
Data loss: up to 2 hours — normal; 13–72 hours — check the pressure sensor; more than 72 hours — replace or recalibrate urgently.
A sharp drop coinciding with an entry in the service-event log is grounds for an on-site check: it could be either a service event or tampering.
Baseline drift over a long period more often indicates a need for calibration; over a short one, it may be just a seasonal change.