Assistance with the CSDM life-cycle sync process
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- Common Service Data Model
Several features help you to ensure accuracy and completeness for the process of syncing legacy data with life-cycle data in the CSDM framework.
Before you perform the life-cycle sync process
- Data migration script
-
Use the fix script from the ServiceNow Community to identify table dependencies. See Migrating into CSDM identifying table dependencies.
- CMDB Data Foundations dashboard
-
Navigate to CMDB Data Foundations Dashboard.
and then select- CMDB dashboard: Each tab provides key metrics that evaluate configuration and customizations in the CMDB.
- The metrics provide visible results of evaluation. Color codes and weighted priority help with planning.
- Each metric includes a link to a remediation playbook with background and plays for remediation.
See Monitor system foundations in the CSDM and the CMDB Data Foundations Dashboards.
- CSDM Data Foundations dashboard
-
Navigate to CSDM Data Foundations Dashboard.
and then selectThe CSDM dashboard focuses on key data elements to support you in implementing the CSDM framework. The reports on each tab display the data metrics that are appropriate for the maturity of your organization's CSDM implementation stage (foundation, crawl, walk, run, and fly). See CSDM Data Foundations dashboard. In particular, the Crawl tab presents a report titled CIs with Mismatched Operational Status and Life Cycle Stage that shows a summary of life-cycle value mismatches among CMDB, asset, and IBI and enables you to view mismatch details. See 'Crawl' stage reports on the CSDM Data Foundations dashboard.
- View the contents of life-cycle tables
-
To view how life-cycle value pairs are mapped in the mapping tables, select All, and then enter life_cycle_stage.list in the search text box.
- Migrating nonconforming CIs into the correct CSDM tables
-
If you already have CSDM data but not in the recommended tables, you can run a script to identify dependencies that you may have created on the nonconforming tables. The results of the script identify referenced dependencies such as reports, UI scripts, business rules, and other references for a specified table (editable in the script). See this post on the Now Community site
- The life-cycle sync process presents the discrepancy report
-
When you start the sync process, the discrepancy report Enabling CSDM life-cycle sync between asset and CI to support product instance helps you to isolate and remediate mapping issues or missing data issues before proceeding with migration and syncing. The report identifies issues and presents links that take you to the mappings that must be resolved before you can sync the data.
On this page
Related Content
- Enabling CSDM life-cycle sync between asset and CI to support product instance
You can align life-cycle values for each product instance on the asset, CI, and IBI tables. A one-time process moves legacy status values for asset and CI across the platform to standard CSDM life-cycle value pairs (life cycle stage and life cycle stage status). Business rules then run regularly to ensure identical IBI, asset, and CI life-cycle data for each product instance.