---
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


---

# Approximated life cycle

# Approximated lifecycle and lifecycle code {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Approximated lifecycle and lifecycle code

ServiceNow provides expanded lifecycle coverage for hardware and consumable models through its Content Service, especially when manufacturers do not publish explicit lifecycle dates.
In such cases, the system generates approximated lifecycle dates using data-driven logic to estimate the most likely lifecycle phases and dates.
Show full answer Show less  
These approximated dates are indicated by specific lifecycle codes, which clarify that the dates are not official manufacturer-published values. Where lifecycle dates are completely unavailable, special codes such as Exception Codes (EXC) and End-of-Phase Codes (END) explain the absence.

## Key Features

* **Lifecycle Codes:** Stored in the *Hardware Lifecycle Code \[snitamcommonlifecyclecode\]* table, these codes describe the nature of the approximated lifecycle records.
* **Lifecycle Code Reference:** The *Lifecycle code* column in the *Hardware Lifecycle Definition \[snhamplifecycledefinition\]* table links to these approximation codes, marking models with approximated lifecycle dates.
* **Data Loading:** A scheduled job, *HAM -- Hardware Life cycles* , loads lifecycle data published by the ServiceNow Content Service into:  
  - *cmdbhardwaremodellifecycle* (hardware models)  
  - *cmdbconsumablemodellifecycle* (consumable models)
* **System Property Control:** The property *approximatedatesinhwlifecycle* controls whether only manufacturer actual lifecycle dates or both actual and approximated dates are loaded. Default is **True** , meaning both are loaded. Setting it to **False** loads only actual dates.
* **Identification:** The *Lifecycle code* column in hardware and consumable lifecycle tables and the Hardware Asset Workspace Model management view shows if lifecycle dates are approximated or official.
* **Manual Entry Limitation:** Lifecycle codes cannot be manually assigned to user-created lifecycle records; they are exclusive to data received from the ServiceNow Content Service.

## Key Outcomes

* ServiceNow customers gain access to extended lifecycle information for hardware and consumables even when official manufacturer dates are missing.
* Approximated lifecycle data helps in planning and managing hardware lifecycle phases more effectively by providing estimated timelines.
* Lifecycle codes provide transparency, allowing users to distinguish between official and approximated lifecycle dates.
* Configurable system properties enable customers to control the inclusion of approximated lifecycle data based on their operational preferences.  
Leverage the expanded lifecycle coverage for hardware and consumable models available in the ServiceNow®
Content library portal when explicit dates from the manufacturer aren't available. Hardware models with approximated lifecycle dates contain a lifecycle code that indicates the dates are approximate.
When manufacturers don't publish official life cycle dates for certain hardware models and consumables, the  ServiceNow® Content Service generates approximated life cycle dates. The approximated lifecycle dates are derived using data-driven approximation logic to determine the most likely life cycle phase dates for the hardware and consumable models.

The estimated life cycle dates are categorized using specific lifecycle codes. These codes indicate that the lifecycle dates aren't the explicit dates published by the manufacturer. When lifecycle dates are
unavailable for any models, codes such as Exception Codes (EXC) and End-of-Phase Codes (END) are assigned to those models. These codes provide clarification regarding the absence of these dates.

The Hardware Lifecycle code \[sn_
itam_common_lifecycle_code\] table stores the approximation codes and its description for the lifecycle records that are curated through approximation logic. For a detailed explanation of lifecycle codes, see [https://support.servicenow.com/kb?id=kb_article_view\&sysparm_article=KB2726382](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2726382).

The Lifecycle code column in the Hardware Lifecycle Definition \[sn_hamp_lifecycle_definition\] table indicates the approximate code for a model's lifecycle. This column references the Lifecycle code column in
the Hardware Lifecycle Code \[sn_hamp_lifecycle_code\] table.

## Load approximated lifecycle date for hardware and consumable models {#approximated-lifecycles-hardware-products__section_c3d_xb2_ngc}

The scheduled job HAM -- Hardware Life cycles retrieves the life cycles date that is published by the ServiceNow Content Service and loads them into the following tables:

* cmdb_hardware_model_lifecycle (for hardware models)
* cmdb_consumable_model_lifecycle (for consumable models)

{#approximated-lifecycles-hardware-products__ul_ulf_ggm_ngc}The system property approximate_dates_in_hw_lifecycle determines whether only manufacturer-provided actual dates or both actual and approximated dates are loaded into the hardware and consumable life cycle tables. The default value of the system property approximate_dates_in_hw_lifecycle is True.

* If this property is set to False, only the actual life cycles from the manufacturer are loaded into the hardware and consumable life cycle tables.
* If it is set to True, both actual and approximated life cycles are loaded into the hardware and consumable life cycle tables.
{#approximated-lifecycles-hardware-products__ul_fdq_cbl_ngc}

## Identifying models with approximated lifecycle dates {#approximated-lifecycles-hardware-products__section_t1y_v5k_pgc}

In both the Hardware Model Lifecycles \[cmdb_hardware_model_lifecycle\] and Consumable Model Lifecycles \[cmdb_consumable_model_lifecycle\] tables, as well as in the Model management view within the Hardware Asset Workspace, the Lifecycle code column indicates if the model's lifecycle phase and dates have been approximated.

* If the Lifecycle code column contains a value, the model's lifecycle phase and dates are based on an approximated lifecycle code.
* If the Lifecycle code column is empty, the model's lifecycle dates are confirmed or explicit dates published by the manufacturer.
* If the Lifecycle code column contains a value, and the model's lifecycle phase and dates are empty, the Lifecycle code column indicates the reason for the absence of these dates.

{#approximated-lifecycles-hardware-products__ul_yrw_k3x_f3c}  
Note:  
When manually adding a new lifecycle record, such as a custom lifecycle or calculated lifecycle, you can't add a lifecycle code value. The lifecycle code is only available for lifecycle records that come directly from the ServiceNow Content Service and can't be set for the user created lifecycle records.

