Point Naming That Survives the Person Who Wrote It

Open an unfamiliar front end and the point names tell you, inside five minutes, whether the last person expected anyone to come after them. AI-3. FAN STATUS. RM214 TEMP, on a floor renumbered two renovations ago. That is the trap: names are written once, by someone holding the whole building in their head, and read for the next twenty years by people holding none of it.

Where the cost shows up

Bad names do not fail loudly; they tax quietly, on every task that touches the database. A commissioning agent burns the first day of functional testing building a decoder ring. An energy study spends its budget mapping points instead of analyzing them.

A convention that fits on an index card

The specific convention matters less than its consistency. A structure that ages well reads general to specific: system prefix and equipment number, then component, then a function suffix. AHU2-SF-STS is air handler 2, supply fan, status. Nothing in it depends on room numbers, tenant names, or the memory of the author.

• System prefix and equipment number match the mechanical schedule: AHU2, CHWP1, BLR1.
• The component names the part: SF for the supply fan, RF for the return fan, CHWV for the chilled water valve.
• The function suffix always comes last, from a fixed set: STS for status, CMD for command, SPT for setpoint, POS for position, ALM for alarm, SPD for speed.
• Temperatures use the suffix alone: AHU2-SAT, AHU2-RAT, AHU2-MAT, with OAT and ZNT for outside air and zone. Terminal units carry floor and box, so VAV-2-14-ZNT locates itself without a floor plan.

Four points from a typical renaming pass show the shape:

AI-3         ->  AHU2-SAT        supply air temperature
FAN STATUS   ->  AHU2-SF-STS     supply fan status
CHW VALVE    ->  AHU2-CHWV-POS   chilled water valve position
RM214 TEMP   ->  VAV-2-14-ZNT    zone temperature, floor 2, box 14

The fixed suffix set is where the discipline pays: a human can read any point cold, and a fault detection rule written once, with a wildcard on the prefix, deploys across every air handler in the building.

Renaming a live system without losing history

Most buildings keep bad names out of fear, not sentiment: trends and graphics are bound to those names, and nobody wants to orphan five years of history for tidiness. The fear is manageable. What breaks depends on how the platform binds its references, so find out on one sacrificial point first.

• Build the rename map offline: every old name, new name, and equipment, reviewed by someone who knows the building.
• Rename the sacrificial point and check whether trend history, graphic bindings, and alarm routing follow the object or break; export any name-keyed history first.
• Stage by system, not alphabetically: rename one air handler and its terminal units, repair its graphics, verify its alarms, then move on, leaving the old name in the point description field for a season so anyone searching the legacy tag still finds the point.
• Walk each renamed system's graphics: command a point and watch the graphic move. Broken bindings fail visibly; the dangerous ones keep displaying a value from a stale duplicate.

None of this is glamorous, which is exactly why it gets skipped. A naming convention is the cheapest infrastructure a building will ever buy: a page of rules and some discipline, purchased once, collected on by every technician, every study, and every upgrade that arrives after the person who wrote the names has moved on.