Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Six months after startup, a technician needs to know whether a reading changed because of the process, the installation or a setting. Radar commissioning records should make that comparison possible. A folder containing unnamed screenshots and a signed acceptance sheet may contain plenty of files but still fail that task.
Start with the questions the next service visit will ask
Which instrument was tested? Where was its distance reference? What was the tank doing? Which configuration was actually left in service? Organise the handover around those questions rather than around the order in which contractors emailed attachments.
Use the site asset tag as the index and retain the serial number separately. The tag usually stays with the measuring point when hardware is replaced; the serial number follows the instrument. Keeping both avoids applying the old unit's evidence to a replacement with different electronics or antenna geometry.
A practical index for radar commissioning records
| Record group | Information needed to interpret it later |
|---|---|
| Identity | Tag, serial number, full configuration, firmware where available and dated nameplate photograph. |
| Geometry | Marked reference plane, nozzle section and dimensions actually measured after installation. |
| Observations | Time, independently known level, material, operating state and meaning of each diagnostic axis. |
| As-left state | Final settings, approved changes, test results and any conditions that remain untested. |
Keep raw files where the instrument supports export, together with a readable copy that does not require an obsolete application. State the software and version needed to open the raw file. A screenshot is useful for interpretation, but it may not contain every parameter required to reproduce the configuration.
For an MV-RD12, identify whether the installed electronics are the two-wire 4-20 mA/HART configuration or the separately specified RS485 version. Record terminal and output documents for that version. A generic family brochure cannot identify which signal path was commissioned.
Preserve changes without losing the accepted baseline
Label the accepted commissioning set as read-only in the site's document system. Add subsequent maintenance records as dated revisions, with the reason for each change and the test that followed it. Overwriting the original file removes the evidence needed to decide when a new fault appeared.
Store operating restrictions next to the test result they qualify. For example, a successful calm-water comparison does not establish performance during agitation. Name the missing observation and the event that will trigger it. Avoid a general statement such as "all conditions satisfactory" when only one state was available.
Before handover, ask someone who did not commission the instrument to retrieve the drawing, identify the as-left configuration and explain one test result. Resolve missing access rights or unreadable files then, not during an outage. Keep credentials out of the engineering evidence package and manage them through the site's access process.
Use the configuration-recovery desk check to test whether maintenance can locate and interpret the delivered records without changing live settings. That exercise checks the handover package; it does not approve a restore to different hardware.
Q1. Is a configuration backup safe to restore to a replacement unit?
Only after checking compatibility with its electronics, firmware and assembly. Treat the file as a reference until the permitted restore procedure is confirmed; do not assume the same model name guarantees identical settings.
Q2. Which date should be attached to an echo screenshot?
The time of acquisition, linked to the process observation. The date the image was pasted into a report does not identify the tank conditions during measurement.
Summary
A usable service record connects equipment identity, physical geometry and observed behaviour. Ask about the records available for the supplied MV-RD12 configuration before specifying the handover package.
