Storage processes in peaking constraints
Indeed, in TIMES you can only have a single capacity for each process.

As my example shows, however, the energetic storage capacity (energy units) is not the only parameter of importance for storage facilities and the maximal power in/out of the storage should also be taken into account. So for a reasonable modeling of storage devices, the energetic capacity as well as the 'flow rate capacity' should be taken into account.

This has some consequences (assuming the storage is modeled following the convention that capacity corresponds to the energetic storage size):
1) Additional equations need to be set up by the user to limit the flow rates to realistic values
2) When determining the storage contribution to delivering the peak (NCAP_PKCNT), one would need to check whether it is the energy aspect or the power aspect, that limits the contribution of the storage (see the example in the previous reply), and the user has to calculate this NCAP_PKCNT by hand, taking these things into account.

So for me, it seems reasonable to make some changes in the modeling part of storage devices, which would allow having an energetic storage capacity as well as a 'flow rate capacity'. When these parameters would be entered by the user, ideally TIMES would automatically take care of both issues (1) and 2)). 

Messages In This Thread
Storage processes in peaking constraints - by Poncelet_K - 20-01-2014, 05:09 AM

Forum Jump:

Users browsing this thread: 1 Guest(s)