Final — Executable Library (Energy)

Energy Sovereignty Atlas

A curated, runnable, auditable set of open tools, models, datasets, and practitioner knowledge for energy planning, grid physics, microgrids, buildings, and materials reality. No “directory layer” is included here — only the extracted components and the minimal structure needed to sequence them.

focus: open + inspectable mode: data → physics → planning → operations → LCA → access outputs: models, timeseries, scenarios, controls, inventories

How to use this atlas

This page is designed to be traversed as a pipeline. The key is not “collecting tools” — it is composing a minimal stack that can be executed locally, audited, and iterated without fragile dependencies.

1) Establish the data spine

Start with open datasets and time series. Snapshot what matters locally. Treat cloud-hosted repositories as sources to mirror, not infrastructure to depend on.

2) Lock demand and constraints

Buildings and appliances define the demand reality. Model them explicitly before attempting “optimal” system builds.

3) Run grid physics and failure modes

Planning outputs are not credible until power flow, voltage, dynamics, and islanding constraints are tested.

4) Execute planning models (scenario engines)

Use optimisation tools to generate scenario spaces and stress tests — not as governance templates.

5) Operate (control + dispatch)

Convert designs into operational logic: energy management systems, microgrid control, EV charging scheduling.

6) Ground in materials (LCA)

Operational “green” claims collapse without embodied impacts, supply chains, and toxicity accounted for.

Practical sequencing principle: model demand and physics first; only then run long-horizon optimisation. Optimisation without physics is a narrative generator.

Legend: tags & sovereignty tiers

Each resource card includes tags for Scale, Function, and an S-tier (sovereignty tier) describing dependency risk.

S-tiers

S2 — fully local / FOSS backbone S1 — open but often used with proprietary/cloud S0 — cloud / SaaS / license constraints

S2 items are preferred as foundations. S1 items can be core if run fully locally and solver/data constraints are controlled. S0 items are treated as ingest/reference or constrained-use utilities.

Scale & Function (examples)

Scale: Device Scale: Building Scale: Microgrid Scale: Region Function: Data Function: Planning Function: Simulation Function: Operations Function: Impact

Scale indicates where the tool lives in the stack. Function indicates what role it plays (data, physics simulation, optimisation planning, operations/control, or material impact accounting).

Tier-0 backbone (minimal executable core)

The Tier-0 backbone is the smallest set that can generate designs, test physics, and operate local systems while remaining auditable. Everything else in this page either feeds into Tier-0 or extends it.

PyPSA Python for Power System Analysis

Scale: Region → Continental Function: Planning + Simulation S2

A core planning and optimisation framework for modern power systems with renewables, storage, and sector coupling (electricity + heat + hydrogen + transport).

Stack role
Used to generate capacity expansion + dispatch scenarios. Outputs feed into grid-physics checks (pandapower / OpenDSS / GridLAB-D) and can be constrained by time series (Renewables.ninja, OPSD) and by LCA inventories (openLCA/Brightway).

Calliope multi-scale optimisation framework

Scale: District → Continental Function: Planning + Simulation S2

Energy system optimisation focused on flexible model design, high spatial/temporal resolution, and repeatable scenario runs with clear separation of framework code and model data.

Stack role
Suitable as a scenario engine where many variants must be explored quickly. Pair with grid-physics tools for feasibility checks.

OSeMOSYS long-horizon energy planning

Scale: National → Regional Function: Planning S1

A long-run integrated assessment and energy planning model generator designed for low barriers to adoption; widely used for policy and national-scale planning. Multiple toolchains exist; some deployments depend on proprietary solvers, others do not.

Sovereignty note
Treat as S2 when run with fully open solvers and locally controlled data; treat as S1 when locked into proprietary solver ecosystems.

TEMOA Tools for Energy Model Optimization and Analysis

Scale: Local → Global Function: Planning S2

Energy system optimisation framework built for transparent scenario analysis and reproducible datasets; designed to support rigorous planning and uncertainty studies.

Stack role
Strong fit for scenario sets where input databases must be versioned and audited. Use alongside LCA (openLCA/Brightway) to ground tech choices.

oemof Open Energy Modelling Framework

Scale: Local → National Function: Planning + Simulation S2

