History Import — Frequently Asked Questions
Switching a plant to Mirox should not mean losing the years its previous monitoring system recorded. These are the questions operators ask before and during a history import. For the step-by-step guide, see Importing a Plant's History.
1. Can I bring the history of my previous monitoring system into Mirox?
Yes. The history import takes one export archive of the previous system, matches the devices in it to the plant's components, and writes the measurements into the plant. Afterwards the production and period graphs, the performance ratio, curtailment analyses, exports and reports reach back to the first day the plant fed in, as if Mirox had been there from the start.
2. What do I need to start?
Three things: a ZIP export of the previous monitoring system, a plant in Mirox whose components already exist so the measurements have a place to go, and a connected Mirox-Agent for that plant, because the agent is what writes the history into the plant's data store. The archive format of supported providers is recognised on its own: you do not pick a provider, and you do not unpack or rename anything.
3. How large may the archive be, and what if my connection drops during the upload?
Archives of several gigabytes are normal. The upload is resumable: if the connection drops or the browser is closed, choose the same file again and the upload continues where it stopped. Nothing has to be started over.
4. How are the devices of the archive matched to my plant?
Every device found in the archive is matched to a component of the plant by serial number first, then by name. Inverters, strings, feed-in meters, irradiation sensors and the control unit are covered. The summary tells you in one line whether everything matched; the component groups show how many of their devices are mapped, and you open a group only when you want to change which data columns are written or where a single device goes.
5. What does "unknown source" mean?
A device the archive carries data for but that matches no component of the plant, for example a pyranometer on a weather mast the plant's records never listed. Its measurements are imported anyway, under a neutral source name, so nothing is thrown away and nothing has to be modelled first. Only devices without any data at all are left out.
6. Can imported data overwrite or mix with the plant's live measurements?
No. Every imported series carries a mark that names it as imported, and the import stops at the moment the plant's own monitoring began. Days that already carry live data are skipped rather than written. A later purge removes only the imported data, never the live measurements.
7. How long does an import take, and does it disturb the live monitoring?
The plant's agent writes one day every few seconds, so several years take a few hours. The pace is deliberately gentle so the plant's live monitoring is never disturbed, and the import pauses by itself while the agent runs one of its own analyses, continuing the moment that work is done. The progress bar shows the days written, the points stored and the remaining time.
8. What happens if the agent restarts or the connection drops during the import?
Nothing is lost. The platform keeps the position of the last day written, and the agent continues from there as soon as it is back. You can also pause and resume yourself, or stop the run entirely; what was written stays until you purge it.
9. Are energy totals consistent after an import?
Yes. Lifetime energy counters are built from the archive's interval energy and only ever increase. When days are written again, every counter continues from the value already stored, so a series never steps down and no energy is counted twice, which is what the platform's yield and revenue figures rely on.
10. A day is missing or incomplete after the import — how do I repair it?
Use Re-import days on the finished import. Choose the first and last day, and the plant's agent writes that range again from the same archive and the same mapping. Days that were already complete are simply written once more with the same values, so a generous range does no harm. Start the range one day before the first missing day; the energy of a day that was only partly written is then credited to the right day.
11. Can I remove imported data again?
Yes. Purge data removes every measurement the import wrote in one step and keeps the archive and the mapping, so the import can be run again, for instance with a changed mapping. Delete then removes the import and its archive from the platform; it is refused while imported measurements may still exist, so purge first.
12. Who can run an import?
Operators of the plant. The Import tab lives in the plant's Data Flow section.