Radar Level Data for Inventory Management: From Distance to Trusted Volume

Radar measures distance from a reference plane to a product surface. Inventory systems need level, volume and sometimes mass or commercial quantity, so additional geometry, density, temperature and data-quality rules are required. A precise distance does not correct an outdated strapping table, incorrect datum or stale telemetry. The engineering task is to create a traceable chain from echo to transmitter level, PLC value, tank table, inventory record and business decision. Define the required uncertainty and update interval, then assign ownership for configuration, master data and reconciliation rather than treating the radar value as self-validating.

Control the measurement datum

Record antenna reference plane, tank zero, empty distance, blocking distance and usable span. Use the same elevation basis in drawings, transmitter, PLC and inventory software.

Document roof movement, floating-roof position or stilling-well reference where relevant. Small datum errors become systematic inventory bias across every transaction.

Use verified tank geometry

Apply a current strapping or calibration table for irregular tanks rather than a simple cylinder formula. Control units, interpolation and table revision.

Account for dead stock, cone or dish bottoms and inaccessible volume. For solids, surface shape adds uncertainty that a liquid strapping table does not address.

Convert volume to mass carefully

Use product density at a defined temperature and composition. State whether the system reports observed volume, standard volume, mass or an estimate.

Integrate temperature and density data only when their source, update time and validity are known. Do not combine fresh level with old laboratory density without a quality flag.

Preserve data quality and time

Transmit value, engineering units, device status and timestamp. Monitor update age, communication loss, out-of-range values and implausible rates of change.

A gateway or cloud platform should buffer records through outages and distinguish reconstructed data from direct measurements. Stale values must not appear current.

Reconcile operations and inventory

Compare opening balance, receipts, transfers, withdrawals and closing balance over controlled periods. Investigate timing, line contents, temperature, density and table revisions before adjusting the radar.

Use discrepancy trends to find systematic bias or unrecorded movement. Preserve audit trails for configuration and manual overrides.

Validate the complete information chain

Check known levels against transmitter distance, PLC units, converted volume and displayed inventory. Verify alarm and report timestamps across systems.

Record uncertainty and acceptance criteria appropriate to the business use. Revalidate after sensor, datum, tank repair, strapping table, density method or software change.

Assign master-data and reconciliation ownership

Define who may change range, tank table, product density, temperature correction, units and manual inventory adjustments. Require revision history and approval for values that affect reported quantity.

Set reconciliation thresholds and investigation workflow before go-live. Persistent imbalance should trigger checks of timing, line contents, transfers and conversion data rather than an undocumented offset applied to the radar reading. Record the person, reason, source evidence and effective time for every approved correction. A periodic independent review should confirm that accumulated manual changes have not replaced the controlled engineering basis or measurement traceability across reporting periods.

Engineering checklist

• Use one controlled elevation datum.
• Verify tank-table revision and units.
• Define density and temperature basis.
• Transmit quality and timestamp with value.
• Reconcile movements before recalibration.
• Test the full echo-to-inventory chain.

Frequently asked questions

Does radar directly measure tank volume?

No. It measures distance; tank geometry or a strapping table converts level to volume.

Why can inventory be wrong when level is stable?

Datum, tank table, density, temperature, timing or stale-data errors can affect the converted quantity.

What data should be stored?

Store value, units, timestamp, quality status, configuration revision and the conversion-table version.

Related measurement solutions

80 GHz radar level meters · Industrial IoT gateways