Radar Level Commissioning Records: Evidence That Supports Maintenance

A commissioning record should allow a future technician to understand what was installed, how it was configured, what conditions were tested and which limitations remained. A signed form containing only pass is not enough. Radar performance depends on geometry, process state, echo selection, output mapping and alarm behavior, all of which may change later. The record should combine measured as-built evidence, diagnostics and end-to-end tests under one equipment tag so maintenance can compare the current condition with a known-good baseline instead of starting every investigation from guesswork.

Record exact equipment identity

Capture tag, manufacturer, full model code, serial number, firmware, antenna, process connection, seal, housing, output and approval markings. Include accessories, barriers, surge devices and configuration tool version. Photograph the nameplate and assembly. Family names or partial codes cannot prove compatibility or explain later spare and firmware decisions.

Preserve as-built geometry

Measure reference plane, nozzle bore and length, antenna projection, orientation, empty distance, tank zero, maximum-level clearance and nearby structures. Record adapters and deviations. Attach photographs with scale and direction. This evidence helps distinguish a later echo change from undocumented mechanical work, settlement or bracket movement.

State process conditions

For each diagnostic or reference point, record product, level, temperature, pressure, foam, agitation, dust, filling or discharge and antenna condition. Identify conditions not reached during commissioning. A clean ambient curve should not be presented as proof for maximum steam, dense dust or production foam.

Save configuration and diagnostics

Export default and as-left parameters, raw echo curves, signal margin, selected distance, status and any false-echo map. Explain departures from standard settings. Use consistent curve scales. Retain files in a format and location another authorized technician can retrieve without relying on one personal laptop.

Document output tests

At several known points record field reference, local distance and level, loop current or digital registers, PLC or DCS engineering value, HMI and historian. Include units, scaling, data type, quality and timestamp. Separate physical, transmitter simulation, current injection and software forcing because each proves a different layer.

Document alarms and faults

Record setpoints, hysteresis, delay, priority, pickup, reset and final action. Test device fault, lost echo, open circuit, power loss, communication interruption and stale data as applicable. Identify every force and bypass and obtain independent confirmation of restoration before release.

List deviations and limitations

State accepted dimensional, process or test deviations with consequence, owner and approval. For untested conditions, define an operating restriction or future verification trigger. Do not bury open risks in free-text notes. A conditional acceptance should have a due date and clear closure evidence.

Make the record retrievable

Store drawings, photographs, settings, curves, test sheets and approvals under a consistent asset index with revision and date. Test retrieval by another user. Link maintenance procedures and early-service inspection. A complete package is valuable only when the site can find and interpret it during a fault.

Engineering checklist

• Capture complete identity and firmware.
• Measure and photograph installed geometry.
• Tie diagnostics to known process states.
• Record every signal layer and unit.
• Test alarms, faults and restoration.
• Index evidence under the equipment tag.

Frequently asked questions

Is a signed pass sheet sufficient?

No. It must contain objective values, conditions, diagnostics and unresolved limitations.

Why keep default settings?

They show which changes were intentional and provide a reference for later configuration review.

Who should accept the record?

Responsible operations, instrumentation and control representatives should approve their respective evidence.

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 · Guided-wave radar level meters