Common Service Data Model (CSDM) in ServiceNow

As organizations increasingly rely on digital services, managing and organizing data efficiently becomes critical to success. ServiceNow’s Common Service Data Model (CSDM) provides a standardized approach to structure and organize service-related data within the platform.

This blog article will explore the goals, purpose, objectives, and design for implementing and maintaining CSDM in your ServiceNow environment.

What is CSDM?

The Common Service Data Model is a framework and data model used in ServiceNow to define and organize Configuration Items (CIs) and services in the CMDB (Configuration Management Database). It provides guidelines on how data should be structured to support business, IT, and digital services across various workflows and processes.

CSDM is not just a one-time initiative but an evolving framework that helps align your CMDB with IT and business processes, ultimately improving visibility and decision-making across your organization.

Goals of CSDM

Among the goals of CSDM are:

1. Provide a Consistent Framework – CSDM offers a standardized way to categorize and manage data, ensuring that services, applications, and infrastructure are well-structured across the ServiceNow platform.
2. Align CMDB to Business and IT Processes – CSDM bridges the gap between business operations and IT, ensuring that your CMDB accurately reflects how services are cocreated and consumed.
3. Improve Decision-Making – by providing a clear view of services and dependencies, CSDM enables better insights into your IT landscape, helping with change enablement, incident response, and problem resolution.
4. Support ITSM, ITOM, and SPM – CSDM helps unify IT Service Management (ITSM), IT Operations Management (ITOM), and Strategic Portfolio Management (formerly known as  IT Business Management – ITBM) processes, making them more effective and aligned with organizational goals.

The primary overarching goal of CSDM is to ensure the CMDB reflects a consistent and accurate service structure that integrates seamlessly with key processes like incident, problem, change management, and service portfolio management.

By implementing CSDM, organizations can:

• Improve the accuracy and quality of CMDB data.
• Create a unified view of the services delivered to the business.
• Enable automation in key processes like discovery, service mapping, and service delivery.
• Support better service management by establishing clear relationships between services, applications, and infrastructure.

Key objectives of CSDM

When thinking about the key goals of CSDM, we should consider:

1. Service Alignment – ensure that CIs are aligned with the services they support, enhancing visibility across the service portfolio.
2. Data Quality – maintain high data quality and integrity in the CMDB by ensuring compliance with ServiceNow best practices.
3. Support Digital Transformation – create a clear service and operational model that scales with the business to enable organizations to transition smoothly toward digital transformation.
4. Improved Reporting – enhance reporting and analytics by providing a structured view of service-related data, allowing for better performance monitoring and resource allocation.
5. Drive Automation – facilitate automation by defining relationships between services and infrastructure and improving workflows like event management, discovery, and orchestration.

Design and Structure of CSDM

CSDM is designed as a hierarchical framework that organizes data around 5 core domains:

1. Build Domain – the build domain focuses on creating and structuring the foundation for technical services. This phase involves establishing the infrastructure and applications required for a specific service. It’s essentially about putting the pieces in place before the service design takes place.
2. Design Domain – captures how services are planned and designed, including business and technical service portfolios. The Design domain is where services are planned and architected. In this phase, teams define the service components, relationships, and processes that will be used to manage these services in real-time. It’s crucial to ensure that your services align with the business objectives.
3. Manage Technical Services Domain – focuses on the operational aspect, helping maintain and support technical services, often in applications and infrastructure. Here, organizations manage the day-to-day health, performance, and availability of technical services. This domain ensures that the services are running smoothly and meeting SLAs.
4. Sell/Consume Domain – the Sell and Consume domain revolves around how services are offered to end users and how they consume them. It’s about making sure that the value of the service is effectively communicated to the customer and that they can easily access and use it. It represents how business services and products are sold or consumed by end users.
5. Manage Portfolio Domain – deals with the overall service portfolio management, ensuring alignment with business objectives.

     The following diagram presents the described domains of the CSDM model.  

At the core of CSDM are key data objects like:

• Business Service – a service delivered to customers.
• Technical Service – a service that supports the business service, typically consisting of applications and infrastructure.
• Application – represents a software application that provides a service.
• Infrastructure – physical or virtual devices that support applications.

