Platform: the shared foundation · CMDB · COBIT EDM / MEA

Dependency map and impact

A dependency map from business service down to hardware: you know the impact of every change and outage before it happens.

ITIL 4 practice · Service configuration management

Illustrative screenshot: Dependency map and impact

What it does

  • Layers from business service through applications and platforms down to hardware and site
  • Item neighbourhood in both directions, grouping by class and layer filters
  • Impact on services: outage, degradation or only loss of redundancy
  • Impact path from cause to service, management as a separate layer

Measurable benefits

  1. Changes with calculated impactshare of changes whose impact on services was known before approval
  2. Time to identify impactfrom reporting an incident to the affected service – calculated by the application, not a meeting
  3. Items in the mapshare of configuration items linked to a business service

The application calculates these indicators from your own data, so you can prove the improvement with numbers from the first month.

Next step

Try CentOps on your own services.

Connect monitoring and discovery and see your service map within the first week. The beta is free for 6 months.

Join the beta →