A consistent tag dictionary helps users trace a signal to its equipment and source. Names such as Pump1 or DO can become ambiguous when several wastewater stations share a platform.
Separate the asset from its signals
An asset identifies equipment; tags identify its running state, faults, measurements or hours. Keep a stable asset relationship and a site identifier so identical equipment names at different stations remain distinct.
Choose and document a convention
An illustrative code such as WWTP01.AER01.DO01.PV can identify a station, aeration area, sensor and measured value. This is an example convention, not a universal standard. Select one that fits existing tools and plant records.
Store meaning beyond the name
Retain units, data type, source address, time and quality as explicit fields. Explain state codes. If units are converted for reports, preserve original values and the conversion rule rather than changing their meaning silently.
Check dependencies before renaming
Identify dashboards, alarms, reports and AI datasets using the tag. Keep old-to-new mappings, version and effective date. Test history across the change and mark sensor replacement or relocation as a separate contextual event.
Records to check
| Record group | Evidence to review |
|---|---|
| Identity | Site, asset, tag and display name |
| Measurement | Meaning, unit, type and source |
| Change | Mapping, effective date and approver |
Prepare an assessment with X-IRIS
Bring the current tag dictionary, asset register and sample records before and after known changes. Review the implementation roadmap and request an assessment to agree a scope that can be tested.
