<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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 = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16915" name=GENERATOR>
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: black; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=purple link=blue>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009>Interesting topic. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009>I know there is work being done on these fronts in
Canada for the A90.1 equivalent in <SPAN class=366451518-24112009>the
</SPAN>MNECB. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009>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></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=459570118-24112009>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></FONT></DIV></DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 9pt; FONT-FAMILY: Arial" align=left><B>Phylroy
Lopez</B><BR>Sustainable Building Specialist<SPAN class=366451518-24112009>
B.ENG LEED AP</SPAN><BR>Stantec<BR><FONT color=gray>1100 - 111 Dunsmuir
Street<BR>Vancouver BC V6B 6A3<BR>Ph: (604) 696-8000<BR>Fx: (604)
696-8100<BR></FONT></DIV>
<DIV style="FONT-SIZE: 13pt; FONT-FAMILY: Arial Narrow" align=left><A
style="TEXT-DECORATION: none" href="http://www.stantec.com/"><B><FONT
color=#993333>stantec</FONT></B><FONT color=#003f6e>.com</FONT></FONT></A>
</DIV>
<DIV style="FONT-SIZE: 9pt; FONT-FAMILY: Arial" align=left> </DIV>
<DIV style="FONT-SIZE: 9pt; FONT-FAMILY: Arial" align=left>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.</DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Arial" align=left> </DIV>
<DIV><SPAN
style="FONT-SIZE: 13.5pt; COLOR: #008040; FONT-FAMILY: Webdings">ü</SPAN> <SPAN
lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: #008040; FONT-FAMILY: 'Arial Narrow'">Please
consider the environment before printing this email.</SPAN></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> 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<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">…</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">…</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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></DIV></BODY></HTML>