Tank Level Tags and Engineering Units: Governance Guide

A tank level value can be technically correct at the transmitter and still become unreliable after it is renamed, rescaled or converted through several systems. Distance, level, percent, volume and mass are different quantities, while millimetres, metres, inches and percent require explicit ranges and reference points. A governance record should give every tag a unique identity, define the authoritative raw value, assign conversion ownership and preserve quality and timestamps. This prevents believable but inconsistent data from reaching operators, historians, remote dashboards and inventory reports.

Define the physical reference

Record antenna or sensor reference plane, tank zero, empty distance, maximum level and alarm points using one physical datum. State whether level rises with the numerical value. Include offsets only once and identify their owner. Drawings, transmitter settings and control-system tags should use the same reference or document the conversion explicitly.

Separate measured and calculated quantities

Distinguish raw distance, level, percent, volume and mass in tag names and metadata. Volume requires a controlled tank table; mass may require density and temperature. Retain the raw measured quantity so later table or density revisions do not erase traceability. Do not label a local solids distance as inventory mass without a validated model.

Create a tag dictionary

Map instrument tag, channel or register, PLC and DCS tags, historian point, gateway topic, cloud field and report label. Include description, unit, data type, scale, resolution, update interval and quality. Use consistent abbreviations but verify platform length and character limits. Unique identity matters more than forcing every system to display an identical string.

Control engineering units

Choose units appropriate to local operations and contracts and state every conversion factor. Avoid mixing decimal and integer scaling or applying unit conversion in multiple layers. Test representative points including alarms. If different users require metres, millimetres or percent, derive each from one authoritative value and label it clearly.

Preserve quality and time

Carry device fault, lost echo, out-of-range, maintenance and communication status with the value. Define timestamp origin and stale age. A last-good level may remain visible for context but must be marked stale and retain its original time. Reports should filter or qualify invalid data instead of silently replacing it with zero.

Assign conversion ownership

Name the owner for range, offsets, tank tables, density, filtering and alarm setpoints. Record reason, approval and effective time for every change. Keep transmitter, PLC and platform backups aligned. Prevent a local maintenance adjustment from silently changing the meaning of historical or remote data.

Test every consumer

At known low, middle, high and alarm points, compare local value, raw signal, each system tag, HMI, historian and report. Test fault, stale communication and recovery. Verify that units and tank identity remain correct after buffering or export. Retain the signed tag map and point results.

Audit future changes

Review the dictionary after tank modification, sensor replacement, range change, software migration or new dashboard. Use regression checks for every downstream consumer. Keep prior table and tag revisions with effective dates so historical values remain interpretable. This turns data naming into an engineering control rather than a documentation exercise.

Engineering checklist

• Use one physical reference datum.
• Separate distance, level, volume and mass.
• Map every system tag and data type.
• Apply unit conversion once.
• Preserve quality, age and original timestamps.
• Test every consumer after changes.

Frequently asked questions

Should percent be the authoritative value?

Usually retain a physical raw quantity and derive percent from a controlled range.

Can different systems use different units?

Yes, if conversions are explicit, tested and tied to one source value.

What makes a tag stale?

Its age exceeds the defined update expectation or its communication quality is invalid.

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 · Industrial IoT gateways