<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=koi8-r"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Garamond;
        panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-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;}
span.BodyTextChar
        {mso-style-name:"Body Text Char";
        mso-style-priority:99;
        mso-style-link:"Body Text";}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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;}
--></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><span style='color:#1F497D'>I’m not sure if you can do it with Global Keywords, but that usually avoids problems for me in parametric runs. I’ve actually setup an eQuest model to calculate ASHRAE 62.1 for single zone systems using keywords and custom user functions.<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'>Take a look at the help files on meters, though: I haven’t had enough time to dig into that to know for sure what it is capable of, but while I was looking up the keyword I pasted in for you earlier, I found notes about how you can set the model to make a determination of which rate to use based on total demand. There are utilities that will bump your rate schedule to the next one if you exceed a specific demand, say, 3 consecutive months of 100kW demand or greater. Apparently, eQuest CAN handle that too, but you have to dig into it to figure out how to get it setup right.<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'>Saying that, I’m guessing there is a way to do what you want to do for the parametric run, but there’s a lot of reading involved in finding the right way.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#1F497D'>Jeremy R. Poling, PE, LEED AP+BDC</span></b><span style='color:#1F497D'><br><br></span><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"'> Shea, Rebecca [mailto:rshea@noresco.com] <br><b>Sent:</b> Monday, July 25, 2011 3:24 PM<br><b>To:</b> Jeremy Poling; equest-users@lists.onebuilding.org<br><b>Subject:</b> RE: [Equest-users] Real Time Pricing / 8760 Utility Rate<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>You know what, I was thinking that the ENERGY-CHG-SCH was just for demand for some reason, and that I didn’t need it since I’m only tracking consumption right now.  I put my schedule in there and it seems to be acting correctly, (more reports will tell).  The EMIT (link below) made exporting an hourly schedule pretty easy since I had the RTP for 2010 in excel already.  For those of you creating 8760 schedules, definitely check it out.<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'>I’m having an issue of getting it to switch rates in a parametric run.  I tried setting up both rates, assigning EM1 to the TOU rate in the baseline and RTP rate to EM1 in the parametric run , but in both cases it calculated the $$ using a sum of both rates.  I ended up creating 2 separate models to compare them, but if someone knows how to switch utility rates I’d love to hear.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Regards,</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Beka Shea</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D'>______________________________________________________________________________________________</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'> <br></span><b><i><span style='font-size:10.0pt;font-family:"Garamond","serif";color:#333333'>NORESCO</span></i></b><b><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'> </span></b><b><span style='font-size:10.0pt;font-family:"Times New Roman","serif";color:#333333'></span></b><span style='font-size:10.0pt;font-family:"Garamond","serif";color:#333333'> 36 Harbor Lake Circle, Safety Harbor, FL 34695 </span><b><span style='font-size:10.0pt;font-family:"Times New Roman","serif";color:#333333'></span></b><span style='font-size:10.0pt;font-family:"Garamond","serif";color:#333333'> Phone: 727.742.6385</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p></div><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"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Jeremy Poling<br><b>Sent:</b> Monday, July 25, 2011 2:53 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Real Time Pricing / 8760 Utility Rate<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>There is a “Energy Charge Schedule” keyword (ENERGY-CHG -SCH) on the “Utility Rate Properties” dialog that accepts a schedule for hourly-use schedules, but as David notes that is a rather complex utility rate to model.  The help file says this about the keyword:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>U-name of a SCHEDULE which specifies an ENERGY-CHG that varies by time of day, week and/or season. The units in the schedule should be $/UNIT. This schedule is used for all time-of-use energy billing (demand time-of-use billing is more complex, and requires the use of multiple BLOCK-CHARGEs). If both an ENERGY-CHG and ENERGY-CHG-SCH are defined, the values will add.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>That’s all it says on this keyword, too…so if your consumption and demand charges both are real-time pricing, there’s quite a bit of work ahead of you.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#1F497D'>Jeremy R. Poling, PE, LEED AP+BDC</span></b><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"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>David Eldridge<br><b>Sent:</b> Monday, July 25, 2011 1:28 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Real Time Pricing / 8760 Utility Rate<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Make an output report of the hourly building electricity consumption/demand values that you need and do it in excel.  Probably will be faster than making that complex of a schedule.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><div><p class=MsoNormal><span style='color:#1F497D'>David</span><o:p></o:p></p><p class=MsoNormal><u><span style='color:black'>                                                                                                </span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>David S. Eldridge, Jr., P.E., LEED AP BD+C, BEMP, BEAP, HBDP</span><o:p></o:p></p><p class=MsoNormal><b><span style='color:#244061'>Grumman/Butkus Associates</span></b><o:p></o:p></p><p class=MsoNormal><u><span style='color:black'>                                                                                                </span></u><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p></div><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></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"'> <a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Shea, Rebecca<br><b>Sent:</b> Monday, July 25, 2011 12:57 PM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> [Equest-users] Real Time Pricing / 8760 Utility Rate</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I know that the joy of eQuest is that if you can schedule it, you can do it.  However – can anyone give me a quick tutorial on how to assign an 8760 schedule as a utility rate?  I used the handy dandy “Energy Model Input Translator” put out by RMI to generate my schedule (<a href="http://www.rmi.org/rmi/ModelingTools">http://www.rmi.org/rmi/ModelingTools</a>) and then I imported the .inp file into eQuest very nicely… now what? <span style='font-family:Wingdings'>J</span> (I made it a “multiplier” schedule, not sure if that is correct, but I’m attaching it here.  I can easily change the schedule type if necessary)<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>As always, any help appreciated.  Thanks for your valuable time,<o:p></o:p></p><p class=MsoNormal>Beka Shea<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>______________________________________________________________________________________________</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><b><span style='font-size:10.0pt;font-family:"Garamond","serif"'>Rebecca Shea</span></b><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><b><i><span style='font-size:10.0pt;font-family:"Garamond","serif";color:#333333'>NORESCO</span></i> </b><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p></div></body></html>