Exploring the CSDM model
Summarize
Summary of Exploring the CSDM model
The Common Service Data Model (CSDM) is a standardized data model that ServiceNow administrators should follow when setting up products and applications. It defines how to structure configuration items (CIs) and their relationships within the Configuration Management Database (CMDB) to ensure data resides in the appropriate tables. This alignment maximizes the value of ServiceNow AI Platform applications and supports accurate, complete business data capture.
Show less
Key Features
- Guidance on Data Placement: CSDM provides clear directions on where to store different types of data within the ServiceNow platform, helping avoid ambiguity in data structures.
- Support for Multiple Business Needs: The CMDB data supports foundational CMDB integrity, asset management, process enablement (such as incident and change management), audit readiness, capacity and cost optimization, and security operations.
- Data Domains Aligned to Service Lifecycle: The model organizes data into domains reflecting stages of a service’s lifecycle:
- Foundation Domain: Core CMDB tables foundational to all products.
- Ideation & Strategy Domain: Captures business concepts and ideas.
- Design & Planning Domain: Contains design and planning data for products or integrations.
- Build & Integration Domain: Holds data related to software development and integration efforts.
- Service Delivery Domain: Manages infrastructure, service instances, applications, and assets.
- Service Consumption Domain: Catalogs services and business offerings for customer consumption.
- Manage Portfolio Domain: Overlays other domains to coordinate service ownership and management.
- Feedback Loops: Information flows back through earlier lifecycle domains to maintain data accuracy and relevance.
- Role-Based Data Responsibilities: CSDM outlines specific roles such as Enterprise Architect, Portfolio Manager, Service Owner, Service Desk, CMDB Manager, and Technical SMEs, clarifying who creates, maintains, and uses data to support services effectively.
Key Outcomes
- Improved impact and risk analysis through well-structured and accurate CMDB data.
- Enhanced business continuity by aligning data with service lifecycle and operational processes.
- Better asset and service management enabling efficient process enablement and audit readiness.
- Optimized use of ServiceNow AI Platform applications by ensuring data integrity and domain alignment.
- Clear governance and ownership of data promoting accuracy and effective service management.
Additional Resources
ServiceNow customers are encouraged to join the ServiceNow CSDM Community and explore available video resources to deepen their understanding and expertise in implementing the CSDM effectively within their instances.
The CSDM is the data model that admins should follow when they set up ServiceNow products and applications. The standards for defining configuration items (CIs) and relationships between CIs in the CMDB help to promote that your data resides in the appropriate CMDB tables. The result is maximum value from ServiceNow AI Platform applications.
Definitions of CSDM terms
See CSDM terms.
Goal of following the CSDM guidelines
Following the CSDM data model helps you to accurately and completely capture the data objects that help you to run your business.
CSDM provides guidance on where to put data in the platform. Because there are multiple ways to identify and use data, the CSDM guidelines help you to determine the best data structures for supporting your organization's services.
Kinds of data
- Foundation (core CMDB population and relationship integrity)
- Asset management (hardware or software asset tracking, license alignment)
- Process enablement (change, incident and release management)
- Conformance and audit (policy adherence, audit readiness)
- Optimization (capacity planning and life cycle and cost management)
- Security operations (exposure mapping, policy enforcement, risk response)
How tables in CSDM data domains support the service life cycle
- When you first start working on an instance, your admins install and populate the CMDB data structures. The data is required to enable your platform features and capabilities. This kind of data is kept in tables that are considered foundational to all products on your instance. We therefore refer to this set of tables as the Foundation domain — it supports all of the other data domains.
- You start with an idea — an idea that implements your business model. The idea or concept is saved in data that you work on in the tables of the Ideation & Strategy domain.
- If your research determines that the idea has merit, you can decide to commit to it and move forward into designing and planning the idea. You might design the products to implement the idea internally or buy something to integrate into your organization's offerings. The supporting data lives in tables in the Design & Planning domain.
- After the design is complete and acceptable, you can hand it off to the teams that will build or integrate the idea. Designers and developers build the software that implements the idea. The supporting data lives in tables in the Build & Integration domain. Information learned in this stage of the product life cycle is fed back into data in the domains that were involved earlier in the digital product's life cycle.
- Now it's time to provide infrastructure and management capabilities. The CIs and assets — service instances, applications, functions, AI, hardware, and software in the Service Delivery data domain. Information learned in this stage is also fed back.
-
You can now release the idea. It's delivered from the infrastructure and management of the Service Delivery data domain to the catalog of service and business offerings in the Service Consumption data domain so that your customers can consume it. Customers can be internal or external. Again, information learned in this stage is fed back.
The Manage Portfolio domain is a layer on top of the CSDM conceptual model that interacts with the other CSDM domains. The typical user, a service owner, might be responsible for services in more than one domain.
Roles that create, maintain, and use the data
- Enterprise Architect and Application Owner
-
- Identify, enter, and maintain data in Business Application records
- Align enterprise applications to capabilities and business strategy
- Manage technology portfolio life cycle
- Portfolio Manager and Service Owner
-
- Own the Service or digital product
- Create Services and service offerings
- Set the SLAs
- Is informed of outages
- Request catalog items to be created for the offerings
- Service Desk, Incident Manager, and Change Manager
-
- Use the Cls and related service-related data to support and maintain services and Cls
- Support Service Operations
- Review and approve changes
- Maintain support processes
- App Service Admin and Technical SMEs
-
- Support, manage, and operate the underpinning technology that services rely on
- Subject matter technical experts that create change requests with data from CMDB
- CMDB Manager and Cl Analysts
-
- Maintain the accuracy and integrity of the CMDB
- Work with various SMEs to certify that the data is accurate and aligned to the data model
- Create Cls and own the SACM processes
CSDM Community
Join the ServiceNow CSDM Community to grow your CSDM expertise.