Silo Radar Handover: As-Built, Echo and Alarm Evidence

Silo radar handover should explain what the instrument measures on an uneven solids surface and how the site will recognize degraded performance. A commissioning value alone cannot show beam position, dust margin, false targets or inventory uncertainty. The package should link as-built geometry and material behavior to diagnostic curves, output and alarm tests under representative filling and discharge. It should also record limitations and maintenance triggers so operators do not mistake local surface distance for precise total mass or reset the radar before useful fault evidence is captured.

Identify the complete installation

Record full model, serial, firmware, antenna, process connection, nozzle, reference plane, orientation, bracket, cable, grounding and approvals. Measure projection and beam clearance. Photograph the roof and internal target direction. Confirm that drawings reflect final adapters and structures rather than the original design only.

Describe material and surface behavior

List products, particle size, moisture, dielectric response, bulk density, angle of repose, dust, deposits, filling and discharge patterns. Note cones, funnels, ratholes, bridging and avalanches. State which local surface the radar observes and how that position supports the alarm, control or inventory purpose.

Capture representative echo evidence

Save raw curves at known empty, filling, loaded and discharge states where possible. Mark product echo, fixed structures, noise floor, signal margin and selected target. Record process state and extraction. Explain any false-echo suppression and prove it does not hide a valid high surface.

Verify conversion and uncertainty

Record distance-to-level reference, units and range. If volume or mass is displayed, identify silo geometry, tank table or model, bulk-density assumptions and material in transit. Compare with survey, weight or production balance and state expected uncertainty. Avoid presenting instrument distance accuracy as inventory accuracy.

Test system outputs

Compare local distance and level with loop current or digital values, PLC or inventory tags, HMI, historian and reports. Verify data type, scaling, quality and timestamps. Test lost echo, device fault, power and communication failure. Stale data should remain identifiable and must not continue as a healthy inventory value.

Test alarms during relevant conditions

Verify high-level setpoint, delay, hysteresis, annunciation and conveyor or gate action. Include maximum filling rate and dust-induced signal loss. Where the high condition cannot be reached, combine model-specific geometry, diagnostic evidence and downstream simulation and record the remaining limitation.

Define maintenance triggers

Set an early-service inspection after representative campaigns. Record antenna deposits, extraction, purge if used, signal margin and lost-echo count before cleaning. Define warning and intervention criteria and safe access. Adjust intervals from repeated as-found evidence rather than a fixed unsupported schedule.

Obtain accountable acceptance

List deviations, untested conditions, temporary controls, owners and review dates. Store drawings, photographs, settings, curves and tests under the equipment tag. Operations, instrumentation and control owners should accept the parts they rely on. Reopen the handover basis after material, inlet, extraction, geometry or software changes.

Engineering checklist

• Record exact identity and installed geometry.
• Explain the observed solids surface.
• Capture filling and discharge echo curves.
• State inventory conversion uncertainty.
• Test quality, stale data and alarms.
• Define evidence-based maintenance triggers.

Frequently asked questions

Does a good empty echo prove filling performance?

No. Dust, cones and moving surfaces require representative evidence.

What should operators do before a reset?

Capture process state, curve, status, output and configuration so the fault can be diagnosed.

Can radar mass be used commercially?

Only with a validated conversion and uncertainty appropriate to that use.

Decision record

Keep a concise approval record that states the operating case, assumptions, accepted limits, responsible owner and evidence reviewed. Attach the relevant drawing, configuration, test results and unresolved deviations. Define what process, mechanical, electrical or software change requires reassessment. This record prevents a technically sound decision from becoming an unsupported setting after staff, equipment or operating conditions change.

Related measurement solutions

80 GHz radar level meters · Rotary paddle level switches