<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>All,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>We have been working with Brandon on the issues he has been
having with the ABS-gbXML-GBS-DOE-2.2-eQuest process flow and would like to note
a few items for clarity.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>1. The DOE-2 and EnergyPlus files created by GBS are
exact translations of what is in the gbXML file exported by the CAD application.
No surfaces are added, modified, or moved. The "misplaced" roof Jeff
mentions is actually a ceiling surface that has been exported as a roof surface
from ABS, and we have encouraged Brandon to report the issue to Autodesk who is
aggressively working on any issues with their gbXML export that are reported to
them by their users.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>2. Jeff and I have spoken about the issues of viewing GBS
created DOE-2 files in eQuest's 2D views and have agreed to work
together to find a solution. The issue in a nut shell, eQuest's 2D plan
view relies on horizontal planar polygons that represent the space boundary and
a planar polygon to represent the bounding story polygon to draw the spaces and
story. That is the primary purpose of these two polygons (space and floor) as
they are not required by DOE-2 for the energy analysis. A real world
example of this horizontal planar polygon limitation is a theatre
floor or a lecture auditorium that have curved or angled floors that
currently can not be viewed in eQuest's 2D view. The curved or angled
floors are represented in gbXML as they are seen in the CAD application and
the resulting GBS created DOE-2.2 files. We have designed our gbXML to DOE-2
translation for these real world scenarios.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>3. gbXML does have a volumetric space representation, one
that is fully 3D. The vast majority of CAD applications do not have 3D
space/room objects that can capture a curvatous room that you may find
in a Gehry building design with walls tilted outward (that is why Gehry went
with Catia a mechanical design CAD application). The CAD vendors are
rapidly expanding their tool's capabilities to have fully 3D space
objects. <SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>DOE-2, eQuest, or EnergyPlus have no 3D volumetric
space objects.</FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>One of the tests we recommend CAD vendors conduct in
testing their gbXML export is a sphere. The link below is to such a sphere that
has been translated to DOE-2 by GBS and is viewed in eQuest's 3D view. This
spherical space can not be viewed in eQuest's 2D view, as it would be too great
of a simplification to represent the curved floor with one planar polygon as
eQuest currently requires for its 2D view. It would also be very difficult
programmatically and error prone to automatically determine where the 2D
planar polygon should be.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN><SPAN class=254493814-31082006><FONT
face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2><A
href="http://development.greenbuildingstudio.com/images/equestsphere.jpg">http://development.greenbuildingstudio.com/images/equestsphere.jpg</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>Though none of what I said above will help Brandon's issue
today, I think his feedback to Autodesk, Green Building Studio, and Jeff will
ensure that our next or future updates and versions meet his real
needs.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>Lastly, today the vast majority of energy modeling requires
hours of human interpretation of drawings and CAD models to build the energy
model. In this process, human interpretation makes apprenticed judgments to
simplify the model given the budgetary and time constraints of the project. The
CAD vendors are pushing the envelope to automate this process to provide
geometrically accurate thermal models of the building as they are represented in
their tools. They have made great progress and are fine tuning the exceptions as
they are reported, so very soon we can shelve our architectural scales as slide
rulers were many decades ago.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>I look forward to that day!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254493814-31082006><FONT face=Arial
color=#0000ff size=2>John</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV align=left><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT
color=#000000><FONT color=#0000ff>John F. Kennedy<BR>President &
CTO</FONT><BR></FONT></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><BR></SPAN><SPAN
style="COLOR: red; FONT-FAMILY: Arial"></SPAN><SPAN
style="FONT-FAMILY: Arial"><STRONG><FONT color=#ff0000><FONT
color=#008000>Green</FONT> </FONT><FONT color=#008000>Building Studio,
Inc.</FONT></STRONG><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A
title=http://www.greenbuildingstudio.com/
href="http://www.greenbuildingstudio.com/"><FONT
title=http://www.greenbuildingstudio.com/
color=#0000ff>www.greenbuildingstudio.com</FONT></A><BR>707.569.7373 x100
v<BR>707.569.7313 f<BR>707.235.1335 c</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> BLDG-SIM@GARD.COM
[mailto:BLDG-SIM@GARD.COM] <B>On Behalf Of </B>Brandon Nichols<BR><B>Sent:</B>
Wednesday, August 30, 2006 9:19 AM<BR><B>To:</B>
BLDG-SIM@GARD.COM<BR><B>Subject:</B> [BLDG-SIM] gbXML CAD data into
eQuest?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN
class=559510216-30082006>All,</SPAN></FONT></DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN
class=559510216-30082006></SPAN></FONT> </DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN class=559510216-30082006>Recently
I have been successful on a number of projects exporting gbXML building geometry
from CAD (Autodesk Building Systems 2007) and importing into version 6
of Trace 700 and version 4.3 of Carrier HAP. </SPAN></FONT></DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN
class=559510216-30082006></SPAN></FONT> </DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN class=559510216-30082006>Have also
tried sending the gbXML to Green Building Studio and downloading the DOE-2 file
they create in an effort to import this data expeditiously into
eQuest. Unfortunately the DOE-2 file created by Green Building studio
is problematic for use in eQuest -- Jeff Hirsch has looked at one made
the following evaluation:</SPAN></FONT></DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN class=559510216-30082006><FONT
size=1></FONT></SPAN></FONT> </DIV>
<DIV><FONT face="Lucida Console" size=2><SPAN class=559510216-30082006><FONT
size=1>It appears that the ACad -> gbXML software creates a building model
that is not easily used in eQUEST and cannot ever be used in the eQUEST wizard,
only in the detail mode. Since it uses an "Energy Plus" style of input model
description (i.e; surface geometry but no floor plan or space layout) it is not
really compatible with eQUEST for detail envelope or space/zone modification
without some difficulty ... since you cannot use eQUEST 2-d view (the primary
way of identifying and modifying space/zone data.)</DIV>
<DIV>
<P>Also, the building geometry is not correct and is difficult to really confirm
in eQUEST ... all the interior and exterior walls extend outside the roof or the
roofs are misplaced at Z low by a couple feet.</P>
<P>Since the creation process does not create any space (room geometry) but only
physically places walls at the site relative the location of the building on the
earth (i.e, it does not geometrically describe the spaces so that they can be
viewed in 2- and 3- dimensions, checking the placement of walls is not possible
(but there are visual problems such as the wall height I mentioned
earlier.)</P></FONT></SPAN></FONT></DIV>
<DIV><FONT face="Lucida Console" size=2></FONT> </DIV>
<DIV align=left>
<DIV align=left><FONT size=2><FONT face="Lucida Console">Does anyone know of an
expeditious way to transfer gbXML geometry data into eQuest accurately -- being
able use the wizards I could live without, so long as space / zone modification
possible <SPAN class=559510216-30082006>in detail edit mode. Or
alternatively, does anyone know if gbXML import is "in the works" for
a future version of eQuest?</SPAN></FONT></FONT></DIV>
<DIV align=left><FONT face=Arial size=2></FONT> </DIV>
<DIV align=left><FONT face="Lucida Console" size=2>Thanks</FONT></DIV>
<DIV align=left><FONT face=Arial size=2></FONT> </DIV><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">
<DIV><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><SPAN
class=212011020-11052004><FONT color=#000000>Brandon Nichols,
PE</FONT></SPAN></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><SPAN
class=212011020-11052004><FONT
color=#000000>Mechanical</FONT></SPAN></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#000080><STRONG>HARGIS ENGINEERS</STRONG></FONT></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#515151>600 Stewart Street</FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#515151>Suite 1000</FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#515151>Seattle, WA 98101<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#515151>www.hargis.biz<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#515151> <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">d
|</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">
206.436.04<SPAN class=212011020-11052004>0</SPAN>0<SPAN
style="mso-spacerun: yes"> </SPAN><B>c | </B>206.<SPAN
class=212011020-11052004>228.8707</SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><SPAN
class=212011020-11052004></SPAN></SPAN><FONT color=#515151><B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">o
|</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
206.448.3376<SPAN style="mso-spacerun: yes"> </SPAN><B>f <SPAN
style="mso-spacerun: yes"> </SPAN>|</B>
206.448.4450</SPAN></FONT></P></SPAN></SPAN>
<DIV> </DIV></DIV>
<DIV> </DIV><PRE>
==================
You received this e-mail because you are subscribed
to the BLDG-SIM@GARD.COM mailing list. To unsubscribe
from this mailing list send a blank message to
BLDG-SIM-UNSUBSCRIBE@GARD.COM
</PRE><PRE>
===========================
You received this e-mail because you are subscribed
to the BLDG-SIM@GARD.COM mailing list. To unsubscribe
from this mailing list send a blank message to
BLDG-SIM-UNSUBSCRIBE@GARD.COM
</PRE></BODY></HTML>