What it is (plain English)
Builds a map showing which pieces of infrastructure work together to deliver a business service — so when the "online checkout" service degrades, you can see exactly which servers, databases, and connections are involved. It turns a flat inventory into service context.
Problems it solves
- Knowing you have 5,000 servers but not which ones deliver which business service.
- Outages where nobody can quickly say what's affected or how badly.
- Alerts that can't be prioritized because business impact is unknown.
What must exist first
CMDB Foundation and Discovery — service maps are built on discovered CIs and their relationships.
What the customer needs to provide
- A list of the business services that matter most (start with the critical few).
- Entry points for each service (the URL or endpoint users hit).
- Access for the mapping process to trace connections (credentials, as with Discovery).
- Business owners who can validate that a generated map is correct.
Where it can go next
Service maps power impact-aware Event Management and Incident Management, service-level dashboards, and change risk assessment scoped to affected services.