<!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:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16430"><!--[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-face {
font-family: MS Mincho;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Stylus BT;
}
@font-face {
font-family: @MS Mincho;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
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.MsoPlainText {
MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
LI.MsoPlainText {
MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
DIV.MsoPlainText {
MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
P.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
P.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
LI.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal-compose
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.PlainTextChar {
FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text"; mso-style-name: "Plain Text Char"
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=571570616-20072011><FONT size=2
face=Arial>Hi Nick,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=571570616-20072011><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=571570616-20072011><FONT size=2
face=Arial>To keep it simple, I would just derate the schedules, your 10/15%
reduction but on an hourly basis (ie one or more hours are moved
to 0%/setback) and apply the RESET-PRIORITY and MIN-RESET-FLOW
keywords. I think averaging it out beforehand and explaining as part of
your modelling methodology in your report would take less time and be easier to
explain. I would start with a small test model, to make sure you have
the right percentages. </FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=571570616-20072011></SPAN><FONT face=Arial><FONT size=2>S<SPAN
class=571570616-20072011>haun</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN
class=571570616-20072011></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN class=571570616-20072011>
<STYLE>
st1\:*{behavior:url(#ieooui) }
</STYLE>
<STYLE>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</STYLE>
<DIV class=Section1>
<P class=MsoNormal><I><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Shaun
Martin LEED AP</SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Principal</SPAN></I></P>
<P class=MsoNormal><I><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Shaun
Martin Consulting</SPAN></I></P>
<P class=MsoNormal><I><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Suite
<?xml:namespace prefix = u1 /><u1:Street u2:st="on"><u1:address
u2:st="on"><?xml:namespace prefix = st1 ns =
"urn:schemas-microsoft-com:office:smarttags" /><st1:Street
w:st="on"><st1:address w:st="on">200 - 420 West Hastings
Street</u1:address></u1:Street></st1:address></st1:Street></SPAN></I><o:p></o:p></P>
<P class=MsoNormal><u1:place u2:st="on"><u1:City u2:st="on"><st1:place
w:st="on"><st1:City w:st="on"><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Vancouver</SPAN></I></st1:City><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt"></u1:City> <u1:State
u2:st="on"><st1:State w:st="on">BC</u1:State></st1:State>
<u1:PostalCode u2:st="on"><st1:PostalCode w:st="on">V6B
1L1</u1:PostalCode></st1:PostalCode></SPAN></I></st1:place></u1:place></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">604-789-1095</SPAN></I></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Arial; COLOR: blue; FONT-SIZE: 10pt"><A
title=blocked::mailto:smartin@shaunmartinconsulting.com
href="blocked::mailto:smartin@shaunmartinconsulting.com"><I><SPAN
title=blocked::mailto:smartin@shaunmartinconsulting.com><SPAN
title=blocked::mailto:smartin@shaunmartinconsulting.com><SPAN
title=blocked::mailto:smartin@shaunmartinconsulting.com><FONT
color=#000000>smartin@shaunmartinconsulting.com</FONT></SPAN></I></SPAN></SPAN></A></SPAN></P>
<P class=MsoNormal><SPAN class=GramE><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">member</SPAN></I></SPAN><I><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt"> CAGBC,
ASHRAE</SPAN></I></P></DIV></SPAN></FONT></FONT></DIV>
<DIV><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Nick
Caton<BR><B>Sent:</B> Wednesday, July 20, 2011 8:45 AM<BR><B>To:</B> James
Hansen; Eurek, John S NWO; David Eldridge;
bldg-sim@lists.onebuilding.org<BR><B>Subject:</B> Re: [Bldg-sim] How have you
approached... (UNCLASSIFIED)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal>Thanks so much for the suggestions!<SPAN
class=571570616-20072011><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I myself have tread the “extensive, realistic
fractional/thermostat scheduling” path before under similar circumstances.
Upon facing a VERY large project, where the amount of explicit scheduling
required for that approach is compounded by the sheer quantity and variety of
occupied spaces benefiting from this relay setup, I am challenged with
brainstorming any acceptable (by LEED reviewer) means of approximating the same
behavior/savings by simplifying the problem…<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Here are some alternative ideas we’ve come up with so far
– I would very much appreciate others’ thoughts on these, or any further
related LEED/USGBC experiences to share as well:<o:p></o:p></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"
class=MsoListParagraph><![if !supportLists]><SPAN
style="mso-list: Ignore">1.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN><![endif]>90.1 already prescribes how we quantify the savings of
occupancy sensors for installed lighting (10 or 15% flat deduction on the
LPD). Rather than define & justify the quantity and timing of
unoccupied hours between varying space types (murky waters at best), one could
instead reduce the loads incident on the affected systems by the same
percentage. This might be accomplished by applying this 10/15% deduction
to the affected spaces’ fractional load schedules (occupancy, equipment &
lighting). One would need to tread carefully to avoid “double-dipping” on
any spaces already claiming a LPD deduction for occupancy sensors.
Baseline model’s schedules would remain unaffected and would be documented
alongside the modified ones to illustrate the difference. <o:p></o:p></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"
class=MsoListParagraph><![if !supportLists]><SPAN
style="mso-list: Ignore">2.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN><![endif]>(Simpler to model, but requiring slightly more
documentation): Let’s say a hospital has an annual average of 85%
occupancy for all its patient rooms. Treating every other room normally,
select a representative sampling (considering envelope loads) of 15% of the
patient rooms. Model those selected rooms as “empty” (set people, lights
and equipment loads = 0) but still conditioned to maintain the thermostat
setpoint (against loads incident from the envelope & neighboring spaces).
Apply the 0% minimum turndown behavior to those “empty” rooms only.
Baseline model would receive identical treatments, excepting the 0% turndown
behavior. Documentation would include illustrating which zones were
sampled against the others, and justification for the net annual “occupancy
rate” used for each space type.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I have mixed feelings – obviously any simplification of the
problem has the potential to under/overstate the savings that might be found
with a more exhaustive scheduling approach, but may result in as good or even a
better estimation provided with solid documentation and execution. Does
anyone think the above approaches could work well, or have any suggestions to
refine the strategies? <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks again!<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><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><IMG id=Picture_x0020_1 alt=cid:489575314@22072009-0ABB
src="cid:571570616@20072011-2F6C" width=119 height=37><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; FONT-SIZE: 12pt">NICK
CATON, P.E.</SPAN></B><B><SPAN
style="FONT-FAMILY: 'Stylus BT','sans-serif'; COLOR: #2d4d5e; FONT-SIZE: 12pt"><o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="COLOR: #cc9900; FONT-SIZE: 7.5pt">SENIOR
ENGINEER<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #cc9900; FONT-SIZE: 7.5pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #2d4d5e; FONT-SIZE: 10pt">Smith &
Boucher Engineers</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; COLOR: #cc9900; FONT-SIZE: 7.5pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #2d4d5e; FONT-SIZE: 10pt">25501 west
valley parkway, suite 200<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #2d4d5e; FONT-SIZE: 10pt">olathe, ks
66061<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #2d4d5e; FONT-SIZE: 10pt">direct
913.344.0036<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #2d4d5e; FONT-SIZE: 10pt">fax
913.345.0617<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><A
title=blocked::www.smithboucher.com href="www.smithboucher.com"><SPAN
style="COLOR: blue; FONT-SIZE: 10pt">www.smithboucher.com</SPAN></A></SPAN><U><SPAN
style="COLOR: blue; FONT-SIZE: 10pt"> </SPAN></U><o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>-----Original Message-----<BR>From: James Hansen
[mailto:JHANSEN@ghtltd.com] <BR>Sent: Wednesday, July 20, 2011 8:40 AM<BR>To:
Eurek, John S NWO; Nick Caton; bldg-sim@lists.onebuilding.org<BR>Subject: RE:
[Bldg-sim] How have you approached... (UNCLASSIFIED)<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>I agree with John, I've done this on a model before and
its painful. Assuming there are 10 hours in a work day, I set up 10
different occupancy and lighting schedules, each schedule being essentially
identical except for a different hour of zero occupancy / lighting. I then
applied these 10 schedules to the different office zones on a floor so that
specific areas were vacant from 8am-9am, some vacant from 9am-10am, etc.
And then for my system, I assumed relatively consistent 10% non-occupied
conditions and reduced the OA at the system level accordingly. If your
non-occupied conditions are more drastic (30%), obviously you can set up your
schedules differently.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>However, if your primary air is also cooling (and not some
sort of DOAS chilled water VAV box), then you are going to also have to specify
10 separate thermostat schedules (really 20 with heating and cooling) so that
the rooms do not have unmet load hours. I'm assuming you go into setback
mode when the offices are unoccupied.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>However, this was under v2.0, so that was a long time ago
and reviewers were not as critical in their reviews.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>GHT Limited<o:p></o:p></P>
<P class=MsoPlainText>James Hansen, P.E., LEED AP<o:p></o:p></P>
<P class=MsoPlainText>Senior Associate<o:p></o:p></P>
<P class=MsoPlainText>1010 N. Glebe Road, Suite 200<o:p></o:p></P>
<P class=MsoPlainText>Arlington, VA 22201-4749<o:p></o:p></P>
<P class=MsoPlainText>703-243-1200 (office)<o:p></o:p></P>
<P class=MsoPlainText>703-338-5754 (cell)<o:p></o:p></P>
<P class=MsoPlainText>703-276-1376 (fax)<o:p></o:p></P>
<P class=MsoPlainText>www.ghtltd.com<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>-----Original Message-----<o:p></o:p></P>
<P class=MsoPlainText>From: bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] On Behalf Of Eurek, John S
NWO<o:p></o:p></P>
<P class=MsoPlainText>Sent: Wednesday, July 20, 2011 9:31 AM<o:p></o:p></P>
<P class=MsoPlainText>To: Nick Caton;
bldg-sim@lists.onebuilding.org<o:p></o:p></P>
<P class=MsoPlainText>Subject: Re: [Bldg-sim] How have you approached...
(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>Nick,<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>I would do it with schedules. This would be the long
method.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>I have the same controls and have not got around to model
it. I would also<o:p></o:p></P>
<P class=MsoPlainText>make many schedules. A different schedule for
occupancy, lights, equipment,<o:p></o:p></P>
<P class=MsoPlainText>ect. Also if this applies to a lot of rooms, you'd
likely make multiple<o:p></o:p></P>
<P class=MsoPlainText>schedules, one assuming that the room is empty from 9~10
another room empty<o:p></o:p></P>
<P class=MsoPlainText>from 2~3. (The inverse for meeting rooms, if you
have multiple meeting<o:p></o:p></P>
<P class=MsoPlainText>rooms, not all meetings will happen at the same
time.)<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>"Is Freedom a small price to pay to stop Global
Warming?"<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>John Eurek PE, LEED AP<o:p></o:p></P>
<P class=MsoPlainText>Mechanical Engineer,<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>-----Original Message-----<o:p></o:p></P>
<P class=MsoPlainText>From:
bldg-sim-bounces@lists.onebuilding.org<o:p></o:p></P>
<P class=MsoPlainText>[mailto:bldg-sim-bounces@lists.onebuilding.org] On Behalf
Of Nick Caton<o:p></o:p></P>
<P class=MsoPlainText>Sent: Tuesday, July 19, 2011 3:59 PM<o:p></o:p></P>
<P class=MsoPlainText>To: bldg-sim@lists.onebuilding.org<o:p></o:p></P>
<P class=MsoPlainText>Subject: [Bldg-sim] How have you
approached...<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>I have a precedent question for everyone... this is not a
"how to" procedural<o:p></o:p></P>
<P class=MsoPlainText>question for any particular software, but to simply feel
out what has worked<o:p></o:p></P>
<P class=MsoPlainText>for others in the past:<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>Here's a quick description of the situation at-hand:
a VAV terminal unit<o:p></o:p></P>
<P class=MsoPlainText>with a "normal" minimum damper position (say, 30%) is tied
by relay to the<o:p></o:p></P>
<P class=MsoPlainText>space occupancy sensor, which also controls the
lights. Upon sensing space<o:p></o:p></P>
<P class=MsoPlainText>vacancy, the minimum airflow damper position is reset to
0% (airflow is<o:p></o:p></P>
<P class=MsoPlainText>permitted to stop, provided thermostat temperature set
point is satisfied).<o:p></o:p></P>
<P class=MsoPlainText>Upon sensing occupancy, the preset minimum damper position
is restored.<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>For LEED/USGBC-reviewed energy models, can anyone relate
success in modeling<o:p></o:p></P>
<P class=MsoPlainText>this or a similar energy-saving behavior in the proposed
model, distinct from<o:p></o:p></P>
<P class=MsoPlainText>the baseline? If so, what approach did you use to
model this behavior and/or<o:p></o:p></P>
<P class=MsoPlainText>quantify the energy savings? <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>I was discussing the possibilities with some colleagues
and have a few ideas<o:p></o:p></P>
<P class=MsoPlainText>for approaches that might all be justifiable, ranging from
simple (and quick)<o:p></o:p></P>
<P class=MsoPlainText>to complex (and time-consuming). <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>There are likely multiple "right" answers here, but I am
hoping to identify<o:p></o:p></P>
<P class=MsoPlainText>some precedent to understand what we can anticipate the
LEED reviewership<o:p></o:p></P>
<P class=MsoPlainText>will accept. <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>Thanks in advance!<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>~Nick<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>cid:489575314@22072009-0ABB<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>NICK CATON, P.E.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>SENIOR ENGINEER<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>Smith & Boucher Engineers<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>25501 west valley parkway, suite 200<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>olathe, ks 66061<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>direct 913.344.0036<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>fax 913.345.0617<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>www.smithboucher.com <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><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=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>The information contained in this communication is
confidential, may be privileged, and is intended only for the use of the
addressee. It is the property of GHT Limited. Unauthorized use,
disclosure or copying of this communication or any part thereof is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify me immediately by return e-mail or by e-mail to
ght@ghtltd.com, and destroy this communication and all copies thereof, including
all attachments. Thank you.<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=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>