Tech Maven Geospatial · 2026

One grid. Four surfaces.
One vegetation program.

GridState, VoltGrid, FieldMapper, and GeoVerse 3D share a single operating picture — from FAC-003 clearance in the office to GNSS trim evidence on the right-of-way.

Pitch deck · auto-advances every 7 seconds · use Next / Previous or the side arrows

The gap

The model, the map, the crew, and the headset do not talk.

Asset records live in the EAM. Corridor GIS lives on a desktop. Vegetation patrols live on paper or a siloed mobile form. The 3D twin is a demo. When a grow-in becomes an outage, the evidence is a folder hunt — not a FAC-003 package.

What breaks

Time-based trim cycles spend money on the wrong spans
MVCD is a PDF table, not a live check against sag and elevation
Field photos never bind back to the work order
Crews enter the ROW without a shared live picture

Why vegetation first

Vegetation is the leading cause of fires and outages on overhead lines.

FAC-003 requires a documented vegetation program: minimum clearance distance, an inspection cycle, and categorized outage reporting. Manual quarterly walks cannot cover a modern transmission system.

$6–8B Estimated annual U.S. utility spend clearing vegetation from overhead lines

51% Reported cost reduction per acre of mechanical trimming after moving from time-based to risk-based programs

$1M / day Order of magnitude for NERC penalties on vegetation-related violations — plus the outage itself

Industry framing from Irth Solutions’ vegetation-management briefing and T&D World risk-based VM case results — planning context, not GridState customer outcomes.

The suite

Four products. One network record.

Hub · API + web

GridState

System of record: assets, FAC-003 corridors, MVCD, work orders, NERC CIP, load flow, SCADA/AMI ingest.

Windows GIS

VoltGrid

Air-gapped desktop GIS: LiDAR, ΔNDVI, CAD/BIM, 3D twin, corridor change detection, TAK, game-engine tiles.

Field + dashboard

FieldMapper

iOS, Android, Windows, and a web work-order dashboard. GNSS, FAC-003 patrols, photos, crew tracking, TAK COP.

XR / AR / MR / VR

GeoVerse 3D

Unity geospatial twin: operator assistance, computer vision, voice control, and safety briefing in the corridor.

How they connect

GridState in the middle. Every other surface is a client of the same model.

Ingest

ESRI + SCADA + AMI

Feature services and telemetry keep GridState’s network state current. VoltGrid can also host those layers offline at an EOC.

Decide

API · web · PostGIS

Work orders, MVCD, inspection due dates, and CIP evidence are authored once in GridState.

Act

Desk, corridor, headset

VoltGrid engineers the corridor. FieldMapper executes. GeoVerse 3D briefs and watches clearance.

Share

REST · SignalR · TAK

Crew location, geofence alerts, and 3D tiles close a common operating picture — including when the WAN is down.

Full diagram: suite architecture

FAC-003 workflow

Sense → measure → trim → prove.

01 SENSE

Corridor scan

VoltGrid LiDAR, drone, satellite, ΔNDVI. Ground patrol when needed.

02 MEASURE

MVCD check

GridState FAC-003-5 Table 2, altitude, sag, and growth allowance.

03 RISK

Prioritize

Weather, wind, fire, and growth — not a calendar cycle.

04 DISPATCH

Work order

Trim plan becomes an assignment on the live corridor.

05 BRIEF

XR safety

GeoVerse 3D + voice: stay out of the MVCD while you work.

06 TRIM

GNSS evidence

FieldMapper photos, location, and form bound to the order.

07 AUDIT

Virtual pass

VoltGrid before/after clearance. Failures reopen the order.

08 RECORD

RSAW pack

Outage cats 1A–4B, R6 cycle, evidence ready for audit.

Lane diagram: FAC-003 vegetation workflow

GridState · backend + web

The compliance spine and the work order are the same object.

FAC-003

Corridors that know their MVCD

Applicable lines: ≥200 kV, PC-designated, WECC path, gen-tie
Table 2 sea-level MVCD with altitude correction
R6 inspection: annual, 18-month maximum gap

