Key Highlights
Relationship Mapping turns a flat inventory into a service-aware map, tracing impact upstream and downstream through the CI type hierarchy, from symptom to root cause and from planned change to blast radius.
One mapping answers two questions, whichever CI opens first.
Each connection carries a Direct type and an Inverse type.
WebApp Runs on Server is also Server Hosts WebApp: one link, both directions.
Whichever CI is the starting point, the dependency is already there to read.
Default and custom relationship types to match the environment.
The full chain for a business service appears in one view.
The Relationship Mapper renders CIs as nodes and dependencies as connecting lines.
CI selection revealing upstream services and downstream components around it.
Follow the connecting lines to see how a business service maps down to its components.
Upstream and downstream CIs are clearly distinguishable on the graph.
Turn change risk from a guess into a fact.
Pick the CI about to be touched and see its blast radius instantly.
Show all upstream business services the change could take down.
Reveal each downstream component that depends on the CI being modified.
Hand the Change Advisory Board a clear scope before the approval decision.
Walk the map from the failing service to the CI that is the real source.
Trace from symptom to cause instead of reconstructing it from memory under pressure.
Follow recorded dependencies rather than guessing which component broke.
Keep the picture accurate with CI-to-Asset status sync, so the graph reflects current state.
Intelligence
Teams need Relationship Mapping the moment a change or incident forces the question "what else does this affect?"
Before approving a change, the Change Advisory Board needs to know which business services sit downstream of the CI being modified.
During an outage, the support team needs to walk from the symptom, a business service that's unavailable, back to the one component that broke.
As the environment shifts, those dependencies have to stay accurate, because an impact analysis is only as good as the map behind it.
How It Works
Connect CIs with Direct and Inverse types describing dependencies from both ends.
Use default types (Connected to, Depends on, Hosts) or create custom relationships.
Admins configure suggested relationship types. Technicians apply them, or manually create un-discoverable business links.
Visualize CIs as nodes and dependencies as lines in the interactive Relationship Graph.
Run impact analysis before change approvals and trace incidents to root cause CIs.
Maintain accuracy via CI-to-Asset status sync and post-incident relationship reviews.
Role-Based Value
Change risk becomes a fact rather than a judgement call, because the blast radius of a proposed change is read off the dependency graph before approval.
Change risk becomes a fact rather than a judgement call, because the blast radius of a proposed change is read off the dependency graph before approval.
Impact analysis stops depending on who happens to know the dependencies.
Impact analysis stops depending on who happens to know the dependencies.
Relationships record in both directions and are reviewed during change control, so the map keeps matching reality instead of decaying after the first quarter.
Relationships record in both directions and are reviewed during change control, so the map keeps matching reality instead of decaying after the first quarter.
Root cause is a path to walk rather than a hunch to defend: follow the failing service down its chain to the component actually at fault.
Root cause is a path to walk rather than a hunch to defend: follow the failing service down its chain to the component actually at fault.
From Visibility to Control
See the blast radius before a change. Read the graph and know exactly what's in scope before the CAB decides: informed approvals, not guesses.
Trace root cause through dependencies. Follow the failing service down its chain to the component at the source, a path the team can walk rather than a hunch to defend.
Carry service-impact awareness into each incident and change. Relationships record in both directions, so upstream and downstream context is there the moment a CI opens.
Keep the model trustworthy over time. CI-to-Asset status sync and relationship reviews during change control keep the map matching reality.
Explore More