Modular Python framework for building custom energy system models. The ecosystem includes specialised packages such as oemof.solph for LP/MILP optimisation.

Stack role
Best when the model architecture must be composed from modules (custom buses, flows, conversion components). Useful as a “framework layer” beneath specific models.

OnSSET Open Source Spatial Electrification Tool

Scale: Region → Country Function: Planning S2

GIS-based least-cost electrification planner selecting between grid extension, minigrids, and stand-alone options across settlements. Designed for energy access and real-world rollout planning.

Stack role
Turns geospatial constraints into actionable electrification investment maps. Pair with off-grid appliance reality (Global LEAP / Efficiency for Access) and humanitarian constraints to avoid “paper access” outcomes.

Data & measurement

This layer supplies datasets, grid time series, and structured energy databases. The core rule is simple: snapshot and mirror critical data locally; never architect “live dependence” on a cloud portal.

OpenEI Open Energy Information

Scale: Country → Global Function: Data S0

Semantic wiki + data hub for energy datasets, mappings, and related information. Best used as a gateway to discover and pull datasets.

Sovereignty note
Treat as ingest/reference. Mirror any dataset that becomes structurally important to local modelling.

OEDI Open Energy Data Initiative

Scale: Country → Global Function: Data S0

Large, centralized repository of energy datasets aggregated from DOE programs and national labs, published through a data lake model. Licensing is often CC BY 4.0 unless otherwise noted.

Sovereignty note
Cloud-centric by design. Use for bulk acquisition, then copy critical slices into local storage and versioned pipelines.

Open Power System Data (OPSD)

Scale: Region Function: Data S1

Curated power system datasets (especially Europe): time series, power plant lists, network-related data packages — processed, documented, and published for modelling use.

License note
Dataset licenses vary. Treat as S2 only for the subsets with explicitly open licensing; otherwise treat as S1 ingest/reference.

Open Energy Platform (OEP)

Scale: Global Function: Data S1

A structured platform for energy-system modelling and data: datasets with metadata, quality indicators, and APIs for programmatic access.

Use pattern
Use OEP to pull structured model inputs and to publish/share datasets with reproducible metadata. Mirror critical tables locally.

Renewables.ninja

Scale: Site → Global Function: Data + Simulation S1

Wind and PV hourly output simulation + downloadable datasets. Used frequently as an input generator for system models.

License / sovereignty note
Treat outputs as data products. If used operationally, cache time series and annotate provenance + parameters in local repositories.

System planning & optimisation

These tools generate scenario spaces: capacity expansion, dispatch, and long-horizon trajectories. The key constraint: they must be paired with grid physics and demand realism (buildings + appliances), or they will output elegant impossibilities.

PyPSA

Scale: Region → Continental Function: Planning S2

Optimisation and simulation for modern power systems with sector coupling. Strong ecosystem and high scalability.

Best used for
High-renewable grid planning, storage sizing, transmission studies, and multi-carrier coupling (electricity/heat/H₂).

Calliope

Scale: District → Continental Function: Planning S2

Scenario exploration framework designed to run many variants from the same base model data.

Best used for
Rapid scenario branching with clear separation between framework code and dataset configurations.

OSeMOSYS

Scale: National → Regional Function: Planning S1

Long-horizon energy planning for policy contexts. Designed for accessibility with low upfront costs.

Best used for
Multi-decade planning where the primary output is a coherent set of investment pathways under constraints.

TEMOA

Scale: Local → Global Function: Planning S2

Planning tool built for transparent, reproducible databases and scenario comparisons.

oemof

Scale: Local → National Function: Planning S2

Modular modelling framework for composing bespoke energy system models; supports LP/MILP via oemof.solph.

ElecSim agent-based electricity market model

Scale: National → Regional Function: Simulation (ABM) S2

Agent-based simulation of wholesale electricity markets (GenCos + demand). Useful where “single omniscient planner” assumptions fail.

Grid physics, dynamics & co-simulation

This layer tests feasibility. It answers: “will voltages stay inside limits?”, “what fails first?”, “does islanding work?”, and “what happens under transients?”. Planning models should feed into this layer before anything is treated as real.

pandapower

Scale: Microgrid → Transmission Function: Simulation + Operations S2