Operations

From finding to crew

Patrol, aerial, LiDAR, or satellite inspection methods
Outage categories 1A–4B: grow-in, fall-in, blow-together
Work order + photo upload with durable sync

Also on the hub

The rest of the utility

NERC CIP, FAC-008 ratings, Newton-Raphson load flow
SCADA / IEC 61850 / AMI telemetry
Switching, LOTO, and emergency restoration

VoltGrid · Windows desktop GIS

The corridor in true 3D — including when the WAN is gone.

Vegetation desk

Before/after COG change detection on a PLS-CADD buffer
ΔNDVI encroachment and DEM/DSM height proxy
LiDAR and forestry analysis for ROW sweep
Virtual audit after the trim crew leaves

Workstation

Embedded GIS server: OGC, ESRI REST, 3D Tiles, I3S
CAD/BIM as-builts, GeoPackage Z+M editing
TAK storm ops, air-gapped LAN share at the EOC
Terrain and imagery out to Unity, Unreal, Cesium

FieldMapper · iOS, Android, Windows, web

The crew never re-types what the corridor already knows.

On the ROW

High-precision collection

External GNSS / NMEA, offline maps (MBTiles, PMTiles, GeoPackage), photos, signatures, and FAC-003 inspection forms.

Work orders

Dashboard for dispatch

Blazor web dashboard plus MAUI clients. Offline-first sync, conflict handling, and resumable evidence uploads back to GridState.

Safety picture

Crew + TAK COP

Live crew location, geofence alerts, emergencies, and GeoChat — on the device and on the supervisor map.

GeoVerse 3D · XR / AR / MR / VR

Clearance you can stand inside. Voice that keeps hands on the tools.

Operator assistance

Unity geospatial twin of the same corridor GridState owns
Computer vision on inspection imagery and live camera
Voice / push-to-talk commands so the crew is not menu-diving under a conductor
TAK interoperability with FieldMapper and VoltGrid

Where it sits

GeoVerse 3D is the immersive client of the suite: VoltGrid supplies terrain and 3D tiles; GridState supplies the network and work order; FieldMapper supplies live crew. Hardware acceptance for XR remains a release gate — the workflow is designed so the headset is assistance, not a single point of failure.

Operating model

Stop trimming by the calendar. Trim by clearance risk.

Time-based (legacy)

Walk or fly the whole system on a fixed cycle
Same prescription on every span
Evidence is a paper patrol sheet
The next storm resets tribal knowledge

Risk-based (this suite)

LiDAR / satellite / ΔNDVI find the spans that will violate MVCD
Weather, sag, fire, and growth change the queue daily
Work order, GNSS photos, and virtual audit are one chain
RSAW package exists before anyone asks for it

A day on the ROW

Tuesday: a 230 kV span is 0.4 ft inside MVCD after heat sag.

06:10 · VoltGrid

Overnight ΔNDVI flags the span. LiDAR height proxy confirms canopy into the Gallet distance.

06:18 · GridState

MVCD for 230 kV at this elevation is 4.0 ft sea-level, scaled. Inspection clock is inside the 18-month R6 window — this is a grow-in risk, not a missed patrol.

07:40 · FieldMapper

Trim order hits the crew tablet. GNSS stakeout, photos, and a geofence around the energized corridor.

08:05 · GeoVerse

Headset brief: stay outside MVCD, watch blow-in. Voice confirms “clear to cut” without looking down.

By 14:00 VoltGrid’s after mosaic passes. GridState closes the order and files the evidence. If this span ever becomes a 1A grow-in outage, the package is already built.

Close

Run the utility in GridState.
See it in VoltGrid.
Work it in FieldMapper.
Stand in it with GeoVerse 3D.

Next step: a 30-day vegetation pilot on one applicable corridor — MVCD baseline, one LiDAR or satellite collect, live work orders, and an RSAW-shaped evidence pack at the end of the cycle.

gridstate.techmaven.net · voltgrid.techmaven.net · Tech Maven Geospatial

One grid. Four surfaces.One vegetation program.