Welcome to the OpenEnergy Platform!

This platform mainly addresses students, researchers and scientists in the field of energy modelling and analytics as well as interested persons in those fields. The platform provides great tools to make your energy system modelling process transparent!

  • You can give, get and document data of your modelling process (figure) through to the OpenEnergy Database (oedb). This includes raw data, processed data and results .
  • You can work with the OpenEnergy Database via the visual interface or a REST-full HTTP-interface. Learn more about the OEP API here.
  • You can describe, find, and compare energy system models, frameworks as well as concrete studies and scenarios with the various Fact Sheets. You can link your code to the model description (Fact Sheets).
  • You can find and refer literature to models and data using the literature-schema of the oedb. We assume you provide code on the platform of your choice (e.g. GitHub). For all data in the database a minimum of metadata is required in order to improve the transparency.
  • You can harmonize your wording with other researchers using the Glossary. We experienced that transparent data and code doesn’t mean that the results of a study are understandable. Within discussions it is a crucial point to “use the same language”. In the Glossary the expressions used in the Fact Sheets and in the data tables can be explained and discussed.
  • You are invited to join our discussion if you have suggestions or you want to involve yourself into the development. You can participate in the discussion on standardisation of the fact sheets or improvements of the oedb or about including further features. Important: The discussions are still going on.
  • You can meet us at the openmod meetings!

With the included tools, we want to promote reproducibility in energy system research. We know that for (most) modelling processes, you need more than just data and code to reproduce results. Especially when complex or different models are involved, a proper code documentation and a description of the steps of the modelling process are needed. We will continuously report and discuss new tools and processes at the openmod meetings. You are invited to contribute!
image/svg+xmlOpenEnergy Platform Raw Data Result Data OpenEnergy Database Scenario log Scenario Factsheet Data Processing Literature Function Model Framework Factsheet Model Factsheet Framework

The function and tools of the OEP are displayed above. Please click on the button to see and learn more about.

Software framework giving the tools and functions for building specifically models in order to find results and answers of research questions.

Energy models or energy system models are computer models of energy systems in order to analyze them. Such models often employ scenario analysis to investigate different assumptions about the technical and economic or other conditions at play. See more on https://en.wikipedia.org/wiki/Energy_modeling

Raw data:
In order to create and calculate scenarios or case studies different raw data are needed to feed the models. Information like weather, spatial information of land-use or infrastructure or time series of energy demand and generation ared used those models. The oedb is structured through predefined schemas in order to organize the heterogeneous data sets contained in the database into defined groups of.

Data processing
The data processing of raw data is done by collecting and data manipulation in order to get model specific data sets (input data).

Scenario log

Result data
Result data our output data of a models.

If you find bugs or if you have ideas to improve the Open Energy Platform, you are welcome to add your comments to the existing issues on GitHub.
You can also fork the project and get involved.

Please note that the platform is still under construction and therefore the design of this page is still highly volatile!

Changes in version 0.3.1


  • Show changelogs

  • Add 'form=csv' option for /rows-API-requests

  • Add button for CSV download


  • Parse integer valued character_maximum_length in put-requests for tables