Solar asset management software for PV inspection teams

The cost of a manual inspection scales with the size of the plant, because someone has to walk the rows and someone has to review the images afterwards. With MapperX, autonomous analysis can reduce manual image review, though cost still depends on module count and campaign requirements. A drone solar panel inspection can cover large areas faster than a handheld survey, depending on site and flight conditions. For asset owners weighing solar panel inspection cost against inspection frequency, this can make annual or seasonal campaigns more practical.

Roof edges, high mounting structures, live equipment and steep or flooded terrain are the parts of a plant where inspection is slowest and least safe, because approaching them on foot requires access equipment and permits. UAV solar panel inspection reaches those areas from the air without putting a technician in front of energized components or at height. The flight is planned once and repeated on the same path in later campaigns, which keeps coverage consistent and comparable. Occupational safety is not a side benefit here: it is the reason many operators moved aerial thermography ahead of manual survey in the first place.

Thermal inspection is a passive measurement, so the measurement itself does not require touching, opening or disconnecting components. The plant can keep producing during the flight, which means an inspection may not need a shutdown window. Avoiding contact with glass, frames and wiring reduces the risk of handling-related micro cracks or damaged connectors, but does not eliminate operational risks. Thermal imaging surveys the site non-destructively and helps identify modules that may need electrical testing.

Reporting is where most inspection projects lose their time: images are sorted, findings are transcribed, tables are rebuilt and the document is formatted by hand. MapperX generates the report from the analyzed campaign data, so the step that used to take days of manual assembly ends with a single export. Traceability improves at the same time, because every line in the report resolves back to the module and the frame it came from rather than to a note someone typed. Nothing is retyped between analysis and document, which removes the transcription errors that make an inspection report difficult to defend.

A report is only useful if the receiving party accepts it. MapperX report structure supports IEC 62446-3, the specification for outdoor thermographic inspection of photovoltaic plants, so an owner, an insurer or an independent engineer can review the findings against a known standard. Acceptance for commissioning, warranty claims or insurance files depends on the inspection evidence and the recipient's requirements.

Different readers need different documents from the same campaign. MapperX lets you filter by plant, campaign, anomaly class, severity or string before exporting, so an owner receives the summary and the maintenance contractor receives the module level work list, both drawn from one dataset. Reports carry your own company details and logo, which matters when you are an inspection provider delivering to your own clients. There is no per report charge and no cap on how many you produce, so re-issuing a document after a repair or splitting one campaign across several stakeholders costs nothing but the export.

A plant is more than an array of modules, and an inspection record that ignores the electrical infrastructure stops being useful the moment a fault sits upstream. In MapperX Studio inverters, transformers, combiner boxes, strings and modules are recorded as components, each with its own attributes, documents and history. A finding can then be read in context: one warm module is a panel issue, a whole string behaving differently points at the combiner or the inverter feeding it. Keeping the electrical layer in the same model as the thermal findings is what allows one platform to replace the spreadsheet that usually sits beside the report.

Field references only work when everyone uses the same names. MapperX Studio numbers strings and panels inside the plant model using a naming format you define, so the label on the combiner box, the identifier in the work order and the row in the report all match. Detailed plant planning is done once and then reused by every campaign, which is what keeps two inspections a year apart comparable. Without that shared numbering, module positions drift between reports and the comparison that makes trend analysis possible quietly breaks, usually without anyone noticing until a warranty claim is questioned.

The digital twin holds the plant layout and its component records in one model that every campaign updates rather than replaces. That is the difference between solar asset management platforms and a folder of inspection reports: the model carries the history of the asset, so a new O&M contractor or a new owner inherits a documented plant instead of reconstructing it from old files. Improved plant management follows from having one current picture, and efficiency follows from acting on it. At handover, commissioning acceptance or refinancing, that documented state is usually the fastest evidence available.

Every operation is logged with its time stamp, the person who performed it and the state it moved the component to, so the work history of a plant can be reconstructed at any point without asking anyone to remember. That record answers the questions that come up long after the work: when the module was replaced, who signed the state change, whether the repair happened before or after the loss appeared in the production data. Reporting to the second is not about surveillance, it is about having a defensible operational history when an owner, an insurer or an incoming contractor asks for one.

Production data alone tells you that output dropped and thermal findings alone tell you that modules are faulty, but neither says whether the two are related. MapperX monitors plant performance data alongside the inspection findings, so a drop can be traced to the string, inverter or module group behind it instead of being investigated from scratch. Evaluating them together shortens the path from symptom to cause, which is where most of the lost production actually accumulates. It also shows whether a completed repair recovered what it was expected to recover, rather than leaving that assumption untested.

Open work, completed work and pending inspections are visible in one place, helping teams address issues before downtime grows. Faults left unaddressed can prolong production losses, especially when teams lack a current view of outstanding work. A shared and current work list supports routine operations and timely intervention, though it cannot guarantee uninterrupted production.

Work orders and their history are recorded as they are completed, so a report on team activity can be produced at any time without collecting messages and photographs from the field. The record covers what was assigned, who carried it out, when the state changed and which campaign the work came from. For an O&M contractor this is the evidence of service delivery that the client eventually asks for, and assembling it retrospectively is where the margin on a maintenance contract usually disappears. Unlimited and current reporting means the answer is a filter and an export rather than a week of reconstruction.

Access is granted per plant and per task, so a subcontractor sees only the site and the work assigned to them while the asset owner keeps the portfolio view. That separation is what allows several parties to work in the same platform without exposing commercial data or the condition of unrelated sites. Authorizing members individually also keeps the audit trail meaningful, because each state change is attributable to a person rather than to a shared login. For portfolios where inspection, maintenance and ownership sit in different companies, this is usually the condition for using one platform at all.

Technical and operational information about the plant is reachable from the same place the work is assigned, so a technician does not open one system for the work order, another for the plant documents and a third for the inspection history. Component records, previous findings, measurements and layout are all attached to the plant model, which means the context arrives with the task. That accessibility is what shortens the time between arriving on site and starting useful work, and it removes the most common reason for a second visit, which is simply not having the right information at hand.