Open jrissman opened 1 year ago
Thanks for this.
Intuitively, it makes sense. There are at least two issues I see with the proposed approach though:
The desire for cofiring in the model is actually less about historical plant types, where cofiring is mainly about oil and gas, and more about compliance options in the future, FWIW.
Anyway, maybe we don't need to tackle this right now, but I'd like to have a longer conversation about it at some point, and I don't think the proposed structure here is quite right.
From: Jeff Rissman @.> Sent: Tuesday, June 13, 2023 2:27 PM To: EnergyInnovation/eps-us @.> Cc: Subscribed @.***> Subject: [EnergyInnovation/eps-us] Handle power plant co-firing and fuel shifting (Issue #278)
Megan and I discussed the most tractable approach to handle co-firing (plants using different fuel types, such as a start-up fuel and a main fuel, or splitting their generation between two fuels). This generally involves using different equipment (i.e., a fluidized bed coal unit and accompanying natural gas equipment), which can have different efficiencies, emissions profiles, etc. We can't just divide up fuel types at the end (i.e., the "hard coal" plants across the fleet are burning 97% coal and 3% natural gas) because this wouldn't reflect the different heat rates and other properties of the fuels used.
The approach we thought of is along these lines:
Optionally, if we have time:
We had fuel shifting before (where it was added to help model KSA plants shifting between crude oil and heavy fuel oil based on the prices of those fuels), so we had planned to re-implement it anyway. Co-firing just gives that capability more relevance in more geographies.
Retrofitting (like a coal-to-gas retrofit, or a non-CCS-gas to gas-with-CCS retrofit) would be handled in a separate "Retrofitting" section of the code, which would update vintage. Retrofitting should not be commingled with fuel shifting in the model structure; they should be two separate, small mechanisms.
- Reply to this email directly, view it on GitHubhttps://github.com/EnergyInnovation/eps-us/issues/278, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK5N6SIGVGP56UNJECTY7L3XLDLL5ANCNFSM6AAAAAAZFOSQTU. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>
Megan and I discussed the most tractable approach to handle co-firing (plants using different fuel types, such as a start-up fuel and a main fuel, or splitting their generation between two fuels). This generally involves using different equipment (i.e., a fluidized bed coal unit and accompanying natural gas equipment), which can have different efficiencies, emissions profiles, etc. We can't just divide up fuel types at the end (i.e., the "hard coal" plants across the fleet are burning 97% coal and 3% natural gas) because this wouldn't reflect the different heat rates and other properties of the fuels used.
The approach we thought of is along these lines:
BHRaSYC Start Year Capacity
.MPPC Minimum Power Plant Capacity
, which we use to quantize new additions and retirements, to a small value like 1 MW or 0.01 MW for any fuel types that can be used for co-firing. This ensures the quantization doesn't interfere with the ability to build or retire plants that use co-firing.Optionally, if we have time:
We had fuel shifting before (where it was added to help model KSA plants shifting between crude oil and heavy fuel oil based on the prices of those fuels), so we had planned to re-implement it anyway. Co-firing just gives that capability more relevance in more geographies.
Retrofitting (like a coal-to-gas retrofit, or a non-CCS-gas to gas-with-CCS retrofit) would be handled in a separate "Retrofitting" section of the code, which would update vintage. Retrofitting should not be commingled with fuel shifting in the model structure; they should be two separate, small mechanisms.