How Naming Conventions Work
A naming convention is a template that generates standardized device names from fields you define. Each {FIELD} in the pattern is replaced with a value when generating a name.
Pattern Tokens
| Token | Meaning | Example Values |
{SITE} | Site or location code | NYC, LAX, DCA, IAD |
{ROLE} | Device function/role | CORE, DIST, ACCS, FWLL, VPNG |
{SEQ} | Auto-incrementing sequence number | 01, 02, 03... |
{SEP} | Separator character (dash, underscore, etc.) | -, _, . |
{CITY} | City abbreviation | NYC, CHI, SFO |
{BLDG} | Building identifier | WS, B12, HQ1 |
{FLOOR} | Floor number | 1, 3, 12 |
{TYPE} | Device type prefix | RTR, SW, FW, SRV |
{COCOM} | Combatant Command (DoD) | CONUS, EUCOM, PACOM |
{BASE} | Military installation name | BRAGG, HOOD, LEWIS |
Reading a Pattern
Example: {COCOM}{SEP}{BASE}{SEP}{BLDG}{SEP}{ROLE}{SEP}{SEQ} with separator -
CONUS
-
BRAGG
-
B12
-
RTR
-
001
= CONUS-BRAGG-B12-RTR-001
Field Types
| Type | Accepts | Width | Example |
| alpha | Letters only (A-Z) | Fixed character count | NYC (width=3) |
| numeric | Digits only (0-9) | Zero-padded to width | 03 (width=2, pad=0) |
| alphanumeric | Letters + digits | Fixed character count | DC1A (width=4) |
| enum | Must be from allowed list | Auto from values | CORE, DIST, ACCS |
| freetext | Any characters | Up to max width | WALLST (width=6) |
| sequence | Auto-incrementing number | Zero-padded to width | 001, 002, 003... |
Quick Examples
| Convention | Pattern | Output | Use Case |
| Site-Sequence | {SITE}{SEQ} | NYC01 | Simple, compact |
| Site-Role-Sequence | {SITE}-{ROLE}-{SEQ} | NYC-CORE-01 | Enterprise standard |
| DoD Standard | {COCOM}-{BASE}-{BLDG}-{ROLE}-{SEQ} | CONUS-BRAGG-B12-RTR-001 | Military/government |
| Simple | {TYPE}-{SEQ} | RTR-001 | Lab/quick deploy |
Click "+ New Convention" to create your own, or "Edit" on any existing convention to modify it. Use "Test Generator" to try generating names interactively.