Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Tank farm radar commissioning must prove which physical tank each displayed value represents. Two similar tanks can show plausible levels even when cables, register assignments or screen labels have been exchanged. Checking only the number on the dashboard may leave a serious identification error undetected.
Trace one loop from the tank to the operating screen
- Identify the physical tank and installed instrument from durable tags and the approved location drawing.
- Trace the cable or network connection to the documented input channel or device address.
- Identify the controller variable, display object, historian record and relevant alarm associated with that input.
- Perform an authorised identification test and record which destinations respond.
Independent witnesses at the field and control room can help prevent two people confirming the same incorrect label. Record the instrument serial number as well as the plant tag. If similar instruments were configured together on a bench, verify addresses and assignments again after installation.
Tank farm radar commissioning needs a tag-specific test record
| Layer | Identity to retain |
|---|---|
| Field | Tank, nozzle, instrument tag and serial number. |
| Input | Terminal and channel, or network address and register assignment. |
| Software | Control variable, screen label, units and historian destination. |
| Test | Authorised test method, expected destination, observed result and restoration confirmation. |
A simulated input can prove the downstream association, but not the physical radar measurement upstream of the simulation point. State where the stimulus was introduced. An approved process observation can provide additional evidence, but do not move fuel or chemicals simply to create an identifying level change without the plant's permission.
Check shared interfaces without confusing identity and scaling
The METRAVON MV-RD12 can be ordered with different analogue or digital arrangements. For analogue loops, label channels and verify the tank-specific endpoints. For a digital network, document the selected electronics and unique addressing required by the system. A correct number at the wrong tag is an identity failure; a wrong engineering value at the correct tag may be a scaling failure.
After identifying the correct route, check the attached alarms and reports as separate destinations. A corrected display label does not necessarily correct a historian or control variable. Remove test overrides using the site's restoration procedure and verify normal operation before completing the record.
Q1. Is matching the local display to the dashboard enough?
Not when neighbouring tanks can have similar values. Use documented loop tracing and an identifiable authorised test to establish the association.
Q2. Must the test reach an actual high-level condition?
No. Use the approved simulation or test procedure appropriate to the function. Do not approach an unsafe fill level to prove that a screen or alarm belongs to a particular tank.
Summary
Accept the association from physical tank to every required destination, not just a plausible display. Send the tank-tag and loop schedule with the proposed MV-RD12 interface for integration review.
