Transmission data is trapped between PLS-CADD, GIS, and the field.

• Software-stack tax — PLS-CADD + ArcGIS Enterprise + CAD + a vegetation tool + an OMS. Each license, each integration, each FTE.
• Round-trip friction — structure & conductor data hops between PLS-CADD, GIS, and CAD via flat-file exports — losing attributes and time.
• Compliance blind spots — NERC FAC-003, NESC clearance, IEEE 516 live-line checked separately, in different tools.
• Data sovereignty — cloud sync is a non-starter for critical-infrastructure GIS subject to NERC CIP.
• Inspection backlog — drone, satellite, and LiDAR captures pile up faster than they become findings.
• Storm & wildfire response — when the network drops, crews need a shared live map that works without the cloud.

Eight analyses. One corridor. One workstation.

• Sag — catenary (Roon + Black), max-sag findings vs NESC limits.
• Clearance — NESC Table 232-1 vertical, horizontal, cross-arm violations.
• Thermal — IEEE 738-2012 ampacity rating + thermal-limit findings.
• EMF — phasor-summed B (µT) + E (V/m) via Biot-Savart.
• Structure — NESC Grade B / C wind + ice + broken-wire overload.
• Vegetation — NERC FAC-003 + NESC Table 3 grow-in / fall-in.
• IEEE 516 — live-line work minimum approach distances.
• Blowout — swing angle + CIGRE galloping ellipse, mid-span contact.

Findings are editable features · scenarios versioned (draft → review → approved → superseded) · KPI dashboard, timeline, compliance & report export.

Audit evidence points at NESC / NERC / IEEE — not "VoltGrid's number."

Plus CIGRE empirical galloping, Roon & Black sag-tension, and NESC-compliant Plan & Profile sheet generation. Every engine is open code in Src/LocalMapServer/Transmission/Engines/.

PLS-CADD, on the map — in one click.

xml        = transmission.xml
kmz        = transmission.kmz
sourceSrid = 2277   // NAD83 / TX Central
targetSrid = 4326

→ 200 OK
structureCount: 142
conductorCount:  287
featureServer:
  /api/spatial/plscadd_.../0  // conductors
  /api/spatial/plscadd_.../1  // structures

Substations & field operations, on the same map.

Everything a utility team needs.

Five capabilities that landed first.

The RF spectrum, fused onto one map.

AI that never phones home.

// "vessels under 10kt near the port"
SELECT * FROM ais_tracks
WHERE sog < 10
  AND ST_DWithin(geom, port, 2000)
→ layer on the map

Speaks every server's language. Then becomes one.

Rebuild the city. Extend the platform.

Unified where everything else is stovepiped.

* Comparative rows are positioning statements, not benchmark results.

Built for the operations floor.

• Tactical Operations Center — radar + blue-force + imagery in one common operating picture.
• Maritime domain awareness — AIS + radar + SAR imagery on one map.
• Disaster response — emergency symbols + live feeds + tasked commercial imagery.
• Border security — sensor fusion + geofencing + CPA deconfliction.
• Training & simulation — CDB 2.0 synthetic environments + game-engine terrain serving.

Map the data you already have.

Engineering plans meet the real world.

• Reads DWG / DXF / DGN via managed OGR + ogr2ogr fallback.
• Georeference with control points (affine / polynomial-2, RMSE preview) or source EPSG.
• Outputs GeoJSON, MBTiles-vector, or GeoPackage — reprojected to EPSG:4326.
• Served as tiles, OGC Features, and FeatureServer under /api/cad/{id}.

Live feeds in. ArcGIS StreamLayer out.

GET /api/stream/{id}/StreamServer
 → streamUrls[0].url

ws  /api/stream/{id}/subscribe
POST /api/stream/{id}/ingest
GET  /api/stream/{id}/query
     ?startMs=&endMs=

// paste URL into ArcGIS Pro

Zero infrastructure. One click.

GET /api/features      OGC
GET /tiles/{z}/{x}/{y} raster
GET /cog/tiles/…       COG stream
GET /api/featureserver ESRI

● live on 192.168.1.24

Multi-protocol serving.

Render every kind of 3D reality.

Decide with the terrain.

{
  "observerZ": 100,
  "viewDistance": 1000
}
→ 360° visibility, mapped

The world, live on your map.

One shared picture for the whole team.

All channels run over the in-process local server — your conversations never leave the network you control.

A modern, dependency-light stack.

• .NET 10 · WPF desktop host with in-process ASP.NET Core / Kestrel.
• CefSharp.Wpf.NETCore 149 + WebView2 for hardware-accelerated rendering.
• ArcGIS Maps SDK for JavaScript 5.1 — primary SceneView.
• NetTopologySuite 2.6.0 · DuckDB · SpatiaLite · GDAL · OGR.
• iTowns · Spark · Three.js — all vendored locally for air-gap use.
• MISB ST 0601 KLV · STAC API 1.0.0 · GTFS protobuf · raw WebSockets for StreamServer.

* Reflects the .csproj / ARCHITECTURE.md build, not the stale README stack.

Built for the field, the desk, and the edge.

From data to decision in minutes.

• Emergency response — field teams share real-time assessments; command aggregates every stream.
• Urban planning — engineering, zoning, and environmental layers in one shared view.
• Defense & intel — secure sharing within classified networks; multi-source fusion.
• Environmental — research stations stream sensor data; live habitat modeling.

* Scenario impact figures are illustrative planning targets.

The GIS server you don't have to buy.

* All ROI / TCO figures illustrative — from internal planning docs. Validate before publishing.

Why not the alternatives?

Choose your deployment.

* Draft planning tiers — final pricing to be confirmed.

The utility roadmap.

• Now — PLS-CADD integration, Transmission Line Analyzer (NESC / NERC / IEEE), substation digital-twin workflows.
• Next — circuit / feeder tracing, distribution analysis, dynamic line rating (DLR) from real-time SCADA, native SCADA protocols (Modbus, OPC UA, IEC 61850, DNP3).
• Enterprise — centralized management console, Active Directory, NERC CIP-aligned access controls, GRID State deep-integration.
• Innovation — AI-assisted damage detection from drone / satellite captures, predictive asset health, AR field-markup.

* Roadmap items are forward-looking and subject to change.