← Articles
Tags/1 min read/— views
SCADA Tag Naming Guide
A practical guide for creating readable, maintainable SCADA tag names across equipment, signals, alarms, trends, and reports.
Tag NamingSCADAStandardsProject Notes
Goal of naming
A tag name should be stable, searchable, and meaningful. It should help people understand where the signal belongs, what it represents, and how it should be used.
Useful fields
A common pattern includes area, equipment, component, signal, and qualifier. Example:
AREA_EQUIP_COMPONENT_SIGNAL_QUALIFIER
The exact format matters less than consistency and documentation.
Good naming habits
- Keep abbreviations controlled and documented.
- Put equipment context before signal detail.
- Use consistent suffixes for commands, feedback, setpoints, and alarms.
- Avoid vendor-specific temporary names as final SCADA names.
- Keep display names human-friendly even if internal names are compact.
Names are not enough
A tag also needs description, units, data type, quality behavior, scaling, alarm limits, historian settings, and owner. Naming is the entry point, not the whole data model.
Practical rule
If another engineer cannot search, sort, and audit the tag list, the naming scheme is not finished.