Radar Level Data in SCADA: Architecture, Quality and Acceptance

A SCADA screen showing a radar level value does not prove a reliable remote measurement. The information chain includes the echo, transmitter calculation, analog or digital output, PLC or RTU register, communications network, historian, alarm engine and operator display. Errors in scaling, byte order, timestamp, quality handling or stale-data logic can make a healthy sensor appear wrong—or make failed data appear current. The project must define the operational purpose, update interval, failure response and evidence required from the field instrument through every system layer.

Define the data contract

List every required point: raw distance, level, volume, temperature, signal quality, device status, alarm state and communication health. Specify engineering units, decimal resolution, valid range and update rate for each value.

Identify the system of record and whether conversions occur in the radar, RTU or SCADA. Duplicated scaling in several layers creates conflicting values and makes later troubleshooting difficult.

Select and document the interface

For 4–20 mA, define live-zero scaling, fault current and loop power. For Modbus RTU, document address, baud rate, parity, register map, data type, byte order and polling limits.

For HART, fieldbus or gateway connections, record supported variables and status mapping. Confirm that the chosen interface exposes the diagnostics needed by operations rather than only the primary value.

Preserve time and data quality

Transmit or assign a trustworthy timestamp close to acquisition. Monitor update age and flag stale values after a defined interval; a repeated last value must not appear to be a fresh measurement.

Map instrument faults, lost echo, maintenance state and communication loss into explicit SCADA quality. Do not replace invalid data with zero or silently hold it without an alarm and visible quality indication.

Design for communications outages

Define local buffering, backfill order and duplicate handling when a remote link returns. Mark reconstructed or delayed records so analysts can distinguish them from real-time data.

Critical pump or overfill protection should remain local and effective without the WAN, cloud service or central server. SCADA is supervision, not a substitute for required independent protection.

Apply practical cybersecurity

Use controlled device addresses, authenticated remote access, least privilege and an approved path for configuration changes. Separate monitoring from write access unless remote control is specifically justified.

Record firmware, configuration backups and change history. A cybersecurity update that changes polling, gateway mapping or time synchronization requires functional revalidation of the measurement path.

Test end to end

Apply known or simulated levels and compare transmitter display, loop or register value, RTU, SCADA, historian and alarm event. Test units, rounding, timestamps and values near both ends of range.

Interrupt sensor power and communications separately. Verify quality flags, alarm delay, local control continuity, buffering and recovery, then store signed results with the final register and tag database.

Define operational ownership

Assign owners for the field radar, RTU, network, SCADA tags, alarm response and historian. Establish a review interval for stale-data events, communication retries and unexplained inventory differences. When a value is disputed, the investigation should preserve the raw distance, device status, register or current, gateway timestamp and displayed result from the same period. This evidence prevents separate teams from correcting their own layer independently and creating a new mismatch elsewhere in the information chain.

Engineering checklist

• Define every value, unit and owner.
• Control analog scaling or the digital register map.
• Carry timestamps and quality with measurements.
• Keep protection effective during network loss.
• Restrict and record remote configuration access.
• Test faults and recovery through the complete chain.

Frequently asked questions

Is the displayed level enough for acceptance?

No. Acceptance must also verify quality, timestamp, alarms, history and failure behaviour.

Should SCADA calculate tank volume?

It may, but the tank table, datum, units and revision must be controlled and traceable.

What happens when communications fail?

The value should become visibly stale or invalid while local control and required protection continue safely.

Related measurement solutions

80 GHz radar level meters · Industrial IoT gateways