Problem
At Crawl and Walk, Application Services are connected to core infrastructure, applications, and ownership groups. However, gaps remain in aligning services with how they are offered and consumed at scale. The Run blueprint solves this by introducing Business Service Offerings alongside Technical Service Offerings, creating end-to-end visibility from infrastructure to business-facing services.
What the Blueprint Includes
The Run phase includes the following entities:
- Application Service – Root entity representing service instances.
- User – Service managers and owners.
- Group – Support and management groups.
- Business Application – Consumes the service and provides business context.
- SDLC Component – Lifecycle components that form part of the application stack.
- Application – Applications that the service depends on.
- Server – Servers hosting the service.
- Technical Service Offering – Packages the Application Service for delivery.
- Business Service Offering – Newly added at Run; provides business-facing service delivery context .
Considerations
- Offerings: At Run, both Technical and Business Service Offerings must be linked to Application Services.
- Dependencies: The model retains the Alternative Link Group rule: each Application Service must depend on either Applications or Servers, but at least one is required. You can add or remove "infastructure CI classes" as required.
- Alignment: Ensure business-facing services (Business Service Offerings) are clearly mapped to technical underpinnings. In this model, only Production environments are required to has business context.
- Plugins: SDLC Component class still requires the “CMDB CI Class Models” plugin.
- Accountability: Maintain accurate ownership and group assignments for traceability.
Benefits
- Full Service Transparency – Links Application Services from infrastructure all the way to business-facing offerings.
- Enables Business Impact Analysis – When a failing Server, for example, is aware of the business impact through Business Service Offerings.
- Improved Service Delivery – Aligns technical services with business offerings for more transparent value reporting.
- End-to-End Traceability – Provides visibility across users, groups, infrastructure, applications, and offerings.
- Operational Maturity – Elevates the CMDB from a technical registry to a service-aware system supporting both IT and business needs.
Related Information
Check other templates related to the Service Delivery.
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 to access the blueprint download page.
