<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<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:"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:"Franklin Gothic Book";
panose-1:2 11 5 3 2 1 2 2 2 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.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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{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;
font-size:10.0pt;}
@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:1771122669;
mso-list-type:hybrid;
mso-list-template-ids:340441658 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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='color:#1F497D'>William, <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Below I have explained my
approach to dealing with unmet load hours, which has never failed me and no
LEED reviewer has ever questioned. It includes info on Baseline
auto-sizing since the two are often related. As a general guideline,
unmet load hours are a control issue rather than a capacity issue. When
capacity is an issue, I find that it’s with the Baseline model. In
dealing with these cases, I have come to the conclusion that G3.1.2.2 and
G3.1.2.8 are at odds with each other in many cases. If I correctly
auto-size the flows off a 20 F delta T but still have too many unmet load
hours, how can I reduce the hours without increasing air flow? It’s
pointless to increase coil capacity without delivering more air to the
zone. So, my basic approach is to get the right controls in place and
then target the remaining trouble zones with increased air flow. I feel
this finds a balance between G3.1.2.2 and G3.1.2.8. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>The magnitude of hours is
important. If you’re in the thousands for a given system, ensure you’ve
selected the right system type according to eQUEST’s definition. For
example, a recent project utilized chilled water fan coil units (two-way
valves) with electric heat. They were constant volume, variable
temperature, single zone, with no central air handler. I had to change
the system type from “fan coil” to “single zone reheat” to get the correct
behavior. An air-cooled heat pump is a PSZ whereas a GSHP is a PVVT (but
also single-zone). So, sometimes a little research is required to ensure
you and eQUEST define the system the same way. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Assuming the system type is
correct…<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For Baseline systems
with auto-sized flows and capacities, start with the correct air flows by ensuring
the G3.1.2.8 requirement is in place:<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For every zone,
define the heating & cooling “Indoor Design Temperature” under Zone
Properties/Basic Specifications. These are not the same as the hourly
T-stat settings, but some would argue that they should be set the same for the
Baseline. So, if occupied heating = 70 F at the T-stat, make that the
indoor heating design temperature, too. Spreadsheet view makes this
process quick. Do not make the heating & cooling design temps the
same; there should be at least a two-degree difference to ensure (somewhat)
stable operation.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'><span style='font:7.0pt "Times New Roman"'>
</span>i.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If applicable, apply
G3.1.3.13 for Baseline Systems 5 & 7 under Zone/Air Flow/Minimum
Flow. Note that this is different than “Min Design Flow”. For all
Baseline system types, leave the Min Design Flow blank to allow the system to
auto-size off the 20 F delta T requirement. For Systems 5 & 7, the
Minimum Flow will override the Min Design Flow if the Min Design Flow is less
than 0.4 CFM/sf. <o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'><span style='font:7.0pt "Times New Roman"'>
</span>ii.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Ensure the Baseline
ventilation is the same as the Proposed ventilation per G3.1.2.5. This
requires specifying a CFM, not a percentage of supply air. It can be done
at the zone or system level, but specifying at the zone level will ensure a
more apples-to-apples comparison if zone-level heating or cooling is involved.
It will also ensure the zone SA never falls below the OA
requirement. <o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>At the system level,
under Cooling/Coil Cap Control, set the “Zone Entering Min Supply Temp” to be
20 F lower than the zone “Indoor Design Cooling Temperature”. Repeat for
the heating coil, setting the “Zone Entering Max Supply Temp” 20 F greater than
the heating Indoor Design Temperature.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For mechanical or
storage spaces, or anywhere there’s a difference in control temperature or
space load, there will probably need to be a separate system. See if
G3.1.1 a) through d) apply to your project and proceed accordingly. Steps
1a) and 1b) still apply, but with different temperatures.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.75in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For all multi-zone
systems, VAV in particular, go through every zone and set the Throttle Range to
at least 4 R (4 – 6 R). This is a reasonable range for stable system
operation.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>NOTE: When adjusting
the Throttle Range, you are, in effect, defining how eQUEST counts unmet load
hours. Increasing the Throttle Range is the same as decreasing the
counter’s sensitivity. It should not be abused, however, and the value
should be reasonable. For a large, multi-zone VAV system, 4 – 6 R is
reasonable. For smaller/single-zone systems, 0.2 – 3.0 R is probably more
reasonable.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.75in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Next, adjust the
system fan, heating, and cooling schedules to reflect a morning warm-up
period. Going from a 85 F night setting to a 75 F occupied setting cannot
be done in one hour. This transition probably needs two to four hours,
adjusting the thermostat a few degrees at a time. Heat pumps are
particularly sensitive to T-stat fluctuations and probably need to make the
transition in two-degree increments; water-cooled equipment may be able to make
the transition a little more aggressively. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Use a schedule to
lock out OA during the warm-up period unless simulating an overnight
flush-out. The DOE2.2 documentation indicates how to do this.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If the design calls
for fans to remain off during unoccupied hours, good luck. In many
climates the zone temps will drift to the extent that they will be difficult to
bring under control within a few hours. It is advisable to define some
sort of setback temp and allow the fans to cycle so that there is a
ceiling/floor to the zone temps (Baseline fans must cycle at night). Naturally,
the larger the delta T between occupied/unoccupied, the longer the transition
period required. This is compounded by systems which are relatively slow
responders. Again, the shift in hourly T-stat setting needs to be
reasonable for the system type & capacity, maybe 2-4 F.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For VAV or VAVVT,
use schedules to deliver 100% flow and heating/cooling supply air temperature
during the warm-up. This may already be accounted for by the type of
thermostat, but a schedule will provide additional assurance. Again, one
can read the DOE2.2 documentation to figure out how to do this.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.75in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>4)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>With basic controls
in place, identify the zones with the largest amount of unmet load hours.
Look at the SS-F report to see the zones’ temperature extremes and the time of
year in which they are occurring. These temperatures can then be
correlated back to the SS-O report to see what time of day they are
occurring. In most cases, if this step is performed before step 3), it
will reveal issues in the morning hours and the need to define a warm-up
period. If the unmet load hours are occurring later in the day, the zone
is probably not getting enough air to satisfy its loads.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If morning warm-up
is not an issue, the next step is to ensure the eQUEST zone loads are close to what
is expected. If modeling an existing design, ensure the internal zone
loads are close to design values (it is assumed the envelope loads are
reasonably close to design values due to fewer unknowns). If the modeler
is not the mechanical engineer, the modeler should contact the engineer and
compare load assumptions. For example, in an elevator equipment room with
a 60 kW motor, is 100% of that load truly sensible (the eQUEST default
value)? Or, is 80% of that 60 kW being used to lift the elevator and only
20% showing up as sensible load? The LS-B report is a good one to compare
to the ubiquitous Trace 700 Zone CheckSum reports. Make adjustments to
the model as needed. The loads will never match exactly, but they should
be in the same ballpark.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Get rid of
infiltration in interior zones if this has not already been done.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.75in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>5)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>At this point, the
zone loads should be reasonably close to design values, the Baseline air flow
should be auto-sizing correctly, and there should be controls in place to
provide a sufficient warm-up period. If too many unmet hours
remain… <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For the Proposed
system, ensure each zone is getting the design supply air. Total supply
air may have been specified at the system level, but this does not mean eQUEST
is allocating the supply to each zone as it was designed. Specify the
design air flow at the zone level. If this does not resolve unmet load
hours, and all other parameters are correct, it is possible that the system is
undersized. It is difficult to offer more generic advice without
reviewing the project in question.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>For the Baseline
system, it is time to begin applying G3.1.2.2. <o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'><span style='font:7.0pt "Times New Roman"'>
</span>i.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>First, modelers need
to be aware of eQUEST’s sizing factors. The System Properties/Basics tab
contains a Sizing Ratio field. This is an overall sizing factor which
impacts the cooling capacity, heating capacity, and supply flow. The
“Cool Sizing Ratio” and “Heat Sizing Ratio” on the Cooling and Heating tabs
only affect the cooling and heating capacities, respectively. So, if one
were to set the system sizing ratio to 1.15 and the heating sizing ratio to
1.25, the net effect is a heating capacity ratio of (1.15)(1.25) = 1.44.
The heating coil would be 44% larger (and out of compliance with G3.1.2.2), and
the air flow would be 15% larger. The same concept applies on the cooling
side. Therefore, I am the opinion that the system sizing ratio should
always be 1.0, and the cooling & heating ratios should be 1.15 and 1.25,
respectively. There is no reason to deviate from these factors unless the
goal is to make a complete mess of the system sizing. Furthermore, it is
useless to resolve unmet hours by playing with coil capacities alone; more air
must be delivered to the zone in conjunction with a larger coil capacity.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'><span style='font:7.0pt "Times New Roman"'>
</span>ii.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Therefore, I believe
the best way to satisfy G3.1.2.2 is to begin with System Sizing Ratio = 1.0,
Cool Sizing Ratio = 1.15, and Heat Sizing Ratio = 1.25. This, along with
following 1a) and 1b) above will ensure the modeler is starting from the
correct point. Look at the Air-Side HVAC Summary report and note the
auto-sized CFM/sf for the zones showing the most unmet load hours. For
those trouble zones, and only those trouble zones, begin incrementally
increasing the Min Design Flow on the zones’ Basic Specifications tab. If
the auto-sized flow is 0.54 CFM/sf, increase it to 0.65 or 0.75 and
re-simulate. Smaller zones may require larger increments to get an extra
10 or 25 CFM. Keep going until the zone’s unmet load hours are eliminated
or satisfactory. By increasing zone flow rather than system sizing
factors, the modeler is indirectly increasing system capacity while ensuring
the additional capacity reaches the trouble zones. I believe this is a
better interpretation of G3.1.2.2 than blindly ratcheting up the system sizing
factors.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:2.0in;text-indent:-.25in;
mso-list:l0 level4 lfo2'><![if !supportLists]><span style='color:#1F497D'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>NOTE: It is
advisable to make multiple passes through all the trouble zones rather than
tackling them all in one round – there is a relationship between adjacent
zones. When the unmet hours are down to around 20 or 30 for a given zone,
move on to the next one. You may notice that bringing down unmet load
hours for one zone also improves the hours for its adjacent zones. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>After all this, unmet load hours
have always been below 300 – usually they’re zero. If it doesn’t work,
there’s something else wrong that will require a more thorough review of the
project. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black;text-transform:uppercase'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
<o:p></o:p></span></p>
<p class=MsoNormal><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600"
o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f"
stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="Picture_x0020_2" o:spid="_x0000_s1027" type="#_x0000_t75"
style='position:absolute;margin-left:0;margin-top:1.35pt;width:52.95pt;
height:67.75pt;z-index:-1;visibility:visible;mso-wrap-style:square;
mso-wrap-distance-left:9pt;mso-wrap-distance-top:0;mso-wrap-distance-right:9pt;
mso-wrap-distance-bottom:0;mso-position-horizontal:absolute;
mso-position-horizontal-relative:text;mso-position-vertical:absolute;
mso-position-vertical-relative:text'>
<v:imagedata src="cid:image001.png@01CA96B2.E31A30D0" o:title="" />
</v:shape><![endif]--><![if !vml]><span style='mso-ignore:vglayout;position:
absolute;z-index:-1;margin-left:0px;margin-top:2px;width:71px;height:90px'><img
width=71 height=90 src="cid:image003.jpg@01CA96B7.36540CE0" v:shapes="Picture_x0020_2"></span><![endif]><b><span
style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
DAKOTA KELLEY</span></b><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
</span><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
</span><b><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
</span><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>Project Designer<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
Office: 214-744-6199<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
Cell: 214-280-3825<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
Fax: 214-744-0770 <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'><a href="http://www.teliospc.com/"><span style='font-family:"Times New Roman","serif"'>http://www.teliospc.com</span></a>
3535 Travis St. Suite 115 <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:black'><a href="mailto:dakotak@teliospc.com"><span style='font-family:
"Times New Roman","serif"'>dakotak@teliospc.com</span></a>
Dallas, TX 75204 <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:#3333FF'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:#3333FF'>| MEP ENGINEERING </span><span style='font-size:8.0pt;
font-family:"Times New Roman","serif";color:#3333FF'>·</span><span
style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:#3333FF'> ENERGY MODELING </span><span style='font-size:8.0pt;font-family:
"Times New Roman","serif";color:#3333FF'>· </span><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:#3333FF'>LEED
CONSULTATION </span><span style='font-size:8.0pt;font-family:"Times New Roman","serif";
color:#3333FF'>·</span><span style='font-size:8.0pt;font-family:"Franklin Gothic Book","sans-serif";
color:#3333FF'> COMMISSIONING |</span><span style='font-size:8.0pt;font-family:
"Franklin Gothic Book","sans-serif";color:#1F497D'>
<o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'>CONFIDENTIALITY
NOTICE: This email is intended only for the use of the individual or entity to
which it is addressed, <o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'>And may contain
information that is privileged, confidential and exempt from disclosure under
applicable law. If you <o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'>are not the intended
recipient, please email the sender immediately, and delete this email from all
computers. Any <o:p></o:p></span></p>
<p class=MsoNormal style='text-align:justify'><span style='font-size:8.0pt;
font-family:"Franklin Gothic Book","sans-serif";color:gray'>distribution or
other use is strictly prohibited. Copyright © 2010 Telios Corporation.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<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"'> William Lopez
[mailto:william@buffalo-energy.com] <br>
<b>Sent:</b> Friday, January 15, 2010 2:45 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Throttling Range<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hello All,<o:p></o:p></p>
<p class=MsoNormal>This question could be too general, However, some of you may
have a consistent way to reduce the throttling range hours. Usually I play with
heating, cooling capacities and thermostat settings, but this time
I am having a hard time trying to reduce unconditioned areas in a heat pump
system.<o:p></o:p></p>
<p class=MsoNormal>I appreciate any help.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><i><span style='font-size:12.0pt;color:#31849B'>William
G. Lopez, CEM<o:p></o:p></span></i></b></p>
<p class=MsoNormal><i><span style='font-size:12.0pt;color:#943634'>Energy
Engineer<o:p></o:p></span></i></p>
<p class=MsoNormal><i><span style='font-size:12.0pt;color:#943634'><o:p> </o:p></span></i></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#943634'>Buffalo Energy,
Inc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#943634'>716-677-4899 P<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#943634'>716-677-4722 F<i><o:p></o:p></i></span></p>
<p class=MsoNormal><a href="mailto:william@buffalo-energy.com">william@buffalo-energy.com</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>