Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Tank inventory reconciliation often compares a delivery ticket with the difference between two tank readings. That difference is not automatically the delivered quantity. Consumption, recirculation, line filling and mismatched timestamps can change the comparison even when the radar measures level correctly.
Define the Transfer Window Before Comparing Totals
Choose the opening and closing times, identify every relevant inlet and outlet, and record the tank's operating state. If the tank continues supplying production during delivery, its net inventory increase will be smaller than the incoming amount. A radar offset should not be changed to conceal that expected difference.
For illustration, an opening inventory of 10 cubic metres, an incoming transfer of 5 and an outgoing transfer of 1 imply 14 cubic metres at closing, assuming a common quantity basis and no other movements. The net increase is 4, not the delivered 5. These numbers describe a volume-balance example, not an instrument acceptance tolerance.
| Record | Align | Possible mismatch |
|---|---|---|
| Opening | Reading time and valid tank state. | A sample taken after delivery starts misses part of the increase. |
| Transfers | Every inlet and outlet during the same interval. | Production demand is incorrectly treated as missing delivery. |
| Closing | Actual transfer end and suitable surface conditions. | Settling, drain-down or delayed reporting changes the comparison. |
| Basis | Observed volume, corrected volume or mass. | Different temperature or density conventions produce unlike totals. |
Tank Inventory Reconciliation Starts With a Valid Level Input
MV-RD12 supplies liquid-surface measurement through its selected output. The tank's volume table and any density correction remain separate parts of the calculation. First establish that raw distance and level are credible; then review the interval and bookkeeping. The liquid-level measurement guide should not be treated as a substitute for a tank-specific calibration table.
Investigate the Pattern of the Difference
Compare several transfers before assigning a cause. A discrepancy tied to ongoing consumption calls for movement records. A height-dependent discrepancy suggests reviewing the tank curve. An error that appears after a range edit calls for configuration history. Keep the raw observations so an explanation can be tested rather than fitted to one favourable delivery.
Reconciliation Questions
Q1. Can the delivery ticket be used to recalibrate the radar?
Not by itself. The ticket and tank change must represent the same quantity, time window and conditions, with known uncertainty. Otherwise a forced adjustment may make one delivery agree while degrading subsequent level readings.
Q2. Does a persistent difference prove a leak?
No. It warrants investigation, but measurement, timing and unrecorded movements must also be considered. Follow the site's approved response to suspected leakage; an inventory comparison is not a standalone leak-safety assessment.
Summary
Send synchronized opening and closing readings, transfer records and conversion revisions for an MV-RD12 application review. Reconcile the same interval on the same quantity basis before changing sensor settings.
