Approving PLC Level Tags: Scaling, Quality and Control Logic

A PLC level tag is an engineered representation of a field measurement, not merely a database name. Approval must show which sensor and variable feed the tag, how raw data becomes engineering units, how faults and stale values are handled, and which alarms or control actions depend on it. Copying logic from another vessel can preserve the wrong range, reference direction or alarm delay. The test should trace representative physical and failure states from the instrument to the final equipment and historian.

Define tag identity and source

Record instrument tag, vessel, input channel or network address, source variable, units, range, reference plane and update interval. Distinguish raw counts, loop current, distance, level, volume and quality tags. Use naming that is consistent but does not hide which conversion or source actually supplies the value.

Verify scaling and engineering meaning

Check 4–20 mA endpoints or digital data type, byte order and scale. Confirm whether level increases as radar distance decreases and where zero is located. Test low, mid and high values, unit conversions, rounding and any tank-table lookup with controlled revision and interpolation.

Implement quality and stale logic

Map open circuit, fault current, lost echo, device fault, network timeout and maintenance mode. Define how long a held value remains usable and show age or invalid status to operators. Control logic should not treat zero substituted for bad data as an actual empty vessel.

Review alarms and sequences

Confirm setpoints, hysteresis, delay, priority, latching, acknowledgement and shelving permissions. Compare delay with fill or drain rate and final equipment response. Test pump, valve, gate or conveyor sequences in manual, automatic and fault conditions, including independent protective channels.

Control simulation and access

Define approved simulation points and ensure forces are visible, time-limited and logged. Restrict scaling, alarm and bypass changes to authorized roles. Back up code and tag database before modifications and record change reason, reviewer and effective time for traceable operation.

Perform site acceptance

Compare known field level, instrument display, raw input, scaled tag, HMI, historian and reports. Test signal and communication failures separately and verify recovery. Remove all simulations and bypasses, then store signed results, code revision and remaining limitations with the instrument record.

Test tag ownership and change control

Identify who may change instrument range, PLC scaling, filtering, alarm setpoints and HMI limits. Require reason, evidence, approval and effective time for each change and keep transmitter and PLC backups aligned. During acceptance, verify that quality and stale status propagate to every consumer and that an interlock does not use an unqualified held value. Review calculated tags, trends and reports for hidden duplicate scaling. A controlled tag record prevents later software maintenance from silently changing the physical meaning or safe response of the level measurement.

Operational proof

After point testing, observe the tag during a representative fill and empty sequence. Confirm direction, rate, filtering, alarm deadband, historian sampling and operator display, and compare the indicated level with an independent reference at useful points. Review every downstream calculation or permissive that consumes the tag. Record any intentionally different display range or rounding. This operational proof catches logic and presentation faults that a forced analog value can miss while preserving a traceable relationship between the physical measurement and plant decisions.

Engineering checklist

• Tie each PLC tag to one physical source.
• Verify range, direction and conversions.
• Expose invalid and stale states.
• Test alarms and final control actions.
• Restrict and log forces and changes.
• Store signed end-to-end acceptance results.

Frequently asked questions

Can PLC scaling be copied from a similar tank?

Only after range, reference, input and tank geometry are verified for the actual installation.

Should a failed value become zero?

No. It should carry invalid quality and invoke the documented safe response.

What must be removed before handover?

Temporary forces, simulations, bypasses and uncontrolled engineering access must be cleared.

Related measurement solutions

80 GHz radar level meters · Industrial IoT gateways