AI knowledge base for photovoltaics and energy technologywhen someone on the roof asks for the string plan and inverter parameters.

Not necessarily. Whatever there is can go in as it is: the photo of the inverter’s rating plate, the label on the back of a module, the grid operator’s email with the metering point number, the photographed delivery note. Sorting happens afterwards, not beforehand. If there are only two sources for a system, the answer is based on exactly those two; whether it becomes clear that there isn’t anything more is a point to check in the demo with one of your early systems. If the system finds nothing for a question, it says so.

No, it doesn’t access any device and doesn’t change any settings. You can ask about what you’ve recorded: the commissioning test report, the printout or screenshot of the parameter list, the verification form the grid operator requires for the set values under the Technical and Organisational Rules (TOR) — country setting Austria, reactive power setpoint — plus the voice note from the roof. Anyone who files that after every setting, even as a photo of the display, can query it at the next fault call instead of ringing the colleague who was up there at the time. How well display photos are read, the demo will show.

You decide that, in three levels: not allowed at all, allowed after approval in the chat, or permanently allowed. For the fault service the middle level is the obvious choice — when an inverter shows a message, the system asks whether it may look outside. From the source you can see what comes from your system folder and what comes from outside.

Who sees what depends on the document type and the role, not on which folder a file once ended up in. An installer role can therefore cover string plan, roof structure, mounting system and service reports, but not calculations, purchase prices or the funding statement. If someone asks about something their role isn’t cleared for, they don’t get the content. In the demo you can try out with a restricted role what comes back.

Only as a file or export, and nothing is changed on the portal itself. A knowledge base isn’t monitoring: it doesn’t report yield losses, and it doesn’t look into a portal of its own accord. What you get out as a monthly report or CSV can be brought in via a scheduled export, encrypted and only over outgoing connections — whether your portal supports that depends on the manufacturer and your access; we check that before we start, before any effort is incurred. Whether tables and reports can be queried usefully, a test with a real export will show. For a complaint to the module manufacturer, what counts anyway is what you’ve filed on the performance warranty and yield history.