Power system modelling and analysis in Python: power flow, OPF, short-circuit, state estimation, time series control loops.

GridLAB-D

Scale: Distribution Function: Simulation S2

Distribution and smart-grid simulation: end-use loads, DERs, automation, and market effects in one environment.

OpenDSS

Scale: Distribution Function: Simulation S1

Open-source distribution system simulator (EPRI). Widely used for DER integration, hosting capacity, and distribution planning studies.

Cross-platform enhancement (recommended)
For cross-platform APIs and extended tooling around OpenDSS, see DSS-Extensions and DSS-Python.

HELICS co-simulation framework

Scale: Microgrid → Interconnection Function: Simulation (co-sim) S2

Federated co-simulation framework for coupling transmission, distribution, communications, markets, and other simulators into one run.

PowerModels.jl

Scale: Transmission Function: Optimisation + Physics S2

Julia/JuMP package for steady-state power network optimisation; a strong alternative when Julia toolchains are preferred.

Distribution companion
For distribution networks, use PowerModelsDistribution.jl.

ANDES dynamics & stability

Scale: Transmission Function: Dynamics Simulation S2

Python library for power system modelling and dynamics: transient stability, small-signal stability, and symbolic-numeric prototyping.

Components & resources (physics building blocks)

Component libraries prevent “magic inputs”. They allow direct modelling of PV output, wind power, marine energy, and battery behaviour so system models can be grounded in transparent physics rather than opaque coefficients.

pvlib python

Scale: Device → Site Function: Simulation S2

Photovoltaic system performance modelling in Python (irradiance → DC → inverter → AC), with benchmark implementations and validated methods.

windpowerlib

Scale: Site Function: Simulation S2

Wind turbine and wind farm power output modelling library; converts weather data and turbine characteristics into generation time series.

MHKiT Marine & Hydrokinetic Toolkit

Scale: Site Function: Data + Simulation S2

Toolkit for marine renewable energy: data ingestion, QC, resource assessment, device performance, and loads (Python & MATLAB).

PyBaMM battery modelling

Scale: Device → Site Function: Simulation S2

Physics-based battery simulation in Python, including degradation and flexible model definitions; useful for storage design and operational constraints.

Operations & control (EMS / microgrids / EV)

This layer turns designs into operational logic. It is where sovereignty becomes tangible: local control, local optimisation, local scheduling, and minimal dependence on cloud orchestration.

OpenEMS Open Source Energy Management System

Scale: Site → Microgrid Function: Operations + Control S2

Modular platform for monitoring and controlling storage, PV, EV charging, heat pumps, electrolysers, and tariff-aware optimisation. Built explicitly around local integration requirements.

pymgrid microgrid simulator (control)

Scale: Microgrid Function: Simulation + Control Research S2

Microgrid simulation environment (rule-based, MPC, and RL-friendly control). Useful for control strategies and stress tests at micro scale.

Maintenance note
The pymgrid maintainer notes future development moved to python-microgrid (drop-in replacement). See the pymgrid README for current status.

ACN-Sim EV charging simulator

Scale: Site → Campus Function: Simulation S2

Data-driven simulator for EV charging systems, capturing battery charging behaviour and infrastructure constraints; used for scheduling algorithm research.

PowerSimulations.jl operations simulation

Scale: Transmission → System Ops Function: Operations Simulation S2

Julia tool for quasi-static power system operations simulation (production cost models, scheduling and dispatch studies), designed for modular decision/emulation models.

Buildings, districts & cities (demand reality)

Buildings are the demand engine and the thermal battery of civilisation. This layer anchors “energy system” work in heat flows, envelopes, HVAC, and urban form.

EnergyPlus whole-building simulation

Scale: Building Function: Simulation S2

DOE’s open-source building energy modelling engine (BEM). Models HVAC, lighting, equipment, water, and advanced controls.

Stack role
Generate realistic load profiles and retrofit impacts; feed microgrid sizing (OpenEMS / pymgrid) and planning constraints (PyPSA / Calliope / TEMOA).

OpenStudio EnergyPlus workflows

Scale: Building → Portfolio Function: Simulation + Workflow S2

Open-source SDK and tools to build and automate EnergyPlus workflows, including graphical interfaces and model management.

ESP-r multi-domain building simulation

