Select Page

DCM Blueprint Library

CSDM-aligned, audit-ready DCM Blueprints to improve your ServiceNow data quality. Use these templates as they are or tweak them to match your requirements. 

ServiceNow Platform Partner
Locations – Hierarchy Starting from Sites v2

Locations – Hierarchy Starting from Sites v2

This blueprint anchors your location data on the Site, then builds a governed hierarchy up through City, State/Province, Country, and Region while tying each site to a responsible Company, an active Contact, and an owning Group. It gives foundation data a single, CSDM-aligned structure to grow from, so sites stay accountable, locatable, and ready to support service management and reporting.

Servers – CSDM 5 Walk

Servers – CSDM 5 Walk

This blueprint models the Walk phase of CSDM 5 for Servers, extending the Crawl-phase ownership and support model with hardware traceability, a formal link to the technology service that manages the server, and visibility into the business application it ultimately supports. It closes the gap where a server has an owner and a support group but no defined place in the technology and business service layers.

AI Digital Assets – Minimum Viable Data

AI Digital Assets – Minimum Viable Data

This blueprint delivers a Minimum Viable Data Model for AI Digital Assets, aligned with ServiceNow’s AI Control Tower (AICT) data model. It gives every AI asset — model, dataset, prompt, agent, AI system, or MCP server — a product model resolved to the right class for its type, a traceable vendor and manufacturer, and clear ownership, so AI initiatives start with the governance foundation AICT and emerging AI regulation expect.

Technology Management Service Offerings – CSDM5 Walk

Technology Management Service Offerings – CSDM5 Walk

This blueprint models the Walk phase of CSDM 5 for Technology Management Service Offerings, giving every technical service a clear owner, an accountable support and management group, and a consistent way to group the configuration items it delivers. It closes the gap where technical services live in the CMDB without a defined provider, preparing the model for catalog exposure and later Service Portfolio maturity.

Business Service Portfolio Management – Taxonomy Model

Business Service Portfolio Management – Taxonomy Model

This blueprint structures Business Services into a managed portfolio by combining a layered taxonomy, clear ownership, and the concrete offerings that sit beneath each service. It builds on the SPM plugin to give the CMDB a navigable service catalog that can be reported on at portfolio, layer, or service level.

Technology Management Service Offerings – Contracts and SLA for DORA

Technology Management Service Offerings – Contracts and SLA for DORA

This blueprint helps you model how a Technology Management Service Offering is governed through commitments, contracts, and SLA definitions so the service can be described, owned, supported, and evidenced in a DORA-friendly way. It is especially useful when you need to show not only what technology service is being delivered, but also under which contractual terms, service levels, and accountability structures it is delivered.

Business Service Offering Subscribers for DORA

Business Service Offering Subscribers for DORA

This blueprint helps you structure Business Service Offerings for DORA by showing who consumes a service offering and how that consumption can be represented across different subscriber types. It is built around a Business Service Offering root and ties it to its parent Business Service, the provider organization, and the consuming parties that matter for operational resilience reporting.

Business Applications to Business Functions – DORA RT.07.01

Business Applications to Business Functions – DORA RT.07.01

This blueprint shows how Business Applications can be used as the design anchor for DORA RT.07.01 reporting, while also connecting the application to the business, service, and technology layers that support a critical or important business function. It is designed to improve traceability from the business capability level down to the service instance and underlying technology management context, with clear ownership and organizational accountability.

Your Blueprint

Your Blueprint

What kind of blueprint you need? Or which blueprints you have found useful and would like to share with other DCM users?

Let us know, and we can work together to draft a blueprint and share best practices within the DCM community.

Departments – Organizational Structure Alignment

Departments – Organizational Structure Alignment

This blueprint defines how Departments, Business Units, Companies, Cost Centers, and Users align to form a clean, authoritative organizational structure. It establishes the foundational data needed for service ownership, reporting, governance, and CMDB alignment before deeper CSDM modeling begins.

Technical Service Offerings – CSDM 4 Walk

