---
sourceDocument: Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-asset-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Product Instance feature in Hardware Asset Management

# Product Instance feature in Hardware Asset Management {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Product Instance feature in Hardware Asset Management

The Product Instance feature in Hardware Asset Management provides a unified representation of products across multiple ServiceNow applications, including IT Asset Management (ITAM), Customer Service Management (CSM), and Configuration Management Database (CMDB).
This feature ensures that any changes made to a product instance are automatically synchronized across assets, configuration items (CIs), and install base items (IBIs), enabling consistent tracking and management of products within your enterprise.
Show full answer Show less  
Currently, this feature is enabled specifically for the Medical device model category.

## Product Instance Identifier (PID) Configurations

A Product Instance Identifier (PID) uniquely identifies a product instance and links the asset, CI, and IBI records. PIDs are generated based on predefined configurations stored in the **Product Instance Identifier Configurations** table. These configurations specify fields used to create the PID and the order of their application.

* PIDs are generated only when the required fields have values; if critical fields are empty, no PID is created, and the asset is not created.
* Assets without serial numbers and in certain states (On order or Pre-allocated) do not generate a PID.
* PIDs are recalculated and regenerated whenever relevant field values change (e.g., serial number updates).
* The PID is stored in the `productinstanceid` field on the Asset, CI, and IBI tables.

For the Medical device model category, PID generation prioritizes the serial number. If the serial number is missing, it uses Parent and Model Component ID fields. To avoid duplicate PIDs, assets with existing serial numbers cannot be duplicated. For custom unique identifiers, the default Serial Number PID configuration can be deactivated and replaced with a new configuration.

Additionally, enabling the system property `snitamenablepidrecalculationforchildasset` will allow PID recalculation for child assets when their parent assets are updated (default is false).

## PID Synchronization Across Asset, CI, and IBI

PID synchronization occurs when:

* Fields used in PID configurations are updated on an asset, CI, or IBI.
* An asset, CI, or IBI is created or updated with values in PID configuration fields.

## Creating or Updating Records

* **Asset creation/update:** Specifying a PID-related field triggers PID generation and synchronization with the associated CI. PID recalculates on field updates.
* **CI creation/update:** PID generates only if an asset is created for the CI. Updating PID fields on the CI copies the values to the asset, recalculates PID, and synchronizes.
* **IBI creation/update:** Creating an IBI with PID fields creates the asset and CI, generates the PID on the IBI, and synchronizes it with the asset and CI. PID regenerates and synchronizes on IBI field updates.

## Practical Benefits for ServiceNow Customers

By using the Product Instance feature, customers can:

* Maintain a single, consistent product representation across ITAM, CSM, and CMDB, reducing data discrepancies.
* Ensure automatic PID generation and synchronization, simplifying asset lifecycle management and reporting.
* Leverage out-of-the-box PID configurations for Medical device assets or customize PID logic to fit unique identifiers.
* Improve traceability by linking assets, configuration items, and install base items through a unified PID.  
You can consistently represent a product along all applications, processes, workflows, and user interactions through the Product Instance feature. Changes made to any of the product representations are synchronized
automatically.

The Product Instance feature enables you to have a common representation for any product tracked as an asset in IT Asset Management, an install base item (IBI) in Customer Service Management (CSM), and a configuration item in Configuration Management Database (CMDB). A Product Instance is associated with assets of a particular model category.  
Note:  
Product Instance is currently enabled only for the Medical device model category.

## Product Instance Identifier (PID) configurations for a model category {#product-instance-for-assets__section_m11_wyt_5zb}

Product Instance Identifier (PID) is a unique identifier for a Product Instance and links asset, CI, and IBI.  
A PID is generated based on the following items defined in the Product Instance Identifier Configurations \[product_instance_identifier_configuration\] table:

* PID configurations
* Order assigned to each configuration

{#product-instance-for-assets__ul_cfl_wkq_b1c}  
Note:  
PID configurations out-of-the-box can't be edited and are read-only.  
Note the following about PID generation:

* If the fields specified in the parameters of PID configurations are empty, a PID isn't generated and the asset isn't created.
* Assets that are in the On order or Pre-allocated state and don't have a serial number won't have a PID generated.
* The PID is recalculated and regenerated whenever changes are made to the fields specified in the PID configuration parameters, for example, updates to the serial number of an asset, CI, or IBI.
{#product-instance-for-assets__ul_zrn_d15_5zb}  
Note:  
The PID is stored in the product_instance_id field of the Asset \[alm_asset\], Configuration Item \[cmdb_CI\], and Install Base Item \[sn_install_base_item\] table.  
For the medical device model category, the default parameters of a PID configuration are based on the Serial number, Parent, and Model Component ID fields of the table. The PID configuration based on the item's serial number is given the highest priority when generating a PID. But when the serial number isn't present, the parameters based on the Parent and Model Component ID fields are considered for generating the PID. If you specify an existing serial number, the PID that is generated would be a duplicate of an existing PID, so the asset isn't created. If you have any customizations, such as using a different custom field instead of the Serial Number as a unique identifier, you should deactivate the Serial Number PID configuration and create a new PID configuration for that custom field.  
Note:  
To enable PID recalculation for child assets when updates are made to the parent asset, set the system property sn_itam_enable_pid_recalculation_for_child_asset to true. The default value is false.

## PID synchronization between an asset, CI, and IBI {#product-instance-for-assets__section_b3v_w15_5zb}

Synchronization of PID between an asset, CI, and IBI happens in the following circumstances:

* Any of the fields of the PID is updated on an asset, CI, or IBI
* An asset, CI, or IBI is with values specified in the fields of the PID configuration parameters.

{#product-instance-for-assets__ul_mvq_vtj_b1c}

Create or update assets
:   When you create an asset by specifying a value for a field included in the PID configuration parameter, based on the PID configuration of the associated model category, the following actions occur:

    1. A PID is generated for the asset based on the field value that you specified.
    2. The asset is created.
    3. The PID of the asset is synchronized with the associated CI.

    {#product-instance-for-assets__ol_ayx_bb5_5zb}

    When you update the field included in the PID configuration parameter of an asset, the PID is recalculated and regenerated based on the new field value. The updated PID of the asset is then synchronized with its
    associated CI.

Create or update a CI

:   When you create a CI, a PID is generated only when the asset is created for that CI. The PID of the asset is then synchronized with the CI.When you update a field included in the PID configuration parameter on a CI, the
    following actions occur:

    1. The field value is copied from CI to the asset.
    2. The PID is recalculated and regenerated for the asset.
    3. The PID of the asset is synchronized with the associated CI.
    {#product-instance-for-assets__ol_fwn_xb5_5zb}

Create or update an IBI

:   When you create an IBI by specifying a field included in the PID configuration parameter, an asset and the associated CI are created. The PID is generated on the install base item and is synchronized with the asset and its associated CI.A PID is regenerated and synchronized when any updates are made to the fields of the IBI that are part of the PID configuration parameters.