What owners, O&M providers, EPCs and commissioning agents fly drones for on utility-scale and commercial solar sites, what the standards ask of those flights, and — use case by use case — how Omniris turns those flights into graded anomalies, repair tickets, progress against the design and sealed custody records.
A solar plant is a very large number of identical parts spread over hundreds or thousands of acres, and many of its faults are too small to show up on the monitoring screen.[5][7] A string that is offline, a bypass diode that has switched on, a cracked cell slowly cooking itself — each costs a little energy, and together they add up. A radiometric thermal camera on a drone sees every one of them as heat, which is why aerial infrared thermography has become one of the two main ways, with manual electrical testing, to inspect the DC side of a plant: at commissioning, every year for preventive maintenance, at the end of a warranty and when a plant changes hands.[5][4] The same imaging finds cracked modules,[5] including front glass broken by hail,[3] and drones are flown during construction to count piles, racking and modules and to check them against the plan.[9]
The flight is the easy part. The industry's standards and guidance put the weight on what happens next: inspection conditions that must be met and documented, anomalies that must be located to the module and graded, a report that a field technician and an asset manager can both act on, and an anomaly list that leads to repairs rather than to another spreadsheet.[1][5] That is where Omniris works.
Radiometric photos become a temperature map. On a Solar site, the anomaly search looks for cells 18 °F (10 °C) above the panels around them, down to one cell, and grades them into IEC TS 62446-3 classes, labelled indicative.
Findings with outline, temperatures, severity, assignee and evidence, worked from a phone and matched, not duplicated, on next year's flight.
Weekly maps and elevation models compared with the design, with progress per design object approved and written back to the schedule.
Every map, finding and report carries a sealed custody record and fingerprint, for warranty, insurance and EPC disputes.
Mission planning, airspace and weather checks, and — in the cloud and data center editions — one-off or recurring marketplace jobs.
Every class says which standard it follows and that it is indicative without an irradiance record, and the report sets out the conditions on the day. See what the results are.
This section summarises published practice: the standards, national-laboratory guidance, international research programmes and trade reporting. Numbers in square brackets point to the Sources. Figures that come only from a vendor are marked "vendor-reported".
| Mission | Who orders it | When | What is flown | What the buyer expects back |
|---|---|---|---|---|
| Preventive aerial thermography | Owner, O&M provider | Once or twice a year[5][7] | Thermal and colour imagery of every row, plant under load | Anomaly list located to the module, classified, with images[5] |
| Commissioning / acceptance | EPC, commissioning agent, owner's engineer | Once, before handover | As above; IEC 62446-1 Category 2 tests include an infrared inspection and string I-V curves[2] | Baseline anomaly list; EPC punch list[5] |
| End-of-warranty and asset transfer | Owner, buyer, lender | Before a warranty expires or a plant changes hands | Full-plant thermal and colour survey | Defect inventory to claim against, or to price into a sale[5][4] |
| On-demand troubleshooting | O&M provider | When monitoring shows a loss it cannot locate | The affected inverter or combiner block | Where the fault is, so the crew goes straight to it[4][7] |
| Balance-of-system thermography | O&M provider | With the module survey or separately | Combiner boxes, cables, connections, fuses, inverters, the substation | Hot connections and components, graded[1][5] |
| Storm and hail damage | Owner, insurer, adjuster | After an event | Thermal and colour imagery of the damaged area | Damage count and locations, documented for a claim; broken front glass often shows as hot cells in thermal[3][8] |
| Construction progress | EPC, owner's engineer | Repeatedly through the build | Colour imagery; LiDAR on some projects[9] | Counts of piles, racking and modules installed; deviations from the plan[9] |
| Vegetation, shading and soiling | O&M provider, vegetation contractor | Through the growing season, or with the thermal survey | Colour imagery; shading and soiling also show in thermal | Where growth is shading panels; when to send the mowing crew[7][5] |
IEC TS 62446-3 recommends a periodic thermography inspection every four years, with the interval for a specific plant agreed with its owner or operator or set by national electrical codes, and it notes that faults of an intermittent or changing nature may or may not be captured at the time of an inspection.[1] In practice:
A working cell turns part of the sunlight into electricity; a cell, substring, module or string that is not delivering power keeps that energy as heat and shows up warmer than its neighbours.[3] The common patterns:
| Anomaly | How it looks | Typical causes |
|---|---|---|
| Hot cell ("hot spot") | One cell, or a few, markedly warmer than the rest of the module | Cracked cell or glass, external shading, internal cell defects[3] |
| Activated bypass diode / substring | One substring of the module uniformly warm, with heat from the operating bypass diode visible at the junction box[1] | Cell mismatch or partial shading forcing the diode on; loss of a connection in the junction box[3][1] |
| Module offline | A whole module warmer than its neighbours | Disconnected module, short-circuited bypass diodes[3] |
| String offline or reversed | A whole string warm | Blown fuse, connector failure, reverse polarity[5] |
| Potential-induced degradation (PID) | A patchwork of warmer cells, often near the frame, in modules near the string's negative end | Voltage-driven shunting in the cells[3] |
| Soiling and bird droppings | Overheated cells with patterns similar to those of internal cell defects; the colour image shows the cause[3] | Bird droppings, debris, vegetation[5][3] |
| Shading | Overheated cells; the pattern depends on the shading source[3] | Small trees and crops nearby; buildings, masts and trees next to the plant[3] |
| Broken glass | Visible in the colour image; in thermal, the damage often creates broken hot cells[3] | Hail and other heavy impacts; extreme mechanical stress on the module frame[3] |
| Hot connections, fuses, cables | Local hot spot on balance-of-system equipment | Loose or corroded contacts, overloaded components[3][1] |
Some faults are subtle: a disconnected string or a shunted cell may be only slightly warmer than its neighbours, and the difference grows with sunlight, which is why the inspection conditions below matter.[3]
IEC TS 62446-3:2017, Photovoltaic modules and plants — Outdoor infrared thermography, is the reference for thermal inspection of PV modules and plants in operation, including cables, contacts, fuses, switches, inverters and batteries.[1] It covers the camera, the equipment that records ambient conditions, the environmental conditions, the imaging procedure (with a section on fast carriers such as drones), evaluation, the projection of temperature differences to nominal irradiance, classes of abnormality, the inspection report, a matrix of thermal abnormalities, and the qualification of personnel.[1] It defines procedures and requirements but no pass/fail criteria, and it was not written specifically for aerial inspection.[4] It classes a drone inspection as a simplified inspection of the whole array, meant to find sub-arrays, strings and modules with obvious problems, which are then examined in a detailed inspection where that is agreed; the projection to nominal irradiance and the allocation into classes of abnormality apply in particular to the detailed inspection.[1]
| Requirement | What is asked | Source |
|---|---|---|
| Sunlight on the panels | At least 600 W/m² of irradiance in the plane of the modules; wind at most 17 mph (28 km/h, Beaufort 4); no more than 2 oktas of cumulus cloud; at 600 W/m² most failures with inactive module parts can be detected | [1][3] |
| Stable conditions during the flight | IEC TS 62446-3 recommends waiting 15 minutes after load or irradiance changes faster than 10% a minute | [1] |
| Plant state | Energised and operating at its maximum power point, in steady state, free of partial shading; soiling checked and cleaned beforehand | [4] |
| Ground detail | IEC TS 62446-3: at most 1.2 in (3 cm) of module edge per thermal pixel, about 5 × 5 pixels on a 6 in cell. The IEA's review gives the same rule for aerial and ground imaging: a distance to target at which a single cell is depicted with ideally 5 × 5 pixels | [1][3] |
| Camera | Images stored with their full radiometric data; IEC TS 62446-3 minimum thermal sensitivity 0.18 °F (0.1 K) NETD | [1] |
| Viewing angle and emissivity | Glass has an emissivity of about 0.85 when viewed within 30° of perpendicular (90°–60°); best practice for aerial inspection defines the angle of view and the distance to target | [3][4] |
| Classes of abnormality | Each abnormality allocated to CoA 1 (no abnormality), 2 (thermal abnormality) or 3 (safety-relevant thermal abnormality) by comparing its pattern and temperature difference with the standard's matrix, whose differences are stated for a normally operating device at 1,000 W/m²; in a detailed inspection, measured differences are projected to that nominal irradiance | [1] |
| Who evaluates | Qualified personnel; ISO 9712 Level 2 thermography is named as orientation | [3][1] |
| Commissioning tests | IEC 62446-1: Category 1 tests for all systems; Category 2 adds string I-V curve measurement and an infrared camera inspection procedure | [2] |
NREL's guidance is explicit: imagery should be processed by a validated routine that identifies module defects and their location in the field, to the module level, labelled so that a technician can find and fix each one; without that, an aerial inspection "simply points out symptoms and the rough location", and troubleshooting on the ground is still needed.[5] A typical deliverable is therefore an anomaly register — each anomaly with its class, its temperatures, a thermal and a colour image, coordinates and, ideally, the block, string and module it belongs to — together with the inspection conditions, a plant-level summary and often an estimate of the power and revenue lost.[5][7]
Two federal actions affect which drones can be bought and flown, particularly foreign-made ones:
Omniris is three things a solar team uses together: a processing stack that turns drone photos into maps, elevation models, temperature maps and 3D models; a secure vault that keeps every file with a tamper-evident custody record; and, in the cloud and data center editions, a marketplace where the flights can be ordered from pilots. The table maps each mission above to what Omniris delivers for it.
| Use case | What Omniris delivers |
|---|---|
| Preventive aerial thermography | Temperature map, Solar-site anomaly search graded in IEC TS 62446-3 classes, measuring tools, report, findings worked to repair. Details. |
| Commissioning baseline and punch list | The same thermal workflow at handover; findings become the EPC's punch list, worked by the EPC's pilots and the owner's team in their own roles. |
| End-of-warranty and asset transfer | A located, fingerprinted anomaly list with findings, evidence images and signed certificates to claim against or price into a sale. |
| On-demand troubleshooting | Fly the affected block and run the same anomaly search; each anomaly is numbered on the map with its coordinates so the crew goes straight to it. |
| Balance-of-system thermography | Spot temperatures and ΔT vs a similar component or ambient, graded; temperature highlights above, below or between values you set, on a straight-down temperature map. |
| Storm and hail damage | Before/after comparison, damage drawn or AI-found and checked by a person, findings, and a situation report for the adjuster. Details. |
| Construction progress | Weekly maps, the design over every flight, progress per design object approved and written back to P6 or Project. Details. |
| As-built and earthworks | Maps, elevation models, point cloud, checkpoint accuracy, cut and fill against the design. |
| Vegetation, shading and soiling | Growth, shading and soiling seen on the colour and temperature maps, filed as findings and assigned to the crew. |
| Getting the flights flown | Mission planning, airspace, weather, checklist; marketplace and recurring jobs in the cloud and data center editions. Details. |
| Year-over-year tracking | Flights filed by date; next year's anomalies added to the open findings they fall on; thermal dates compared side by side, by swipe or blink. |
The full description of Omniris thermal processing is in the Thermal Imaging paper. This section covers what a solar inspection uses, and what the Solar site type changes.
Upload the flight's thermal and colour photos together. Omniris recognises the thermal photos, converts each to surface temperature and stitches them into a temperature map in which every pixel is a measured temperature. Only a map whose values pass a temperature check is labelled THERMAL, and only those are read by the tools, the report and Orion (the Omniris assistant).
Supported radiometric cameras include the DJI Mavic 3 Thermal, Matrice 4 Thermal, Matrice 30T, Zenmuse H20T / H20N and H30T and Mavic 2 Enterprise Advanced; the Skydio X10 and other FLIR radiometric cameras (those other than the X10 are labelled "camera not validated"); and the MicaSense Altum and Altum-PT thermal band.
For the DJI and FLIR cameras, the conversion uses five settings, reviewed under Temperature measurement settings and saved with the job: emissivity, distance, humidity, air temperature and reflected temperature. Humidity and air temperature are prefilled from the weather reading nearest the capture time, and the dialog names the source and the hour; distance from the drone's recorded height. Emissivity defaults to 0.95. The IEA's review gives about 0.85 for module glass viewed within 30° of perpendicular and 0.95 for polymer backsheets,[3] so for a module survey set the emissivity to suit the glass.
Every site in Omniris has a type: Agricultural, Solar (PV plant), Roof / building envelope, or Other. Setting a site to Solar changes where the anomaly search starts, and how the report is worded. Every value remains editable for each run.
| Setting | General start | Solar site start | Why |
|---|---|---|---|
| Rise above background | 10 °F (5.6 °C) | 18 °F (10 °C) | The lower edge of the range IEC TS 62446-3 gives for a single hot cell as a thermal abnormality: 18–72 °F (10–40 K) averaged over the cell, with more than 72 °F (40 K) safety-relevant[1] |
| Background | The whole map's typical temperature | The panels around each spot, within a 33 ft (10 m) square | A hot cell is judged against its neighbours, so a temperature drift across a large plant neither hides a fault on the cool side nor flags a whole warm block. |
| Smallest area | 10 ft² (0.93 m²) | 0.26 ft² (0.024 m²), one cell | Sized to the smallest common crystalline cell (6.1 in, 156 mm square); newer cells are larger. Where a map pixel is larger than a cell, the smallest area is one pixel. |
| Grading | None | IEC TS 62446-3 classes of abnormality | Each anomaly graded on its average rise (below) |
| Direction | Warm | Warm | Hot-cell faults are warm anomalies |
Each anomaly is graded on the average rise of its pixels over their local background, using the specification's hot-cell figures (it gives no hot-cell figure below 10 K, so a smaller rise is shown as CoA 1):
| Class | Average rise | Label | Action shown |
|---|---|---|---|
| CoA 1 | below 18 °F (10 °C) | No abnormality | No action |
| CoA 2 | 18 °F (10 °C) to 72 °F (40 °C) | Thermal abnormality | Check the cause; rectify in a reasonable period |
| CoA 3 | Above 72 °F (40 °C) | Safety-relevant thermal abnormality | Interrupt operation promptly; check and rectify |
The standard's classes are defined for temperature differences projected to a nominal irradiance of 1,000 W/m². Omniris does not record irradiance with the flight, so it grades the measured difference as flown, and every place a class appears — the panel, the report and Orion — says that the grade is indicative. With the Solar starting values every anomaly found rises at least 18 °F, so CoA 1 appears only when you lower the threshold. On rows with wide gaps, the 33 ft background square also takes in ground between rows; the result states the background mode and square size it used. The specification also classes a drone survey as a simplified inspection, meant to find the modules that need a closer, detailed inspection.[1]
In the Site Navigator (the map view of a site's flights), a THERMAL layer is coloured with the ironbow scale over that flight's 2nd–98th percentile and gains five tools. Every number comes from the stored temperatures, °F first with °C beside it:
Illustrative example values. A single hot cell (rank 1 and 3) and a warm substring (rank 2) as the report lists them.
The stitch report is generated once and saved with the results. For a thermal flight on a Solar site it contains the temperature map with its scale, the ten highest-ranked anomalies with their class column and the basis of the classes, the weather during the flight, or on its day when the flight window is not known (air temperature and wind), from a weather archive, and a solar note. The note cites the conditions IEC TS 62446-3 calls for — at least 600 W/m² of plane-of-array irradiance and wind below 17 mph (28 km/h) — asks the reader to check the recorded wind against that limit, and states that irradiance was not recorded, so the grades are indicative rather than a standard-compliant classification. If detection is re-run after the report was made, Refresh Report brings it up to date.
Orion, the Omniris assistant, reads the same saved results. Ask it for the hottest spot or for the anomalies on a flight and it answers with the temperature map, a numbered marker and the coordinates; it never estimates a temperature, and it sees only what the person asking is allowed to see. A read-only Site Navigator link lets someone without an Omniris account — an owner, an O&M contractor, a module supplier — read point temperatures, area statistics, temperature highlights and the latest anomaly search on the shared flights.
An anomaly table tells you where the plant is hot. A finding is what gets it fixed: a work item with a place on the map, a category, a severity, a status, a person responsible, evidence images and a complete history. Findings are described in full in the Findings paper; this is how they serve a solar O&M programme.
Promote a single anomaly from the panel with its flag button, promote every anomaly at or above a severity in one step, or tick Create findings before the search runs so the results are filed when it finishes. An automatic run files the anomalies the search kept (at most 50 per search), most severe first, within your organization's limit for automatic runs (500 by default); anything over that limit can be promoted in one step.
A finding made from a thermal anomaly keeps the anomaly's outline on the map, its centre, its peak temperature, peak and average rise, area and the settings of the search that found it. Its position comes straight from the map, with an uncertainty of at least 3.3 ft (1 m), or twice the map's pixel size where that is larger.
Each organization sets rules that turn a temperature rise into a category and severity. The starting rules file a thermal anomaly by its peak rise: 27 °F (15 °C) or more is High, 7.2–27 °F (4–15 °C) Medium, 1.8–7.2 °F (1–4 °C) Low, and less Info. The starting rules never file a thermal finding as Critical; an organization that wants Critical for the largest rises edits its own rules. The IEC class stays on the anomaly and in the report; the finding's severity is your organization's own scale.
An evidence image of the anomaly is cut from the temperature map, and its fingerprint is sealed into the finding's custody record.
The technician assigned is emailed. In the Omniris mobile app they see their open findings on a map, navigate to each one, change its status, comment and add photos — with or without signal. Statuses move through four stages: untriaged, active, resolved and dismissed (false positive or duplicate).
When next year's anomaly falls on a finding that is still open, in the same category, it is added to that finding as new evidence instead of opening a second one. Resolved and dismissed findings are never reopened by a new sighting.
The Findings view lists and maps every finding with filters and bulk updates. Named groups ("Inverter 3", "Work order 112") organise them by block or campaign. Exports are GeoJSON, CSV and KML, up to 20,000 at a time; signed webhooks and an API with read-only or read-write tokens keep a work-order system in step.
Matching is by position. A new anomaly within a few feet of an open finding in the same category is added to it, so on tightly packed rows check that a matched finding is the same module before closing it out. Each finding shows how many sightings it was built from, and its history records every match.
On a solar build, drones are flown to count what has been installed — piles, racking, modules — and to catch piles, fencing and trenches that are not where the plan puts them.[9] Omniris covers this through its stitching, comparison and design-progress tools. The Stitching paper and the Design and Progress paper describe them in full.
Import the design — IFC, DWG, DXF or DGN — and each element becomes a named object on the site, drawn over every flight on the map and in 3D. Import the Primavera P6 or Microsoft Project schedule and link activities to design objects: pick them on the map, draw around an area, or match by a rule such as layer name against activity code. Each object then counts by number, length, area, volume, mass or percent, and after each flight it is measured one of three ways:
| Method | What it does | On a solar build |
|---|---|---|
| Elevation at grade | How much of an object's footprint is at the design height, within a tolerance (±0.1 ft by default); survey-grade flights only | Pads and graded areas |
| Detected present | AI, run on the flight, finds the thing being built inside the object's footprint; opt-in per object type | Objects drawn as footprints in the design, where the item can be seen from above |
| Manual | A person records how much is in place, on the web or from a phone on site, even offline | Anything — including pile points and cable runs, which are lines and points rather than footprints |
Measured values are proposals until a person approves them; one approval covers a flight and is sealed into the custody record. Approved progress rolls up to percent complete against plan, a forecast finish and earned value, and Export to schedule writes physical percent complete and actual dates into a copy of the P6 or Project file. Findings, files and issues can be kept in step with Procore and Autodesk Forma.
Open-vocabulary AI detection finds, outlines and counts objects you name in plain words, on photos or full-resolution orthomosaics. Each result is a draft a person checks, corrects and marks verified, with a sealed record of the changes (see the AI Detection paper). Omniris publishes no accuracy figure for counting solar components; the count is as good as the check.
The commissioning thermal survey runs through the same workflow as any other: a temperature map, a graded anomaly list and findings that become the EPC's punch list, with the EPC's pilots and the owner's team working the same findings in their own roles. A delivery from a pilot to a client carries the findings filed in the delivered folders, with their history and evidence. The electrical side of commissioning — insulation, polarity and I-V curve results under IEC 62446-1 — stays in your test equipment's records.
The as-built map, elevation models and point cloud export as GeoTIFF, LAZ and CAD files or publish to ArcGIS. A drone survey is not a licensed land survey; where a stamped survey is required, a licensed surveyor is still needed.
Hail is about 2% of solar insurance claims but more than half of claim costs, with utility-scale hail claims averaging about $58 million.[8] After an event, the owner needs to know quickly how many modules are broken and where, and the insurer needs that count documented. Omniris supports the documentation; the assessment remains a person's.
Omniris follows the published standards where it uses them, says which ones, and does not claim that a flight or a report complies with them. Whether an inspection meets IEC TS 62446-3 depends on the conditions on the day, the camera, the flight and the qualifications of the person evaluating it.
| Standard or guidance | What Omniris does with it | Outside its scope |
|---|---|---|
| IEC TS 62446-3:2017 | The Solar site type starts the anomaly search at the standard's hot-cell line, grades anomalies into its classes of abnormality, and the report quotes its irradiance and wind conditions | Record irradiance, project differences to 1,000 W/m², apply the full abnormality matrix (pattern by pattern), or certify the inspection |
| IEC 62446-1:2016 | The thermal survey can be part of the Category 2 commissioning tests' infrared inspection | Run or store the electrical tests (insulation, I-V curves) |
| Weather during the flight | Air temperature and wind for the flight window, printed in the report from a weather archive | Measure irradiance, cloud passage or module temperature on site |
| Map accuracy | Ground control, RTK and checkpoint error reported on the delivered map | Replace a licensed survey |
Solar inspection results end up in warranty claims against module suppliers, in disputes with EPCs over punch-list items, in insurance claims and in due diligence when a plant is sold. In each case the question is whether the file in front of you is the one that was produced on the day. Omniris keeps every file in a vault with a tamper-evident custody record, described in the Evidence Integrity paper:
The custody record proves what happened to a file in Omniris. It does not prove that the inspection conditions were met on the day; the report's conditions note and the recorded weather are there so a reader can judge that.
In the Omniris cloud and data center editions, an owner or O&M manager can order a flight as a job on the Omniris marketplace. Marketplace, payments and payouts are not part of on-premises installations, where the same processing and analysis run on flights your own team uploads.
The mission planner, described in the Mission Planning paper, turns an area into a flight plan: a grid for a straight-down map, a crosshatch, corridor, perimeter or orbit for 3D, with overlap, speed and motion blur worked out from the camera, optional terrain following, and no-fly zones enforced. It exports to DJI Pilot 2, DJI Fly, Litchi, QGroundControl and others; Omniris writes the file, and the pilot flies it in the aircraft's own app. For a thermal survey, the planner sizes ground detail from the visible camera, so set the height from the thermal camera's specification.
A marketplace job can require a drone on the Blue UAS list: a pilot with no aircraft on that list among the aircraft registered to their account cannot apply for it. Federally funded projects should still confirm that the aircraft flown is not from a covered foreign entity under the American Security Drone Act.[15]
| To | How |
|---|---|
| An owner, contractor or supplier without an account | A read-only Site Navigator link for one site: chosen dates and layers, temperatures and the latest anomaly search, findings if you include them, optional password and expiry, revocable at any time. See the Sharing and Delivery paper. |
| GIS | Findings as GeoJSON or KML; maps as GeoTIFF; publish to ArcGIS; site boundaries as GeoJSON, KML, KMZ or Shapefile. |
| Spreadsheets | Findings as CSV; comparisons and saved volumes as CSV. |
| Work-order or asset-management software | Signed webhooks on every finding change, and an API with read-only or read-write tokens and a change feed. |
| Construction platforms | Procore and Autodesk Forma: findings kept in sync, deliverables sent; approved progress written back to Primavera P6 or Microsoft Project files. |
Site boundaries can carry custom fields — text, whole numbers or decimals, for the whole site or per flight date — so a block polygon can hold its inverter number, capacity or an inspection score you track from flight to flight. Values are entered by hand. Sites, boundaries and the Site Navigator are described in the Site Management paper.
Omniris runs in four ways, with the same thermal processing, anomaly search, findings, reports and custody records in each:
| Deployment | Where the plant's data lives | Marketplace |
|---|---|---|
| Omniris cloud on Microsoft Azure | Omniris's cloud storage and processing | Yes |
| Omniris cloud on Google Cloud | Omniris's cloud storage and processing | Yes |
| Omniris data center edition | Storage and servers in Omniris's own data center | Yes |
| On-premises | Your own servers | No — commerce is off; your own pilots upload |
A self-hosted installation with Hybrid enabled can send a thermal stitch to the cloud when its own machines are busy or too small; the result lands in the local vault like any other run. Utilities and owners whose plants count as critical infrastructure can keep imagery of them on their own servers.
A solar inspection result is used for repairs, warranty claims and sales, so Omniris states what its numbers mean where they appear:
Industry facts in this paper come from the sources below, read in October 2026. Omniris product behaviour is described from the product itself.