Trace the feeder. Preview the isolation. New

Electric network connectivity over the PLS-CADD lines you've already imported: trace upstream, downstream, or both from any start structure, filter by circuit, cap the hops — and preview an isolation by opening cut points to see exactly which structures and sections go de-energized. On the map, in an in-map panel, fully air-gapped.

Upstream · Downstream · Bothcircuit_id filter Max hopsIsolation preview PLS-CADD topologyMap highlight

Connectivity · Phase 1

The switching-desk question, answered on the map

"If I open these two structures, what goes dark?" Network Trace builds a connectivity graph from your PLS-CADD conductors — from_structure → to_structure, section by section — and walks it in milliseconds. Results highlight live on the map next to your outage overlay and corridor findings.

Directional trace — upstream / downstream / both from any start structure, optional circuit_id filter and maxHops cap.
Isolation preview — declare open (cut) structures and optional energizing sources; get back the de-energized structures and sections.
Built from your import — topology comes straight from staged PLS-CADD DuckDB imports (plscadd_*); geometry is only needed for the highlight.
In-map panel — Ribbon → TRANSMISSION → CORRIDOR → Trace; or drive it from the REST API / JS bridge for scripted studies.

/api/networktrace

POST /api/networktrace/build
{ "dbId": "plscadd_7f2a" }   → nodes · edges · circuits

POST /api/networktrace/trace
{ "startStructure": "T-114",
  "direction": "downstream", "maxHops": 40 }

POST /api/networktrace/isolation
{ "openStructures": ["T-114","T-131"] }
→ de-energized structures + sections, highlighted

In-App Screenshot

Transmission Network Trace & Isolation Analysis Widget

VoltGrid desktop — Transmission Line Analysis Network Trace and Isolation widget — Transmission Network Trace floating widget shown in default state ready for directional BFS traces, start structures, and isolation modeling

Why this matters for ops

Connectivity next to everything else you know

🔌

Planned-work scoping

Preview which spans a clearance affects before the switching order is written — and see it against parcels, crews, and outages.

🌩️

Storm triage

Trace downstream of a damaged structure from the corridor-damage findings to bound the customer impact area.

🧪

Scripted studies

The BFS engine sits behind a plain REST contract with unit-tested isolation semantics — batch what-if runs from any script.

Honest boundary: Phase 1 is a connectivity trace over imported PLS-CADD topology — it is not load flow, protection coordination, or a live switching/OMS integration, and it requires structure/section data with consistent structure numbers. Pair it with the OMS/SCADA overlay for the live outage picture.