# Presentation: 698492

## Building Data ExchangeSoftware Interoperability

- Robert J. Hitchcock, Ph.D.
- Building Technologies Department
- Lawrence Berkeley National Laboratory

**This work is supported by the U.S. Department of Energy and the California Energy Commission**

## Overview

**What is software interoperability?**
**What does interoperability offer?**
**In general**
**For building simulation**
**Current interoperability data standards.**
**Current state of these standards.**
**Current software implementation status.**

## What Is Software Interoperability?

- Ability to archive and exchange detailed building data between project participants and their various software tools.
- Exchange is based on commonly agreed upon building data model standards.
- Different software tools import/export common data by mapping their internal representation to the data model standard.

## What Does Interoperability Offer?

- Data Acquisition from Upstream Participants & Tools
- Data Archival for Downstream Participants & Tools

**Notes:**
To understand the benefits of interoperability, we should view it within the context of information management across the complete life cycle of a building project.  Not only the usual focus of the design phase.
The holy grail of interoperability is a standard data repository that would allow us to archive data at any point in the life cycle, from any software tool in use at that point, so that we can acquire data from upstream participants and tools (e.g., architects and CAD), and archive data for access by downstream participants and tools (e.g., building operators and FM tools).

## Data Acquisition from Upstream

- Geometric Data
- Building Elements
- Building Equipment
- Non-Geometric Data
- Material Properties
- Building Services Equipment Properties
- Building Systems Operation

**Notes:**
What are some of the specific benefits of interoperability to those of us involved in building simulation?
Data acquisition from other participants within the same phase (e.g., design) is also part of this picture.
For example, you might import geometric data from architectural CAD into your HVAC design software where you add data like thermal zoning and duct layouts, and pass these data on to other design team members like the electrical engineer.

## Data Archival for Downstream

- Building and System Design Performance
- Expected Loads
- Equipment Performance
- Design Performance Benchmarks
- Simulation Context Data
- Occupancy & Usage
- Thermal Zoning
- Building Systems Operation
- Weather

**Notes:**
A more long term benefit of data interoperability is that key data regarding the designed building performance and operation can be archived for downstream access by building operators and renovators.

## Current Interoperability Data Standards

- Object Data Model
- Object-oriented model of the entire building
- Elements (e.g., Walls) and Relationships (e.g., Walls->Space)
- Archive and exchange complete project data set
- Industry Foundation Classes (IFC)
- Internet Data Exchange Models
- Extensible models of data subsets
- Product libraries (e.g., Chillers)
- Exchange of product and other data subsets to support transactions over the Internet
- XML: aecXML, ifcXML

**Notes:**
The types of data we have just been talking about can only be exchanged between different participants and their tools if we have defined standards for how those data will be represented.
There are currently two languages, or flavors of data standards for interoperability that are being worked on.

## Current State of Object Data Model

- Geometric Data
- Location, Shape, and Relationships of Building Elements
- Site, Building, Building Story, Space, Wall, Window, Door, Column, Beam, Stair, Furniture, Boiler, Chiller, Pump, Fan, etc.
- Non-Geometric Data
- Material Properties
- Thermal Conductivity, Specific Heat Capacity, Boiling Point
- Equipment Properties
- e.g., Boiler: Type, Heat Output, Pressure Rating, Energy Input Rate, Heat Transfer Rate, Thermal Efficiency, Energy Source
- Building Services Project 8 – HVAC for Simulation
- http://eetd.lbl.gov/btp/iai/bs8

## Current State of XML Data Model

- E-Commerce
- Initial draft based on existing models
- Building Simulation
- Initial draft based on existing simulation tools
- IFC to XML conversion
- GPC 20 - Definitions for HVAC&R
- Monday 8:30am-12noon CC/208

## Implementation Status

- CAD including HVAC Design
- Model Viewing/Checking
- Energy Simulation
- Energy Code Checking
- Cost Estimation
- Construction Planning
- Software Development Toolboxes

**Notes:**
5 CAD, 3 Model Viewing, 2 Energy Simulation, 1 Energy Code Checking, 1 Cost Estimation, 1 Construction Planning, 2 Toolboxes

## Implementation Caveats

- Certified Compliance vs. Full Functionality
- Focused on Geometry
- Different Released Versions of Standard
- Not Mature Implementations
- Minimal Real Project Experience