Continuity's operating picture tilted in 3D: Europe in perspective on satellite terrain, regional feed markers, the Ukraine planning ring with six numbered candidate areas, and an object inspector listing the evidence for Lviv by source and state.

Logistics planning · Military · Emergency management · Ground rescue

Know what is there.
Plan what can actually be done.

Continuity is a logistics planning platform for operations where the infrastructure is damaged and the data is incomplete. It fuses frontline evidence, infrastructure state and power need into one model, then plans supply, movement and restoration with the crews, equipment, corridors and fuel on hand.

Every value states its source. Missing data is never rounded up.

Open the console Specifications

Evidence radius: 10 km
Substations: ≥ 35 kV
Contingency: N-1
Provenance states: 8

From the product source. Full table below.

01 — Capabilities

Evaluate the ground. Size the need. Plan the work.

Frontline data

Mapped substations, lines, hospitals, water works. Satellite, thermal, weather and connectivity feeds, each reporting fresh, cached, stale or not configured.

Power need

Critical loads as kW sinks in a typed dependency graph. Capacities start unknown; planning defaults are applied and labelled assumed.

Restoration plan

Crews, equipment, corridors and hourly power flow solved together. Plans compared on time to essential service, cost and N-1 resilience.

02 — Operating picture

One picture. Every feed labelled.

Feeds, candidate areas, an inspector naming each source and its state. The hero shows the same picture tilted in 3D.

The flat 2D operating picture: satellite map of Ukraine with the planning ring and six numbered candidate areas, regional feed markers, a situation strip along the bottom reading what the public map knows about this area, and the object inspector for Lviv on the right. — Shown: 28 substations ≥ 35 kV, 12 hospitals and water works within 10 km of Lviv; 4 of 5 regional feeds connected; available power unverified.

03 — Dependency model

Typed nodes. Typed edges. Bottlenecks named.

Generator → line → substation → feeder → critical load. Identity and position observed. Topology inferred, rule stated. Capacities unknown until entered.

The dependency model tilted in 3D over satellite terrain, with typed callouts for a shared substation marked binding limit, an independent supply and a shared communications provider, an hour slider, and hour-by-hour tables of what each site gets. — Practice example, invented and labelled simulated. Shared substation A + B at 0 of 0 kW is the binding limit; independent supply C 10 of 10 kW; shared communications provider 160 of 300 Mbps.

04 — Restoration planner

One incident. Three plans. Each names its weakness.

One mixed-integer programme assigns crews and equipment, chooses corridors and dispatches power hour by hour, with an N-1 contingency at the end of the horizon. An action that cannot be staffed names what is missing.

The Restoration view: an incident callout reading Substation K-14 destroyed, 180 MW of supply lost; callouts for a generator commissioning team, a 300 tonne mobile crane, an intact feeder and a cross-border interconnector tie; a left rail of power network, ways to get power back and teams; a service-recovery chart; and a right panel comparing fastest, most complete and safest plans against doing nothing. — Practice incident, invented: Substation K-14 destroyed, 180 MW lost. Fastest, most complete and safest against doing nothing. No partner records connected; teams and equipment are placeholders.

05 — Continuity SIM

Rehearse before committing.

Break a substation, choose a strategy, place generators, batteries, crews and closures on a 3D city. Read the consequences hour by hour. Nothing counts until staffed, routed, equipped and connected.

Continuity SIM in 3D over a satellite city: an incident callout reading Substation K-14 destroyed, 180 MW of supply lost; a district residential feeder on partial power; a left rail of strategies with Plan A, B and C scores; a build palette of generator, battery, temporary substation, facility, crew and equipment; and an hour-by-hour strip along the bottom. — Practice city, invented: Plan A 83/100, Plan B 88/100, Plan C 95/100. Scores compare plans from the same registry, not real-world outcomes.

06 — Evidence · Personnel

What is real, how fresh, what it cannot tell you.

Certified personnel, specialised support and volunteers are separate classes, never interchangeable.

The Evidence view: a list of sources for the selected region, each with a plain-language limit, a badge such as saved copy, updated recently, historical or not connected, and the time it was last read. — Each source with its state and last-read time. A hot spot is not confirmed damage.

The People and Skills view: three counters for public evidence records, confirmed public availability reading Unknown, and the OSM candidate search radius, above a table of organisations with evidence type, area, reporting period, availability and provenance columns. — Shown: confirmed public availability — Unknown. A listed organisation is not a staffed, qualified crew.

07 — Provenance

Eight states. No promotion without a source.

LIVElive feed, source named
OBSERVEDfrom the map
REPORTEDby a named partner
ASSUMEDplanning default, not measured
INFERREDestimate, rule stated
STALEold, last-seen stated
SIMULATEDpractice data, invented
UNKNOWNno source recorded

Not established by public data

Spare grid capacity. Plant operation. Fuel stocks. Crew availability. Land permission. Legal eligibility. Assumptions stated, or partner records with declared provenance.

08 — Specifications

Model envelope.

Evidence radius: 10 km around a candidate centre; infrastructure.py
Substation threshold: ≥ 35 kV modelled; below, a distribution transformer, counted not modelled; evidence_graph.py
Area envelope: Up to 28 substations and 12 critical facilities per area; evidence_graph.py
Line contact: Line touches substation at ≤ 250 m; evidence_graph.py
Node types: site · critical_load · compute_asset · power_asset · substation · communications_provider; dependency_graph.py
Edge types: powered_by · connected_through · supplied_by · requires_component · backed_up_by; dependency_graph.py
Provenance: live · observed · reported · assumed · inferred · stale · synthetic · unknown; dependency_graph.py
Planner: One mixed-integer programme: crews, equipment, transport corridors, hourly power flow. N-1 contingency at the end of the horizon; restoration.py
Evidence sources: OpenStreetMap via Overpass · Sentinel-2 · VIIRS thermal · Open-Meteo forecast and 30-day reanalysis · PeeringDB · RIPE Atlas · Cloudflare Radar; live.py · infrastructure.py · satellite.py
Feed states: fresh · cached · stale · not configured; live.py
Partner data: One documented contract; declared provenance kept; PARTNER-DATA.md
Hosted function limit: 120 s; vercel.json

09 — Planning regions

Six regions. Same rules.

01Ukraine
02Gaza / oPt
03Sudan
04Eastern DRC
05Myanmar
06Yemen

Focus rings are illustrative screening areas, not boundaries.

Open the console. Start from the map.

Open the console Provenance rules

Know what is there. Plan what can actually be done.