Dear openmod community,
I’m happy to announce that we have made the code of NRGISE, our simulation framework for local energy systems, publicly available!
We tried hard to make NRGISE easy to adapt, extend, and hack, so it can support a wide range of research use cases involving local energy systems and microgrids.
Code: GitHub - nrgise-open/nrgise-open: NRGISE Open is a Python framework for simulating local energy systems over time. · GitHub
Documentation: NRGISE Open Docs
Note that we are sharing the code under CC BY-NC-SA 4.0. We know this is not an OSI-compliant open-source licence and comes with limitations, but the code is publicly available and free to use and adapt for noncommercial purposes like academia and education.
Best
Tobi
2 Likes
Hello @tobirohrer This looks like a useful step in the right direction.
I do think that an AGPL‑3.0‑or‑later license would be a better choice under the circumstances. That particular license is not a “non‑commercial” license but neither is it particularly attractive to commercial software developers.
I did not see a copyright notice in the GitHub repository. Copyright notices are good practice. Attribution details are required under Creative Commons licensing. A record of authorship is also necessary in a research context (Di Cosmo et al 2026:4).
I would advise against users running or contributing to non‑OSI approved software for three reasons. First, the patent grant in OSI‑approved licenses is useful — and although United States software patents are not likely to be present in this case, users cannot be certain. Second, the software will fall under the European Cyber Resilience Act (CRA) in December 2027 given that further substantive development of the codebase takes place — so again users are faced with some uncertainty should they wish to further distribute their version of the software. Third, under current licensing, contributors may also face liability exposure under the recently revised European Product Liability Directive (PLD) (Colanna 2025:§5.2.1). Moreover, if the CRA does apply, Fraunhofer ISE will become a “manufacturer” and thereby need to meet a number of statutory obligations under that Act.
Following the FSFE‑sponsored REUSE protocol for machine-readable legal metadata is recommended.
Stepping back, it would be better for Fraunhofer ISE to develop a more comprehensive policy on open source software. There are many excellent resources on how organizations can set up Open Source Program Offices (OSPO) and develop OSS strategies. There are also a number of software law firms in Germany who could advise in this context.
If the objective is to encourage contributions and even build some momentum, then an OSI‑approved license is more-or-less essential.
Under the circumstances, the name “NRGISE Open” is not particularly appropriate either.
If Fraunhofer ISE would like to continue this discussion offline, I would be happy to engage. Best, R.
PS: for those interested, both references are worth reading.
Sources
-
Colonna, Liane (1 April 2025). “The end of open source? Regulating open source under the Cyber Resilience Act and the new product liability directive”. Computer Law and Security Review. 56: 106105. ISSN 2212-473X. doi:10.1016/j.clsr.2024.106105. 
-
Di Cosmo, Roberto, Sabrina Granger, Konrad Hinsen, Nicolas Jullien, Daniel Le Berre, Violaine Louvet, Camille Maumet, Clémentine Maurice, Raphaël Monat, and Nicolas P Rougier (12 March 2026). “CODE beyond FAIR: a roadmap for reusable research software”. Scientific Data. 13 (1): 514. ISSN 2052-4463. doi:10.1038/s41597-026-06705-6. 
▢
1 Like
Hi Robbie,
Thanks for the honest feedback and pointers.
As I mentioned in the announcement, we’re aware that CC BY-NC-SA is not an OSI-approved open-source license and that this limits reuse and collaboration. Yet making the code publicly available is a first step for us (speaking for us as team, not for Fraunhofer ISE as there are OSI-license-compliant projects at ISE already). For now, I hope making the framework available will still be useful to researchers working on local energy systems, within the limitations we’ve stated.
Thanks for the hint about the copyright, i will check that soon.
Best
Tobi
Worth remembering that the CRA exempts products placed on the EU market before 11 December 2027 unless they undergo substantial modifications that change their functionality or purpose. So ongoing development of a research codebase may well trip that threshold? Something to be aware of.
The definition for free and open source software provided in the CRA aligns with the definition that the Open Source Initiative uses for its approval process. So your best bet is probably ultimately an OSI approved license. Best, R.