Critical infrastructure
See which dependencies may be exposed before assuming impact.
SKALV connects incoming evidence to the nodes and dependencies your operation relies on. Possible exposure stays separate from confirmed impact until the evidence or human verification supports it.
The node model
Substations, pumping stations, exchanges, depots, control systems and the sites they serve are modelled as nodes with attributes an operator recognises: what it is, where it is, and what it serves.
The dependency model
Dependencies between nodes are explicit and directional. That makes second-order exposure visible: a signal about one node produces a traceable path to the functions that depend on it, with each step inspectable.
Source monitoring
Telemetry, operator feeds and public warnings are bound to named sources with health tracking, so an absent reading is treated as a gap in knowledge rather than as a normal reading.
Consequences, stated as possibilities
A consequence records what may be affected and why, with the supporting evidence attached. It becomes confirmed impact only when evidence or verification supports it — the difference is visible in the record itself.
Field verification
Questions that only a person on site can answer are issued as verification tasks with a clear scope, and the response is recorded as evidence against the specific node.
See SKALV with your own operational scenario.
Bring a real scenario — the sources you follow, the functions you cannot lose — and we will show where SKALV fits and where it does not.