Dependency Map

Last Updated: May 7, 2026
Estimated Reading Time: 6 minutes

Overview

Dependency Map turns synced ServiceNow CIs and relationships into an interactive topology view. Use it to inspect service dependencies, understand upstream and downstream relationships, and prepare for change-impact analysis.

When To Use It

Use Dependency Map when you need to:

  • understand how CIs are connected
  • inspect the supporting infrastructure for a service
  • identify relationship gaps
  • prepare for a Blast Radius analysis
  • explain topology to service owners or change reviewers

Core Concepts

Nodes

Nodes represent Configuration Items such as services, applications, servers, databases, and network devices.

Node appearance may reflect type, health, criticality, or other view settings.

Edges

Edges represent ServiceNow relationships. Direction matters when analyzing dependency flow. A relationship can indicate that one CI depends on, runs on, contains, hosts, or connects to another CI.

Focused Views

Large CMDBs can be noisy. Use search, filters, and focus mode to inspect a smaller part of the topology.

Navigation

Common controls include:

  • pan by dragging the canvas
  • zoom with scroll or zoom controls
  • click a node to inspect details
  • click an edge to inspect relationship details
  • search for a CI by name
  • use fit-to-screen after changing filters

Layouts

Different layouts answer different questions:

| Layout Type | Best For | |-------------|----------| | Force-directed | natural clusters and relationship density | | Hierarchical | parent-child dependency chains | | Layer-based | infrastructure and service tiers | | Service-focused | business or application service context | | Network-oriented | connectivity and network-heavy views | | CSDM-oriented | service model structure | | Grid | scanning and presentations |

If the map feels crowded, filter first. A smaller graph is easier to read and performs better.

Detail Panels

Click a node to review:

  • CI name and class
  • health status
  • key attributes
  • relationship counts
  • available actions

Click a relationship to review:

  • relationship type
  • source and target CIs
  • direction
  • compliance or quality indicators when available

Common Workflows

Inspect a service

  1. Search for the service or application.
  2. Focus on the selected node.
  3. Review upstream and downstream relationships.
  4. Open related CIs as needed.

Prepare for change review

  1. Find the CI that will change.
  2. Inspect direct relationships.
  3. Use Blast Radius for formal impact analysis.
  4. Export or reference findings in the change process.

Find relationship gaps

  1. Filter to the relevant service or CI class.
  2. Look for isolated or unexpected nodes.
  3. Confirm gaps in ServiceNow.
  4. Route confirmed correction work through Remediation Workbench or CSDM Workbench.

Performance Guidance

For large environments:

  • filter to one environment
  • reduce node count before changing layout
  • use focus mode
  • avoid rendering broad all-CI maps when investigating a specific issue

Related Articles