<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:"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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;
font-family:"Verdana","sans-serif";
color:windowtext;}
span.EmailStyle18
{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";}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-weight:bold;}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";}
.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;}
-->
</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'>James et al,<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'>Rohini will need to create performance curves to make this
particular comparison. Otherwise using the default curves will result in identical
part load performances.<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'>The following is excerpted from the following (short) recommended
reading concerning what IPLV means: <a
href="http://ashrae-cfl.org/2010/03/understanding-iplvnplv/">http://ashrae-cfl.org/2010/03/understanding-iplvnplv/</a><o:p></o:p></span></p>
<p style='margin-left:.5in'>IPLV (or NPLV) = 0.01A+0.42B+0.45C+0.12D<o:p></o:p></p>
<p style='margin-left:.5in'>Where:<o:p></o:p></p>
<p style='margin-left:.5in'>A = COP or EER @ 100% Load<o:p></o:p></p>
<p style='margin-left:.5in'>B = COP or EER @ 75% Load<o:p></o:p></p>
<p style='margin-left:.5in'>C = COP or EER @ 50% Load<o:p></o:p></p>
<p style='margin-left:.5in'>D = COP or EER @ 25% Load<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>John is saying knowing only the IPLV and the 100% load condition
efficiency (variable ‘A,’ above) is not enough information to extrapolate the IPLV
curves to compare the two chillers. <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'>For the exercise of comparing the two non-centrifugal chillers
of the same technology/type, I would just focus on making a custom EIR-FPLR
(not EIR-fPLR&dT) for each chiller, and use the library CAP-FT AND EIR-FT
curves. My understanding is the effects of temperature on capacity and EIR
outside of centrifugal VSD chillers is negligible. NOTE: Whenever using any
of the default library chiller performance curves, that means you MUST
normalize to and specify the chiller at ARI conditions – those curves aren’t
normalized to anything else.<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'>So! If you can find the IPLV A, B, C and D values for both
chillers’ curves, you could come up with your EIR-FPLR curve coefficients (<u>curve
type = quadratic or cubic</u>) using a curve-fit in excel… or alternatively
make eQuest figure the coefficients by entering those points as raw data.<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'>You may more easily just make your own curves, following John’s
advice and getting part load unloading curves (100%, 90%, 80%... etc) held at a
constant chilled & condenser temperature to match the ARI* conditions (85CWT
if this is water cooled) at which you’re specifying the chiller capacity/EIR.
Again, you could either go into excel, normalize the data (review DOE2 help
entry for EIR-FPLR), make a scatter chart, and get the coefficients using a
curve fit… or enter the data as raw points into eQuest and the coefficients
will be figured by eQuest… whatever makes more sense to you.<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'>For others and personal future reference…. If you are looking to
make an <u>EIR-fPLR&dT</u> curve (for centrifugal chillers or otherwise): Ask
your rep instead for multiple (minimum 3) part load unloading runs, holding the
delivered chilled water temp constant, and vary the condenser water temperature
incrementally for each run (i.e. 85, 75, 65). Choose a range of CWT’s that
cover the anticipated range to be encountered in the actual design. This will
get you enough data to have the minimum 3 delta-T’s represented in your part
load data points to build this curve correctly. You’ll be using eQuest “raw-data”
entry method to make it generate the coefficients.<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'>* Rather than ARI conditions (85F CWT), you could be normalizing
to Design condition EIR/CAP, provided you’re making a full set of custom curves
in the same fashion.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><img border=0 width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CBD4DB.F3986BD0" 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<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Smith & Boucher Engineers</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><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>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'>
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>James
Waechter<br>
<b>Sent:</b> Friday, February 25, 2011 10:55 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] using IPLV in eQuest<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>John,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>If
the only parameter Rohini enters into the program is the full-load EIR – which
he said is the same for both chillers – how will eQuest know to bend the curves
differently for the two chiller options. It is my understanding that
program would use the same chiller efficiency curves for both machines even
though their IPLVs are different.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>In
order to overcome this issue, are you saying Rohini should get chiller
performance data from each of the manufacturers and enter his own custom
curves? I recall there was a discussion on that topic a few months back.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>James
Waechter Jr., P.E., CEM, LEED A.P.<br>
Energy Engineer – Rocky Mountain Region<br>
p 303 215 4062 | m 727 686 3248<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>McKinstry</span></b><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
Consulting | Construction | Energy | Facility Services<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><a
href="http://www.mckinstry.com/"><span style='color:windowtext'>www.mckinstry.com</span></a>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><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"'>
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>John
Aulbach<br>
<b>Sent:</b> Friday, February 25, 2011 9:41 AM<br>
<b>To:</b> R B; eQUEST Users List<br>
<b>Subject:</b> Re: [Equest-users] using IPLV in eQuest<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>Rohini:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Won't happen. IPLV is a number which has one equation and 4
unknowns. Actually, three unknowns as you know the 100% point. You need a
manufacturer's curve run at 85F constant condenser water temperature. Let
eQuest do the curve bending after that. ARI curve won't work right.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>John
R. Aulbach, PE, CEM<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Senior
Energy Engineer<o:p></o:p></span></p>
<div>
<div>
<div class=MsoNormal><span style='font-family:"Calibri","sans-serif";
color:#17365D'>
<hr size=2 width="30%" noshade style='color:#17365D' align=left>
</span></div>
</div>
</div>
<p class=MsoNormal><b><span style='font-family:"Calibri","sans-serif";
font-variant:small-caps;color:navy'>Partner</span></b><b><span
style='font-family:"Calibri","sans-serif";font-variant:small-caps;color:green'>
</span></b><b><span style='font-family:"Calibri","sans-serif";font-variant:
small-caps;color:#006600'>Energy</span></b><b><span style='font-family:"Calibri","sans-serif";
font-variant:small-caps;color:navy'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>1990
E. Grand Avenue, El Segundo, CA 90245<br>
W: 888-826-1216, X254| D: 310-765-7295 | F: 310-817-2745<o:p></o:p></span></p>
<p class=MsoNormal><a href="http://www.ptrenergy.com/"><span style='font-family:
"Calibri","sans-serif";color:purple'>www.ptrenergy.com</span></a><span
style='font-family:"Calibri","sans-serif";color:#1F497D'> </span><a
href="mailto:%7C%20jaulbach@ptrenergy.com"><span style='font-family:"Calibri","sans-serif"'>|
jaulbach@ptrenergy.com</span></a><span style='color:#1F497D'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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"'> R B <slv3sat@gmail.com><br>
<b>To:</b> eQUEST Users List <equest-users@lists.onebuilding.org><br>
<b>Sent:</b> Fri, February 25, 2011 7:25:18 AM<br>
<b>Subject:</b> [Equest-users] using IPLV in eQuest</span><o:p></o:p></p>
<div>
<p class=MsoNormal>Hi All, <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I would like to compare two screw chillers with same full
load kW/ton and different IPLV kW/ton. I am using the full load number for the
EIR. Where can the IPLV number be used? Is there some way to scale the
performance curves to reflect different IPLV's?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>-Rohini<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><br>
This email is the property of McKinstry or one of its affiliates and may
contain confidential and/or privileged information. If you are not the intended
recipient or have received this e-mail in error please notify the sender
immediately and delete this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden. <o:p></o:p></p>
</div>
</body>
</html>