<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=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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"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";}
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:10.5pt;
font-family:Consolas;}
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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:443311824;
mso-list-type:hybrid;
mso-list-template-ids:1785917646 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1112286313;
mso-list-type:hybrid;
mso-list-template-ids:-809321692 1918517576 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:"MS Mincho";
mso-bidi-font-family:"Times New Roman";}
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=WordSection1>
<p class=MsoNormal>Hi John!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Here’s some thoughts generally following your queries for
everyone’s benefit. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Keep in mind that for some of these questions – there are
no black and white answers, all you’ll ever get is “what works for
me.” I expect others will concur & courteously differ with me
on at least a few points =).<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>If sticks are analogous to the bare minimum required by
90.1, then make a Mona Lisa with sticks =). LEED models are at once both difficult
and simple – there are many rules and procedures to follow, but the
degree of accuracy expected of the final product is not nearly so rigorous as
historically calibrated models and similar. It’s a whole different
ball game. I’ve written much on how LEED models are not “predictive
models” (nor should they be). Be very clear with yourself and your
colleagues/clientele on that point, or else be prepared to spend an extra few
magnitudes of time on the project.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>As a general rule: scheduling can be as simple or
complex as you like, provided baseline & proposed models are treated identically.
Some exceptions exist where the scheduling can/should differ (common
example in my models: exterior lighting controls). Start “simple,”
(work with the default libraries/curves), then add detail to the models as is necessary.
For example: one weighted plug load schedule for the entire building is in many
cases absolutely fine, but you may find it necessary to break things out
further to demonstrate actual equipment performance in your proposed model
(such as in an IT room with a mini-split) – refine schedules as you need
to along the way, and just make sure the baseline receives the same refinements
as you go.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Define custom equipment performance curves as is
necessary to get credit where it’s due, or where it’s known/expected
your software’s library curves do not cut it for that system type.
Library curves are themselves totally acceptable provided they’re a
reasonable approximation. Be prepared to document and create custom
curves however should your reviewer ask for it, particularly if you are using equipment
known to require custom curves to be modeled correctly.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Restroom exhaust: depends on the software you’re
using, where the air is coming from, and the answers can vary for both proposed
and baseline models… G.3.1.2.8. speaks to relief systems if that’s
what you’re getting at.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>5.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Baseline infiltration: don’t believe it’s
defined through appendix G... but a very good question! I know 90.1
addresses envelope sealing to some extent but I don’t think there’s
anything quantified for the overall construction’s leakage rate… I
match proposed model levels as practice, and haven’t had the issue come
up yet. Would love to hear if others have successfully documented
something different for baseline/proposed!<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>6.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Humidity control should be considered if it is in the
actual design. 90.1 requires humidity setpoints be kept the same between
the models, alongside thermostat setpoints somewhere in that big 2-column table.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>7.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Picking a “close” construction is something
I used to do, until I learned that actual constructions aren’t really so
hard to define after all. Either approach can be acceptable for LEED’s
rigor in my experience, but as with anything it depends on the reviewer lottery
(some may not accept an approximation). As a practice these days, I do
carefully define each layer for the envelope constructions, and make a point to
keep a photocopy of the referenced envelope construction details in my project
design file. Makes for easy documentation later.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>8.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Generally: All baseline capacities (airflows/gpms/heating/cooling)
are auto-sized in the model in a “sizing run” – corresponding
efficiencies for each are worked from those quantities. Refer to Appendix
G (and the archives here) for specifics ;-).<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoNormal>General advice:<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Trace-specific questions I can’t help much with,
but for any modeler I’d advise reading Appendix G, then reading Appendix
G again. Appendix G pretty much sets the bar regarding what you must do
irrespective of the energy modeling software of choice. It’s pretty
prescriptive, and should be read that way. Don’t hesitate to refer
to earlier sections (incl. Appendix A) and give them a cursory review from time
to time as you try to better define baseline behavior for various systems.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Anyone unfamiliar with submitting EAc1 for LEED v3 <u>really
really really</u> must log in, and download the EAp2 excel spreadsheet that will
be uploaded for documentation. It would be a good idea to grab the EAc1
template (pdf) while you’re there. Review the spreadsheet/template
carefully for your project before starting and periodically as you develop your
models… the excel spreadsheet is pretty much a one-stop shop for what
your reviewer will be looking at down the road, and can help remind you of what
needs attention along the way. I consider myself very familiar with 90.1,
and still do this with every LEED project.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The 2007 90.1 user’s manual is a worthwhile text
for those intermediate to modeling under 90.1. Get a few projects under
your belt first then you’ll get more out of it.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>If you meet a fellow energy modeler in person it’s
totally appropriate to buy him/her a beer. Fist bumps are fine for some
of the population, but watch for a confused expression and be prepared to gracefully
transition into a handshake.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Don’t wax your car in direct sunlight.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Water your lawn in the early AM.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Call your mother sometimes.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Real bikers wear spandex.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>~Nick<o:p></o:p></p>
<p class=MsoNormal><img width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CC1BC9.15A5DDF0" alt="cid:489575314@22072009-0ABB"><b><span
style='font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>Smith &
Boucher Engineers</span><span style='font-size:7.5pt;font-family:"Times New Roman","serif";
color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913
345.0617<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><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'> </span></u><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: bldg-sim-bounces@lists.onebuilding.org [mailto:bldg-sim-bounces@lists.onebuilding.org]
On Behalf Of Eurek, John S NWO<br>
Sent: Thursday, May 26, 2011 4:57 PM<br>
To: bldg-sim@lists.onebuilding.org<br>
Subject: [Bldg-sim] Training (UNCLASSIFIED)<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Classification: UNCLASSIFIED<o:p></o:p></p>
<p class=MsoPlainText>Caveats: NONE<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I am looking for training.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>What I'd like to learn.<o:p></o:p></p>
<p class=MsoPlainText>How detailed to models need to be for LEED? Do I
make a stick figure or the<o:p></o:p></p>
<p class=MsoPlainText>Mona Lisa<o:p></o:p></p>
<p class=MsoPlainText> Do I make one schedule for
the building or one per room.<o:p></o:p></p>
<p class=MsoPlainText> Do I make unloading curves
for the equipment or use the defaults.<o:p></o:p></p>
<p class=MsoPlainText> How is exhaust air from
restrooms supposed to be handled.<o:p></o:p></p>
<p class=MsoPlainText> What is the baseline
infiltration rate supposed to be.<o:p></o:p></p>
<p class=MsoPlainText> Does humidity need to be
considered.<o:p></o:p></p>
<p class=MsoPlainText> Do I need to model the
wall construction or can I pick something<o:p></o:p></p>
<p class=MsoPlainText>close and type in the u-value<o:p></o:p></p>
<p class=MsoPlainText> What is the ft of heat for
the baseline design if I use a boiler.<o:p></o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>Not counting the rooms geometry there still seems to be
over 500 (maybe 1000)<o:p></o:p></p>
<p class=MsoPlainText>different values in Trace that can be adjusted.
Some large like the type of<o:p></o:p></p>
<p class=MsoPlainText>system to small like is it draw thru or blow thru (or the
Outside long wave<o:p></o:p></p>
<p class=MsoPlainText>emissivity of the window which the architect still hasn't
found for me).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I understand that when comparing different options (such
as R value A or B)<o:p></o:p></p>
<p class=MsoPlainText>the detail doesn't need to be on the gnat's ass. So
energy modeling at the<o:p></o:p></p>
<p class=MsoPlainText>onset of a project isn't too hard to figure out. What is
required for a LEED<o:p></o:p></p>
<p class=MsoPlainText>reviewer to get a warm fuzzy from my model is the big
question I'd like to<o:p></o:p></p>
<p class=MsoPlainText>get training on.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The simple answer is to do it all, consider everything,
but then reality sets<o:p></o:p></p>
<p class=MsoPlainText>in and I have a budget to consider.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Classification: UNCLASSIFIED<o:p></o:p></p>
<p class=MsoPlainText>Caveats: NONE<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>Bldg-sim mailing list<o:p></o:p></p>
<p class=MsoPlainText>http://lists.onebuilding.org/listinfo.cgi/bldg-sim-onebuilding.org<o:p></o:p></p>
<p class=MsoPlainText>To unsubscribe from this mailing list send a blank
message to BLDG-SIM-UNSUBSCRIBE@ONEBUILDING.ORG<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>