Problem
CMDB is “just for techies” if you’re missing the business context. In the end, every Configuration Item should be related to business and users to understand business impact and promises made.
Organizations often struggle to maintain clear ownership and lifecycle relationships between Business Service Offerings and the services or catalogs that consume them. Without standardized links, it becomes difficult to:
- Track which service offerings are active and who manages them.
- Understand dependencies between business and application services.
- Align the service catalog with operational data in the CMDB.
This blueprint solves those challenges by defining the Run-phase configuration for business service offerings that are already live, ensuring all supporting relationships are complete and compliant with CSDM 4.
What this Blueprint Includes
This is a CSDM Run phase template includes the following entities related to Business Service Offerings:
- Business Service Offering (root) – the defined unit of service consumption published to users.
- Business Service – the logical service that the offering belongs to.
- Catalog – the catalog that holds catalog items linked to offerings.
- Catalog Item – the items that represent requestable services/products.
- Application Service – the technical instance that underpins and delivers the offering.
- User – individuals associated with ownership or management.
- Group – teams responsible for support or management.
- Service Portfolio – groups and categorizes services for visibility and lifecycle management.
Considerations
- Ensure Service Offerings are filtered for Business Service classification only.
- Review and align Group assignments with your organization’s operational model.
- Confirm all User references (Managed by / Owned by) point to active records.
- The Application Service relationship should reflect actual operational dependencies (e.g., service instances or mapped application components).
- Keep Catalog and Catalog Items synchronized with the offering’s lifecycle stage.
- Optionally extend the model to include approval groups or additional references based on your change or release processes.
Benefits
- Improves visibility of who manages, supports, and consumes business service offerings.
- Ensures consistency across CMDB, Service Catalog, and operational services.
- Enables automation of change and incident workflows through complete reference data.
- Supports service reporting and impact analysis by linking business and technical layers.
- Strengthens alignment with the CSDM Run phase and prepares for Fly maturity stage.
Related Information
Check other blueprints related to Service Consumption.
How to Get This Blueprint?
If you’re already a Data Content Manager Customer, you can download the Blueprint from the Knowledge Base. You will need your login credentials.