Technical Service Offerings – CSDM 4 Walk

The Technical Service Offerings – CSDM 4 Walk blueprint helps organizations mature their CMDB by modeling technical service offerings that connect infrastructure, applications, and service operations. It builds on CSDM 4’s guidance for the Walk phase, where technical services become structured and governed through defined ownership, catalog alignment, and operational support groups.

Service Instances – CSDM 5 Crawl

Service Instances – CSDM 5 Crawl

This blueprint helps organizations establish a foundational CMDB structure for Service Instances following the CSDM 5 Crawl phase. It introduces the key relationships that connect technical infrastructure, business applications, and users, enabling better visibility into how services are delivered and supported across the enterprise.

Servers – CSDM 5 Crawl

Servers – CSDM 5 Crawl

This blueprint defines the CSDM 5 Crawl-phase data model for Servers, ensuring that every discovered or integrated server record is connected to responsible people, groups, and the services it supports. It helps organizations move from basic CMDB population toward service-aware infrastructure data management.

Business Applications – CSDM 4 Walk

Business Applications – CSDM 4 Walk

This blueprint defines how to structure and govern Business Applications in the CMDB at the Walk stage. It extends the Crawl model by adding stronger service context links, ensuring Business Applications are consistently tied to ownership, support, and technical service offerings.

Value Streams – CSDM 5 Foundation

Value Streams – CSDM 5 Foundation

This blueprint structures value streams and connects them to business capabilities, processes, and services. It provides a way to model how products and services deliver value, ensuring organizations can trace business outcomes back to supporting capabilities and IT applications.

Business Applications – CSDM 5 Crawl

Business Applications – CSDM 5 Crawl

This blueprint provides a starting point for modeling Business Applications in the CMDB at the Crawl phase. It ensures that Business Applications are tied to clear ownership, support groups, lifecycle components, and service instances—establishing a reliable foundation for application governance and service alignment.

Application Services – CSDM 4 Run

Application Services – CSDM 4 Run

This blueprint represents the Run-phase maturity model for Application Services in CSDM. It builds on the Crawl and Walk stages by expanding service context to include both Technical and Business Service Offerings, ensuring Application Services are fully aligned with service delivery, ownership, and infrastructure.

Business Applications – Minimum Viable Data

Business Applications – Minimum Viable Data

This blueprint defines the minimum viable data model for Business Applications. It ensures that Business Applications are consistently managed by assigning ownership from a data management point of view, and linking applications to the Service Instances they use.

Personal Computers – Connected to Users and Contracts

Personal Computers – Connected to Users and Contracts

This blueprint ensures that every personal computer (PC) in the CMDB is properly connected to the people and contracts that govern its lifecycle. It provides a practical model to validate that all PCs have an active user, an asset record, and a valid contract, while maintaining key identification attributes.

Users – Organizational Structures

Users – Organizational Structures

This blueprint ensures that all users are properly connected to organizational structures such as departments, business units, companies, and managers. It creates a reliable foundation for workflows, reporting, and governance by making sure user records are not isolated or incomplete.

Business Service Offerings – CSDM 4 Run

Business Service Offerings – CSDM 4 Run

This blueprint describes how to structure and govern Business Service Offerings in the Run phase of the CSDM journey. It ensures that offerings are clearly tied to services, consumers, and operational responsibilities, supporting end-to-end visibility and control.

Servers – CSDM 4 Crawl

Servers – CSDM 4 Crawl

This blueprint provides a foundation for modeling Servers in the Common Service Data Model (CSDM) at the Crawl stage. It ensures Servers are properly connected to people, groups, and services, reducing data quality issues and improving operational control.

The CMDB Data Quality Playbook

A Practical Guide for Improving ServiceNow Data Quality, Governance and AI-Readiness.

  • A practical way to establish ownership and roles
  • The 5-step model for data quality improvement
  • Best practices for engaging data providers
  • Five common pitfalls in CMDB data quality and how to avoid

We need your contact information to send you this eBook and communicate with you. You can unsubscribe anytime.