ADR-OT-0001: OT sensor node naming convention¶
Status¶
Accepted — 2026-03-31
Context¶
OT field devices (ESP32 nodes) need a naming convention that is cluster-aware, zone-aware, scalable, and aligned with IEC 62443 zone and conduit model.
Decision¶
Pattern: cae{cluster}ot{zone}esp{n}
Zone Map¶
| Zone | Physical Location |
|---|---|
| ot1 | Basement |
| ot2 | Main floor / garage |
| ot3 | Outdoor |
| ot4 | Rack monitoring |
Current Nodes¶
| Node ID | Location | Sensors |
|---|---|---|
| caneast-c1-ot1-esp1 | Basement — sump pit | HC-SR04 level, float switch flood |
Alternatives Considered¶
cae1esp1 (no zone) — Flat namespace, doesn't scale, no zone semantics.
cae1-ot-zone1-esp1 (hyphenated) — DNS-safe names prefer no nested hyphens.
UUID-based naming — Not human-readable, poor ops experience.
Consequences¶
- All new OT sensors must follow this pattern
- MQTT topic structure must align with zone numbering (see ADR-OT-0002)
- Ansible OT inventory groups nodes by zone
- IEC 62443 zone model can be demonstrated using this naming as an anchor
References¶
- IEC 62443-3-3 zone and conduit model
- ADR-OT-0002 (MQTT topic structure)