When Should You Create or Update a Scan Data Model?

Scan data models are hierarchical by design and each asset type will always have a data model associated with it. These models define the data to be collected from devices during discovery and are a key component of the Asset Discovery engine.

Default Configuration 

The out-of-the-box configuration for scan data models is designed to facilitate the collection of commonly used and relevant data from various devices, using mechanisms and protocols such as SNMP, WMI. and more. However, organizational needs often require customization to collect additional or unique data. In such cases, you can either update an existing scan data model or create a new one.

When to Update an Existing Data Model

If you need to expand the scope of collected data from existing device types: 

• Update the corresponding data type.

• Once updated, save the data model and run the discovery process again—new details will be collected from the devices.

• For example, for SNMP-enabled devices, quickly use the native MIB library to browse and add SNMP MIBs. For more guidance, refer to the respective help topics on Updating Data Models.

When to Create a New Data Model

If a device has a unique MIB that does not apply to other device types or you need to use additional commands to retrieve unique or highly specific information that isn’t covered by the existing data model: 

• Create a new data model for a specific asset type.

• Once created, save the data model and run the discovery process.

This approach ensures the data model remains organized and relevant to the specific asset type.

By maintaining and tailoring your scan data models, you ensure the discovery process meets your organization’s specific needs, while maximizing the utility of collected data.

For more guidance, refer to the help topics on Creating Data Models.