Build & Integration domain in the CSDM model
- UpdatedJul 31, 2025
- 2 minutes to read
- Zurich
- Common Service Data Model
Development teams use the tables in the Build & Integration domain during the build effort (systems development life cycle — SDLC or Agile development) of digital products. The tables represent the logical development details of the enterprise applications (digital products) to be deployed and used by your organization. These are not operational CIs.
Tables and relationships in the Build & Integration domain
An SDLC component is a CI that represents a unique development effort of code. It represents parts of a larger business application or digital product broken down into its individually developed components. In other words, the SDLC component is a software element of a larger application or technology. SDLC component CI records in the SDLC Component [cmdb_ci_sdlc_component] table enable the DevOps product to provide enhanced capabilities for visualizing and managing your application development pipeline.
Records in the table are not operational and are not direct targets of the ITSM Incident Management, Problem Management, or Change Management processes. You therefore are not required to configure SDLC component records. The SDLC Component table is available through the CMDB schema version 1.33.
The DevOps Change Data Model is built on a powerful data model that connects your DevOps toolchain to the work and data already in the platform. The model provides the ability to accelerate changes while ensuring effective and transparent risk management.
The Build & Integration domain includes the following tables and relationships:
- Business application (Service Consumption domain) Contains::Contained By SDLC component
- SDLC component has a Contains::Contained By relationship with the Service instance table in the Service Delivery domain.

Tables used during the Build & Integration phase of the service life cycle
The Al System Digital Asset represents the Software/ Application components for Al and Gen Al services. For the purposes of build, integration, and Al governance, the Al System Digital Asset (ServiceNow, third party, or custom) represents the deployable software source, binaries, and components that feed into the Build & Integration pipelines. An asset can be deployed or not currently deployed.

Types of SDLC component
- Application: A service instance is a deployed instance of the SDLC application component. Examples include micro services and APIs. The build team typically builds service instances on behalf of the Service Owner (as described in Manage Portfolio domain in the CSDM model).
- Infrastructure: Any infrastructure CI that represents a snapshot of its configuration details is a deployed instance of the SDLC infrastructure component. Examples include database and security configurations.