- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2026 01:15 PM
Hello Dears
I am currently working on a ServiceNow implementation that includes the following modules:
• ITSM (Incident, Change, Problem, Request)
• ITOM (Discovery + Service Mapping)
• SAM Pro (Software Asset Management)
• SPM (Demand Management)
As part of the CMDB design, we are trying to build our implementation following ServiceNow best practices and align our approach with the CSDM framework. We would appreciate clarification on the following:
1. cmdb_ci_service vs cmdb_ci_business_app — correct usage boundary
My current understanding is:
• cmdb_ci_service represents operational services consumed by end users and is the correct CI class to associate with ITSM records (Incidents, Changes, Problems, Requests). It is also can be auto-populated by Service Mapping.
• cmdb_ci_business_app represents business applications from an organizational/portfolio perspective, lives in the Design domain of CSDM, and is more relevant to APM and SPM rather than ITSM ticket association.
Is this understanding, correct? And what is the recommended CSDM relationship between these two classes — specifically in a context where Service Mapping is active and populating Services how will these services be classified as Application Services, Business Services or Technology Management Service — following best practices? In addition, if we have a Business Application that can be considered a Service as well what will the best practices in defining the name for it as a Business Application and as s Service?
2. Mapping Business Applications to Software Entitlements in SAM
Given that cmdb_ci_business_app will be used as the anchor for Demand Management in SPM — is it a supported and recommended best practice to link Business Applications to their underlying software entitlements in SAM Pro?
#CMDB
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 11:06 PM
Hi @Majdsalim ,
Your understanding is generally correct and aligns well with CSDM principles.
For cmdb_ci_business_app, think of it as the logical representation of an application from a business, portfolio, and architecture perspective. It is primarily used for ownership, lifecycle management, investment planning, and SPM/APM use cases.
For operational processes such as Incident, Change, Problem, Event Management, Discovery, and Service Mapping, the recommended CSDM approach is to use Application Services and Business Services rather than the Business Application record itself.
When Service Mapping is enabled, the discovered services are typically created as Application Services, which represent the running application and its supporting infrastructure. These Application Services can then support one or more Business Services that represent the business capability consumed by users.
A simplified relationship model would be:
Business Service → Application Service → Infrastructure CIs
and
Business Application → Application Service
This provides traceability between the portfolio view and the operational view while maintaining CSDM alignment.
Regarding naming, if the Business Application and Service represent the same business capability, it is common to keep the business name on the Business Application (e.g., "SAP ERP") and use environment- or operation-specific names for Application Services (e.g., "SAP ERP Production", "SAP ERP UAT").
For your second question, associating Business Applications with software products/models used by the application is a common practice and provides valuable insights for SAM, APM, and SPM reporting. However, entitlement compliance calculations should continue to be driven by Software Models, Installations, Entitlements, and Contracts. The Business Application should be treated as a consumer or owner context rather than the licensing source of truth.
Following this model keeps ITSM, ITOM, SAM Pro, and SPM aligned with CSDM while maintaining clear separation between business architecture, operational services, and software licensing.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2026 01:10 AM
Yes, your understanding is generally correct and aligns with CSDM best practices. In CSDM, cmdb_ci_business_app represents the logical/business-facing application from a portfolio and ownership perspective, mainly used in APM/SPM and business planning. On the other hand, cmdb_ci_service (more specifically Application Services under CSDM) represents the operational service consumed by users and is the recommended CI to associate with ITSM processes such as Incidents, Changes, Problems, and Requests. With Service Mapping enabled, discovered services are usually classified as Application Services because they represent running operational services supported by infrastructure. The best-practice relationship is typically: Business Application → supports/provided by → Application Service. If the same application is also exposed as a service, use different naming conventions to avoid confusion — for example, “SAP ERP” as the Business Application and “SAP ERP Production Service” as the Application Service.
Regarding SAM Pro, yes — linking Business Applications to software entitlements is both supported and recommended. In mature CSDM-aligned environments, the Business Application acts as the governance and planning anchor, while SAM tracks software usage, licenses, and entitlements underneath it. This relationship provides better visibility for cost, ownership, compliance, lifecycle management, and Demand Management within SPM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 11:06 PM
Hi @Majdsalim ,
Your understanding is generally correct and aligns well with CSDM principles.
For cmdb_ci_business_app, think of it as the logical representation of an application from a business, portfolio, and architecture perspective. It is primarily used for ownership, lifecycle management, investment planning, and SPM/APM use cases.
For operational processes such as Incident, Change, Problem, Event Management, Discovery, and Service Mapping, the recommended CSDM approach is to use Application Services and Business Services rather than the Business Application record itself.
When Service Mapping is enabled, the discovered services are typically created as Application Services, which represent the running application and its supporting infrastructure. These Application Services can then support one or more Business Services that represent the business capability consumed by users.
A simplified relationship model would be:
Business Service → Application Service → Infrastructure CIs
and
Business Application → Application Service
This provides traceability between the portfolio view and the operational view while maintaining CSDM alignment.
Regarding naming, if the Business Application and Service represent the same business capability, it is common to keep the business name on the Business Application (e.g., "SAP ERP") and use environment- or operation-specific names for Application Services (e.g., "SAP ERP Production", "SAP ERP UAT").
For your second question, associating Business Applications with software products/models used by the application is a common practice and provides valuable insights for SAM, APM, and SPM reporting. However, entitlement compliance calculations should continue to be driven by Software Models, Installations, Entitlements, and Contracts. The Business Application should be treated as a consumer or owner context rather than the licensing source of truth.
Following this model keeps ITSM, ITOM, SAM Pro, and SPM aligned with CSDM while maintaining clear separation between business architecture, operational services, and software licensing.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2026 01:10 AM
Yes, your understanding is generally correct and aligns with CSDM best practices. In CSDM, cmdb_ci_business_app represents the logical/business-facing application from a portfolio and ownership perspective, mainly used in APM/SPM and business planning. On the other hand, cmdb_ci_service (more specifically Application Services under CSDM) represents the operational service consumed by users and is the recommended CI to associate with ITSM processes such as Incidents, Changes, Problems, and Requests. With Service Mapping enabled, discovered services are usually classified as Application Services because they represent running operational services supported by infrastructure. The best-practice relationship is typically: Business Application → supports/provided by → Application Service. If the same application is also exposed as a service, use different naming conventions to avoid confusion — for example, “SAP ERP” as the Business Application and “SAP ERP Production Service” as the Application Service.
Regarding SAM Pro, yes — linking Business Applications to software entitlements is both supported and recommended. In mature CSDM-aligned environments, the Business Application acts as the governance and planning anchor, while SAM tracks software usage, licenses, and entitlements underneath it. This relationship provides better visibility for cost, ownership, compliance, lifecycle management, and Demand Management within SPM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2026 04:55 AM
Hi all,
I need to build a query to identify which Business Applications are utilizing a specific Software Product (e.g., Kafka). Best possible way for all may be 100k software products,
Based on our CSDM framework, tracing this requires traversing depends on-hop relationship:
Business Application (cmdb_ci_business_app) -> Consumes ->
Application Service (cmdb_ci_service_auto / cmdb_ci_service_discovered) -> Contains / Depends on ->
Software Product (e.g., Kafka installed on the underlying infrastructure)
My ask: What is the most performant and maintainable way to identify and query multi-hop path for all the software products in ServiceNow?
Would setting up a custom Database View joining these tables and cmdb_rel_ci be more efficient?
Any insights on best practices for querying this architecture would be appreciated.
Thanks,
Query multi-hop CSDM relationships: Mapping Business Applications to underlying Software Products
#ITAM #ITOM #SAM #CMDB #CSDM
need solution for this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
There are two different questions in here and I think separating them is most of the answer.
"Which Business Applications use Kafka" is a lookup. "The same path for all 100k software products" is a materialisation problem. They want opposite solutions, and conflating them is usually what makes a Database View look like the right idea.
For the single-product lookup, turn the traversal around. You have written it top-down, starting at cmdb_ci_business_app and walking to the product. Kafka is a small seed set, so start there and walk up. At your volumes the direction of travel matters more than the indexing does.
For all products at once, I would not use a Database View. Three self-joins on cmdb_rel_ci is the expensive part, not the CI tables, and a view re-pays that cost on every single read while giving you very little to index against. What has held up for me is flattening it on a schedule: a job that walks the path and writes a flat Business Application to Software Product table, with the path it used recorded on the row, refreshed nightly or weekly. Then everything downstream queries something flat, and the expensive traversal happens once rather than per reader.
The maintainability trap is the one you have already half-spotted by naming both cmdb_ci_service_auto and cmdb_ci_service_discovered. Whatever you build, be explicit about which service classes are in scope and store that as part of the result. Otherwise someone adds a class six months from now, the number moves, and nobody can tell whether the estate changed or the query did.
Then the part I would want to know before I trusted any of it.
That path only returns Business Applications whose relationships are actually populated, and the two hops do not come from the same place. Consumes, between the Business Application and the Application Service, is usually asserted by a person during onboarding. Contains / Depends on, below it, is usually discovered. So they have different coverage, and the gaps are rarely in the same applications. What comes back is "the dependencies that happen to be modelled", which is genuinely useful but is not the same thing as the list you asked for, and the difference matters if the next step is a migration, an upgrade window or a vulnerability response.
Two cheap checks. How many Business Applications have no downward relationship at all — those can never appear in your result whatever is running underneath them. And how does the relationship walk compare against the raw software install records, which are discovered and therefore have completely different coverage from the modelled path. If walking relationships finds 40 Business Applications for Kafka and the install data says it is on 300 hosts, that gap is the finding rather than an error.
Where those two disagree is usually the most interesting output of the whole exercise.
So whatever you flatten, carry both numbers on it: what the modelled path found, and what the install data found. A single number invites everyone downstream to treat it as complete, and this is exactly the kind of question where nobody goes back and checks.