Unconditioned spaces and Space ZONE-TYPE vs. Zone TYPE

3 posts / 0 new
Last post

I just noticed that the space ZONE-TYPE can be different than the
corresponding zone TYPE. For example, EL2 Core Spc (G.C7) has ZONE-TYPE
"Conditioned" while EL2 Core Zn (G.C7) has TYPE-ZONE "Unconditioned".
The program/model doesn't seem to have a problem with this and runs
fine. Is this a deliberate capability intended by the DOE2.2/eQUEST
programmers? Perhaps this is done to allow space loads (lighting,
equipment etc.) to show up in the loads reports (LS-C, LS-D, LS-F) but
not be transferred to systems? Hmm.

William Bishop, PE, BEMP, LEED(r) AP

Bishop, Bill2's picture
Offline
Joined: 2011-09-30
Reputation: 0

I have noticed that and not knowing what the impact of it is I always make
them the same.

Carol

cmg750's picture
Offline
Joined: 2010-10-05
Reputation: 0

In my experience when you run a compliance simulation such as T24
compliance, the two must be the same (both listed as conditioned or both
as unconditioned), otherwise you will receive a warning and eQuest will
automatically default your TYPE-ZONE to match what your ZONE-TYPE (or
vice versa, I don't remember).

-Nilay

Nilay R. Desai's picture
Offline
Joined: 2011-09-30
Reputation: 0