IES-VE User Forum

I do not; someone else might though.

No prob.

I'm unsure if this behaviour is 'by-design' or not. My guess is not so we have some investigation to do. In the meantime, I suggest using the additional pump 'meters' to help track your energy and run multiple sims with the different pumps. Then manually export the energy data in VistaPro ...

In the CHW loop dialog, go to 'Primary Loop'; hit the dropdown menu from 'Single Pump' to 'Dedicated Chiller Pumps'.

This will allow you access to three unique pumps. So long as you have sequenced the chillers correctly, the pumps should engage more sequentially.

There's a XLS for editing Pump ...

TLDR: In a coil-then-fan (draw-through) AHU configuration, the BIAS controller is a dT sensor that measures the heat pickup from a Fan, then asks the coil to account for it; thus achieving the target leaving temperature.

https://imgur.com/a/n0YVGDF
https://imgur.com/a/n0YVGDF
https://imgur.com ...

I would use the "Edit Multiple Adjacenies" button in Apache to assign an adjacent temperature. You would need to create the temp profile first in Apache Profiles.

I'm trying to figure out how to add images here... to share this useful feature. I hope this works:

Phil - aland82 now already knows the following, but for the sake of the forum;

IES are 100% up to date with the requirements of the performance approach of Title 24 Compliance, this approach requires software .
The additional reports required by a local plan-checker are not part of the performance ...

Ben - you're workflow is correct (using the spreadsheet). Maintaining the raw gbXML throughout might actually slow you down afterwards.
Generally my recommendation (as is from others in your company) is to strip all the thermal data out and paste in the relevant pieces (e.g. LPDs) afterwards.
Liam