<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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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:"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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 5 6 2 2 2 3 2 4;}
/* 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.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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
color:black;}
span.EmailStyle21
{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.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There is also a 90.1 compliance tool associated with the new
version of Hevacomp Simulator which runs energy plus. I have not yet tried it,
but it is a feature they list on the website and in their online tutorial. If
anyone has used it, comments/feedback would be greatly appreciated. <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'>Sam<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;
color:#1F497D'>--<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Sam Mason<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Atelier Ten<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>
<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"'>
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Lopez,
Phylroy<br>
<b>Sent:</b> Tuesday, November 24, 2009 1:18 PM<br>
<b>To:</b> Equest Forum<br>
<b>Subject:</b> Re: [Equest-users] Equest Base Model vs. ASHRAE 90.1<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Interesting topic. </span><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","sans-serif";
color:blue'>I know there is work being done on these fronts in Canada for the
A90.1 equivalent in the MNECB. </span><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","sans-serif";
color:blue'>EE4 does an automatic reference case for it's building simulation.
It is a double edge sword.. It provides consistency and prevents gaming from a
compliance point of view, but workarounds can be ugly and requires editing both
proposed and reference files. But at the very least you have a starting point
where most of the mundane tasks of creating a reference case is taken care of. </span><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","sans-serif";
color:blue'>I know a bunch of people, myself included, that have scripts
written in Perl or Ruby to, say, automatically rotate the building
and average the results as required in a90.1, or change all the constructions to
A90.1 standard for my region. It would be nice to have a place to share / keep
some scripts that tweak a DOE inp files. Or even better yet have a
post-processor feature in eQuest that users. For that matter an Energyplus
scripts repository would be nice as well.</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><b><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'>Phylroy
Lopez</span></b><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'><br>
Sustainable Building Specialist B.ENG LEED AP<br>
Stantec<br>
<span style='color:gray'>1100 - 111 Dunsmuir Street<br>
Vancouver BC V6B 6A3<br>
Ph: (604) 696-8000<br>
Fx: (604) 696-8100</span><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:13.0pt;font-family:"Arial Narrow","sans-serif"'><a
href="http://www.stantec.com/"><b><span style='color:#993333;text-decoration:
none'>stantec</span></b><span style='color:#003F6E;text-decoration:none'>.com</span></a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif"'>The
content of this email is the confidential property of Stantec and should not be
copied, modified, retransmitted, or used for any purpose except with Stantec's
written authorization. If you are not the intended recipient, please delete all
copies and notify us immediately.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:Webdings;
color:#008040'>ü</span> <span lang=EN-GB style='font-size:10.0pt;font-family:
"Arial Narrow","sans-serif";color:#008040'>Please consider the environment
before printing this email.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></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"'> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>David S
Eldridge<br>
<b>Sent:</b> Tuesday, November 24, 2009 9:05 AM<br>
<b>To:</b> Equest Forum<br>
<b>Subject:</b> Re: [Equest-users] Equest Base Model vs. ASHRAE 90.1</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:black'>I know there is some work on a
document to provide a framework for developers to implement automated (or even
semi-automated!) generation of base cases within their software for various
purposes.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:black'>Keep an eye out for that,
I’m not sure of the current status or timing of it. Even prior to
implementation by any developers it will be a great resource for our community
when we make these comparisons manually.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:black'>David<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>http://www.grummanbutkus.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<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"'>
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Nick
Caton<br>
<b>Sent:</b> Tuesday, November 24, 2009 10:20 AM<br>
<b>To:</b> jwearstler@larseneng.com; Equest Forum<br>
<b>Subject:</b> Re: [Equest-users] Equest Base Model vs. ASHRAE 90.1<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'>At the moment, it’s up to the end-user to be sure your
baseline model is meeting the 90.1 minimum baseline criteria. If you
haven’t already checked it out, Appendix G explains how the model is to
be set up and calibrated to a level of performance (measured via unmet load
hours) that’s to be in the same ballpark as your proposed design.
If you apply all design criteria there into eQuest, then you’re following
90.1.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>…</span><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'>Until the day comes when software developers are producing
“intelligent” energy modeling software that makes evaluative
decisions as effectively as a human being, I don’t think the task of
“generate a baseline energy model per 90.1” is even a feasible
concept. Even if such a (complex) feature was around to use, you’d
still have to do a complete proposed model for the baseline to reference for
geometries/occupancies/zoning/etc – building the baseline after that is
not a huge relative investment of time in my experience… <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 summary, I don’t think effective/useful energy modeling
for 90.1-based compliance is conceptually possible without involvement from a
human that’s at least somewhat familiar with 90.1’s Appendix G
– it cannot be automated without a degree of accuracy loss that I think
most would find unacceptable. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>…</span><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'>For the record, I do think a good “wishlist” item
for the coming versions of eQuest, to facilitate easier, more consistent and
less error-prone 90.1 baseline modeling for users of all experience levels,
would be to create a library of 8 systems for use during HVAC system
wizard-level definition (See attached screenshot/paint masterpiece for
when/where/what I’m thinking). These would define a set of defaults
for one of the 8 standard baseline systems, but would still require the
end-user to determine project specific wizard-level criteria (such as climate
zone-specific economizer/high limit requirements and such). I’ve
noted that the recent 90.1-2007 and 90.1-2004 are identical in these
definitions, so that lends some consolation that such efforts would not become
“out-of-date” for some time to come.<o:p></o:p></span></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><br>
________________________________________________________________________<br>
This e-mail has been scanned for all viruses by Star. The<br>
service is powered by MessageLabs. For more information on a proactive<br>
anti-virus service working around the clock, around the globe, visit:<br>
http://www.star.net.uk<br>
________________________________________________________________________<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the MessageLabs Email Security System.<br>
For more information please visit http://www.messagelabs.com/email <br>
______________________________________________________________________<o:p></o:p></p>
</div>
</body>
</html>