Organizing your CIs within these domains and objects creates a structured data model that enables a clearer view of service dependencies and relationships.

CSDM implementation stages

Implementing CSDM isn’t an overnight process. ServiceNow suggests a phased approach to ensure successful adoption. These phases can be considered progressive steps in the maturity of your organization’s service data model.

ServiceNow’s CSDM (Common Service Data Model) implementation is typically broken down into several key stages, each focusing on building and improving the data model within the Configuration Management Database (CMDB).

Here are the main stages:

1. Foundation Stage – the initial stage focuses on setting up Foundation Data, such as locations, users, groups, business units, and basic configuration items (CIs). This ensures that the core data structure is in place for building accurate service models.
2. Crawl Stage – in this phase, organizations start modeling basic IT services by associating configuration items with foundational data. The focus is on creating Business Applications, Application Services, and Technical Services, building simple relationships between CIs, and preparing for deeper service management processes.
3. Walk Stage – this stage introduces Business Services, which are mapped to the Application Services and technical infrastructure. Here, organizations establish more detailed relationships between business services or processes and IT infrastructure, enabling better visibility and reporting for service management.
4. Run Stage – the CSDM is fully operational in this stage, with a complete and dynamic service portfolio. Services are linked to business capabilities, and detailed service health and service level management are enabled. Organizations can leverage this model for continuous improvement and real-time decision-making.
5. Fly Stage – in the Fly phase, organizations have reached the pinnacle of CSDM adoption. Services are fully integrated, optimized, and deliver maximum value, and the organization is benefiting from continuous improvement in service management.

These stages ensure a structured and scalable approach to implementing CSDM, aligning IT infrastructure with business services for enhanced operational efficiency and service delivery.

CSDM Practical Examples of Implementation

Crawl Stage

We can refer to the diagram below as a practical example of modeling the ServiceNow Platform.

Figure 2 (below) presents three environments of Xanadu release:

• PROD,
• TEST,
• DEV

modeled as Application Services. All are related with a Business Application called ‘ServiceNow Platform.’

Next to ‘ServiceNow Platform’ are three other business applications:

• ‘SN Knowledge Management’,
• ‘SN Incident Management’,
• ‘SN Service Catalog and Request Management.’

The more ITSM processes are used, the more business applications related to them are defined.

These business applications represent the ServiceNow Incident Management application, Knowledge Management application, Service Catalog application, and Request module.

As there are three environments (PROD, TEST, DEV), we need to model three application services and connect them with business applications. ServiceNow Platform is a Platform Host and hosts all other business applications, such as SN Knowledge Management, SN Incident Management, and SN Service Catalog and Request Management.

Walk Stage

We can refer to the diagram below as a practical example of modeling the ServiceNow Platform.

Figure 3 presents ServiceNow as a Business Service called ‘End User Services.’ End users can choose specific Service Offering like ‘Service Request and Catalog Management’. This business service (End User Services) consists of three Service Offerings: it is possible to choose them:

• Incident Management.
• Knowledge Management.
• Service Catalog Request Management.

Each Service Offering corresponds with a dedicated Application Service on ServiceNow PROD.

The more services an organization delivers on the ServiceNow platform, the more related Service Offerings will appear, such as Problem management, Change management, etc.

Sii x ServiceNow

With the cloud-based ServiceNow AI platform, we automate processes and facilitate the work of departments to increase productivity within entire organizations.

ServiceNow offering

Conclusion

While the Common Service Data Model may not yet be perfect, its value to organizations is undeniable. It provides a clear, structured way to align technical services with business needs, ensuring that service management is effective and scalable.

By adopting CSDM, organizations can drive improved service delivery and governance, regardless of where they are in their maturity journey. The successful adoption of CSDM hinges on a thorough understanding of its terms and definitions across the organization. Numerous implementations have demonstrated that this foundational knowledge significantly increases the chances of successful CSDM deployment within an organization.

Sources

CSDM 4. 0 DRAFT White Paper

***

If you are interested in the ServiceNow area, be sure to also take a look at other articles by our experts.