Endogenise industry heat supply in steam, medium and high T segments#611
Endogenise industry heat supply in steam, medium and high T segments#611
Conversation
…kus/pypsa-eur-sec into endogenous_industry
for more information, see https://pre-commit.ci
… endogenous_industry
|
For the split between low, medium and high temperature we can use data from https://www.agora-industry.org/publications/direct-electrification-of-industrial-process-heat, 50% high temperature, 13% low temperature, 37% medium temperature |
|
For medium temperature heat the biomass route has an |
for more information, see https://pre-commit.ci
I couldn't find a better source. I would suggest to merge it as it is and add an issue. The medium and high temperature split in the best case should be done per country and not based on an EU average. |
|
Data cross check with the Agora report
Currently, we have (including GB, Norway, CH)
|
|
Other sources to look at metis 3 study s5 |
I agree with @toniseibold that it is inconsistent, I'd suggest adding it as an issue in technology-data. In DEA there is also a condensing boiler option with higher efficiency, but it does not make much sense for industrial steam which is >150oC. Added an issue in technology data. |
|
Hi, actually I'm looking into using this (thanks as always to those that have put in the effort), but was wondering if this should be combined with a little bit of code in |
|
I will also quickly note that in the context of myopic foresight, I quickly ran into infeasibilities related to the Unsurpringly, there are some similarities to #960. Allowing the model to phase out and replace existing capacities at some cost might make sense (in order to guarantee feasibility at least). |
It looks to me like there is a significant discrepancy between the definitions used for low-, medium- and high-temperature heat between the Agora report and this PR. This PR would certainly benefit from clear definitions in terms of where the temperature-boundaries go between low / medium / high. If you look at the paper industry, for example, pypsa-eur currently (pre this PR) assumes a significant uptake of solid biomass energy demand towards 2050 as almost all heat required by this industry (>200TWh) is assumed to be supplied by biomass by then. In this PR, the biomass-supplied heating demand is translated to low-temperature heat. The way this Agora report is currently read implies an assumption that low-temperature heat is <100C. However, the same report implies that the vast majority of heat demand for the paper industry is between 100C and 200C (i.e. "medium heat"?). This confusion between low/medium heat also leads to a presumably unwanted result: the total demand for low-temperature heat goes up significantly as the planning horizon goes from 2020 to 2050 (as far as I can understand, a result of large fractions of heat demand in 2050 being assumed to be supplied by solid biomass initially in For more credible results, relative demands for low-, medium- and high-temperature should not change so much between 2020 and 2050. Probably what is needed is some work precisely in (Heat demand is already classified directly in I hope this all makes sense; I got sucked in to the topic a little bit while trying to understand industrial demand for heat and biomass better. It actually started because I noticed that pypsa-eur currently produces an infeasible model for "Low" ENSPRESO biomass scenario, because so much industrial biomass demand is hard-coded. I don't have all that much time to spend on this, but let me know if some suggestions in the form of code would be appreciated, and I might have a go at it. |
|
(On another note, the supplementary material to https://doi.org/10.1002/ente.202300981 also contains a very nice spreadsheet with process heat distributions (<100C, 100-200C, 200-500C, >1000C) that are "ready to go".) |
|
By the way, I found a couple of errors in the implementation with regards to CO2 management, which you can find in my "fork" of this branch: koen-vg@4e43daa |
In this PR, the temperatures start at 100C (originally termed steam, might be good to change back to avoid this confusion), so the Agora low temperature is not included. It was assumed electrified in build_industry_sector_ratios, so that demand exists elsewhere. The idea was that the current industrial biomass heat demand is dominated by steam generation (say in pulp/paper, food etc), at 100-200C. The exogenously set gas demand was split between medium (~200-500C) and high (>500C). Makes sense to adapt that split accd. to newer data for the current situation. For the future, some of the high temp demand was electrified too, for example EAFs, which is treated outside of this PR as well (so reduces the highT heat demand to be considered here, looking at the Agora data that is quite a chunk). |
|
Heya @lisazeyen @fneum, after an initial nudge from @Irieo I took up this PR, and aim to push it through while with the group. I wanted to make an initial proposition of what that could look like to discuss. What seems to be there looks quite strong already, but as @lisazeyen pointed out, the total heat demands (when compared to Agora) are maybe a bit too off for comfort (I suspect because only methane demand is interpreted as heat demand), and both @fneum and @koen-vg have suggested actually going into JRC for a more refined integration. Also, to prevent double counting with methanol, chlorine, ammonia, etc., it seems sensible to implement this already in the To get a feeling, I went through
This is a snippet of what the respective code looks like, just going through the very transparent and clear (This already highlights issues relating to which technology's efficiencies to use) Summing up, I would
We also have project partners in RESILIENT with perfect expertise to check some of the assumptions I would be making along the way, so I could rope them in. @fneum @lisazeyen @Irieo @koen-vg @millingermarkus I would be very keen to hear your thoughts about the plan, the less I hear the more I will be knocking on Fabian's door on a daily basis, he approved that >:) |
|
@LukasFrankenQ that sounds like a good plan! I think the main issue is the discrepancy with the demands in the different heat segments and the confusion with low temp heat (see my comment above), and improving that upstream of this PR is a good idea, since this problem is there also in the current version, and the endogenous industrial heat should be optional. Then one could also endogenise the choice of electrification, which is now hard coded in the build_industry scripts. Please beware of the steam demand (generally ~160-200C), which is not suitable to connect with urban central heat (at the moment "low temp" in this PR, but originally "steam", and not compatible with the low enthalpy heat demand). The <100, 100-200, 200-500 and >500 are suitable in my mind, but maybe a higher one is needed too (>1000 or so), and I have also played around with <120C steam which is easy to obtain with current heat pump technology and needed for S-DAC, but my impression is that industrial heat pumps are developing fast, so maybe the latter is redundant. I think some of the Resilient colleagues can inform this decision. |
|
Great that someone is picking this up :)
I'm a little confused by this; aren't the sector ratios used to prepare sector-coupled networks? It's a little indirect, but the I think the initial work you've done on directly classifying JRC heat energy demand by sector/use into explicit temperature ranges is great. At a high level, implementation-wise, is the idea to track heat at different temperature bands directly as distinct energy/fuel inputs in the industry sector ratios, along the same lines as electricity, coal, methane, etc.? I.e. where currently the rows of Do with this feedback what you want! |
|
@koen-vg , thank you, valid points! You are right about the ratios, I mixed up the scripts, good to see its used and deleted that part of the comment. Yes, that is the kind of indexing I am aiming for, however to the preserve the exogenous option, it might be best to make a multiindex like |
|
Something like that would certainly be an option. Just another few loose thought/considerations on this matter:
Anyway, you are the one who is spending time on this now and is doing the work of implementing it, so don't put too much weight on my thoughts :) |


PyPSA/pypsa-eur-sec#316