how does normalization works once we get data in cmdb_sam_sw_install table.

PriyankaAng · ‎09-11-2024

Hello Team,

Please help me to understand how the data normalization been done once we get installed software data in cmdb_sam_sw_install table. Also for the un-normalized data what actions/steps one should follow to achieve 100% Normalization.

Community Alums · ‎09-11-2024

Hello,

The data normalization process in ServiceNow' involves identifying and reconciling the software discovered on your systems with the correct software models and versions to ensure consistency and accuracy across the CMDB. Here's a detailed explanation of how the data normalization is handled and the steps to follow for un-normalized data:

1. Discovery of Installed Software:
When a discovery tool (like ServiceNow Discovery, SCCM, or another integration) identifies software on a device, it populates the cmdb_sam_sw_install table.
This table holds raw discovery data, such as the software name, version, and publisher, but this data might not always match exactly with the standard software models defined in the ServiceNow SAM database.
2. Software Discovery Model Creation:
Upon the creation of a new software installation record in the cmdb_sam_sw_install table, a Discovery Model is either created or linked to an existing Discovery Model in the cmdb_sam_sw_discovery_model table.
The Discovery Model acts as a bridge between the raw discovery data and the normalized software models (SAM software models) stored in ServiceNow.
3. Normalization Process:
Once the discovery model is created, ServiceNow tries to normalize the data using its built-in Normalization Engine. The process involves:
Discovery Map (DMap): ServiceNow uses predefined mappings called Discovery Maps (or Normalization Rules) that link discovered software names, versions, and publishers to the correct Software Models in the SAM database.
If a match is found based on the discovery model’s name, version, and publisher, it is normalized successfully, and the corresponding Software Model is assigned.
4. Partial Normalization:
If ServiceNow can't find a matching version in the Discovery Map for the discovered software, the software is marked as Partially Normalized.
This happens when the software name or publisher is matched, but the version is either missing or incorrect.
In this case, the software model might still be linked, but the version needs manual input to complete the normalization process.

dreinhardt · ‎09-11-2024

Hi @PriyankaAng,

There are some "SAM Normalization Scheduled Jobs" that are responsible for the Normalization Exercise of "Software Discovery Models" that gets executed on a daily or weekly basis.

Some SAM Normalization Scheduled Jobs are as follows: -

Run normalization job daily - Daily
SAM - Find Normalization Suggestions - Weekly
SAM - Normalize discovery models using content library rules - Daily

(Source: Discovery Software Model Normalization - ServiceNow Community)

Please find below some helpful sources about discovery model normalization:

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.