<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Juan,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you model the balconies as window overhangs, and you don’t have a ton of unique balcony footprints, it isn’t terribly labor-intensive to address, particularly if you pick this up during the wizards. Attached
are a few past discussions / illustrations covering that strategy further.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Circumstances allowing, it *might* be easier/quicker to approximate the balconies along any given orientation as a series of building shades, but in most cases I think you’ll find it less time consuming to check
out the window fin/overhang inputs first.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you should have any “exterior” lighting/fans/outlets/etc. to model at those balconies, you can either include those inputs inside the apartments or define them as exterior loads on the meter.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">~Nick<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:JA"><img width="119" height="37" id="Picture_x0020_1" src="cid:image002.jpg@01CE9DC8.B3C7AA30" alt="cid:489575314@22072009-0ABB"></span><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E;mso-fareast-language:JA"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E;mso-fareast-language:JA"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E;mso-fareast-language:JA">NICK CATON, P.E.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900;mso-fareast-language:JA">SENIOR ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900;mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E;mso-fareast-language:JA">Smith & Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900;mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E;mso-fareast-language:JA">25501 west valley parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E;mso-fareast-language:JA">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E;mso-fareast-language:JA">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E;mso-fareast-language:JA">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:JA"><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style="font-size:10.0pt;color:blue">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue;mso-fareast-language:JA">
</span></u><span style="color:#1F497D;mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:JA">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:JA"> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Juan Carlos Lopez<br>
<b>Sent:</b> Tuesday, August 20, 2013 4:13 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Balconies in Multifamily High Rise Building<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="ES-MX">Hello<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX"><o:p> </o:p></span></p>
<p class="MsoNormal">I’m modeling a 14 floor Multifamily High Rise building, but It has to have Balconies in the façade, there are 4 departments per floor oriented in west and east facades, the balcony must be in the living room and master suit too, my question
is: Do I have to model balcony per balcony in each department and floor? Because if it is the case, there will be like 60 balcony.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there any way to model the balconies in group, instead of do it as a fixed shape separately?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks in advance
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif";color:#5B655E;mso-fareast-language:ES-MX">Juan Carlos López<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="ES-MX" style="font-size:10.0pt;color:#15345B;mso-fareast-language:ES-MX"><img border="0" width="77" height="57" id="Imagen_x0020_1" src="cid:image003.png@01CE9DC8.B3C7AA30" alt="ibe"></span></b><span lang="ES-MX" style="mso-fareast-language:ES-MX"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX"> <o:p></o:p></span></p>
</div>
</body>
</html>