cmdb_ci_service vs cmdb_ci_business_app — correct usage boundary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
54m ago
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
