[Equest-users] Interpreting SIM reports - CHW plant improvements

Thu Jun 13 12:00:03 PDT 2019

Once you convert to DOE-2.3, you have additional sizing options and other CHW plant improvements. For example:

  *   For SIZING-OPTION, you can choose the COINCIDENT (simultaneous) peak load of all attached coils, or the NON-COINCIDENT total of all peak coil loads. (Or PRIMARY based on the attached equipment capacities.)
  *   The SIZING-WINDOW specifies how design-days are treated.
  *   You can specify the design LOOP-FLOW (gpm) if already known.
  *   You can specify the RATED-EDB and RATED-EWB for the corresponding coil ZONE:COOLING-CAPACITY.
  *   You can specify a STARTUP-COOL-DT that sizes the cooling coil based on the space temperature reduction you have to achieve per hour of operation.

~Bill

William Bishop, PE, BEMP, BEAP, CEM, LEED AP
Senior Energy Engineer

[Pathfinder-EA-logo-2]T: (585) 698-1956                        F: (585) 325-6005
bbishop at pathfinder-ea.com<mailto:wbishop at pathfinder-ea.com>        www.pathfinder-ea.com<http://www.pathfinder-ea.com/>
134 South Fitzhugh Street
Rochester, NY 14608               [cid:image005.png at 01D521F6.1AF7DA60]         Ask me why Carbon Fee & Dividend may be right for you.

From: Equest-users <equest-users-bounces at lists.onebuilding.org> On Behalf Of Erik Kolderup via Equest-users
Sent: Thursday, June 13, 2019 2:08 PM
To: Nicholas Caton <Nicholas.Caton at se.com>
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Interpreting SIM reports

Hi, Nick.

I think that the capacity of the cooling loop will be based on the sum of the capacities of cooling coils connected to the loop, assuming the sizing option for the loop is "secondary" rather than "primary". If you look at the SV-A report and sum up capacity of all the cooling coils, does that get you to 13 MBtu/hr? If you want the loop sized based on chiller size, then the sizing option for the loop should be "primary".

-Erik

Erik Kolderup, PE, LEED AP
erik at kolderupconsulting.com<mailto:erik at kolderupconsulting.com> | 415.531.5198 | www.kolderupconsulting.com<http://www.kolderupconsulting.com>

On Thu, Jun 13, 2019 at 11:02 AM Nicholas Caton via Equest-users <equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>> wrote:
Hi everyone,

Can anyone help me assert or correct my understanding on something?  This is from a model built in v3.65, b7175, doe2.2 engine (with intent to upconvert the project to doe2.3 before I’m done).

Report PV-A lists the capacity for each heating/cooling loop.  Here I’m cropping to just the loops, and highlighting what I’m used to thinking of as the “peak” coincident capacity requirement for a chilled water loop – 13.909 MMBtu/hr (that’s millions):

[cid:image006.jpg at 01D521F6.1AF7DA60]

The following reports PS-H go into more detail on each item listed in PV-A.  Here is the report for the same “Chilled Water Loop,” with a coule more highlights:

[cid:image007.png at 01D521F6.1AF7DA60]

Immediately, I note that 13.909 MMBtu/hr (1,159 tons) aligns with PV-A, however I do not see that number matching (intuitively) any of the other figures or sums provided on this sheet.  The figure 5,625.126 kBtu/hr (469 tons) aligns with my expectations for peak load on the loop, where nominal capacity of the associated chillers on this loop are in the same ballpark (one is 444 tons and one is 210 tons on paper & @ design conditions, and I’m told they commonly do not need to engage the smaller chiller during the dead of summer).

Can anyone help me reconcile the differences between what’s reported as “Cooling Capacity” in PV-A, in relation to the annual peak loads indicated for the same loop in the PS-H report?

Thanks!

~Nick

[cid:image005.png at 01D515A3.47EDD880]
Nick Caton, P.E., BEMP
  Senior Energy Engineer
  Regional Energy Engineering Manager
  Energy and Sustainability Services
  Energy Performance Contracting

D
M
F
E

913 . 564 . 6361
785 . 410 . 3317
913 . 564 . 6380
nicholas.caton at se.com<mailto:nicholas.caton at se.com>

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[cid:image006.png at 01D515A3.47EDD880]

_______________________________________________
Equest-users mailing list
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
To unsubscribe from this mailing list send  a blank message to EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG<mailto:EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 9336 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1554 bytes
Desc: image005.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 44782 bytes
Desc: image006.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 306303 bytes
Desc: image007.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 255 bytes
Desc: image008.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 8477 bytes
Desc: image009.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 1903 bytes
Desc: image010.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190613/37e3499b/attachment-0011.jpg>