Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
A radar installation may be mechanically complete while its most demanding operating condition remains untested. Radar commissioning handover should make that distinction visible. A general "working correctly" entry is not enough for the engineer who must diagnose a later fault or authorise a change.
Separate completed work from accepted performance
Record installation inspection, configuration, physical measurement checks and receiving-system tests as distinct activities. Each has a different evidence source. A simulated current can verify a PLC scale without proving the antenna sees the real surface.
For each acceptance requirement, attach the result or identify the missing condition. Avoid empty checkboxes that can be mistaken for a completed inspection. Where the project permits conditional acceptance, record who accepted the condition, its operating restrictions and the action required to close it.
| Record group | Minimum useful content |
|---|---|
| Installed identity | Tag, model, serial identity, output version and actual connection arrangement. |
| As-left settings | Values or supported export, revision, date and responsible person. |
| Test evidence | Reference method, process state, observations and explicit pass criteria. |
| Open items | Untested condition, limitation, owner and agreed completion action. |
Make radar commissioning handover usable after a replacement
Include the measurement reference plane and any physical offsets in the record. Identify the tank-table revision if the output is converted to volume. Record which system owns each calculation so a replacement technician does not apply the same correction in both transmitter and PLC.
For METRAVON MV-RD12, the selected electrical and mechanical construction should match the handover documents. If settings can be exported, verify that the file is readable and associated with that unit. If not, retain an organised parameter record rather than claiming that a backup exists.
Close the work with an explicit restoration check
Confirm that temporary simulations, test modes and authorised bypasses have been addressed under the site's return-to-service procedure. Check the final value and validity at the operator interface. Record the live value, its quality status and the final operating mode; a screenshot alone does not establish which temporary settings were removed.
Deliver the documents where operations and maintenance can retrieve them. Include the approved contact route for unresolved model or installation questions; a file held only on a commissioning laptop is difficult to use during an outage.
Q1. Can normal low-level operation justify accepting an untested high-level condition?
Not by itself. Record the limited observation and the separate evidence for the upper range. Any conditional acceptance belongs to the responsible project authority, not to a general assumption that the rest will behave identically.
Q2. Does restoring a settings file prove the replacement is ready?
No. The replacement's version, mounting and measurement reference may differ. Verify the applicable settings and repeat the required installed checks before returning it to service.
Summary
Leave a record that distinguishes evidence from unfinished work. Send the MV-RD12 configuration and outstanding test conditions for review before closing the instrument handover.
