A map showing which supplier carries which system and which system carries which business process — with a one-click outage simulation.
Dependency graph across suppliers, assets and business processes (RTO/MTPD) with flow type, data categories and redundancy per edge; deterministic outage propagation, single-point-of-failure KPI, saved scenarios and AI assessment with redundancy recommendations.
Every company depends on things it does not run itself: the cloud service for accounting, the internet line, the server in the basement. This module draws those dependencies as a map. You connect suppliers, systems and business processes with arrows, and with one click you see what stops when a part fails — and how long your business can take it.
The module builds a directed dependency graph over the existing supplier and asset registers plus a new process layer with RTO and MTPD. Edges carry flow type (data, service, network, power, physical), data categories and a redundancy flag. Outage propagation is deterministic: a node fails if a non-redundant supply fails or all redundant supplies of the same type fail. The result lists affected nodes with path, breached RTO/MTPD per process and the union of affected data categories.
Features
Map with suppliers, systems and business processes as nodes.
Arrows between nodes: what supplies what, which data flows.
Marker whether a path is doubly secured.
One-click outage simulation with selectable duration (4 hours to 7 days).
KPI showing which parts endanger the whole business.
Saved scenarios with an AI assessment and suggestions.
Nodes reference existing suppliers and assets — no double entry.
Business processes with criticality, owner, RTO, MTPD and optional RPO.
Edges with flow type, direction, data categories and redundancy flag.
Propagation with hop depth and cause path, cycle-safe.
Single-point-of-failure KPI across all non-process nodes at 24 hours.
Scenarios as snapshots; AI assessment with situation, data risk and redundancy recommendations.
How it works
You create your most important business processes and state how long they may stand still.
You bring suppliers and systems onto the map.
You draw arrows from what supplies to what depends on it.
You click a node and let the outage be calculated.
You save the result and get suggestions on what to do.
Record business processes with RTO/MTPD; each lands on the map automatically.
Bring suppliers and assets from the existing registers onto the map or create them via quick entry.
Draw edges with Ctrl + drag and set flow type, data categories and redundancy.
Choose a trigger, set the outage duration, simulate; save the result as a scenario.
Trigger the AI assessment and turn the redundancy recommendations into measures.
Use it forKnow in advance what stops when a cloud service or device fails.
Use it forBusiness impact analysis and continuity planning based on the real supply chain.
In the ICT minimum standard
ID · Identify
ID.AM-3Catalogue all of your internal communication and data flows.
ID.BE-4Dependencies and critical functions for delivery of critical services are established.
DE · Detect
DE.AE-4Determine the impact of possible events.
Known limitationsThe simulation works with the recorded flows and redundancy flags — anything not on the map is not considered. It does not replace an emergency exercise.