Data Requirements, Integration & API.

Only data the utility already maintains: tower silhouettes/geometry, conductor datasheets, and GPS coordinates of each tower, plus optionally SCADA/AMI feeds and GIS data to enrich the model. The Vegetation Management module additionally needs a LiDAR survey or high-resolution satellite imagery of the corridor. No hardware procurement, no installation campaigns - which is why implementation moves faster than a typical sensor rollout.

Each GridSight® module runs as a self-contained service block on a stateless request-response pattern, aligned with the platform's periodic 15-minute computation cycle. On the way in, GridSight® ingests data from your SCADA/EMS via MQTT, your GIS for network topology, and weather providers for meteorological inputs - it doesn't replace any of these, it reads from them. On the way out, results populate the GridSight® dashboards, 3-D viewer, maps and alerts directly, and work orders or maintenance records can be exported to your EAM or ERP systems through standardised REST APIs.