Loading content
Service impact describes the analysis and assessment of how incidents, changes, or performance degradations affect a service's availability and functionality. It supports prioritization, stakeholder communication, and technical remediation. Used in operations and architecture, it provides structured decision input for SLAs, SLOs and risk assessments.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Service impact is the effect of an event, change, or outage on delivered service and the business processes that depend on it.
The term follows the service-management practice of assessing incidents and changes by their consequences for services and business. ISO/IEC 20000-1 provides a normative framework for the service management system.
Start with the affected service and trace dependencies to users, business processes, and technical components. Describe scope, duration, severity, and affected functions separately from cause. This turns a technical signal into a prioritizable assessment of consequence.
Shows how many users, functions, or business processes are affected.
Assesses significance of the degradation for performance, security, or business.
Connects technical components to the visible service and its consequences.
Service impact supports incident prioritization, change assessment, and communication. An impact statement describes consequences; it is neither a root-cause analysis nor a technical health indicator.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.