Quick Summary
- Utility asset inspection software ties every drone photo, finding, and repair to a specific pole, span, or device, so the asset map it starts with decides how useful the results are.
- Most programs build that map from a GIS export loaded as a KML or CSV file, then fix gaps in the field.
- Field crews will find poles that are missing, moved, or mislabeled in GIS. Good software lets pilots add those assets in flight and flags photos that do not match.
- Utileyes, drone inspection software for utilities, maps assets from KML or CSV, organizes photos by asset ID, and exports findings as ArcGIS-compatible CSV.
Utility asset inspection software is the system that links each inspection photo and finding to the exact asset it describes. It only works as well as the asset map loaded into it before anyone flies.
Utileyes is cloud-based drone inspection software for utilities, built by people who flew utility inspections. Most guides on this topic compare feature lists. This one starts a step earlier, with the asset list itself: where it comes from, what breaks it, and how to keep it clean from first flight to final export.
If you already have a program running and want the full workflow, see our post on managing a drone inspection workflow from flight to action.
What is utility asset inspection software?
Utility asset inspection software is a platform that stores inspection data by asset instead of by flight, folder, or date. Each pole, span, transformer, or switch gets one record. Photos, condition notes, and severity tags attach to that record, so anyone can open an asset and see its full inspection history in one place.
The difference matters most after the flight. A folder of images named by camera timestamp tells a reviewer nothing. A list of poles, each with its photos and a severity grade, tells a supervisor where to send a crew.
The asset is also how regulators think about inspection records. California's General Order 165, for example, says inspection records must specify the circuit, area, facility, or equipment inspected, along with the inspector, the date, any problems found, and the scheduled date of corrective action. Software built around the asset makes that kind of record a byproduct of normal work.
Why does the asset map matter before the first flight?
The asset map tells the software which pole each photo belongs to. If the map is incomplete or wrong, photos land on the wrong asset or on no asset at all. Reviewers then spend hours sorting images by hand, and findings can reach the wrong crew. Fixing the map before flying is easier than fixing the data after.
GIS records are rarely a perfect match for what stands in the field. Peter Batty of SSP Innovations has written that the lag between installing equipment and recording it in GIS is measured in months at most utilities. Storm rebuilds, emergency replacements, and joint-use changes all widen that gap.
A drone inspection is one of the few times someone looks closely at every asset on a circuit. That makes it a good moment to catch map errors, as long as the software is set up to capture them instead of hiding them.
How do you load poles and spans into inspection software?
Most utilities export assets from GIS as a KML or CSV file with an asset ID, coordinates, and a few attributes, then import that file into the inspection platform. The software places each asset on a map. Supervisors can then group assets into circuits or work areas and assign them to pilots before anyone drives out.
A clean import usually follows the same steps:
- Pick the scope. Export one circuit or work area at a time. Smaller batches are easier to check.
- Keep the GIS asset ID. Use the same ID your work order system uses, so findings can flow back without a lookup table.
- Include coordinates for every row. Assets without a location cannot be matched to GPS-tagged photos.
- Load and review on the map. Look for points in the wrong place, duplicate IDs, and gaps along the line.
- Assign the work. In Utileyes, supervisors use a lasso tool on the map to assign poles and spans to each pilot.
KML asset mapping is popular because most GIS tools can export it and most mapping tools can read it. CSV works just as well when it carries an ID, latitude, and longitude.
What should happen when field assets don't match GIS?
When a pilot finds a pole that is missing, misplaced, or mislabeled in GIS, the software should capture it as a new or corrected asset, not discard it. The pilot adds an asset point in flight, and the reviewer confirms it. Those corrections go back to the GIS team so the next inspection cycle starts from a better map.
Common mismatches crews run into:
- Missing assets. A pole or device stands in the field but has no GIS record.
- Misplaced assets. The GIS point sits a span away from the real pole.
- Duplicate or retired IDs. A replaced pole still appears next to its replacement.
- Photos on the wrong asset. GPS drift or a quick flight between close poles drops images on a neighbor.
Utileyes runs QA checks during upload and flags images that look mismatched or misplaced, so the pilot can fix them while the flight is still fresh. Pilots can also generate asset points in flight when the map has a gap.
Which asset details should an inspection record carry?
An inspection record should carry enough detail to find the asset, judge its condition, and assign the repair without opening another system. That means an ID, a location, the asset type, the inspection date and inspector, the findings with a severity level, and the photos that support them. Everything else is optional and depends on your standards.
| Field | Why it matters | Where it usually comes from |
|---|---|---|
| Asset ID | Links photos, findings, and work orders to one record | GIS export |
| Latitude and longitude | Matches GPS-tagged photos to the right asset | GIS export, corrected in the field |
| Asset type | Sets which inspection form and checklist apply | GIS export |
| Circuit or work area | Groups assets for flight assignment and reporting | GIS export |
| Inspector and date | Shows who looked and when | Inspection software |
| Findings and severity | Ranks repairs by outage risk, fire hazard, or safety | Reviewer in inspection software |
| Photos (RGB and thermal) | Gives crews and reviewers the evidence | Drone upload |
If you are deciding how to build a utility pole inspection form, start with this list and add only what your crews will act on. Utileyes supports customizable inspection forms and severity tagging set to each utility's own standards.
How does inspection data get back into GIS?
Inspection data gets back into GIS through a structured export keyed to the same asset IDs that came in. A CSV with asset ID, coordinates, findings, and severity can be joined to existing GIS layers. Corrected locations and new assets go back the same way, so the map improves after every cycle.
Utileyes exports findings as CSV files compatible with ArcGIS and ESRI tools. It integrates with existing GIS and work order systems instead of replacing them. That keeps GIS as the system of record while the inspection platform handles photos, review, and dispatch.
For a deeper look at the connection points, read how drone inspection software integrates with GIS and work order systems.
What this looks like in the field
Utileyes was built with utility linemen and drone pilots. The founders personally flew more than 10,000 utility inspections, and the leadership team has more than 50 years of combined utility operations experience. The asset-first workflow comes from that field time.
In practice, the work runs like this. A supervisor loads a circuit from a KML file, lassoes the poles for each pilot, and sends them out with preloaded flight plans synced to GIS data. Pilots drag and drop their photos when they land. Utileyes auto-organizes them by GPS location and asset ID and flags anything that looks out of place.
Reviewers grade findings by severity, and urgent issues go straight to crews. With that setup, the time from photo captured to crew dispatched can be as little as 15 minutes. Utilities that run this in-house can also see about 50% lower inspection cost than outsourcing to vendors. You can see each step on the How It Works page.
FAQ
What is the difference between asset inspection software and photo storage?
Photo storage keeps images in folders. Asset inspection software attaches each image and finding to a specific asset record. That lets reviewers grade condition and crews act on it by pole, not by file name.
Do I need clean GIS data before starting a drone inspection program?
No. You need a usable starting map with asset IDs and coordinates. The inspection itself is a good way to find and fix gaps, as long as the software lets pilots add or correct assets in the field.
What file formats work for KML asset mapping?
Most platforms accept KML or CSV. Utileyes builds the asset map from either format, or from asset points that pilots generate in flight.
Can drone inspection results go back into ArcGIS?
Yes, when the export is keyed to your asset IDs. Utileyes exports findings as ArcGIS/ESRI-compatible CSV files that can be joined to existing layers.
How should inspection findings be prioritized?
Use severity tags tied to your own standards, such as outage risk, fire hazard, and safety priority. Sorting by severity across assets shows crews which repairs come first.
What if my utility has no drones yet?
Utileyes helps utilities get started through partners, including hardware recommendations and Part 107 training resources.
Start with the map, finish with the repair
Utility asset inspection software pays off when every photo lands on the right asset and every finding reaches the right crew. That starts with a clean asset map and a workflow that improves it each cycle.
See how Utileyes builds the asset map, organizes photos, and routes findings. Schedule a demo.
