1 / 52

MP308-3 Heating and Cooling Load Calculations and Energy Model Development From an Autodesk® Revit® MEP Model Utilizing

MP308-3 Heating and Cooling Load Calculations and Energy Model Development From an Autodesk® Revit® MEP Model Utilizing gbXML. Phillip Cunningham, EIT, LEED AP Mechanical Engineer, KlingStubbins. About the Speaker.

erek
Download Presentation

MP308-3 Heating and Cooling Load Calculations and Energy Model Development From an Autodesk® Revit® MEP Model Utilizing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MP308-3 Heating and Cooling Load Calculations and Energy Model Development From an Autodesk® Revit® MEP Model Utilizing gbXML Phillip Cunningham, EIT, LEED AP Mechanical Engineer, KlingStubbins

  2. About the Speaker Phillip Cunningham EIT, LEED AP joined KlingStubbins in 2006 after earning Bachelor’s degrees in both Architectural Engineering and Civil Engineering from Drexel University. He has contributed to many of the firm’s large commercial and laboratory projects in the areas of mechanical system design, LEED certification, and life-cycle analysis. His efforts in Building Performance Energy Modeling and Building Information Modeling (BIM) have improved KlingStubbins’ ability to fulfill their commitment to incorporating sustainable design practices into their projects. Contact Information: pcunningham@klingstubbins.com

  3. About the Firm Architecture Engineering Interiors Planning Philadelphia, PA Cambridge, MA Raleigh, NC San Francisco, CA Washington, DC Beijing, China

  4. About the Audience • Contractors, CM’s, Owners? • Sales and Service? • Architecture? • Engineering? • Digital Office? Using BIM? • Use of gbXML?

  5. Learning Objectives • Understand how gbXML works • Explore the use of gbXML in various applications • Typical challenges encountered creating accurate gbXML • Discussion of model management and workflow using gbXML

  6. BIM, meet sustainable design… What is BIM? • Documentation • Visualization • Quantification • Coordination • Logistics • Simulation/Analysis • Fabrication

  7. Complex, Interrelated Simulations

  8. Climate Utility Rate Operating Profiles Annual Energy Consumption Solar Gain Ventilation Mechanical Systems Building Simulation Fuel Mix Materials Internal Loads

  9. What is gbXML? • XML – Extensible Markup Language • XML stores data and allows transport between applications • Strict File Structure ensures compatibility • gbXML is a schema of XML created specifically for buildings • Converts a 3d model to text arranged in a hierarchy • It does not do anything. It carries information from point A to point B.

  10. Why do I need gbXML? • Represents building geometry • Stores other data related to load calculations • Provides a common conduit between applications • Should save time and improve accuracy over manual entry.

  11. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML>

  12. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML> A treelike hierarchy of ELEMENTS.

  13. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML> A treelike hierarchy of ELEMENTS. Each element has one or more VALUES and children ATTRIBUTES.

  14. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML> A treelike hierarchy of ELEMENTS. Each element has one or more VALUES and children ATTRIBUTES.

  15. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML> A treelike hierarchy of ELEMENTS. Each element has one or more VALUES and children ATTRIBUTES. Elements can repeat, but structure is always enforced. SYNTAX is required.

  16. What does gbXML LOOK like? <gbXML> <Campus id="cmps-1"> <Location> <Name>User Defined</Name> </Location> <Building id="bldg-1"> <Space id="sp-101"> <Name>101</Name> <Area>100</Area> </Space> </Building> <Surface id="su-sp-101" surfaceType="SlabOnGrade"> <AdjacentSpaceId spaceIdRef="sp-101" /> <RectangularGeometry> <Azimuth>0</Azimuth> <Tilt>180</Tilt> <Height>4.2</Height> <Width>10</Width> </RectangularGeometry> </Surface> </Campus> <Zone id="zone-Default"> <Name>Default</Name> </Zone> </gbXML> A treelike hierarchy of ELEMENTS. Each element has one or more VALUES and children ATTRIBUTES. Elements can repeat, but structure is always enforced. SYNTAX is required. Schema prescribes fixed values called ENUMERATIONS.

  17. How BIG is gbXML? • 388ELEMENTS and ATTRIBUTES • Hundreds more ENUMERATIONS • UNLIMITED file/storage capacity • Not all available elements used

  18. Elements used by Revit MEP

  19. Elements used by Trace700

  20. Only common gbXML are transferrable

  21. How is gbXML used? • 2-D representations • Trace700 • HAP • 3-D representations • IES VE • Ecotect • Non-geometrical Data • Internal loads • Occupancy • Zone assignments • System configuration • Utilization Schedules

  22. How is gbXML used? • Space properties exported to third party software • Simulation tools evaluate the input • Calculated results are brought back into model • Results populate space properties • Can be tied to duct and equipment sizing, schedules, and more

  23. Creating gbXML in Revit MEP • Place Spaces • Fill ALL voids • Space separation lines to bound open areas. • Use zones to combine spaces. • Set plenum or occupancy.

  24. Helpful guides for creating spaces • Revit MEP 2010 User’s Guide • CADLearning video on Creating Spaces • Inside-the-system Blog (search various related postings)

  25. Exporting and Reviewing gbXML Tasks: • Review spaces and analytical surfaces • Isolate rooms and surfaces • Settings for export • Review warnings Complaints: • Cramped viewer • Select rooms in view • Partial export options • Complexity of export

  26. Surface Naming Convention (Orientation)-(Space#)[-(Other space#)]-(Exposure)-(Type)-(sequence number) [Opening Type+#] Orientation: Direction/Azimuth of Surface N,NE,E,SE,S,SW,W,NW T = top of horizontal surface B = bottom of horizontal surface X = horizontal shade element Exposure: Exterior (“E”), Interior (“I”), or Underground (“U”) Type: Wall (“W”), Roof (“R”), Ceiling (“C”), Floor (“F”), Shade (“S”) Opening Type: Window (“W”), Door (“D”), Opening (“O”)

  27. Surface Type Determination

  28. Common gbXML Issues: Plenums above ceilings

  29. Common gbXML Issues: Complex Vertical Volumes

  30. Common gbXML Issues: Slivers and Gaps

  31. Common gbXML Issues: Architect’s Room Separation Lines • Can not be ignored in MEP model • Often used for several uses; not ideal zoning • Compromise with architects

  32. Common gbXML Issues: Curtain Walls • Material Transparency >3% • Export complexity refers to openings only • Simple: exports a single surface • Complex: exports as multiple surfaces, panel by panel • With shading: surface with export any unknown surface as a shade • With mullions: all surfaces exported separately

  33. Common gbXML Issues: Curtain Walls Simple Complex

  34. Curtain Wall Types • Not all curtain walls are made the same way. • Embedded walls • Cleaner export, reduced flexibility • Panel systems • Fragmented exported, greater architectural flexibility • Facets….forget it.

  35. gbXML interpretation by 3rd party applications • Data conversion to “fit” existing platforms • Rotations/Azimuth • Slabs, underground walls • Plenums • Shading Devices • Internal Loads Data may not be importing how you assume!

  36. 3rd party gbXML handling • Partial importing options • Overwriting/replacing data • Know how data is matched (Name, ID, CAD Object ID) • Potential for some creative data handling!

  37. Push the limits: What else gbXML do for me? • Explore the schema • Create and modify data

  38. Using elements not support by Revit <AirLoop id=“FCU-1" systemType="FanCoil“><Name>FCU-1</Name></AirLoop>

  39. Create gbXML manually Several XML editors available online, too!

  40. View and Edit gbXML in Excel

  41. Create gbXML with VBA

  42. Why go to such extremes? • Design moving target • Repairing inaccurate data • Supplementing incomplete data • Exploring alternatives • More iterations = Better Decisions

  43. Example 1: Changing Glass Area

  44. Example 2: The “No-Model” Model

  45. Workflow Issues • Incomplete Models • Overdeveloped Models • “Cleaning up” gbXML • Take-off models are NOT parametric! • Space upkeep • Verifying accuracy • So many spaces! • Are we any better off than hand take-offs??

  46. The Ideal Workflow Geometry, Load criteria Analytical Model BIM Model Load and Simulation results

  47. The (unfortunate) Actual Process Arch model gbXML-1 gbXML-2 Simulation model

  48. BIM waits for no one… Arch model

  49. Coordinated Parallel Models

  50. Moving Forward • Where is gbXML headed? • Who maintains it? • Open source • gbXML advisory board • Autodesk? • What else could/should it do? • Dynamic worksharing • Simplify architecture • Improve feedback for accuracy • Data transferred consistent with simulation needs

More Related