--- sourceDocument: Zurich ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/servicenow-platform Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Service Delivery domain # Service Delivery domain in the CSDM model {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 11 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Service Delivery domain in the CSDM model The Service Delivery domain in the CSDM model represents the end-to-end system responsible for delivering technology services to internal and external users. It includes infrastructure, technologies, integration patterns, operational models, and service delivery networks that support business applications developed in the Build \& Integration domain. This domain encompasses the digital products, deployed instances, and related components that provide and sustain service delivery in operational environments. Show full answer Show less ## Key Features * **Core Tables:** Includes tables for technology management services, technology management offerings, service instances (formerly application services), dynamic CI groups, and request catalogs. These tables support managing CIs, their relationships, and service delivery configurations. * **Service Instances:** Logical representations of deployed systems or application stacks, supporting multiple types (data, network, operational process, connection, facility). They underpin business and technology management services and enable monitoring via Event Management. * **Technology Management Services and Offerings:** Technology management services are linked with service owners and layered under business services. Offerings define specific service options such as performance levels, geography, availability, and support groups, and can be requested via catalogs. * **Dynamic CI Groups:** Groups of CIs created through CMDB queries, facilitating efficient management of infrastructure components related to technology management offerings and service instances. * **Relationships:** The domain defines relationships among service instances, business applications, infrastructure CIs, and technology management offerings, supporting comprehensive visibility and control. * **Applications and Infrastructure CIs:** Applications are discovered programs providing specific functions and are considered infrastructure CIs; infrastructure CIs represent physical and logical components like servers, databases, and routers. * **Integration with Other Domains:** Service Delivery aligns with ITSM processes (Incident, Problem, Change Management), Event Management, and Service Portfolio Management, enabling operational monitoring and portfolio governance. ## Practical Use for ServiceNow Customers * Manage and monitor the technology services that support your business applications and infrastructure effectively. * Use service instances to represent and map deployed systems, facilitating impact analysis and performance tracking. * Leverage dynamic CI groups to automate grouping of infrastructure components, simplifying management and change processes. * Define technology management offerings with clear service commitments and options, enabling consumers to request tailored services through catalogs. * Understand and maintain relationships among technology services, infrastructure, and applications to improve service reliability and decision-making. * Integrate with Event Management to detect and address health issues proactively in your service delivery environment. ## Key Outcomes * Improved visibility into the operational services and technologies delivering business value. * Enhanced ability to manage service performance, availability, and support through defined service offerings and commitments. * Streamlined service delivery processes by using consistent service instance representations and dynamic groupings. * Better alignment between technology management services and business services within the Service Portfolio Management framework. * Support for ITSM and ITOM processes through structured service and infrastructure data models. The Service Delivery domain represents the overall end-to-end service delivery system that includes the infrastructure, technologies, integration patterns (infrastructure, systems, data, processes, dependency models), service delivery networks, and operational models. Together, these items deliver the CSDM-conforming services to internal and external users and organizations. ## Tables in the Service Delivery domain {#manage-tech-servs-domain__section_lnw_s23_qfc} Users of tables in the Service Delivery domain provide and manage the operational environments and infrastructure that support your organization's business applications (as developed in the Build \& Integration domain). Typical users are service instance owners (for application and platform) and service delivery owners or service providers (for infrastructure and delivery). The tables in the Service Delivery domain represent the technology that your business sells or consumes in the provider view. Service Mapping and Discovery populate the tables. The tables in the domain also enable you to manage CIs and their relationships. The domain includes the following tables: * Technology management service (formerly Technical service) \[cmdb_ci_service_technical\] table. The Service Classification is Technical Service. * Technology management offering (formerly Technical service offering) \[service_offering\] table. The Service Classification is Technical Service. * Request catalog. Technology consumers can request technology management offerings through a request catalog. Catalogs are described in detail in [Service Catalog](https://www.servicenow.com/docs/5qz5yKUQ7shR1Shylr8j2A "Use the ServiceNow Service Catalog application to create service catalogs that provide your customers with self-service opportunities. Customize portals where your customers can request catalog items such as service and product offerings. You can also standardize request fulfillment to ensure the accuracy and availability of the items in the catalogs."). * Dynamic CI group \[cmdb_ci_query_based_service\] table. Service Classification is Technical Service. Technology management services in Event Management use the cmdb_ci_query_based_service table. * Service instance (called application service before CSDM v5) \[cmdb_ci_service_auto\] tables. The Service Classification is Application Service. * For manually-created and Service Mapping: Mapped Application Service \[cmdb_ci_service_discovered\] table (included in the base system). * When query-based: \[cmdb_ci_query_based_service\]. * When tag-based: \[cmdb_ci_service_by_tags\]. {#manage-tech-servs-domain__ul_t1v_l4j_qfc} {#manage-tech-servs-domain__ul_vt4_bms_mjb} The CIs in this domain are deployed instances of digital products and their related and discoverable components (such as installed applications, servers, and network components) plus documentation of the services that provide and support the deployed instances. The domain also represents the portfolio of technology management services in use. For more information on life cycles, see [Definitions of life-cycle values for tangible/physical CIs](https://www.servicenow.com/docs/qsb_05MdO8FnwZTVEvPaRA "The tangible/physical life-cycle states represent the overall life cycle of physical assets and CIs as related to their products. Tangible/physical assets are physical items that are stocked, for example computers, monitors, and keyboards. The stages and statuses for the tangible/physical life-cycle process are visible only in hardware-related tables in Asset Management and the CMDB."). The services are operational, which means that you can select them for ITSM Incident Management, Problem Management, or Change Management. ## Relationships between Service Delivery tables {#manage-tech-servs-domain__id_bbn_cf3_qfc} * SDLC component Contains::Contained by Service instance (optional to use this item). * Business application Consumes::Consumed by Service instance. * Service instance (a logical representation of a deployed system or application stack)Depends on::Used by /Sends Data To:: Service instance. * Service instance Depends on::Used by Application. * Application Runs on::Runs Infrastructure CIs. * Technology management service uses a reference attribute to specify the relationship with Infrastructure Technology management offering. Published to service owners and typically underpins one or more business services. A Technology management service may have an operational view made up of one or more Technology management offerings. * Technology management offering Contains::Contained by Service instance. Stratification of the Technical Service into options, including localization/geography, environment, pricing, availability, capability, support group (INCIDENT), technical approval group (CHANGE) and packaging options. * Technology management offering Contains::Contained by Dynamic CI Group. * Dynamic CI Group (a dynamic grouping of CIs, based on results of CMDB Groups queries) uses a related list to specify the relationship with Infrastructure CIs. * Business Service Offering Depends on::Used by Service instance. {#manage-tech-servs-domain__ul_blx_zb3_qfc} Note: Business services and technology management services connect to the spm_service_portfolio through the spm_taxonomy_node. See [Service Portfolio Management taxonomy](https://www.servicenow.com/docs/access?context=SPM2-taxonomy&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). ## Tables used during the Service Delivery phase of the service life cycle {#manage-tech-servs-domain__section-service-deliv-active-tables} ## Tables used during the Service Delivery phase of the service life cycle {#manage-tech-servs-domain__section_kd4_vfh_5fc} ## AI component tables used during the Service Delivery phase of the service life cycle {#manage-tech-servs-domain__section-ai-component-active-tables} API: The API data model is made available within the CMDB to assist in managing your API data. As part of API Insights, you can centralize your management of APls including, but not limited to, viewing API details, comparing APls, identify and resolve data gaps, and manage service relationships. API Function: from a virtual perspective. API Application: From an on-premises perspective. Al Function: Al SaaS applications deployed on public cloud platforms that offer scalable, on-demand services for machine learning, data processing, and Al-driven tasks. The applications provide flexible solutions without the need for on-premises infrastructure management. Al Application: Al software applications that can run on various platforms such as Linux, Windows, Docker containers, or Kubernetes (K8) clusters. The platforms support diverse Al workloads, including machine learning models, data analytics, and intelligent services or Al- enabled applications. ## Technology management services {#manage-tech-servs-domain__section_pwd_pzt_mjb} Technology management services are associated with service owners and are typically layered under one or more business services or service instances. A technology management service may have one or more technology management offerings. Users of technology management services can view and manage the technologies that you provide to the business. Event Management enables you to monitor service performance. You can also use Event Management to identify health issues for related infrastructure CIs and service instances. Technology management services can be managed as part of the Service Portfolio in the Service Consumption domain (that is, a Service Portfolio hierarchy can be referenced from a technology management service). This allows for a more complete hierarchy and management of both technology management services and business services within the Service Portfolio Management workspace and related workspaces. You can make better decisions when you know how spend on technology management services can improve performance and reliability of your business services. Note: Business services and technology management services connect to the spm_service_portfolio through the spm_taxonomy_node. See [Service Portfolio Management taxonomy](https://www.servicenow.com/docs/access?context=SPM2-taxonomy&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). ## Technology management offerings {#manage-tech-servs-domain__section_ncg_d15_mjb} Technology consumers can request technology management offerings (TMO) through the request catalog. Catalogs are described in [Service Catalog](https://www.servicenow.com/docs/5qz5yKUQ7shR1Shylr8j2A "Use the ServiceNow Service Catalog application to create service catalogs that provide your customers with self-service opportunities. Customize portals where your customers can request catalog items such as service and product offerings. You can also standardize request fulfillment to ensure the accuracy and availability of the items in the catalogs."). The consumer can typically select the following features and options: * Level of performance * Location or geography * Environment * Pricing * Availability * Capability * Support group (for incident) * Technical approval group (for change) * Packaging options (commitments) {#manage-tech-servs-domain__ul_t23_35y_lkb} Tip: Use dynamic CI groups to significantly improve management. For more information, see [Synchronize user groups for a technology management offering](https://www.servicenow.com/docs/qM1qnm83_flLHoPqBudBgA "Synchronize group assignment attributes on entire CI classes and individual CIs by creating a dynamic CI group for use by a technology management offering."). Technology management offerings typically have the following components: One or more service commitments : A service commitment defines the service delivery obligations agreed to between the consumer and the provider. Service commitments uniquely define the level of service in terms of availability, criticality, scope, pricing, and other factors. For example, an organization may offer two levels of support for a service instance: * Support for a production-level offering: Provides a high level of availability and criticality for production instances. Includes a 24/7, 5-minute response time guarantee (24 hours per day seven days per week). * Support for a non-production-level offering: Limited availability and criticality for non-production instances. Includes a 60-minute response time guarantee between 8:00 a.m. and 5:00 p.m., Monday through Friday. {#manage-tech-servs-domain__ul_yp4_s25_mjb} A service offering subscription that records which users have access to an offering : A technology management offering references the Service Categorization attribute in service tables to denote whether a technology management offering or offering is related to a business service or to a technology management service. Technology management offerings that are mapped to the \[service_offering\] table are classified as "technology management service" and are derived from the service. The technology management offering is based on how the parent serves a specific technical need. Every technology management service should have at least one technology management offering. Important: Each CI associated through a Dynamic CI Group can be related to only one technology management service or technology management offering. Conflicts can result when one service includes multiple offerings with different SLAs, OLAs, Support Groups, and commitments. ## Dynamic CI groups {#manage-tech-servs-domain__section_gg1_qm5_cmb} A dynamic CI group is comprised of CIs that result from a CMDB Groups query. For example, you can create a dynamic CI group based on location: "all web servers in Detroit" or "all Oracle databases in Mumbai". Note: Dynamic CI groups contain only CIs and can't contain other CI groups. Dynamic CI groups are mapped to the \[cmdb_ci_query_based_service\] table and are classified as either service instance or technology management service, as applicable. You might want to use dynamic CI groups in the following situations: Query-based service instance : You don't have Service Mapping enabled yet, but you have 12 servers and three database instances in MyAppServiceProd. You can replace your spreadsheets with a dynamic CI group as a service instance. See [Use the Dynamic CI Group method to populate application services](https://www.servicenow.com/docs/AZlOHKokJEYb~UUWkgpFAw "The Dynamic CI Group method for populating an application service, automatically generates a dynamic CI group. The members of the CMDB group that the dynamic CI group is based on, populates the application service. The application service continuously synchronizes with the CMDB group to reflect any changes in membership in the CMDB group."). Managed group of Infrastructure CIs : The web servers in Detroit are managed by the DetroitRockCity technology management offering. Instead of manually creating relationships from technology management offerings to Infrastructure CIs, use a dynamic CI group. A single relationship from your technology management offering CI (DetroitRockCity) to your dynamic CI Group (web servers in Detroit) gives you the visibility you need. A way to manage patches for your CIs : In Change Management, you can select the dynamic CI group for the CIs that you must update and use a business rule to auto-populate the Affected CI field. ## Service instances (called application services before CSDM v5) {#manage-tech-servs-domain__section_qrh_5m5_cmb} Service instance a relabel of \[cmdb_ci_service_auto\], which previously was called application service. Application services still exist. They were there as extended tables depending on how you managed that application service. For manual creation or service mapping, you go into the mapped application service. For tag-based, it would live in the tag-based application service table. The tables still exist and they are still application services and you're still gonna go to the application service wizard to create application services. New types of service instances are extensions of \[cmdb_ci_service_auto\]: * Data service instance \[cmdb_ci_data_service_instance\] * Network service instance \[cmdb_ci_network_service_instance\] * Operational Process service instance \[cmdb_ci_operational_process_service_instance\] * Connection service instance \[cmdb_ci_connection_service_instance\] * Facility service instance \[cmdb_ci_facility_service_instance\] {#manage-tech-servs-domain__ul_nrp_hh5_rfc} The Service Instance (called application service before CSDM v5) \[cmdb_ci_service_auto\] table supports service instances. A service instance is a set of interconnected applications and hosts that are configured to offer a service. A service instance is a logical representation of a deployed system or an application stack. Using service instances, you can view maps and change history for services. For example, the Event Management application can monitor service performance and identify health issues for service instances. Service instances can be internal, like an organization's email system or customer-facing, like an organization's website. For example, creating financial reports through a web-based application requires a computer, web server, application server, databases, middleware, and network infrastructure. The applications and hosts are configured to offer the service of financial reporting. A service instance represents an instance of such a business application or system in the development, test, or production environment. Service instances are the entry points for the Service Mapping feature. Service instances underpin a business or technology management service and are mapped to the CMDB Service Instance (called application service before CSDM v5) \[cmdb_ci_service_auto\] table for common reporting. Service instances are key relationship entities for IT Service Management (ITSM), IT Operations Management (ITOM), Strategic Portfolio Management (SPM), and Customer Service Management (CSM). Service instances include relationships between business applications, business services, technology management services, applications, and infrastructure CIs. You can expose a service instance by using the related business or technology management offering. For more information, see [Use Application Services dashboard to monitor health](https://www.servicenow.com/docs/lRdAS~iv5D3ReQPKfiOaHw "Use insights from the Application Services dashboard to reduce the number of incomplete application services by populating them and adding missing data. To use application services effectively, ensure that application services are fully configured and are populated."). Types of service instance in the Service Instance data model: * Data service instance * Network service instance * Operational Process service instance * Connection service instance * Facility service instance {#manage-tech-servs-domain__ul_wlb_brs_rfc} The table that a service instance maps to depends on the method used to create it:{#manage-tech-servs-domain__table_utv_mmk_qmb__entry__2} | Method used to create the service instance | Mapped to table | |-|-| | Top Down Discovery (Service Mapping) | cmdb_ci_service_discovered | | Dynamic CI Group (Query-based) | cmdb_ci_query_based_service | | Tags | cmdb_ci_service_tags | | Manual entry, using the Create a Service Instance form (formerly, the Create an Application Service form) | cmdb_ci_service_discovered | [Table 1. Methods mapped to tables] {#manage-tech-servs-domain__table_utv_mmk_qmb} * For more information about service instances and the methods you can use to create them, see [Application services](https://www.servicenow.com/docs/eE~CtriK27xA6lKWN2iC4g "Understand application services, learn about different application service types and how multiple ServiceNow business units and products use them.") and [Create an application service](https://www.servicenow.com/docs/HGiqhn7CKxGwHk7mRRW2nA "Create an application service to adhere to Common Service Data Model standards and to standardize the organization, maintenance, and monitoring of services in your organization."). * You can specify required attributes for service instances. For more information, see [Modify the attributes and relationships required for application services](https://www.servicenow.com/docs/rE_JDoFesTyIdD1eCd1Lxw "Modify the lists of attributes and relationships that are required when creating application services."). * You can set a relationship between a service instance and the components of other CSDM domains. See [Service Mapping](https://www.servicenow.com/docs/access?context=c_ServiceMappingOverview&version=zurich&pubname=zurich-it-operations-management&ft:locale=en-US). {#manage-tech-servs-domain__ul_c44_kxk_dxb} ## Applications {#manage-tech-servs-domain__section_yfn_qnq_5mb} An application is any program or module that defines behavior and performs a specific function. Applications are typically discoverable instances and provide a specific set of functions for one or more services. * The application table and extended tables contain uniquely discovered instances of code in use on the host. * Applications are considered infrastructure CIs. * The instance is limited to the applications on a single host. This limitation ensures that applications are uniquely identified during discovery. * There's a one-to-many (and not a one-to-one) relationship between the application and the service instance. A single installed application, such as a database instance, may support multiple service instances depending on the configuration and the use of the applications. {#manage-tech-servs-domain__ul_n4n_rnq_5mb} Note: The application table \[cmdb_ci_appl\] isn't an inventory or portfolio of your applications. Don't make the mistake of storing managed application details in the application table. Those details (inventory or application portfolio objects) belong in the business application table (as documented in [Design \& Planning domain in the CSDM model](https://www.servicenow.com/docs/jmgdE30lYIDRQPojDKOzmA "Enterprise architects and digital product owners work on the design and planning of digital products that your organization can either buy or build.")). ## Infrastructure CIs {#manage-tech-servs-domain__section_bd3_jdb_1wb} Infrastructure CIs are managed physical and logical components. A CI can be a single module, such as a server, database, or a router or a complete system such as a web server, database, or infrastructure. The underlying infrastructure components or CIs can be complicated. The complexity increases as data structures are layered on top of physical CIs. For that reason, you should work with a business relationship manager or enterprise architect to define your business capabilities and business applications. ## CSDM videos in the ServiceNow Community {#manage-tech-servs-domain__section_ljb_mww_mwb} [Playlist of all CSDM videos](https://www.youtube.com/playlist?list=PLkGSnjw5y2U7QNr9jL6TAgwQvYBI_LEtK) **Related tasks** * [Synchronize user groups for a technology management offering](https://www.servicenow.com/docs/qM1qnm83_flLHoPqBudBgA "Synchronize group assignment attributes on entire CI classes and individual CIs by creating a dynamic CI group for use by a technology management offering.")