---
sourceDocument: Yokohama ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/servicenow-platform

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Service Delivery domain

# Manage Technology Management Services domain in the CSDM framework {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Manage Technology Management Services domain in the CSDM framework

The Manage Technology Management Services domain in the Common Service Data Model (CSDM) framework governs the configuration items (CIs) and tables used by IT Operations Management (ITOM) tools like Service Mapping and Discovery.
It focuses on deployed digital products, their components, and the technology management services that support them.
These operational services are essential for IT Service Management processes such as Incident, Problem, and Change Management.
Show full answer Show less  
This domain serves technology service owners, service instance owners, and technology consumers who request technical offerings through the Service Catalog. It integrates with Event Management for performance monitoring and supports service portfolio management to improve decision-making regarding technology investments.

## Key Features

* **Core Tables:** Includes tables like Technology Management Service (\[cmdbciservicetechnical\]), Technical Service Offering (\[serviceoffering\]), Dynamic CI Group (\[cmdbciquerybasedservice\]), Mapped Application Service (\[cmdbciservicediscovered\]), and Service Instance (\[cmdbciserviceauto\]). These tables represent technology services, offerings, dynamic groupings of CIs, and service instances.
* **Technology Management Services:** These are linked to service owners and typically structured under business services. They have one or more offerings that consumers can request via the service catalog, with defined service commitments such as availability and support levels.
* **Technology Management Offerings:** These offerings specify features like performance, location, environment, pricing, and support groups. They include service commitments defining delivery obligations and support different tiers such as production or non-production.
* **Dynamic CI Groups:** Allow grouping CIs dynamically based on queries (e.g., all servers in a location). Useful for managing infrastructure, relationships, and patching without manual updates.
* **Service Instances:** Logical representations of interconnected applications and hosts delivering a service. They support monitoring, mapping, and relationship management across ITSM, ITOM, and other domains. Creation methods include Service Mapping, dynamic CI groups, tags, or manual entry.
* **Applications and Infrastructure CIs:** Applications are discovered software instances on hosts and considered infrastructure CIs. Infrastructure CIs include physical and logical components such as servers, databases, and routers. Proper classification avoids confusion between application inventory and business application portfolios.

## Practical Benefits for ServiceNow Customers

* Enables comprehensive management of deployed technology services and their components, improving visibility and control.
* Supports integration with ITSM workflows, allowing technology services to be selected for incident, problem, and change processes.
* Facilitates dynamic grouping of infrastructure CIs, reducing manual effort and errors in configuration and maintenance tasks.
* Improves service portfolio management by linking technology management services with business services for better investment and performance decisions.
* Provides structured service offerings with clear commitments, allowing consumers to select appropriate technical services tailored to their needs.
* Supports monitoring and health assessment through Event Management, enhancing operational reliability.  
The Manage Technology Management Services domain involves the tables used by IT Operations Management (ITOM) products such as Service Mapping and Discovery. These are deployed instances of digital products and their related and discoverable components and documentation of the services that provide and support the deployed instances.

The CIs in this domain are discovered items such as installed applications, servers, and network components. The Manage Technology Management Services
domain also represents the portfolio of technology management services in use. These services are operational, which means that you can select them for ITSM
Incident Management, Problem Management, or Change Management.

Typical users are service instance owners (for the application and platform) and technology service owners (for the infrastructure and delivery). Technology consumers can request technical service offerings through the request catalog. Catalogs are described in detail in [Service Catalog](https://www.servicenow.com/docs/SM5JQFexJu_oR7haj0sliQ "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 tables in the Manage Technology Management Services domain represent the technology that your
business sells or consumes in the provider view. Service Mapping and Discovery populate the tables. They also enable you to manage CIs and their relationships. Those products accelerate the process and minimize errors, but you aren't required to use them. The domain includes the
following tables:  
* Technology management service \[cmdb_ci_service_technical\] table (formerly Technical service --- renamed in CSDM v5)
* Technical service offering \[service_offering\] table
* Request catalog.
* Dynamic CI group \[cmdb_ci_query_based_service\] table. Technology management services in Event Management use the cmdb_ci_query_based_service table.
* Mapped Application Service \[cmdb_ci_service_discovered\] table (included in the base system)
{#manage-tech-servs-domain__ul_vt4_bms_mjb}

## 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 Sell/Consume 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=yokohama&pubname=yokohama-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 detail in [Service Catalog](https://www.servicenow.com/docs/SM5JQFexJu_oR7haj0sliQ "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}  
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 [Populate an application service using the Dynamic CI Group method](https://www.servicenow.com/docs/carsI7Pz1tJpht5u36zygQ "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 Technical service offering. Instead of manually creating relationships from Technical service offerings to Infrastructure CIs, use a dynamic CI group. A single relationship from your Technical service 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 you need to update and use a business rule to auto-populate the Affected CI field.

## Service instances (formerly application services) {#manage-tech-servs-domain__section_qrh_5m5_cmb}

The Service Instance \[cmdb_ci_service_auto\] table (formerly Application Service table --- renamed in CSDM v5) 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 \[cmdb_ci_service_auto\] table (formerly Application Service table --- renamed in CSDM v5) 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 technical service offering. For more information, see [Monitor the health of application services on the Application Services dashboard](https://www.servicenow.com/docs/T5drxtglZNlh6OhZyyWLbQ "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.").  
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 --- renamed in CSDM v5) | 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/HyIXCV~~14IFXRZbIO2rCg "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/wnVYlMLrf78~IacK9~fL7Q "Create an application service to adhere to CSDM standards and to standardize the organization, maintenance, and monitoring of services in your organization.").
* You can specify required attributes for service instances. See [Specifying attributes and relationships for service instances](https://www.servicenow.com/docs/aVEBRU54lp2wGoY9eaRMng "Use the Service Instance Settings module to specify the attributes and relationships that are required when a user creates a service instance.") and [Modify the attributes and relationships required for application services](https://www.servicenow.com/docs/RwLJJyJG42Fo8Q6vevJEzQ "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=yokohama&pubname=yokohama-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 domain in the CSDM framework](https://www.servicenow.com/docs/RO9xBlKTTWTql0lJDKU7vQ "The Design domain supports the design and planning of digital products. CIs in the Design domain aren’t operational, so you can’t select them for Incident Management, Problem Management, or Change Management. Enterprise architects and application owners are the typical users of tables in this domain.")).

## 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)