<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 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:Complex;
panose-1:0 0 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:"Arial","sans-serif";
color:windowtext;}
span.emailstyle21
{mso-style-name:emailstyle21;
font-family:"Arial","sans-serif";
color:navy;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle210
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1509321074;
mso-list-type:hybrid;
mso-list-template-ids:348151114 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regarding the modeling of water-cooled chillers, chilled water
loops, and HVAC systems in IES <Virtual Environment>:<o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In response to user demand, IES is expanding the capability for
HVAC systems modeling within IES <Virtual Environment> to more thoroughly
represent both conventional and unconventional HVAC systems. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>While not yet publically released or announced, in-depth
capability for modeling water-cooled chillers and chilled water loops within
the IES <Virtual Environment> ApacheHVAC application has been developed
and implemented. This capability is presently undergoing testing and will be
available in the next release later this spring. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The new water-cooled chiller model is described by three performance
curves: <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>varies cooling capacity with entering condenser water
temperature<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>varies electric input ratio (EIR) with chilled water temperature<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>varies electric input ratio (EIR) with part-load fraction. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>These scalable performance curves are pre-defined for common
chiller types: screw; centrifugal (hermetic, with or without VSD, and open);
and reciprocating (hermetic and open). Where water flow is variable, performance
curves are provided for pumps. These include constant-speed/variable-flow “riding
the pump curve” and electronically commutated variable speed. For expert
users, parameter values are editable in the equations describing the
performance curves for chillers and pumps. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In addition to selecting appropriate performance curves, the
user is able to specify interconnected performance inputs for capacity, COP,
condenser and chilled water temperatures, flow rates, and loop delta-T at both rated
and design conditions. An input is provided for the load fraction below which
the chiller will cycle on and off. The user also has control of operating
parameters such as condenser-water setpoint and variation of this setpoint via a
formula profile (which may reference outdoor or indoor conditions and other
sensed variables), chilled supply water temperature (SWT), and ramped SWT reset
between high and low outdoor temperature setpoints. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The cooling tower and condenser-water loop use essentially the same
cooling tower model that is provided for the waterside economizer component in
the current version of ApacheHVAC. The cooling tower model presently includes a
two-speed fan with flow fraction setting for each speed, approach, range, and
electric input ratio. This tower and condenser-water loop model accounts for changes
in outdoor conditions, chiller heat rejection, and user-controlled tower operating
parameters as described above. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Primary and secondary chilled water loops are modeled for the
first release of this new facility in a PRM-compliant “common pipe”
configuration. For this configuration, the primary loop uses a constant-speed
pump that operates whenever the chiller is running and the secondary loop with
flow controlled to maintain the specified CHW supply temperature and loop
delta-T. Either a constant-speed/variable-flow pump riding the pump curve or a
variable-speed pump with variable speed drive (VSD) can be specified for the secondary
(chilled-water distribution) loop. Cooling coils, chilled ceilings, etc. are
then assigned to the secondary loop associated with a particular chiller.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The currently available release of the VE uses a simpler model
that does provide means of describing the performance of a water-cooled chiller,
cooling tower, and pumps in relation to both part-load fraction and outdoor
wet-bulb or dry-bulb temperatures. This is presently done via a matrix of user
input data points for the chiller COP, condenser-water pump power, cooling
tower fan power, and chilled-water pump power. With appropriate inputs, the
chiller COP in this simpler exiting model can be thus be varied according to
both load fraction and outdoor conditions, while the power for the associated pumps
and fans can separately be varied according to load fraction. However, because
this simpler model does not use the type of curves that many EnergyPlus and
DOE-2 users are accustomed to and does not explicitly model the thermodynamics
of the CW, primary CHW, and secondary CHW loops or their controls, the new facilities
described above have been developed to do just this.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It is worth noting that the USGBC generally supports the
selection of the simulation tool that will most accurately represent what the
user is attempting to model, while also suitably addressing the 90.1 PRM requirements
for the baseline model. This requires a degree of professional judgment and USGBC
approval is on a case-by-case basis. For example, one might be attempting to
model a novel air handler configuration, such as a DOAS with indirect
evaporative cooling, DX dehumidification, and a desiccant wheel regenerated by waste
heat from the DX condenser coil, in a building that uses passive chilled beams fed
by a water-cooled chiller. In such a case, it may be that the benefits of added
detail in modeling the air handler configuration, desiccant wheel, and the
combined radiant and convective effects of the passive chilled beams would
outweigh certain limitations with respect to other aspects of the system, such
as chiller sequencing. Similar professional judgment may need to be exercised to
appropriately account for heat transfer mechanisms and system dynamics when
modeling a UFAD system, displacement ventilation, double-skin façade, earth
tube pre-conditioning, natural ventilation, mixed-mode operation, or highly
customized controls. Ultimately the energy modeler has to make an informed
selection of the most appropriate tool for the project at hand. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Finally, with regard to the “One Model” topic that
started this Bldg-Sim thread, the IES <Virtual Environment> is intended to
address the need for an interdisciplinary range of technical analyses within a
single, integrated model. In part, this is provided through interoperability
with other tools, such as SketchUp, Revit, and other BIMs, thus minimizing and
potentially eliminating the need for preparing a separate 3D model. The
<VE> also includes a range of applications, several of which were
described by users earlier in this thread, for integrated analysis of solar
shading, daylight modeling, daylighting controls, thermal mass and dynamic load
calculations, natural ventilation, thermal comfort, airflow, IAQ, conventional HVAC
systems, building-integrated HVAC systems, etc. The <VE> provides a range
of tools for analysis appropriate to each stage of the design process, facilitating
both quick, early reduction of building loads followed by detailed
investigation of technical opportunities. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hopefully this helps to clarify the capabilities of the VE for
those concerned specifically with modeling HVAC systems and more generally with
the “one-model” approach.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left
width=553 style='width:331.5pt;border-collapse:collapse;margin-left:.45pt;
margin-right:.45pt;margin-bottom:8.2pt'>
<tr style='page-break-inside:avoid'>
<td width=83 valign=top style='width:49.5pt;padding:.7pt .7pt .7pt .7pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:115%;mso-element:frame;mso-element-frame-hspace:2.25pt;
mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:
column;mso-element-left:-4.5pt;mso-height-rule:exactly'><!--[if gte vml 1]><o:wrapblock><v:shapetype
id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t"
path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="Picture_x0020_2" o:spid="_x0000_s1026" type="#_x0000_t75"
alt="IES logo CMYK" style='position:absolute;margin-left:-2.55pt;
margin-top:-43.5pt;width:44.7pt;height:43.2pt;z-index:1;visibility:visible;
mso-wrap-style:square;mso-wrap-distance-left:9pt;mso-wrap-distance-top:0;
mso-wrap-distance-right:9pt;mso-wrap-distance-bottom:0;
mso-position-horizontal:absolute;mso-position-horizontal-relative:text;
mso-position-vertical:absolute;mso-position-vertical-relative:text'>
<v:imagedata src="cid:image001.jpg@01C9ABF7.9FBB3DD0" o:title="IES logo CMYK" />
<w:wrap type="topAndBottom"/>
</v:shape><![endif]--><![if !vml]><span style='mso-ignore:vglayout;
position:relative;z-index:1;left:-3px;top:0px;width:60px;height:58px'><img
width=60 height=58 src="cid:image003.jpg@01C9AC15.07041AD0"
alt="IES logo CMYK" v:shapes="Picture_x0020_2"></span><![endif]><!--[if gte vml 1]></o:wrapblock><![endif]--><br
style='mso-ignore:vglayout' clear=ALL>
<b><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></b></p>
</td>
<td width=188 valign=top style='width:112.5pt;padding:.7pt .7pt .7pt .7pt'>
<p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:2.25pt;
mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:
column;mso-element-left:-4.5pt;mso-height-rule:exactly'><b><span
style='font-size:13.0pt;font-family:"Calibri","sans-serif";color:navy'>Timothy
Moore <br>
</span></b><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:navy'>Senior Consultant<br>
Special Projects <o:p></o:p></span></b></p>
</td>
<td width=283 valign=top style='width:169.5pt;padding:.7pt .7pt .7pt .7pt'>
<p class=MsoNormal style='margin-top:3.0pt;mso-element:frame;mso-element-frame-hspace:
2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;
mso-element-anchor-horizontal:column;mso-element-left:-4.5pt;mso-height-rule:
exactly'><span style='font-size:8.0pt;font-family:"Calibri","sans-serif";
color:navy'>Office: 415 983-0603<br>
<u><a href="mailto:timothy.moore@iesve.com"><span style='color:navy'>timothy.moore@iesve.com</span></a></u><br>
</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.iesve.com/"><span style='font-size:8.0pt;color:navy'>www.iesve.com
</span></a></span><span style='font-size:8.0pt;font-family:"Calibri","sans-serif";
color:navy'><br>
<br>
<o:p></o:p></span></p>
</td>
</tr>
<tr style='page-break-inside:avoid'>
<td width=553 colspan=3 valign=top style='width:331.5pt;padding:.7pt .7pt .7pt .7pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:115%;mso-element:frame;mso-element-frame-hspace:2.25pt;
mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:
column;mso-element-left:-4.5pt;mso-height-rule:exactly'><span
style='font-size:8.0pt;line-height:115%;font-family:"Calibri","sans-serif";
color:navy'>**Design, Simulate + Innovate with the <Virtual
Environment>**</span><span style='font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
</td>
</tr>
<tr style='page-break-inside:avoid'>
<td width=553 colspan=3 valign=top style='width:331.5pt;padding:.7pt .7pt .7pt .7pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:115%;mso-element:frame;mso-element-frame-hspace:2.25pt;
mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:
column;mso-element-left:-4.5pt;mso-height-rule:exactly'><span
style='font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.iesve.com/disclaimer.html"><span style='font-size:8.0pt;
line-height:115%;color:navy'>Email Disclaimer</span></a><o:p></o:p></span></p>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Marcus
Sheffer<br>
<b>Sent:</b> Thursday, March 19, 2009 7:01 AM<br>
<b>To:</b> 'm.lebourhis'; bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] [SPAM] Re: One model<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>USGBC does allow calculations outside the model for end uses
which do not impact other end uses such as exterior lighting or domestic hot
water. If the cooling central plant can be completely isolated and you
can demonstrate that the loads placed on it are exactly the same in both models
then it may be allowed. In order to do this with a high degree of accuracy
you may have to build virtually the same model in both versions of the
software. You would also need to very thoroughly explain your modeling
procedures and calculations. By the time you did all that my guess is
that you would be better off just submitting the whole model in eQUEST instead
of justifying the combination.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So as a LEED reviewer I would be highly skeptical of the
scenario you suggest and would likely scrutinize it to a significantly higher
degree compared to all calculations in one model. As I understand it
IES-VE does not yet model water cooled systems very well so I might suggest
that it is simply not an appropriate modeling tool to use for this particular
project.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Marcus Sheffer<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>7group<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
bldg-sim-bounces@lists.onebuilding.org [mailto:bldg-sim-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>m.lebourhis<br>
<b>Sent:</b> Thursday, March 19, 2009 7:14 AM<br>
<b>To:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> [SPAM] Re: [Bldg-sim] One model<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=FR style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Hi all,</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I am also currently working with IES-VE for LEED energy modeling. I
am finding it very efficient to compute the loads on the project I am working
on, which is quite huge and relatively complex in terms of geometry/envelope.</span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>However, it gets harder to model the water chilling plant as required
by Appendix G, and I am actually doing this part of the modelling with my own
excel calculation sheets and with DOE-2 curves. </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I was wondering; how will this approach be received by the USGBC? Could
they possibly require that the whole modeling is carried out with a single
package? Has anyone had problems validating EA1 with part of the energy
modelling being external to the simulation tool?</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I have also been thinking of somehow using EnergyPlus or eQuest
(preferably the latter) just for the water chilling plant modeling. Has anyone
ever used one of these two tools to compute the systems energy from a cooling
demand calculated in an other simulation package?</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Regards</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Mathieu Le Bourhis</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span lang=FR>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><b><span lang=FR style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span
lang=FR style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
bldg-sim-bounces@lists.onebuilding.org [mailto:bldg-sim-bounces@lists.onebuilding.org]
<b>De la part de</b> Field, Kristin<br>
<b>Envoyé :</b> jeudi 12 mars 2009 21:40<br>
<b>À :</b> bldg-sim@lists.onebuilding.org<br>
<b>Objet :</b> Re: [Bldg-sim] One model</span><span lang=FR><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=FR> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I tried out IES-VE a few months or a year ago with some people
because the potential for this type of integration seemed very exciting.
However, we found the HVAC side to be pretty basic. For a lot of building
types, there are significant savings to be had by changing HVAC control schemes
and/or configurations and using HVAC types that were not well-represented in
IES-VE the last time I saw it. It seemed like a great interface to use if
you were trying to design a building to use minimal energy due to envelope,
orientation, natural ventilation, etc. In other words, it seems strong on
the loads calculation side. On the system use side, though, it seemed a
lot more limited than DOE2 or EnergyPlus. For that reason, I have also
stuck with the multiple-tools method. I agree with all who wrote that it
would be wonderful to have one integrated tool in the future! Rob does
bring up an interesting point about the resolution of spaces needed for
daylighting vs. thermal vs. architectural modeling. Architects especially
have to be so detailed in their models that I’ve often just ended up
using the floor plans they provided, deleting a bunch of elements out of those,
and scaling wall heights and windows. Other than that, their 3D models
only serve to help me visualize the building myself. It would be nice if
we didn’t end up tripling the effort like we all do now, but so far I
don’t see a great way around it (unless you don’t need complex
system modeling – then you could use IES-VE as discussed below).</span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Kristin Field</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span><span lang=FR><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>CARNEY
Ronan<br>
<b>Sent:</b> Wednesday, March 11, 2009 10:34 PM<br>
<b>To:</b> Rob Guglielmetti; Ross Harding<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] One model</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Actually, I'm utilising IES to do HVAC design, Energy Analysis, PMV
calc, lighting lux design, lighting power intensity design and natural daylight
analysis all in line with the Australian Standards and Green Star (another form
of LEED) requirements. </span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Although the software costs money, I've found it to be worthwhile
battling against it's flaws and it gives us the results which we require. </span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><strong><u><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Please note, this is a one model approach</span></u></strong><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>. It's
easy to start a project at CD (concept design) stage within Google Sketchup and
to utilise the freeware version of IES to do alternate design analysis.
However, it's way better if the full suite is purchases and the model is
crossed over into IES. Within IES multiple analysis and detailed designs can be
modelled quickly and with fantastic final project results. I know, I've done
it.</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Also with the daylight analysis, if you've got a detailed building
with over 100000 surfaces, it's going to take forever to do the analysis,
that's my only issue with the software. However, the software is developing
multithreading facility within it's software, therefore decreasing the time for
analysis dramatically.</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Should anyone want to discuss my approaches further, and are in
Brisbane, I welcome the opportunity to meet and greet with you.</span><span
lang=FR><o:p></o:p></span></p>
<p><b><i><span style='font-size:10.0pt;color:navy'>Regards,</span></i></b><span
style='font-size:10.0pt'><br>
<b><i>Ronan Carney</i></b><br>
</span><span style='font-size:10.0pt;font-family:Complex'>Electrical Engineer</span><span
style='font-size:10.0pt'><br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:maroon'>Project Services</span></b><span style='font-size:10.0pt'><br>
</span><span style='font-size:10.0pt;font-family:Wingdings;color:blue'>*</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:purple'>Level 5B
80 George St</span><span style='font-size:10.0pt'> </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:purple'>Brisbane</span><span
style='font-size:10.0pt'><br>
</span><span style='font-size:10.0pt;font-family:Wingdings;color:blue'>(</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ph:</span><span
style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'>(07) 3224 5983</span><span style='font-size:10.0pt'><br>
</span><span style='font-size:10.0pt;font-family:Wingdings;color:blue'>2</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Fax: (07) 3224 6151</span><span
style='font-size:10.0pt'><br>
</span><span style='font-size:10.0pt;font-family:Wingdings;color:blue'>,</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Email<span
style='color:blue'>:</span></span><u><span style='font-size:10.0pt'> </span></u><a
href="mailto:Ronan.Carney@projectservices.qld.gov.au"
title="mailto:Ronan.Carney@projectservices.qld.gov.au"><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'>Ronan.Carney@projectservices.qld.gov.au</span></a>
<span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Rob Guglielmetti<br>
<b>Sent:</b> Thursday, 12 March 2009 1:12 PM<br>
<b>To:</b> Ross Harding<br>
<b>Cc:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Bldg-sim] One model</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal>On Mar 11, 2009, at 6:09 PM, Ross Harding wrote:<span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span lang=EN-AU
style='font-size:9.0pt;color:#144FAE'>The ultimate goal for us would be to use
one model for daylight and energy models, but I haven’t found that quite
that simple as most software requires varying drawing techniques.</span></span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal>Amen brother! Another issue is that while the energy
model has to include the total building -- all spaces and systems -- to be a
complete picture of the energy use, a Radiance-based daylight model does not
necessarily require all the spaces to be modeled simultaneously. Indeed,
the accuracy of the ambient calculation is directly affected by the maximum
size of the scene, and so conducting a simultaneous daylight simulation of an
entire building at an acceptably rigorous ambient resolution can be -- is
generally -- time-prohibitive.<span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal>As mentioned in a recent thread on this list, Thomas
Bleicher's "su2rad" plugin for SketchUp can export a SU model to
Radiance format and there is also an E+ plugin to allow one to use the same SU
model for E+ analysis; in theory, these three components (SketchUp, su2rad and
the E+ plugin) allow for a "single model" approach to energy and
daylight modeling. However, because the su2rad exporter wants to take the
entire model and create a single Radiance scene description, that creates the
aforementioned problem of the ambient calculation getting out of hand fairly
quickly. I suppose through intelligent layering and model structuring,
one could create a model that could be exported to Radiance in "space
components", but I'm not sure if this is compatible with the E+ plugin's
layering/model organization requirements.<span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal>- Rob Guglielmetti<span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>********************************************************</span><span
lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Kristin
M. Field</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Engineer
II - Mechanical</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Electricity,
Resources & Building Systems Integration</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>National
Renewable Energy Laboratory</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1617
Cole Blvd.</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Mail
Stop #1725</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Golden,
CO 80401</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Phone:
303.384.7376</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Fax:
303.384.7540</span><span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
<p class=MsoNormal> <span lang=FR><o:p></o:p></span></p>
</div>
</body>
</html>