NatLabRockies / NatLabRockies/OpenStudio

Peer-to-peer trade for surplus on-site generation (local flexibility market)

Open
#5,425 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement Request Triage
Dominant language
C++
Stars
646
Forks
237
Avg merge
3d 11h
Merged PRs (30d)
10

Description

Hi OpenStudio/EnergyPlus developers and users,

I hope this message finds you well.

I would like to ask a question regarding the potential for simulating a local energy flexibility market using OpenStudio/EnergyPlus.

Specifically, consider a scenario involving two buildings simulated within OpenStudio/EnergyPlus: one equipped with on-site generation (e.g., PV systems), and the other without. During certain hours, the building with on-site generation produces surplus electricity. I am wondering whether it is possible, instead of exporting this excess energy to the grid, to simulate the transfer of this energy directly to the other building.

In essence, this would require modeling two distinct electricity purchasing mechanisms: one from the main utility grid and another from neighboring buildings within a local energy network.

I am not sure whether OpenStudio/EnergyPlus currently supports such a capability and would greatly appreciate your insights or any possible workarounds to model this functionality.

Thank you very much for your time and support.

Sincerely,
Behnam Mohseni Gharyehsafa
Maynooth, Ireland

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source files, tests, or entry points. Start by checking current OpenStudio and EnergyPlus support for multiple buildings, surplus generation, and inter-building electricity flows; define the required modeling behavior and a validation scenario before estimating implementation work.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.