<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=iso-8859-1"><meta name=Generator content="Microsoft Word 15 (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:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:"Lucida Bright";
panose-1:2 4 6 2 5 5 5 2 3 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.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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal0, li.xmsonormal0, div.xmsonormal0
{mso-style-name:x_msonormal0;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsochpdefault, li.xmsochpdefault, div.xmsochpdefault
{mso-style-name:x_msochpdefault;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.xemailstyle18
{mso-style-name:x_emailstyle18;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.xemailstyle20
{mso-style-name:x_emailstyle20;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:3241701;
mso-list-template-ids:109870340;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:323165856;
mso-list-template-ids:1317313448;}
@list l2
{mso-list-id:815950496;
mso-list-template-ids:-1585423800;}
@list l2:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1012606842;
mso-list-template-ids:1296871050;}
@list l3:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1175848694;
mso-list-type:hybrid;
mso-list-template-ids:1361628422 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5
{mso-list-id:1836649182;
mso-list-template-ids:520678176;}
@list l5:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6
{mso-list-id:2108652714;
mso-list-template-ids:-1697982840;}
@list l6:level1
{mso-level-start-at:3;
mso-level-tab-stop:.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="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>All, <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for all your help with this, you have given me a much better picture of the field. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Curious to find out one more thing. Wonder what confidence interval between model output and utility consumption data may be expected with reasonable effort of 10-12 modeling hours for straightforward 100,000 square foot building if we have two different scenarios:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoListParagraph style='margin-left:0in;mso-list:l4 level1 lfo7'>Good as-built drawings for a 15 yr old building.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l4 level1 lfo7'>No historical drawings and mostly estimated/guesswork for 100 year old building. <o:p></o:p></li></ol><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All reasonable assumptions welcome. <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>Tom<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><i><span style='font-family:"Garamond",serif;color:#404040'>Tom McGovern, PE, LEED AP<o:p></o:p></span></i></p><p class=MsoNormal><b><span style='font-size:16.0pt;font-family:"Lucida Bright",serif;color:#185610'>Geatain Engineering<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Garamond",serif;color:#404040'>112 West 34<sup>th</sup> Street, 18<sup>th</sup> Floor<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Garamond",serif;color:#404040'>New York, NY 10120<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Garamond",serif;color:#404040'>Office: (844) 443-2824<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Garamond",serif;color:#404040'>Cell: (631) 521-3594<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Garamond",serif;color:#185610'><a href="http://www.geatain.com"><span style='color:#185610'>www.geatain.com</span></a><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:7.0pt;font-family:"Garamond",serif;color:#404040'>This email and any attachments are intended only for the named recipient(s) and may <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:7.0pt;font-family:"Garamond",serif;color:#404040'>contain information that is privileged and confidential. If received in error, keep all<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:7.0pt;font-family:"Garamond",serif;color:#404040'>information confidential and permanently delete this email and any attachments. <o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Equest-users <equest-users-bounces@lists.onebuilding.org> <b>On Behalf Of </b>David Eldridge via Equest-users<br><b>Sent:</b> Tuesday, May 22, 2018 11:55 AM<br><b>To:</b> equest-users@onebuilding.org<br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div id=divtagdefaultwrapper><p><span style='font-size:12.0pt;color:black'>I was going to mention GenOpt as one option, and which actually just showed up in another thread on bldg.-sim mailing list.<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>However, the "standard" GenOpt installation can optimize one function, so as a calibration tool there would be an additional step to develop a CV (RMSE) and/or mean bias error for the results compared to the real utility data.<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>The autotune methods such as a presentation from Dr. New at ORNL given to IBPSA-USA and ASHRAE, or optimization platforms give a better control over the parameters to be varied. The code that you can get from GitHub to do this though is for EnergyPlus, not eQUEST or DOE2.2.<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>With GenOpt I also don't believe you'd be able to supply ranges for all the variables - so the program would minimize error but a solution could include nonsensical parameters if that satisfied the error function.<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>David<o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Equest-users <<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>> on behalf of Jones, Christopher via Equest-users <<a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>><br><b>Sent:</b> Tuesday, May 22, 2018 10:28:37 AM<br><b>To:</b> Kathryn Kerns; Aaron Powers; Nicholas Caton<br><b>Cc:</b> <a href="mailto:equest-users@onebuilding.org">equest-users@onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=xmsonormal>As Niels Bohr said, “Prediction is very difficult, especially about the future”.<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><div><p class=xmsonormal><b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Christopher R Jones, P.Eng.</span></b><o:p></o:p></p><p class=xmsonormal><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>T+ 1 416-644-0252</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:8.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=xmsonormal><img border=0 width=60 height=29 style='width:.625in;height:.302in' id="x_1cc2331b-d8c3-424e-81de-2b17716d444e.png_x003f_ver_x003d_1495657656000" src="cid:image001.png@01D3F1DA.9A088310"><o:p></o:p></p></div><p class=xmsonormal> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=xmsonormal><b>From:</b> Equest-users [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Kathryn Kerns via Equest-users<br><b>Sent:</b> Tuesday, May 22, 2018 11:19 AM<br><b>To:</b> Aaron Powers <<a href="mailto:caaronpowers@gmail.com">caaronpowers@gmail.com</a>>; Nicholas Caton <<a href="mailto:Nicholas.Caton@schneider-electric.com">Nicholas.Caton@schneider-electric.com</a>><br><b>Cc:</b> <a href="mailto:equest-users@onebuilding.org">equest-users@onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations<o:p></o:p></p></div></div><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>I have never been a fan of those performance contracting energy savings projects and our company has steered clear of them for the reasons listed below. I have done fluid and thermal finite element modeling and energy modeling for about 30 years off and on, and the only thing that can be said for these models is they show the user how something changes as a result of changing certain variables. The models do not predict the future nor do they justify the past.<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Sometimes a difficult concept to get across to people.<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal><b><span style='font-size:12.0pt;font-family:"Arial",sans-serif;color:black'>Kathryn Kerns</span></b><o:p></o:p></p><p class=xmsonormal><b><span style='font-family:"Arial",sans-serif;color:#1F497D'>Systems Specialist</span></b><o:p></o:p></p><p class=xmsonormal><b><span style='font-size:12.0pt;font-family:"Times New Roman",serif;font-variant:small-caps;color:teal'>BCE</span></b><b><span style='font-size:10.0pt;font-family:"Times New Roman",serif;font-variant:small-caps;color:teal'> </span></b><b><span style='font-size:12.0pt;font-family:"Times New Roman",serif;font-variant:small-caps;color:teal'>Engineers, Inc.</span></b><o:p></o:p></p><p class=xmsonormal><b><span style='font-size:9.0pt;font-family:"Times New Roman",serif;color:black'>| Ph: 253.922.0446 | Fx: 253.922.0896 |</span></b><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal><b>From:</b> Equest-users <<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>> <b>On Behalf Of </b>Aaron Powers via Equest-users<br><b>Sent:</b> Monday, May 21, 2018 5:30 PM<br><b>To:</b> Nicholas Caton <<a href="mailto:Nicholas.Caton@schneider-electric.com">Nicholas.Caton@schneider-electric.com</a>><br><b>Cc:</b> <a href="mailto:equest-users@onebuilding.org">equest-users@onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><div><p class=xmsonormal>Very well put Nick, and an important perspective from the world where savings projections are guaranteed. 2 + 2 = 4, but so does 10 - 6<o:p></o:p></p><div><p class=xmsonormal> <o:p></o:p></p><div><p class=xmsonormal>On Mon, May 21, 2018 at 7:13 PM, Nicholas Caton via Equest-users <<a href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=xmsonormal>As an energy engineer in the performance contracting side of the industry, a defining skillset for my job is creating and then calibrating models to fit historical utility data. We calibrate our models to a degree of rigor allowing our business to guarantee savings projected from those models (and write shortfall checks when we’re wrong). I don’t generally talk up my background, but I think in this case it helps to know where my voice is coming from to press a nuanced response:<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>It's <u>possible</u> (again, not built-in) to automate iterative model input manipulation to “auto-tune” a building energy simulation to match a set of utility bills. You can even get the curves to fit extremely tightly over multiple meters. I’ve gone so far as to build some such tools from scratch, and that experience has taught me some very important lessons I didn’t set out to find. Among them, an “auto-tuned” model where many inputs are guided by randomization and computer logic can in practice become <u>very</u> difficult to trust for projecting savings, even on a relative “doesn’t need to be seen on the bills” level. <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>On the other hand, if you careful to bound “auto-tuning” techniques to reasonable input ranges, and specifically to address “unknowable” model inputs which cannot be measured or reasonably estimated/inferred, the results can become much more useful, even enlightening. This “optimal” usage of the likes of monte carlo analysis, with and without machine learning algorithms, is anything but an “easy” button. <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>I use doe2/eQuest as my primary energy simulation platform, however all of the above advice is platform-agnostic and holds true whether you’re crunching degree-day analyses in excel or wielding rooms of supercomputers in the cloud with e+.<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>If calibration <u>matters</u>, and you’re not doing so just to tick some prescriptive box, best practice during model development is to keep mindful track of which inputs are: <o:p></o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='mso-list:l1 level1 lfo1'><u>Known</u> <o:p></o:p></li></ol><ol style='margin-top:0in' start=1 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoNormal style='mso-list:l0 level2 lfo2'>General Hierarchy of “Known:” Design/Construction Documents < As-Builts < RCx reports < Current field measurements & observations<o:p></o:p></li><li class=MsoNormal style='mso-list:l0 level2 lfo2'>Be mindful that construction documents and nameplate data are better than nothing, but commonly do not match reality and may be better considered as “informed estimates.” Allow some room for doubt. <o:p></o:p></li></ol></ol><ol style='margin-top:0in' start=2 type=1><li class=MsoNormal style='mso-list:l3 level1 lfo3'><u>Estimated</u> <o:p></o:p></li></ol><ol style='margin-top:0in' start=2 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoNormal style='mso-list:l2 level2 lfo4'>For existing buildings, this most inputs will be “estimated.” <o:p></o:p></li><li class=MsoNormal style='mso-list:l2 level2 lfo4'>If for example you have to define fan power based on scheduled static pressure loss and airflows on the drawings… that’s just aligning your estimate with the designer’s. Actual is probably something different.<o:p></o:p></li><li class=MsoNormal style='mso-list:l2 level2 lfo4'>Software defaults you understand are ready to “own” or explain fall under this category<o:p></o:p></li><li class=MsoNormal style='mso-list:l2 level2 lfo4'>This includes anything “auto-sized” <o:p></o:p></li></ol></ol><ol style='margin-top:0in' start=3 type=1><li class=MsoNormal style='mso-list:l6 level1 lfo5'><u>Guesswork</u> <o:p></o:p></li></ol><ol style='margin-top:0in' start=3 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoNormal style='mso-list:l5 level2 lfo6'>This includes software defaults that you are relying upon but haven’t yet investigated/understood. <o:p></o:p></li><li class=MsoNormal style='mso-list:l5 level2 lfo6'>This includes “known unknowns” for lack of information / resources. <o:p></o:p></li><li class=MsoNormal style='mso-list:l5 level2 lfo6'>A pretty common example is envelope constructions where (a) you have no architectural details/specifications to reference all the layers in the middle and (b) you aren’t budgeted/resourced to tear up a client’s walls to find out what’s inside.<o:p></o:p></li></ol></ol><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Considering the degree of input complexity for something like an eQuest model, I feel there will always be some blend of all if these input categories for every project and every individual modeler. Experience helps, though as the years pile on, for every new topic I get a lock on measuring/estimating, I feel like I learn about two more issues that were previously not on my radar… “the more I see the less I know!”<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Having rough estimates and unknowns is fine, but the more that you <u>know</u> or else can <u>reasonably estimate</u>, the better your initial calibration results will turn out, and the quicker the process of iteratively “tuning” a model will go. When you have a good record kept of which inputs are particularly solid vs. estimated/guesswork, you can work your way up the tree, marrying that knowledge to assumed/tested input sensitivity on the results, and plot a course to find your way back to the billed amounts!<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Hope this is helpful!<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>~Nick<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><div><p class=xmsonormal><span style='font-family:"Arial",sans-serif;color:#3A7A46'><img border=0 width=726 height=9 style='width:7.5625in;height:.0937in' id="x_m_1979403371695839565Picture_x0020_1" src="cid:image002.png@01D3F1DA.9A088310"></span><o:p></o:p></p><p class=xmsonormal><b><span style='font-family:"Arial",sans-serif;color:#3A7A46'>Nick Caton, P.E., BEMP</span></b><o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=724 style='width:543.0pt;border-collapse:collapse'><tr><td width=230 valign=top style='width:172.3pt;padding:0in 0in 0in 0in'><p class=xmsonormal><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'> Senior Energy Engineer</span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'> Regional Energy Engineering Manager</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'> Energy and Sustainability Services</span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'> Schneider Electric</span><o:p></o:p></p></td><td width=291 valign=top style='width:218.3pt;padding:0in 0in 0in 0in'><p class=xmsonormal><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069'>D </span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'>913.564.6361 </span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069'>M </span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'>785.410.3317 </span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069'>F </span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'>913.564.6380</span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069'>E </span><span style='color:#1F497D'><a href="mailto:nicholas.caton@schneider-electric.com" target="_blank"><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'>nicholas.caton@schneider-electric.com</span></a></span><o:p></o:p></p></td><td width=203 valign=top style='width:152.4pt;padding:0in 0in 0in 0in'><p class=xmsonormal align=right style='text-align:right'><span style='font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469'>15200 Santa Fe Trail Drive<br>Suite 204<br>Lenexa, KS 66219<br>United States</span><o:p></o:p></p></td></tr><tr style='height:4.0pt'><td width=724 colspan=3 valign=top style='width:543.0pt;padding:0in 0in 0in 0in;height:4.0pt'><p class=xmsonormal><span style='color:#3A7A46'><img border=0 width=722 height=49 style='width:7.5208in;height:.5104in' id="x_m_1979403371695839565_x005f_x0000_i1025" src="cid:image003.png@01D3F1DA.9A088310"></span><o:p></o:p></p></td></tr></table><p class=xmsonormal> <o:p></o:p></p></div><p class=xmsonormal> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=xmsonormal><b>From:</b> Equest-users [mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>David Eldridge via Equest-users<br><b>Sent:</b> Saturday, May 19, 2018 2:08 PM<br><b>To:</b> <a href="mailto:equest-users@onebuilding.org" target="_blank">equest-users@onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations<o:p></o:p></p></div></div><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>If you mean automatically adjusting the parameters of the model inputs to minimize error against the actual utility data by using a basis such as ASHRAE Guideline 14, then no eQUEST does not have that capability built in.</span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>You wouldn’t be changing the internal calculations – some review of the inputs and outputs should provide insight into what variables are known and which are assumed and may have a reasonable range of values resulting in a better fit to the utility data.</span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>With some on-site data such as what you’d be collecting for energy audits anyway, you can usually get an accurate model to start with, or with few iterations.</span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>There are other code/programs/platforms available that can help optimize, but requires a little more effort up front to either run the programming yourself or using a packaged program to setup the modeling files in a different program and tell the optimization program which variables have which range of values to be allowed.</span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>I hope this helps.</span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>David</span><o:p></o:p></p><div><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal><b><span style='color:#1F497D'>David S. Eldridge, Jr.</span><span style='color:#244061'>, P</span><span style='color:#1F497D'>.</span><span style='color:#244061'>E</span><span style='color:#1F497D'>.</span><span style='color:#244061'>, LEED AP BD+C, BEMP, BEAP, HBDP</span></b><o:p></o:p></p><p class=xmsonormal><span style='color:#1F497D'>Associate</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:4.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><span style='color:#365F91'>Direct: (847) 316-92</span><span style='color:#1F497D'>24</span><span style='color:#365F91'> | Mobile: (</span><span style='color:#1F497D'>773</span><span style='color:#365F91'>) </span><span style='color:#1F497D'>490</span><span style='color:#365F91'>-</span><span style='color:#1F497D'>5038</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:10.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=xmsonormal><b><span style='color:#244061'>Grumman/Butkus Associates</span></b><span style='color:gray'> </span><span style='color:#365F91'>| 820 Davis Street, Suite 300 | Evanston, IL 60201</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:9.0pt;color:gray'>Energy Efficiency Consultants and Sustainable Design Engineers</span><o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal><u><span style='font-size:9.0pt;color:gray'><a href="http://grummanbutkus.com/" target="_blank"><span style='color:gray'>grummanbutkus.com</span></a></span></u><span style='font-size:9.0pt;color:gray'> | <u><a href="http://grummanbutkus.com/blog" target="_blank"><span style='color:gray'>Blog</span></a></u> | <u><a href="https://www.facebook.com/pages/GrummanButkus-Associates/1385285015032526" target="_blank"><span style='color:gray'>Facebook</span></a></u> | <u><a href="https://twitter.com/grummanbutkus" target="_blank"><span style='color:gray'>Twitter</span></a></u></span><o:p></o:p></p></div><p class=xmsonormal><span style='color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=xmsonormal><b>From:</b> Equest-users [<a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Tom McGovern via Equest-users<br><b>Sent:</b> Friday, May 18, 2018 4:45 PM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> Re: [Equest-users] eQUEST Calculations<o:p></o:p></p></div></div><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Hello, <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Have a question regarding the internal calculations performed by eQUEST. Am new to eQUEST and just looking to understand some basics. Trying to figure out if there is some way to modify internal eQUEST calculations so baseline model may be adjusted to fit existing utility bills or if there is no way to modify internal eQUEST calculations and we need various end arounds to fit baseline eQUEST model to fit existing utility bills. <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal>Thanks, <o:p></o:p></p><p class=xmsonormal><br>Tom McGovern<o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><p class=xmsonormal> <o:p></o:p></p><div><div><div><div><div><p class=xmsonormal> <o:p></o:p></p></div></div></div></div></div><p class=xmsonormal><br>______________________________________________________________________<br>This email has been scanned by the Symantec Email Security.cloud service.<br>______________________________________________________________________<o:p></o:p></p></div></div><p class=xmsonormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Equest-users mailing list<br><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org" target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p></blockquote></div><p class=xmsonormal> <o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:gray'><br><br>NOTICE: This communication and any attachments ("this message") may contain information which is privileged, confidential, proprietary or otherwise subject to restricted disclosure under applicable law. This message is for the sole use of the intended recipient(s). Any unauthorized use, disclosure, viewing, copying, alteration, dissemination or distribution of, or reliance on, this message is strictly prohibited. If you have received this message in error, or you are not an authorized or intended recipient, please notify the sender immediately by replying to this message, delete this message and all copies from your e-mail system and destroy any printed copies. You are receiving this communication because you are listed as a current WSP contact. Should you have any questions regarding WSP's electronic communications policy, please consult our Anti-Spam Commitment at <a href="http://www.wsp.com/casl">www.wsp.com/casl</a>. For any concern or if you believe you should not be receiving this message, please forward this message to <a href="mailto:caslcompliance@wsp.com">caslcompliance@wsp.com</a> so that we can promptly address your request. Note that not all messages sent by WSP qualify as commercial electronic messages. <br><br>AVIS : Ce message, incluant tout fichier l'accompagnant (« le message »), peut contenir des renseignements ou de l'information privilégiés, confidentiels, propriétaires ou à divulgation restreinte en vertu de la loi. Ce message est destiné à l'usage exclusif du/des destinataire(s) voulu(s). Toute utilisation non permise, divulgation, lecture, reproduction, modification, diffusion ou distribution est interdite. Si vous avez reçu ce message par erreur, ou que vous n'êtes pas un destinataire autorisé ou voulu, veuillez en aviser l'expéditeur immédiatement et détruire le message et toute copie électronique ou imprimée. Vous recevez cette communication car vous faites partie des contacts de WSP. Si vous avez des questions concernant la politique de communications électroniques de WSP, veuillez consulter notre Engagement anti-pourriel au <a href="http://www.wsp.com/lcap">www.wsp.com/lcap</a>. Pour toute question ou si vous croyez que vous ne devriez pas recevoir ce message, prière de le transférer au <a href="mailto:conformitelcap@wsp.com">conformitelcap@wsp.com</a> afin que nous puissions rapidement traiter votre demande. Notez que ce ne sont pas tous les messages transmis par WSP qui constituent des messages electroniques commerciaux. <br></span><br><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:whitesmoke'><br><br>-LAEmHhHzdJzBlTWfa4Hgs7pbKl </span><o:p></o:p></p></div></div></body></html>