<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:st="" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/sharepoint/soap/workflow/"
xmlns:ns2="http://schemas.microsoft.com/office/2006/digsig-setup"
xmlns:ns3="http://schemas.microsoft.com/office/2006/digsig"
xmlns:ns4="http://schemas.openxmlformats.org/package/2006/digital-signature"
xmlns:ns5="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:ns6="http://schemas.microsoft.com/office/2004/12/omml"
xmlns:ns7="http://schemas.openxmlformats.org/package/2006/relationships"
xmlns:ns8="http://microsoft.com/sharepoint/webpartpages"
xmlns:ns9="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:ns10="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ns11="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/"
xmlns:ns12="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
xmlns:ns13="urn:schemas-microsoft-com:">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (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]--><o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
        {mso-style-priority:99;}
span.MSOHYPERLINK
        {mso-style-priority:99;}
a:visited
        {mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
        {mso-style-priority:99;}
p.MSOACETATE
        {mso-style-priority:99;}
li.MSOACETATE
        {mso-style-priority:99;}
div.MSOACETATE
        {mso-style-priority:99;}
span.BALLOONTEXTCHAR
        {mso-style-priority:99;}

 /* Font Definitions */
 @font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"Stylus BT";
        panose-1:2 14 4 2 2 2 6 2 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:Calibri;}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:Tahoma;}
span.BalloonTextChar
        {font-family:Tahoma;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:Calibri;
        color:windowtext;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@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><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>In my experience, I have generally
included plug loads to the extent of the owner/ architect basis of design.  Any
additional process required to reach 25% is included as an internal load directly
on the meter with no contribution to internal gains.  I have not identified, as
of yet, anything that would instruct me to do otherwise but I have not taken a
very close look at G-2007 yet.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>kevin<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=2 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
bldg-rate-bounces@lists.onebuilding.org [mailto:bldg-rate-bounces@lists.onebuilding.org]
<b><span style='font-weight:bold'>On Behalf Of </span></b>Nick Caton<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, April 30, 2010 1:55
PM<br>
<b><span style='font-weight:bold'>To:</span></b>
bldg-rate@lists.onebuilding.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Bldg-rate] LEED+90.1
Process/Plug Loads Conundrum</span></font><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>

</div>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>Something
new occurred to me this week and I’d love to hear others’ thoughts!<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>LEED
prescribes baseline/proposed energy models to follow ASHRAE 90.1 with a
caveat:  the “process energy costs” must total 25% of the baseline energy
costs.  By extension, 90.1 requires the same loads/schedules be applied to
the proposed model as they have to match.  As an aside, the LEED EAc1
templates appear to calculate/check this using process energy consumption (not
cost), but that’s not what I’m getting at…<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>I
just had a typical case where I had to inflate the baseline internal
miscellaneous equipment loads to get to 25%.  These additional loads were
substantial enough that when applied to the proposed model/design, I ran into
many unmet cooling hours for the equipment capacities entered.  <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>Then
I realized:  We can define additional equipment electricity loads but
simultaneously apply a multiplier (in eQuest anyway – I expect this is feasible
other programs also) to reduce/negate the corresponding heat load
contributions.  This results in the energy consumption/costs showing up
correctly in the final results/reports, but does not artificially inflate the
internal loads that the baseline/proposed systems must handle.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>Would
this practice (which incidentally can be a time saver) of accounting for extra
process/miscellaneous loads without extra thermal contributions be in line with
the intent of ASHRAE/USGBC?  It would still normalize the otherwise
unstandardized process consumption/costs of the baseline/proposed models
between different building types…<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>On
the other hand, if it really is the intent of USGBC to add arbitrary additional
internal heat loads to our models that our actual designs were not designed and
sized for, does it follow that we should allow the proposed models to autosize
cooling equipment/fan capacities and not specify them (this would seem
incongruous with 90.1 to me)?<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>~Nick<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><img
width=119 height=37 id="Picture_x005f_x0020_1"
src="cid:image001.jpg@01CAE87F.057C4000" alt="cid:489575314@22072009-0ABB"></span></font><b><font
color="#2d4d5e" face="Stylus BT"><span style='font-family:"Stylus BT";
color:#2D4D5E;font-weight:bold'><o:p></o:p></span></font></b></p>

<p class=MsoNormal><b><font size=2 color="#2d4d5e" face="Stylus BT"><span
style='font-size:11.0pt;font-family:"Stylus BT";color:#2D4D5E;font-weight:bold'><o:p> </o:p></span></font></b></p>

<p class=MsoNormal><b><font size=2 color="#2d4d5e" face="Stylus BT"><span
style='font-size:11.0pt;font-family:"Stylus BT";color:#2D4D5E;font-weight:bold'>NICK
CATON, E.I.T.</span></font></b><b><font size=3 color="#2d4d5e" face="Stylus BT"><span
style='font-size:12.0pt;font-family:"Stylus BT";color:#2D4D5E;font-weight:bold'><o:p></o:p></span></font></b></p>

<p class=MsoNormal><font size=1 color="#cc9900" face=Calibri><span
style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span></font><font
size=1 color="#cc9900" face="Times New Roman"><span style='font-size:7.5pt;
font-family:"Times New Roman";color:#CC9900'><o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#2d4d5e" face=Calibri><span
style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></font></p>

<p class=MsoNormal><st1:City w:st="on"><st1:place w:st="on"><font size=2
  color="#2d4d5e" face=Calibri><span style='font-size:10.0pt;color:#2D4D5E'>olathe</span></font></st1:place></st1:City><font
size=2 color="#2d4d5e"><span style='font-size:10.0pt;color:#2D4D5E'> ks 66061<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#2d4d5e" face=Calibri><span
style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color="#2d4d5e" face=Calibri><span
style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></font></p>

<p class=MsoNormal><i><font size=2 color="#2d4d5e" face=Calibri><span
style='font-size:10.0pt;color:#2D4D5E;font-style:italic'>Check out our new
web-site @ </span></font></i><font color="#1f497d"><span style='color:#1F497D'><a
href="www.smithboucher.com" title="blocked::www.smithboucher.com"><font size=2><span
style='font-size:10.0pt'>www.smithboucher.com</span></font></a></span></font><u><font
size=2 color=blue><span style='font-size:10.0pt;color:blue'> </span></font></u><font
color="#1f497d"><span style='color:#1F497D'><o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>

</div>

</body>

</html>