To simplify organising and finding resources in large, complex environments, we're introducing additional device data and expanded metadata directly within interfaces - including a new Device Name
field that provides another way to identify the device each interface belongs to. This makes it easier to build resource groups with devices and their interfaces, and to search for resources in multiple ways across dynamic topologies.

Adding Meaningful Metadata
Beyond device association, we’ve introduced three new descriptive fields that add semantic clarity to every interface:
-
Object Alternative Name
This field allows SevOne administrators to assign a custom name to an interface object, independent of the name reported by the device. It’s especially useful in environments with inconsistent naming conventions, making interfaces easier to identify and manage across different systems
-
System Description
Pulled directly from the device configuration—referred to as the Interface Description—this field typically reflects the intended use or role of the interface. It provides valuable context about how the device itself is defined.
-
User Description
This field lets administrators override the System Description with their own annotation. It’s helpful when the device-provided description is unclear, missing, or doesn’t align with internal naming standards—allowing teams to document interfaces in a way that fits their operational or business context.