https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/ServiceNow_CIS-DF/page_65_img_2.jpg The Common Service Data Model (CSDM) organizes CMDB data into domains that reflect how services are planned, delivered, and consumed. Correct placement of objects is essential for reporting, ownership, and downstream ITSM, ITOM, and IRM use cases. Design and Planning domain → Business Process Business Processes describe how the business operates and what capabilities are required. These are planning constructs used to design services and applications before they are built or delivered. Foundation domain → Business Application Business Applications are foundational reference objects that represent what applications exist and who owns them. They anchor ownership, lifecycle, and governance but are not directly operational. Service Delivery domain → Application Service Application Services represent running, operational technical services (often created via Service Mapping). They are central to Incident, Change, and Event Management, making them part of Service Delivery. Sell / Consume domain → Business Service Business Services represent what is offered to customers or consumers. They define value delivery, SLAs, and consumption context, which is why they belong in the Sell/Consume domain. This mapping aligns with CSDM v5 guidance and ensures clear separation between planning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMDB.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/ServiceNow_CIS-DF/page_64_img_1.jpg The CMDB Health Dashboard organizes data quality into practical, action-oriented metrics: Audits validate correctness by comparing CI values against defined expectations (rules, policies, certifications). Duplicate CIs represent redundant records and should be reduced to improve trust and reporting accuracy. Orphan CIs lack required relationships or key context, limiting impact analysis and service visibility. Recommended fields are not mandatory but add diagnostic value during incidents and problem investigations. Required fields are enforced by the platform and closely tied to Identification & Reconciliation remediation. Stale CIs signal aging data that no longer reflects the current environment. This mapping aligns with CMDB Data Foundations best practices and how the Health Dashboard is designed to guide prioritization and remediation.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/ServiceNow_CIS-DF/page_56_img_2.jpg In ServiceNow, duplicate CI management spans detection, insight, and remediation: The CMDB Health Dashboard – Correctness surfaces where duplicates exist and their impact, providing visibility and prioritization. Certification Tasks support governed resolution, allowing assignment to individuals or groups to validate and correct data. De-duplication Templates enable bulk remediation, ideal when standardized merge rules can be applied across many duplicates. The Duplicate CI Remediator offers a guided, record-by-record wizard, preserving relationships and history for safer individual resolutions. De-duplication Tasks are the work items generated by these processes, but they do not themselves represent an outcome—hence not applicable. This mapping aligns with CMDB Data Foundations best practices, ensuring duplicates are identified, prioritized, and remediated efficiently and safely.

This is standard ServiceNow platform behavior for upgrades. When a customer modifies an out-of-the-box (OOTB) record, such as a script transform, the system flags it as a customization. During a platform or application upgrade, if a new version of that record is included in the update, the system will not overwrite the customer's changes. Instead, it creates a "Skipped" record in the Upgrade History. The administrator must then review the skipped change and decide whether to revert to the new OOTB version, merge changes, or retain the customization.

A. Upgrades are designed to be resilient and do not stop due to customizations; they log them as skipped changes for later review.

C. The upgrade process will start and complete, but it will bypass the application of the update for the customized script transform.

1. ServiceNow Product Documentation. Upgrades. Section: "Review and resolve skipped records". It states, "During an upgrade, the system skips any record that has been customized... The system saves the upgrade version of the record so that you can compare the versions and revert your customization if you want."

2. ServiceNow Developer Documentation. Upgrades and Clones. Section: "How the upgrade process works". This guide explains that the system tracks customer updates (sysupdatexml) and if a record has been updated by the customer, the upgrade for that specific record is skipped.