Blog / Technical guide
Building a tag list for a smart-water pilot
Define a focused first set of signals for monitoring water assets across multiple sites.
HOSON WATER editorial ·
Begin with an operating question
Choose a first decision the pilot should improve, such as identifying loss of production, tracking a decline in membrane permeability or finding repeated alarms across remote sites. Map that decision to the minimum flow, pressure, quality and equipment-state tags required. Include site and train names so comparable signals can be grouped without losing their physical context.
Document what each tag actually means
Record the unit, source device, update frequency, expected range and quality flag. Include whether the signal is measured, calculated or entered by an operator. Agree on time synchronization and define how missing or stale values are shown. Avoid presenting an old reading as current simply because the screen still has a number to display.
Test against a known operating event
Verify a planned stop, restart or quality deviation with site operators and compare events in the platform with local logs. Note where the pilot needs better instrumentation or a change to the alarm logic. Use the results to decide which signals are ready to roll out to other sites.