<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=us-ascii">
<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
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.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:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{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;}
/* List Definitions */
@list l0
{mso-list-id:661470619;
mso-list-type:hybrid;
mso-list-template-ids:582411288 345538002 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F02D;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.25pt;
text-indent:-.25in;
font-family:Symbol;}
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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As a note, the USGBC reviewer’s advice is in line with the
requirements of Energy Star for detached buildings on a campus with shared
parking: for separate buildings on a campus, the parking area (surface and/or
garage) must be divided between the buildings when entered into Portfolio
Manager. If this is a LEED 2009 project and the owner plans to comply
with the 5-year metering requirement via Energy Star, setting up the model in
that manner will make it consistent with the mandatory minimum M&V
requirements. I’m not sure what led to the decision to model each
building in a separate PD2 file (other than scheduling of the design work
meaning Building 4’s model won’t be needed for some time after
Building 1’s model is done), but it might provide some benefit to model
the campus in one file. I would think this would be true in 2 specific
cases:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If there is a single meter covering all campus electrical use (not
uncommon for campuses), allowing the model to calculate a coincident demand for
cost purposes that might be lower than the sum of the demands for the four
separate model<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:38.25pt;text-indent:-.25in;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Credit for daylighting is being pursued and there is a potential
for one of the buildings to shade another, making the combined model file more conservative
on energy savings from daylighting than the four individual models<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'>I have done a split PD2 file approach on a model before and
while it made sense when it was setup and the project was small (10K SF total),
responding to comments was more difficult. For example, if there was some
error in the baseline U-Value then each model file would have to be corrected
individually instead of changing the wall type in a single model (4 changes
instead of 1). Just some thoughts to consider.<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'>I would partially agree with the reviewer, though – the
parking garage needs to be part of the model and with a split model you would
have to put the parking garage into each of the four models. I probably
would have taken a slightly different approach, though – If the campus is
not modeled in a single model, the parking garage should be modeled on its own,
with the resulting energy divided between the four models proportionate to the
number of spaces allocated to each building or the proposed occupancy of each
building, since those are the factors that determine how much of the garage
each building would use.<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><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>JEREMY R. POLING, PE, LEED AP</span></b><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Associate Vice President,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Senior Sustainability Analyst<br>
Strategic Services<br>
<i>Site Solutions | Operations | Sustainability</i></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>
<br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#C75B12'>EPSTEIN</span></b><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:#1F497D'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:gray'>Architecture<br>
Interiors<br>
Engineering<br>
Construction</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><br>
<br>
</span><b><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:green'><o:p></o:p></span></i></b></p>
<p class=MsoNormal><b><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:green'>Epstein is a firm believer in sustainability. We ask that you
please consider the environment before printing this e-mail.</span></i></b><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:gray'><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>Walson,
Kristy<br>
<b>Sent:</b> Tuesday, October 05, 2010 8:21 AM<br>
<b>To:</b> 'Pasha Korber-Gonzalez'; eQUEST Users List<br>
<b>Subject:</b> Re: [Equest-users] LEED-parking garage question/advice needed<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Pasha,<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'>Having modeled a few parking garages in various software at this
point, I also do not agree with the LEED representative's suggestion. In
my experience, parking garages typically have daylighting controls to turn off
perimeter lights during the day. This would be tough for a simulation
program to model without creating a separate building for the parking
garage. I know you said that the parking garage would not be utilizing
any ECM's, but I like to leave my options open in case an owner comes back and
decides that the payback is well worth the money spent up-front for controls.<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'>If you end up incorporating the lighting as a bulk load on the
electrical meter at each building, just remember that you'll need 2 bulk loads
- one for daytime garage lighting and one for night time exterior
lighting. If you're sure they won't be adding ECM's at a later date, then
I think the bulk load idea will work. Just be sure to spend some time on
your lighting schedule because the lighting savings seen between the baseline
and proposed models for a parking garage can be significant and you don't want
to lose any of this benefit. Good luck!<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><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kristy Walson, PE, LEED AP</span></b><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#333333'>Mechanical Engineer / Sustainable Design</span></i><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'><o:p> </o:p></span></p>
<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>Pasha
Korber-Gonzalez<br>
<b>Sent:</b> Tuesday, October 05, 2010 9:13 AM<br>
<b>To:</b> eQUEST Users List<br>
<b>Subject:</b> [Equest-users] LEED-parking garage question/advice needed<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi,<br>
<br>
I would like to get a few opinions from some fellow simulators on a modeling
approach for a LEED project. Please share your opinion/advice if
you are interested.<br>
<br>
Project: Four separate buildings that surround an open-air
parking garage structure (all above grade.)--Location is Miami, FL<br>
Intent: All Four buildings (as a whole project) are going for
LEED certification. Each building will be modeled in it's own .pd2 file
as the simulator would prefer to manage the models in this manner versus using
a campus modeling approach in a single .pd2 file.<br>
<br>
USGBC recommendations where that the parking garage should be divided (or
split) into four pieces and 1/4 of the parking garage should be included with
the buildings in each of the separate model files.<br>
<br>
The ISSUE is this: My simulation gut instinct is telling me that
this is a really bad way to include the energy use of a parking garage in a
project model....(I was actually shocked that this was the advice from a LEED
representative.) So I am trying to advise my colleague that
it might be better to not include the actual parking structure (i.e. separate
shell) in each model, but to calculate the lighting use (on a schedule of
operation) for the parking garage lighting and then simply add in that energy
as a kW input on a separate meter and assign a ltg operating schedule to
it. With this approach it would be easier to take the advice
of the LEED folks and input 1/4 of the installed kW in each of the separate
model files, rather than wasting time with building in (& managing) another
shell in each model file. (FYI-there are no other ECM's that will
be accounted for in the parking garage.)<br>
<br>
<br>
What do you think of this approach? Do you think that it is
significant and important to include the "physical" presence of the
parking garage in each of the model files? What approach would you
take?<br>
<br>
Thanks for your time as always...<br>
<br>
Pasha :)<o:p></o:p></p>
</div>
</body>
</html>