4

One-time peak demand tariff calculation

I am analyzing a building for which the electricity demand tariff is calculated only based on the one-time highest monthly peak calculated over 15 min intervals. It is my understanding that the "Demand Window Length" specified in the tariff object counts every single one of the peak occurrences exceeding that window which is way higher than what a one-time demand charge would be. Is there a way to force the tariff to only calculated the peak demand for a one-time monthly occurrence?

Also, based on this post it looks like there is no way to get hourly data out of E+. I need that hourly data to:

  1. Potentially adjust the demand window length to different values and check which one comes closer to the one-time peak demand calculations

  2. Visualize the hourly data for the client since the project has weird schedules which is not possible with only the monthly tariff calc outputs E+ spits out.

Any thoughts?

Amir Rezaei's avatar
841
Amir Rezaei
asked 2016-09-13 08:38:31 -0500
__AmirRoth__'s avatar
4.4k
__AmirRoth__
updated 2017-04-16 14:56:38 -0500
edit flag offensive 0 remove flag close merge delete

Comments

@JasonGlazer and @David Goldwasser, I know you both have posted about this before. Any suggestions on how to effectively get that hourly data out?

Amir Rezaei's avatar Amir Rezaei (2016-09-13 08:39:45 -0500) edit
1

could you use:

UtilityCost:Charge:Simple,
    Annual Demand,           !- Name
    Annual Tariff,           !- Tariff Name
    totalDemand,             !- Source Variable
    Annual,                  !- Season
    DemandCharges,           !- Category Variable Name
    $/kW;                    !- Cost per Unit Value or Variable Name
MatthewSteen's avatar MatthewSteen (2016-09-13 10:20:44 -0500) edit
1

with:

UtilityCost:Tariff,
    Annual Tariff,           !- Name
    Electricity:Facility,    !- Output Meter Name
    kWh,                     !- Conversion Factor Choice
    ,                        !- Energy Conversion Factor
    ,                        !- Demand Conversion Factor
    ,                        !- Time of Use Period Schedule Name
    ,                        !- Season Schedule Name
    ,                        !- Month Schedule Name
    QuarterHour;             !- Demand Window Length
MatthewSteen's avatar MatthewSteen (2016-09-13 10:22:10 -0500) edit

Thanks @MatthewSteen.

Amir Rezaei's avatar Amir Rezaei (2016-09-13 13:09:16 -0500) edit
add a comment see more comments

1 Answer

3

I think setting the Demand Window Length to QuarterHour is exactly what you are looking for. It takes the highest quarter hour for the month and uses that for the demand computation in the UtilityCost:Tariff object. Please be aware that the timestep set in in TimeStep object should be 4 or 12.

There currently is no way to get hourly energy costs from the UtilityCost:Tariff object. If you would like to see that added you can vote for it here.

If you are just looking for hourly electrical energy or demand data, that is available. See the Electricity:Facility meter.

JasonGlazer's avatar
6.8k
JasonGlazer
answered 2016-09-13 11:10:01 -0500
edit flag offensive 0 remove flag delete link

Comments

Thanks for confirming my thoughts, originally I thought the object adds up all the occurrences of the demand exceeding the window but now I realize it only picks the one that has the highest peak demand which is exactly what I needed. Voted for the new feature to be added.

Amir Rezaei's avatar Amir Rezaei (2016-09-13 13:08:52 -0500) edit
add a comment see more comments