Closed Kirktj closed 9 years ago
Good questions.
1a. Demand charges are calculated per month, so the algorithm attempts to shave the highest peaks in the month. We're pretty sure the charge/discharge cycle is optimal. Example of peaks you see that aren't shaved? 1b. We only do arbitrage currently from a distribution utility perspective. What other value streams would you like to see?
@delysis might have other details.
1b. From the ES toolkit: "Although each case is unique, if a plant used for electric energy time-shift is in the right location and if it is discharged at the right times, it could also serve the following applications: electric supply capacity, T&D upgrade deferral, transmission congestion relief, electric service reliability, electric service power quality, and ancillary services."
2a/5. I didn't phrase this well. Depending on what battery you use the cycle life will vary depending on the DoD of each cycle. Ideally the algorithm managing the charge/discharge cycle would factor in the SoC if necessary and model could predict the battery's useful life based on cycle life, not just financial projection length since some load profiles will result in more cycles than others.
Thanks for the follow up.
1a. We need to see the timescale for that graph. Without the timescale the behavior could be correct or not--it's impossible to know. The algorithm is in the source code at /omf/omf/models/energyStorage.py. 1b. We're considering these other value streams. How to monetize them and stack them is a huge research question. 2a. What qualifies as a cycle for a given battery is a huge research question.
Looking at it my guess is that because it's in the same month as the other peak it's not the highest?
Yes, correct.
I'm going to close this and create a generic energyStorage issue where we can track other things.
First Impression questions: