Tank Radar Level Site Approval: Application and Risk Review

Site approval should show that the selected tank radar is suitable for the actual duty and that its limitations are managed. A radar proven on clean ambient liquid may not be suitable for a pressurized, condensing, foaming or hazardous tank with a long nozzle. Likewise, an accurate process measurement is not automatically an independent overfill safeguard. Approval should bring process, mechanical, instrumentation, control and safety evidence into one decision record and define which changes require the application to be reviewed again.

State the operational purpose

Define whether level is used for indication, automatic control, inventory, transfer, high alarm or environmental reporting. Set range, accuracy, response, availability and failure consequence from the purpose. Identify any independent high-high or low-low function and keep its design and proof testing separate from the process transmitter.

Characterize process conditions

Record product and cleaning fluids, dielectric behaviour, temperature, pressure, vapour, foam, condensation, coating, agitation and abnormal states. For changing recipes, define the full approved envelope. Compatibility and echo claims should cite evidence for the exact antenna and seal rather than broad technology statements.

Verify tank geometry

Measure reference plane, zero, empty distance, nozzle, maximum level, internals, inlet and outlet. Check the beam across the operating range and review floating roofs, stilling wells or moving structures. Reconcile drawings with the as-built tank and record any inaccessible assumptions as limitations.

Assess failure and overfill risk

Identify credible false-low, false-high, frozen and lost-signal causes. Calculate alarm and shutdown response against maximum fill rate and remaining freeboard. Confirm invalid-value behaviour in the control system. Where consequence requires independent protection, assess common power, logic, mounting and maintenance failures.

Confirm integration and maintainability

Verify supply, output, barriers, communication, units, quality mapping, alarms and final actions. Ensure the antenna and electronics can be inspected or replaced safely. Set initial inspection from buildup, corrosion, weather and consequence, then revise it using documented as-found evidence.

Approve with controlled evidence

The approval package should include application data, exact model, drawings, certificates, compatibility basis, configuration, echo curves and acceptance method. List residual limitations, owners and review triggers. Reopen approval after product, range, fill rate, nozzle, control duty, firmware or protection changes.

Set decision ownership

Assign a named owner for process data, geometry, instrument selection, control integration and overfill protection. The final approver should verify that each discipline's evidence uses the same reference levels and operating envelope. Record disagreements and their resolution rather than averaging incompatible assumptions. If approval depends on supplier application experience or a future high-level test, state the evidence, boundary and interim control. Periodically review open assumptions until they are closed. This governance prevents a site approval from becoming a signature collected without responsibility for the actual measurement and risk decision.

Approval conditions

A site approval may be unconditional, conditional on defined actions, or rejected pending missing evidence. Conditional approval should name the action, owner, due date, operating restriction and verification method; vague notes such as monitor during operation are not sufficient. Confirm that temporary controls are visible to operators. Close each condition after evidence review and retain it with the application file. This approach keeps schedule decisions transparent without turning unresolved measurement or overfill risk into a permanent undocumented operating practice.

Engineering checklist

• Define purpose and consequence.
• Record the full process envelope.
• Verify as-built geometry and beam.
• Assess faults, fill rate and freeboard.
• Confirm integration and safe maintenance.
• Store limitations and reapproval triggers.

Frequently asked questions

Is radar approval transferable between tanks?

Only when geometry, process, duty, environment and protection requirements are demonstrably equivalent.

Can the process radar be the high-high trip?

Only if the risk assessment and required independence support that architecture.

What should trigger reapproval?

Changes affecting product, geometry, range, filling, firmware, control logic or safety duty.

Related measurement solutions

80 GHz radar level meters · Guided-wave radar level meters