I don't think any naming convention is unbreakable. We can always make someone's face red with a special combination of building acronyms and room#'s.
Perhaps part of the reason we don't use VLan 666...
To categorize my standardizations I will be going about this from a device type / machine type - first rung, & then function / installed Supervisors & Modules that may be special function - second rung.
Once I have my base set of hardware setup's I would then create a baseline config for each. Set that up in Orion and create a policy to show any noncompliance to the baselines.
I'll have to check on tying the Policy to the nodes, Initially I would consider group's for this. But Using custom properties may be good, and we have tiered location tracking setup with custom properties and might be able to easier my 'Regions' or 'Buildings' to tie some of the baselines to their respective nodes.
Once I get that far, I'll be looking for tips or firing from the hip.
- Cheers!