Edge-gateway acquisition and cloud monitoring of a multi-inverter rooftop photovoltaic system in a zero-carbon park: vendor-independent design and field deployment
Rooftop photovoltaic (PV) generation is a core contributor to zero-carbon parks, but the inverter fleets that produce it are often locked inside a manufacturer’s closed cloud, so the owner cannot freely access, aggregate or audit the data. This paper reports the design and ongoing field deployment of a vendor-independent edge-gateway and cloud-monitoring system for a 15-inverter rooftop PV installation in a building-integrated PV (BIPV) project in Wuhan, China. The fleet comprises three Growatt models (10000UE, 20000UE and MID 20KTL3-X). The originally installed OEM datalogger was bound to a closed platform whose backend was inaccessible and whose reporting address could not be changed, blocking redirection of the data to the owner’s self-hosted platform. To recover data ownership, an independent industrial IoT gateway is deployed as an RS-485 Modbus-RTU master that polls the inverters over two buses and publishes to a self-hosted server over MQTT/HTTP via a cellular link. The cloud platform stores the telemetry, computes generation, specific yield and inverter efficiency, and applies threshold, peer-comparison and communication-status checks on a zero-carbon dashboard. At the time of writing, 3 of the 15 inverters are integrated and uploading data, while the remaining 12 are offline or pending verification of wiring, Modbus address, model and rated-capacity information. The integrated subset has recorded about 399.9 MWh cumulatively on the platform. Full-fleet clear-day, overcast-day and carbon-reduction figures are therefore presented as preliminary estimates derived from the integrated units under an explicitly stated comparable-output assumption, not as measured 15-inverter totals. We also describe a field case of an inverter that displays a fault while still generating. Irradiance and module-temperature sensors are not yet installed, so the performance ratio is left to future work. The system demonstrates a practical, reproducible path to vendor-independent PV monitoring.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.