Dependency Graph and Blast Radius

The dependency graph maps how assets feed and depend on each other across power, fluids, signal, and control, supporting incident response, change management, and finding single points of failure.

Building the graph

Open Dependencies in the sidebar. From any asset, declare upstream dependencies (what it needs to function) and downstream dependents (what runs off it). Click Add dependency, search the other asset, and choose an edge type: power, fluid, signal, or mechanical. Build top down from the most critical equipment; about 60 to 80 percent coverage of what you would want in an emergency is the sweet spot. Skip trivial cabling and comfort dependencies.

What it shows

The graph renders assets as nodes with typed edges. Click an asset to see one-hop neighbors, toggle two hops for cascading effects, filter by edge type, and color by criticality, condition, or age.

Blast radius

Click an asset and choose Blast radius to highlight everything downstream that fails with it. Use it for outage impact assessment before scheduled work, to find single points of failure by sorting on blast radius size, and for instant incident response.

Auto-detection and tips

If you connect IoT or a building management system, Rivolq suggests dependencies from observed timing correlations under Suggested edges. Always review before accepting. Annotate edges with notes and update dependencies during commissioning so they do not go stale.