Your grid lives in silos.

• Siloed GIS / CAD / BIM — asset records, as-built drawings, and substation models sit in tools that never share a map.
• Storm response goes dark — when the storm rolls in and backhaul drops, cloud GIS drops with it.
• Enterprise GIS cost — server farms, per-seat licenses, and dedicated staff before the first feeder is mapped.
• Field disconnect — crews in the right-of-way can't see, or feed, the operating picture.

Everything a utility GIS team needs.

Five capabilities that landed first.

Storm-ops sensing, fused onto one map.

AI that never phones home.

// "poles last inspected before 2020"
SELECT * FROM poles
WHERE inspected_yr < 2020
  AND ST_DWithin(geom, feeder_12, 500)
→ layer on the map

Click. Digitize. Done.

Three complementary tools: foundation-model segmentation for complex scenes, color-based capture for fast one-offs, detection for class-labelled finds. All local inference.

Your enterprise lakehouse, on the map.

{
  "kind": "FabricLakehouse",
  "oneLakeUri": "abfss://ws@onelake...
                /Assets.Lakehouse",
  "tableFilter": ["poles",
                  "conductors",
                  "outages"]
}
→ DPAPI-encrypted profile
→ views via delta_scan()
→ /api/spatial/fabric-prod/…

Speaks your GIS stack's language. Then becomes one.

Rebuild the substation. Extend the platform.

Unified where everything else is stovepiped.

* Comparative rows are positioning statements, not benchmark results.

Built for the storm room.

• Storm response — crew tracking + damage imagery + tasked commercial collection in one operating picture.
• Vegetation & ROW — multispectral indices + LiDAR + change detection along the corridor.
• Transmission corridor planning — terrain analysis, viewshed, routing, CAD overlays.
• Substation digital twin — BIM/IFC import + LoD2.2 reconstruction + point clouds.
• Wildfire risk — burn indices + NWCG symbology + geotagged field photo intake.

Map the data your utility already has.

As-built drawings meet the real grid.

• Reads DWG / DXF / DGN via managed OGR + ogr2ogr fallback.
• Georeference with control points (affine / polynomial-2, RMSE preview) or source EPSG — rubber-sheet substation drawings onto the map.
• Outputs GeoJSON, MBTiles-vector, or GeoPackage — reprojected to EPSG:4326.
• Served as tiles, OGC Features, and FeatureServer under /api/cad/{id}.
• Pairs with PLS-CADD import — structures + conductors, with FileGDB / PostGIS / GPKG / GeoJSON export.

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 grid reality.

Decide with the terrain.

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

The field, live on your map.

One shared picture for every crew.

All channels run over the in-process local server — coordination never leaves 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 every corner of the utility.

Pairs with GRID State.

• GRID State — Tech Maven Geospatial's robust electric utility management solution: asset, operations, and network state management.
• VoltGrid — the desktop geospatial / 3D digital twin companion that gives those assets a living map.
• Works operationally together — GRID State manages the utility's operational records; VoltGrid lets you visualize, edit, analyze, and coordinate in the field.
• One vendor, one grid picture — from the record of the grid to the 3D reality of it.

The enterprise GIS you don't have to buy.

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

Why not the alternatives?

DER · OMS · vegetation & storm · EAM.

Trace it. QA it. Chart it. Pack it.

Choose your deployment.

* Draft planning tiers — final pricing to be confirmed.

The utility roadmap.

• Now — PLS-CADD import, Transmission Analyzer (sag/clearance/vegetation/thermal… + operator My Layers), network connectivity trace & isolation preview, as-built vs design QA, ROW encroachment, DER hosting choropleth, OMS/SCADA overlay, corridor vegetation & storm change detection, Maximo / Cityworks EAM read (with geo core), data charts, offline tile packs, CAD modernization, 3D/Z GPKG editing.
• Next — DER study import / time-series choropleth (merge-ready), deeper substation & inspection workflows, EAM write-back, native OT protocol adapters (DNP3 / ICCP) where gateways aren't enough.
• Future — outage prediction / restoration ETA, full OpenDSS/CYME in-process studies, CMMS bidirectional sync.
• Together — deeper operational pairing with GRID State across the product line.

* Roadmap items are forward-looking and subject to change. Shipped items above are on main.