A configuration item describes something you need to understand to deliver a service. Relationships explain how items depend on each other. In a Depends on::Used by relationship, the parent depends on the child. If the child router fails, its parent service may be affected. Reversing the two fields reverses that operational meaning.
Create explicit relationships and retain both endpoints as existing configuration items. An incident count is not a dependency map. Use the relationship list to identify the supported impact, then confirm the service owner’s evidence before authorizing a real change. This workspace models CI records and typed relationships. It does not run Discovery, the Identification and Reconciliation Engine or automatic impact analysis. The supplied service and infrastructure records are fictional.
Trace a service dependency using its direction and existing CI identities.