[Equest-users] Multi-Zone Spaces (Atria) and Open to Below

[Tom Butler]

I've found this blog entry from Brandon Nichols to be helpful.

http://elcca-exchange.blogspot.com/2007/03/equest-multi-level-spaces.html

tb

From: Berke Çelikel [mailto:berkecelikel at erketasarim.com]
Sent: Saturday, October 23, 2010 2:48 AM
To: 'Aman Hehar'; equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Multi-Zone Spaces (Atria) and Open to Below

Hi Aman,
I have the same problem, I have tried almost everything but it did not work. If anybody can help about this subject please let me now also.
I will be really appreciated.

Berke

From: Aman Hehar [mailto:AHehar at morrisonhershfield.com]
Sent: Friday, October 22, 2010 7:56 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Multi-Zone Spaces (Atria) and Open to Below

Hello All,

I need clarification on a 3 story building I am attempting to model in eQUEST.

Basically, there are a few zones that are open to below (first floor opens all the way up to the third floor).  The way I currently have the building modelled in the DD wizard is that each individual floor is modelled as its own shell.

I see the options for "Multi-Level Zone (atrium) and "Open to Below" in the "Zone Names and Characteristics" window of the Shell Component DD wizard.  However, the notes in the help files are ambiguous.

For the zones that are open to below, should I do the following:

-Set the zone on the ground floor as Multi-Level Zone (Atrium)
-Set the zones on the second and third floor as Open to Below

The above does not seem to give me the expected results.  I have also tried setting the zones on the second and third floor as "Open to Below" and "Multi-Level Zone (atrium)".  That seems to work, but I am missing the roof component on the third floor.

Any help would be appreciated.

Thanks,

Aman



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20101025/5a2ec7f0/attachment-0002.htm>