Scale: Building Function: Simulation S2

Building performance simulation modelling heat, air, moisture, light, and electrical power flows with high control over resolution and coupling.

City Energy Analyst (CEA) urban energy systems

Scale: District → City Function: Simulation + Planning S2

Open-source urban building energy modelling platform for low-carbon city design, district heating/cooling studies, and infrastructure scenarios.

LCA & material grounding (embodied reality)

This layer prevents energy modelling from collapsing into pure operational accounting. It answers: “what is embedded in the hardware?”, “what is the upstream burden?”, “what is displaced or shifted?”

openLCA

Scale: Device → System Function: Impact (LCA) S2

Open-source life cycle assessment software for footprinting and sustainability modelling, from simple products to large process systems.

openLCA Nexus LCA databases

Scale: Device → System Function: Data (LCA) S1

Data portal for LCA inventory databases and sustainability datasets used by openLCA and other workflows.

License note
Many high-quality inventories are proprietary; treat database access as S1 unless explicitly open licensed.

Brightway Python LCA framework

Scale: Device → System Function: Impact (programmatic LCA) S2

LCA and environmental impact framework designed for large datasets and programmatic experiments; strong for integration into modelling pipelines.

Humanitarian, access & off-grid appliances

This layer forces energy modelling to confront fragile contexts, displacement settings, weak-grid markets, and real appliance performance. It contains both field knowledge hubs and the market / performance intelligence needed to spec systems that actually work.

Humanitarian Energy Knowledge Hub

Scale: Site → Region Function: Education + Tools S0

Living knowledge base for energy access in humanitarian and displacement settings: planning tools, case studies, and sector updates.

Practical Action — Energy resources

Scale: Site → Region Function: Practitioner Knowledge S0

Practitioner-grade resources on energy access, clean cooking, off-grid systems, and real-world barriers/opportunities in low-income contexts.

Global LEAP Awards (Clean Energy Ministerial)

Scale: Device Function: Market Signal + Testing S0

International competition identifying high-quality, energy-efficient off-grid appliances; winners/finalists undergo accredited lab testing.

Efficiency for Access — Market series & surveys

Scale: Device → Market Function: Market Intelligence S0

Reports and datasets describing off-grid and weak-grid appliance markets, demand, and impacts — a critical complement to purely technical modelling.

CLASP — Global LEAP programs & tools

Scale: Device → Market Function: Tools + Evidence S0

Research, tools, and procurement mechanisms supporting efficient appliances in off-grid and weak-grid settings.

Integration rules (what plugs into what)

The atlas becomes operational when each layer’s outputs are treated as inputs for the next layer. The rules below define the default wiring.

Rule A — Data → Planning

Time series and structured datasets from Data & measurement feed planning engines (PyPSA, Calliope, OSeMOSYS, TEMOA, oemof, OnSSET). Any dataset used more than once should be snapshotted and versioned locally.

Rule B — Demand realism first

Build demand constraints using EnergyPlus, OpenStudio, ESP-r, and CEA. Off-grid contexts should cross-check appliance-level power and usage patterns with Global LEAP and Efficiency for Access.

Rule C — Planning → Physics

Every planning output must be tested in grid physics tools: pandapower, GridLAB-D, OpenDSS, and when needed for dynamics: ANDES. For coupled simulations (T&D + comms + markets), use HELICS.

Rule D — Design → Operations

Operational control stacks use OpenEMS (site/microgrid management), pymgrid / python-microgrid (microgrid control simulation), and ACN-Sim (EV charging scheduling simulation). Operations at system level can be stress-tested with PowerSimulations.jl.

Rule E — Materials reality always on

Any technology pathway should be grounded with life cycle assessment using openLCA and/or Brightway, pulling inventories as appropriate from openLCA Nexus. If inventories are proprietary, treat them as constraints with explicit licensing and provenance rather than hidden assumptions.

Rule F — Access & fragility are not optional

Energy access work should be cross-validated against: Humanitarian Energy Knowledge Hub and Practical Action resources, with appliance performance and market intelligence from Efficiency for Access. Without this, models drift into high-capacity assumptions and fail under real constraints.

Default build order (repeatable): data → demand → physics → planning → operations → LCA → access. If any step is skipped, treat downstream outputs as provisional.