<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial MT Black";
panose-1:1 1 1 1 1 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>To follow up on the previous questions, I’ve wondered the
same thing – what if you want to assign multiple spaces to one zone in eQuest?
For example, two rooms are being supplied by the same VAV box. They need to be
created as two SPACES (on the “Building Shell” and “Internal Loads” tabs)
because of different internal loads, but then on the “Air-Side HVAC” tab, both
of the spaces need to be assigned to one ZONE. Is this possible?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial MT Black";
color:black'>KATIE L. M. TUTTLE</span><span style='font-size:8.0pt;font-family:
"Arial MT Black";color:black'> </span><span style='font-size:8.0pt;font-family:
"Arial","sans-serif";color:black'>EI, LEED<sup>®</sup> </span><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#566C11'>AP</span><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><br>
</span></b><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#566C11'>Mechanical Designer<br>
<br>
<img width=200 height=52 id="Picture_x0020_1"
src="cid:image001.gif@01CA935C.150D54F0"
alt="cid:image001.gif@01CA316F.E77202A0"><br>
<br>
<b>Henderson Engineers, Inc.</b></span><span style='font-size:9.0pt;font-family:
"Arial","sans-serif";color:black'> 8325 Lenexa Drive Lenexa,
KS 66214<br>
<b><span style='font-variant:small-caps'>dir</span></b> 913 742 5508 <b><span
style='font-variant:small-caps'>tel </span></b>913 742 5000 <b><span
style='font-variant:small-caps'>fax</span> </b>913 742 5001</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>
</span><b><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:#566C11'><a href="http://www.hei-eng.com/"><span style='color:#566C11'>www.hei-eng.com</span></a><o:p></o:p></span></b></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] On Behalf Of James Hansen<br>
Sent: Tuesday, January 12, 2010 6:31 AM<br>
To: omoltay@mimtarch.com; equest-users@lists.onebuilding.org<br>
Subject: Re: [Equest-users] Walls and Zones<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Instead of deleting interior walls, why not just convert
them do a different type? If I have a large open office with multiple zones,
I'll just set up all interior walls to be of type "Air".<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Here are the available wall types from the help file:<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>INT-WALL-TYPE<o:p></o:p></p>
<p class=MsoPlainText>Specifies the type of interior wall through code-words
that identify the type of heat transfer that occurs across the wall.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>STANDARD <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The default. Designates an interior wall that separates
two spaces and conducts heat between the spaces. It can be defined with a
CONSTRUCTION with TYPE=U-VALUE or TYPE=LAYERS although the heat storage effects
of the wall are accounted for only if TYPE=LAYERS. If you choose a CONSTRUCTION
with TYPE=U-VALUE, the U-value should be less than 0.709 Btu/ft2-F-hr (4.02
W/m2-K), which is the limiting value for two air films and a very low
resistance solid layer. The NEXT-TO keyword is required for this wall type.
However, if the NEXT-TO space is the same as the space in which the wall was
defined, the program will change INT-WALL-TYPE to ADIABATIC.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>ADIABATIC <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Designates an interior surface that does not conduct heat
between spaces but can store heat. This type should be used to separate spaces
that are considered to be identical and are, therefore, defined with MULTIPLIER
or FLOOR-MULTIPLIER in the SPACE command. An example is the wall, ceiling, or
floor that separates identical spaces that are side-by-side on one floor of a
building or above one another in a multistory building. This type of wall
should have delayed construction.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>INTERNAL <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Designates an interior surface that lies completely
inside a space. An example is a water wall used to store solar energy in a
space. Another example is a wall between two rooms that are modeled as a single
space. This type of wall should have a construction with TYPE=LAYERS; in this
case the thermal mass of the wall will be considered in the space's custom
weighting factor calculation<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>AIR <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Designates a non-physical interior surface with no mass
(i.e., an opening between spaces) across which convection can take place. This
type of wall should have a CONSTRUCTION with TYPE=U-VALUE. In this case, we
recommend an approximate U-value of 2.7 Btu/ft2-hr (15.3 W/m2). The NEXT-TO
keyword is required for this wall type.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>If the "AIR wall" is part of a daylit space,
its INSIDE-VIS-REFL values need to be specified (even though it is not a
physical wall) since daylight can be reflected back across the AIR wall from
the adjacent space. The values to use for INSIDE-VIS-REFL in this case are
determined as follows. Assume that the AIR wall, of area A, is defined in space
1 and separates space 1 and space 2. Let the spaces have inside surface area Si
(excluding the AIR wall) and area-weighted visible reflectance ri excluding the
AIR wall). Then INSIDE-VIS-REFL=(R2 , R1) where Ri is the cavity reflectance of
space i given by<o:p></o:p></p>
<p class=MsoPlainText> Ri = A * ri / (Si - (Si -A)*rI)<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>GHT Limited<o:p></o:p></p>
<p class=MsoPlainText>James Hansen, PE, LEED AP<o:p></o:p></p>
<p class=MsoPlainText>Senior Associate<o:p></o:p></p>
<p class=MsoPlainText>1010 N. Glebe Rd, Suite 200<o:p></o:p></p>
<p class=MsoPlainText>Arlington, VA 22201-4749<o:p></o:p></p>
<p class=MsoPlainText>703-338-5754 (Cell)<o:p></o:p></p>
<p class=MsoPlainText>703-243-1200 (Office)<o:p></o:p></p>
<p class=MsoPlainText>703-276-1376 (Fax)<o:p></o:p></p>
<p class=MsoPlainText>www.ghtltd.com<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>From: equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] On Behalf Of
omoltay@mimtarch.com<o:p></o:p></p>
<p class=MsoPlainText>Sent: Monday, January 11, 2010 6:54 PM<o:p></o:p></p>
<p class=MsoPlainText>To: equest-users@lists.onebuilding.org<o:p></o:p></p>
<p class=MsoPlainText>Subject: [Equest-users] Walls and Zones<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Dear all,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I have not received a reply to my previous question, so
here is a<o:p></o:p></p>
<p class=MsoPlainText>simplified version of it: I see that everytime I create a
zone in the<o:p></o:p></p>
<p class=MsoPlainText>Wizards, eQuest builds walls around these zones. Does
every zone (or every<o:p></o:p></p>
<p class=MsoPlainText>space) need to have walls around? Would it be a problem
if I delete these<o:p></o:p></p>
<p class=MsoPlainText>walls afterwards?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>For example, when I have a large open office, I would
like to have several<o:p></o:p></p>
<p class=MsoPlainText>zones. So after the Wizard creates the building
description, I have to<o:p></o:p></p>
<p class=MsoPlainText>delete all the walls around these zones.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Is this normal procedure?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Omer Moltay, LEED AP<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>_______________________________________________<o:p></o:p></p>
<p class=MsoPlainText>Equest-users mailing list<o:p></o:p></p>
<p class=MsoPlainText>http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org<o:p></o:p></p>
<p class=MsoPlainText>To unsubscribe from this mailing list send a blank
message to EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The information contained in this communication is
confidential, may be privileged, and is intended only for the use of the
addressee. It is the property of GHT Limited. Unauthorized use, disclosure or
copying of this communication or any part thereof is strictly prohibited and
may be unlawful. If you have received this communication in error, please
notify me immediately by return e-mail or by e-mail to ght@ghtltd.com, and
destroy this communication and all copies thereof, including all attachments.
Thank you.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>_______________________________________________<o:p></o:p></p>
<p class=MsoPlainText>Equest-users mailing list<o:p></o:p></p>
<p class=MsoPlainText>http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org<o:p></o:p></p>
<p class=MsoPlainText>To unsubscribe from this mailing list send a blank
message to EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG<o:p></o:p></p>
</div>
<pre>
This email and any files transmitted with it are confidential and
are intended solely for the use of the individual or entity to whom
they are addressed. This communication represents the originator's
personal views and opinions, which do not necessarily reflect those of
Henderson Engineers, Inc. If you are not the original recipient or the
person responsible for delivering the email to the intended recipient,
be advised that you have received this email in error, and that any use,
dissemination, forwarding, printing, or copying of this email is strictly
prohibited. If you received this email in error, please immediately
notify administrator@hei-eng.com.
</pre></body>
</html>