Radar Level Retrofit for Tank Farms: Standardization and Migration Planning

A tank-farm radar retrofit is a portfolio project, not a repeated single-instrument replacement. Tanks may differ in height, roof, nozzle, stilling well, product, pressure, hazardous classification, temperature and inventory method. Standardization can reduce spares and training, but forcing one antenna or configuration onto every vessel creates hidden failures. The project should classify tanks into verified application groups, preserve historical inventory and alarm behavior, and stage cutover without losing operational visibility. Each installation still requires its own reference datum, configuration and acceptance record within a common engineering framework.

Build a tank-by-tank asset register

Record tag, service, dimensions, roof type, nozzle, internals, range, old model, output, approvals, configuration and failure history. Photograph every mounting location.

Identify tanks with floating roofs, stilling wells, agitators, low dielectric products, foam, condensation or pressure. These features create separate design classes.

Define sensible standardization

Standardize enclosure, communication, display, configuration naming and spare philosophy where conditions permit. Select antenna and process connection by verified application group.

Document exceptions rather than hiding them. A specialist device for a difficult tank is preferable to a common model that has inadequate signal or certification.

Control datum and inventory continuity

Establish the reference plane, tank zero, empty distance and usable span for every vessel. Reconcile them with strapping tables and the inventory system.

Archive pre-change readings and configuration. Plan how historical trends, alarms and reports remain comparable after a reference or linearization change.

Stage installation and cutover

Group work by operating availability, isolation needs, scaffolding, weather and hazardous permits. Define temporary indication and rollback for critical tanks.

Verify mechanical and electrical readiness before shutdown. Do not discover incompatible nozzles, glands or barriers after the tank has been released for work.

Verify network and alarm integration

Test HART, fieldbus, RS485 or analog scaling, tag mapping, timestamps and quality status. Confirm cybersecurity and address management for connected devices.

Prove high and low alarms, fault current, lost echo and communication loss. Independent overfill protection must remain effective during migration.

Create repeatable acceptance evidence

Use one checklist for drawings, model code, installation, echo curve, known level, PLC value, inventory conversion, alarms and documentation. Store results by tank tag.

Review early operating data across fill and transfer cycles before closing each group. Feed lessons into later tanks without changing accepted units informally.

Govern project-wide changes and exceptions

Use a controlled design register for standard settings, approved alternatives and tank-specific deviations. Changes discovered during one installation should be assessed for applicability before being copied to the rest of the farm.

Track completion by verified function rather than installed device count. A tank is not complete until measurement, inventory conversion, alarms, communications, documents and operator handover all meet the agreed acceptance criteria. Review unresolved exceptions before each deployment wave and assign an owner, risk classification and closure date. Do not allow schedule pressure to turn a temporary workaround into the undocumented standard for later tanks, operating shifts or future projects.

Engineering checklist

Create a complete asset register.
Standardize only within proven application groups.
Control each tank datum and strapping table.
Stage cutover with temporary visibility.
Test network quality and independent alarms.
Store acceptance evidence by tank.

Frequently asked questions

Can one radar model cover every tank?

Only if each tank’s geometry, product, range, pressure, temperature and certification are within the verified application envelope.

How is inventory continuity protected?

Archive old data, control reference changes and reconcile new values against strapping tables and known levels.

What should be standardized?

Common interfaces, documentation and spares can be standardized while antennas and process connections remain application-specific.

Need a project-specific review? Send process data, drawings, photographs and acceptance criteria through our contact page.