<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:"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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 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";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:129514614;
mso-list-type:hybrid;
mso-list-template-ids:598623952 -620754098 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:3;
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";}
@list l1
{mso-list-id:443841800;
mso-list-type:hybrid;
mso-list-template-ids:-1893717144 -24329290 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:3;
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";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Firstly, apologies for the cross-posting, but it appears this topic
has grown include many lists so I can’t come up with an alternative!<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'>Secondly, a huge thanks to Carol, James and a large number of
others (who shall remain unnamed until they should decide to join the public
discussion) who have given me direct input on their personal thoughts, outside
of the mailing lists.<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'>I have received a flood of suggestions regarding approaches when
the intent is to follow the 25% rule, and additionally regarding how one might
go about appeasing a USGBC LEED model reviewer when attempting to document a
lower figure. My impression up until this point, based on colleagues’
experience/advice, has been that attempting to substantiate anything less than
25% process loads would be a futile task and would be flatly rejected. As a
result I never really considered this to be an option available to us LEED energy
modelers. I now understand that for many, documenting something less than 25% has
proven a feasible, if occasionally exhaustive, task.<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'>When the intent is to follow the 25% baseline process load prescriptive
requirement, I have been exposed (again outside of the lists) to a surprising
number of unique viewpoints and seemingly legitimate approaches which have led
to successfully reviewed LEED model submissions for others.<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'>Among the approaches to build the process loads to 25% are:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<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'>Adding a single direct internal/external load to the project
electrical meter in addition to the designed space equipment loads – this approach
avoids additional internal heat gains.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<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'>Adding additional or redefining designed space equipment loads,
adding internal heat sources. If and when these additional loads should result
in too many unmet cooling hours in the proposed model, there are two basic approaches:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l1 level2 lfo2'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Courier New";color:#1F497D'><span style='mso-list:Ignore'>o<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'>Specify
larger system cooling capacities and/or airflows<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l1 level2 lfo2'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Courier New";color:#1F497D'><span style='mso-list:Ignore'>o<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'>Allow
those systems cooling capacities/airflows to auto-size<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><u><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>Keeping</span></u><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> the designed space
equipment loads without adding any further, but modifying their utilization
schedules to increase space equipment usage during non-peak cooling hours – this
of course adds heat to the models, but avoids unmet cooling hours due to clashes
with proposed system cooling capacities.<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'>I sincerely hope Carol and others will not misunderstand… Myself
and others do not wish to “game the system,” but we seem to have a variety of
viewpoints as to what the intent is for the 25% rule. <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'>If it may help and add to the discussion, my personal opinion
leading up to this inquiry has been that the default 25% rule exists simultaneously
as a means of normalizing the “difficulty level” of attaining LEED EAc1 points
for projects with various actual process loads. Perhaps at some point in time,
somebody decided it would be unfair for someone designing a LEED Platinum
toolshed with zero process loads to have an easier time of it than some poor
sucker trying to get some EAc1 credits for an automotive manufacturing facility
with immense process loads?<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'>I will unfortunately be unable to participate in or respond to
this topic of discussion for some time as I will be away from my inbox. I very
much look forward to gaining a better understanding of how we as a group might
come to agree on a “best practice” for this issue. If anyone should currently
have access to a relevant CIR that would probably be very useful.<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'>A humble thanks again to everyone,<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'>~Nick<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'><img width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CAE893.495A1F40" alt="cid:489575314@22072009-0ABB"></span><b><span
style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";
color:#CC9900'>PROJECT ENGINEER</span><span style='font-size:7.5pt;color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Check out our new web-site @ </span></i><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a
href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span
style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:blue'> </span></u><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 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>Carol
Gardner<br>
<b>Sent:</b> Friday, April 30, 2010 5:12 PM<br>
<b>To:</b> bldg-sim@lists.onebuilding.org; eQUEST Users List<br>
<b>Subject:</b> [Bldg-sim] Fwd: [Bldg-rate] LEED+90.1 Process/Plug Loads
Conundrum<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>---------- Forwarded message
----------<br>
From: <b>Carol Gardner</b> <<a href="mailto:cmg750@gmail.com">cmg750@gmail.com</a>><br>
Date: Fri, Apr 30, 2010 at 2:40 PM<br>
Subject: Re: [Bldg-rate] LEED+90.1 Process/Plug Loads Conundrum<br>
To: James Hess <<a href="mailto:JHess@tmecorp.com">JHess@tmecorp.com</a>>,
Nick Caton <<a href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>>,
Karen Walkerman <<a href="mailto:kwalkerman@gmail.com">kwalkerman@gmail.com</a>><br>
Cc: "<a href="mailto:bldg-rate@lists.onebuilding.org">bldg-rate@lists.onebuilding.org</a>"
<<a href="mailto:bldg-rate@lists.onebuilding.org">bldg-rate@lists.onebuilding.org</a>><br>
<br>
<br>
Hi Nick,<br>
<br>
I'm glad you raised this issue. <br>
<br>
First, I agree with James, and have heard from other people, that LEED accepts
documentation saying something as basic as "hey, I don't have 25% plug
loads".<br>
<br>
Second, when you have to create a baseline to measure up from, you are forced
to say what that baseline is. For instance, in 1985-86, working on the
BPA-funded Energy Edge project, we had to figure out the baseline for a group
of buildings being designed to exceed the current energy codes by 30%. We
didn't have a baseline then. To deal with this we assembled a group of people
that we euphemistically called The Greybeards (so sorry to you all). The tables
now known as G3.1.1A & G3.1.1B in Standard 90 came out of what we created
in that moment of time. We were trying to limit what is called "gaming the
system"<br>
<br>
So now it seems it has been deemed important to control the baseline a little
more: by specifying plug loads at 25%. The goal of trying to limit gaming the
system might be the source of the 25%. The danger which Nick has clearly
demonstrated in his email is that what is meant to control gaming the system,
may now actually be creating it.<br>
<br>
Further thoughts/comments welcome,<br>
<span style='color:#888888'><br>
Carol</span><o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal>On Fri, Apr 30, 2010 at 1:42 PM, James Hess <<a
href="mailto:JHess@tmecorp.com" target="_blank">JHess@tmecorp.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>This is a good question. On prior projects we have
worked on, I have found that you can have less than 25% plug loads, so long as
you have some documentation to back it up.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>For example, we are currently working on a prison
project. The plug loads are very low for obvious reasons; they don’t
provide stereos, computers, ipods, TV’s, etc. to the inmates (typically, all
they get is an alarm clock/radio that uses ~ < 10 watts). There is no
way on this project that we could get the plug loads to come in at 25% unless
we artificially jacked them up to levels that would never exist in
reality. We would have a similar problem in that the Proposed Design
equipment would not be able to cool the spaces. So, we just document the
loads we do have and I believe we are good. The project has been through
the 1<sup>st</sup> review and this has not come up as an issue. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I believe we have had other projects where we documented
the loads we had and passed the review with no problems. We will
typically develop a simple spreadsheet and document the internal loads that
each room has. That is easy enough to do these days I believe, for most
applications. For example, a typical desktop computer uses about 65 watts
on average, monitor = ~ 45 watts (depending on size), clock radio ~ 10 to 15
watts, etc. you get the point. (get a “Killawatt” power meter from Amazon
and have some fun taking some measurements to see approximately how much power
stuff uses, guaranteed to provide hours of fun).</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Just provide some documentation on some good reasonable
estimates for the loads and I think you will be fine.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>An alternate method is to use default values from Table
G-B from the ASHRAE 90.1-2007 Users Manual.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>For example, the Receptacle Power Density for the Office
Building Type is 0.75 watts/SF per Table G-5.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>If using that value results in the process loads being
less than 25%, my comment to the reviewers would be that the 0.75 watts/SF is
the value determined by ASHRAE to be appropriate for the building type.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I think the most important thing is to use something
reasonable and defendable, and make it the same between the Baseline and
Proposed Design energy models. Our experience indicates that it does not
have to be exactly 25%, can be less than 25% or greater than 25%, depending on the
building.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>One thing that is interesting is that on federal
projects, per EPACT requirements, you do not have to factor in the
process/recep loads for the purpose of determining whether the 30% savings requirement
has been met. That makes it easier to show 30% savings. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Thanks!</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Regards,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>JAH</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;color:#00B050'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span
style='font-size:10.0pt;color:#00B050'>James A. Hess, PE, CEM</span></i></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#1F497D'>Senior Energy Engineer</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#1F497D'>TME, Inc.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#1F497D'>Little Rock, AR</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Mobile: 501-351-4667</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.5pt;font-family:Consolas;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.5pt;font-family:Consolas;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'> </span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:bldg-rate-bounces@lists.onebuilding.org" target="_blank">bldg-rate-bounces@lists.onebuilding.org</a>
[mailto:<a href="mailto:bldg-rate-bounces@lists.onebuilding.org" target="_blank">bldg-rate-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Nick Caton<br>
<b>Sent:</b> Friday, April 30, 2010 12:55 PM<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt'><br>
<b>To:</b> <a href="mailto:bldg-rate@lists.onebuilding.org" target="_blank">bldg-rate@lists.onebuilding.org</a><br>
<b>Subject:</b> [Bldg-rate] LEED+90.1 Process/Plug Loads Conundrum<o:p></o:p></span></p>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Something
new occurred to me this week and I’d love to hear others’ thoughts!<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>~Nick<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Error!
Filename not specified.</b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span
style='font-size:10.0pt;color:#2D4D5E'>Check out our new web-site @ </span></i><span
style='color:#1F497D'><a href="http://www.smithboucher.com" target="_blank"
title="blocked::www.smithboucher.com"><span style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;color:blue'> </span></u><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>_______________________________________________<br>
Bldg-rate mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/bldg-rate-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/bldg-rate-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a
href="mailto:BLDG-RATE-UNSUBSCRIBE@ONEBUILDING.ORG" target="_blank">BLDG-RATE-UNSUBSCRIBE@ONEBUILDING.ORG</a><br>
<br>
<o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>