-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sector coupling
versus model coupling
#1521
Comments
@OpenEnergyPlatform/oeo-domain-expert-energy-modelling : Any feedback on these proposals? |
Both concepts are very important, I agree with your definition of model coupling, but the term sector coupling for me is often applied in the context of optimizing energy use the energy system, so this should be part of the definition. What about:
|
I am fine with this. |
From the BMWK: What is exactly sector coupling?
The Clean Energy Wire states:
From Fridgen (2020):
I mostly agree but in that sense I would not define it as a direct subclass of
|
I disagree with defining |
In general, sectors in the context of energy systems interact in one way or another. For example, in the old context of fossil fuels, the vehicle sector and power plant sector had definitively interactions mostly related to upstream production and supply chains. Is not like decoupled sectors really exists. What is different in this context is that the sectors and their interactions are explicitely being evaluated for a common goal, decarbonisation in this case. |
Let me show further advantages of using |
If we try to be more strict on what we often see in the literature as
|
Hm, I am sorry, but I miss a defining item and I do not really agree with the definition:
|
@UStucky |
With what you say in context I would argue that sector coupling is a
We would need then axioms to define the boundaries of a This is particularly tricky given our existing definition of
This means that everything that we allow within the boundaries of an energy system would be automatically sector coupled, if we characterize sector coupling soley on the fact that the sectors transfer energy among themselves. To avoid this, we could add a co-optimization clause but can that be axiomized or would be only identifiable by definition? We haven't really added any axioms that relate |
Just for completion, here is an exerpt from:
Automatic translation:
|
I found this definition from BDEW:
It is cited and translated in a paper:
I like this definition, because it shows that sector coupling is about various aspects:
|
Within a the BMBF Kopernikus Projekt enavi we hat a lenghtly discussion on the definition of sector coupling. This has been condensed in paper: 10.1007/s12398-018-0241-3 |
I still have the problem with the definition as a process. For me, a given process has to be defined by partial processes down to elementary activities. I do not see that there is a sector coupling process as such. There are processes of planning, they take sector coupling elements and include them into the plan of an eneregy system. There are processes of installing energy systems. They take devices that are designed to realize sector coupling and build them into the overall system. |
From the source @carstenhoyerklick posted:
This analysis comes back to defining as a
BFO implementation of
Is not stated explicitely but processes can be part of other processes. Although I do not really know what happens with cocurrency, we would need some feedback from @OpenEnergyPlatform/oeo-general-expert-formal-ontology This just me throwing ideas around but what about
|
Other thread of thought I have is Is sector coupling a |
Be aware of #1507 😬 |
I may still not fully understand the BFO, but yes, sector coupling as I have characterized it should be a dependent continuant. |
IMHO this is very related. I think we are missing a lot of Policy theory vocabulary. There is probably more sophisticated terms than the previously mentioned
The closest application I can currently think about is the OEKG. But I think that the ontology definition should precede the software implementation and not the other way around. This is because by design, the OEO is primarily a reference ontology (for annotation) , not an application ontology, or so I understood from the paper. Applications then should refer to the ontology only for annotation porpouses. For instance I think object-oriented design is beyond scope. If we want to expand the ontology to other kinds of applications we have always the option of generating subsets of the ontology in the form of OWL profiles. OWL profiles are used to create ontologies specific to some applications. For example the EL profile works for ontologies with a lot of classes, whereas the RL profile is designed with applications with reasoning in mind. I recently closed an issue regarding alternative profiles #1430 but if we see the need of opening it another issue for some specific profile we can always do that.
This definition sounds definitively like
|
As discussed in the OEO-Dev meeting today, for a start we can implement sector coupling as a plan specification and use the definition of the BDWE l-emele cited above: or more condensed:
I think as a descriptor term for the scenario factsheets this will do, even though we may need another concept for describing how the coupling of energy sectors is realized physically in the end. |
I agree to this proposal. |
Maybe we could substitute "establish and optimize energy flows across sectorial borders with respect to cost, environmental impact, and sustainability" for "optimize energy consumption of energy transformation processes from more than one sector" |
I suggest to find a final definition in the next Dev-Meeting, I don't see that we can solve the issue here. I put it on the agenda. |
I am ok with discussing this in a meeting evetually. Anyway, I think the written discussion may be helpful for preparation, because one has time to read and think... In general, I prefer short definition, too. We can extend it with longer elucidations. E.g. like this:
|
In OEO dev meeting 60 we had only little time to discuss this topic. But we had at least a few conclusions:
|
I revisited the discussions and here are some proposals based upon:
|
What would be the use case of |
I am ok with the proposals for
What about adding this elucidation to either the process, or to both, as already proposed above? I'd somehow relate both classes to each other, via axioms at least. |
The proposal for |
Would it make more sense to use an energy system instead of the energy system? Since I think that a system is subject to boundary definition, I consider ambiguous to talk about a system that contains it all. |
Looks like an agreement on |
…coupling add model coupling, sector coupling and sector coupling technology #1521
Description of the issue
The concepts
sector coupling
andmodel coupling
are two concepts that are missing. Sometimes these two terms are used interchangeably by non-experts. But for the OEO we should clearly distinguish them. However, as there are some overlaps between the two concepts (e.g. sector coupling is often depicted by model coupling) we should discuss these terms together.Ideas of solution
Workflow checklist
I am aware that
The text was updated successfully, but these errors were encountered: