1.3 CSDM Lifecycle Stage Governance

CSDM Lifecycle Stage Governance

One of the greatest challenges in enterprise CMDB governance is the lack of a standardized status taxonomy. Historically, different ServiceNow products and modules used separate, unaligned fields to track the status of configuration items and assets. For example, ITSM applications referenced the install_status field on the base Configuration Item table, ITOM Discovery relied on the operational_status field, and ITAM Asset Management used the hardware_status and install_status fields on the Asset (alm_asset) table. This fragmentation resulted in data discrepancies, broken integrations, and operational friction, such as a server being marked as "Retired" in the Asset table while still showing as "Operational" in the CMDB.

To resolve these conflicts, ServiceNow introduced the Common Service Data Model (CSDM) Lifecycle standard. This framework unifies status tracking across the entire platform by introducing two standard fields:

1. Lifecycle Stage (lifecycle_stage)
2. Lifecycle Stage Status (lifecycle_stage_status)

---

1. The CSDM Lifecycle Taxonomy

The CSDM Lifecycle standard groups status values into four macro-level stages, each containing specific status values that track the progression of a CI from initial planning to disposal:

• Plan: Represents CIs that are in the planning, design, or procurement phase.
  • Statuses: Pipeline, Plan
• Build: Represents CIs that are undergoing configuration, deployment, or are stored in warehouse inventory.
  • Statuses: Inventory, Build
• Run: Represents CIs that are actively operational, undergoing maintenance, or are temporarily out of service.
  • Statuses: Operational, Repair, Temporarily Out of Service
• End of Life: Represents CIs that have been decommissioned, retired, or disposed of.
  • Statuses: Retired, Consumed, Obsolete

CSDM Lifecycle Stage and Status Matrix

---

2. Enabling Lifecycle Mappings and the Migration Job

Adopting the CSDM Lifecycle standard requires moving away from legacy status fields. Because existing instances contain millions of records referencing legacy statuses, ServiceNow provides a structured migration utility called the Lifecycle Mapping Migration.

To activate this functionality, administrators configure the system property glide.cmdb.csdm.lifecycle.mapping.active. When this property is enabled, the system references the Lifecycle Mapping (lifecycle_mapping) table. This table contains the rules that define how combinations of legacy status fields translate to the new CSDM fields. For instance, a mapping rule dictates that if install_status is 1 (Installed) and operational_status is 1 (Operational), the record's CSDM fields should be updated to lifecycle_stage = Run and lifecycle_stage_status = Operational.

Once mappings are enabled, the platform executes synchronization logic. When a user or discovery source updates a legacy status field, the platform automatically updates the corresponding CSDM fields. Conversely, updating the CSDM fields will write back to the legacy fields. This bi-directional sync maintains compatibility with legacy client scripts, business rules, and integrations that have not yet been refactored to query the CSDM fields.

---

3. Asset-to-CI and CI-to-Asset Synchronization

A key benefit of CSDM Lifecycle Stage Governance is the synchronization between Asset Management and Configuration Management. Configuration items represent the physical and logical aspects of a technology (the "Run" state), while assets represent the financial and contractual aspects (the "Buy" and "Own" states).

Under the CSDM standard, lifecycle transitions are synchronized automatically. When a server's lifecycle status is updated to Run / Operational, the asset synchronization engine automatically updates the corresponding asset record's status to In Use. Likewise, when a hardware asset is marked as Retired in the asset table, the corresponding configuration item is automatically moved to End of Life / Retired in the CMDB.

This automated synchronization prevents billing discrepancies, ensures compliance with software licensing limits, and gives IT asset managers and security teams a unified, accurate view of the technology footprint throughout its entire lifecycle. Product teams across ITSM, ITOM, and ITAM leverage these fields to prevent unauthorized usage or false positive discovery updates on retired infrastructure.

When resolving discrepancies, the asset-to-CI synchronization business rules (such as 'Sync Asset-CI Operational State') evaluate changes in real-time. If conflicts occur where both asset and CI statuses are modified simultaneously, the platform defaults to the asset's financial state as the ultimate source of truth, prompting the administrator to resolve the mismatch manually.