Mastering CI–Asset Lifecycle Synchronization and CMDB Lifecycle Tables

[satyasubraV3614]

1. Asset

• Represents the financial and ownership view of an item (cost, owner, vendor, lifecycle)
• Tracks the complete lifecycle from procurement → usage → retirement
• Mainly used for asset management activities like audits, compliance, and cost optimization

2. Configuration Item (CI)

• Represents the technical view of an item (server, application, database, etc.)
• Maintains relationships with other CIs, helping in impact analysis
• Used for incident, change, and service mapping to understand dependencies

3. Difference between Asset and CI

• Asset focuses on “Who owns it and how much it costs”, while CI focuses on “How it works and what it is connected to”
• Asset lifecycle is financial, whereas CI lifecycle is operational/technical

4. Why do we need to relate them

• To ensure data consistency between financial and technical records
• To avoid mismatches like Asset = In Use but CI = Retired
• To get a complete view of an item, combining ownership, cost, and technical impact

5. Asset–CI Mapping

• In ServiceNow, Asset and CI represent the same item, and they are connected using reference fields (ci in Asset and asset in CI)
• ServiceNow uses an Asset–CI Field Mapping table to define which fields should be synchronized (serial number, model, assigned user, etc.)
• Earlier, lifecycle was handled using legacy fields:
  • On CI → install_status, hardware_status
  • On Asset → state, substate
• These fields show a basic state like Installed, In Use, Retired
• OOTB business rules automatically sync these values between Asset and CI

6. Life Cycle Mapping

• ServiceNow introduced Lifecycle Stage and Lifecycle Stage Status to provide a structured lifecycle instead of relying only on legacy fields
• Lifecycle Stage → High-level phase (Plan, Build, Operate, Retire)
• Lifecycle Stage Status → Detailed condition (In Use, In Maintenance, Retired)
• The Lifecycle Mapping table (life_cycle_mapping) maps legacy values to Stage and Status
• Example:
  • install_status = Installed → Stage = Operate, Status = In Use
  • install_status = Retired → Stage = Retire, Status = Retired
• Once lifecycle sync is enabled:
  • Lifecycle fields are automatically populated and synchronized
  • Ensures consistency across all CI classes
  • Improves reporting and aligns with CSDM best practices

7. Tables related to Life Cycle

• Lifecycle Mapping (life_cycle_mapping)
  Maps legacy fields like install_status or Asset state to Lifecycle Stage and Status. Ensures standardized lifecycle representation across CI and Asset records.
• Lifecycle Stage (cmdb_lifecycle_stage)
  Defines high-level phases such as Plan, Build, Operate, and Retire. Provides a consistent lifecycle structure across all CI classes.
• Lifecycle Stage Status (cmdb_lifecycle_stage_status)
  Defines detailed conditions like In Use, In Maintenance, or Retired. Improves clarity and lifecycle tracking.
• Lifecycle Object (cmdb_lifecycle_object)
  Links lifecycle definitions to specific CI classes. Allows flexibility while maintaining standard lifecycle models.
• Lifecycle Validation (cmdb_lifecycle_validation)
  Ensures only valid stage and status combinations are used. Helps maintain data accuracy and consistency.
• Lifecycle Control (cmdb_lifecycle_control)
  Controls allowed transitions between lifecycle states. Ensures proper and logical lifecycle movement.