13.02.2013 Views

Advanced Building Simulation

Advanced Building Simulation

Advanced Building Simulation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Developments in interoperability 211<br />

The AF Models are translated into XML schemas in order to be machine readable.<br />

Each AF in fact represents a minimal “product model” and a (small) subschema of<br />

the kind presented in Section 8.2.3. In this case the subschema does not represent the<br />

input model of a simulation tool, but the combination of input and output of a particular<br />

analysis function irrespective of the simulation tool that will perform it.<br />

Typically the AF schema is much smaller than the subschema of the complete input<br />

and/or output model. The other difference is that AF schemas are not defined as<br />

“parts” of a bigger <strong>Building</strong> Model (as in Section 8.2.3) but as bottom-up defined<br />

schemas that define a modular and tool independent analysis step, which recurs<br />

routinely in design analysis scenarios.<br />

At run time an AF model needs to be populated through data interfaces that “pull”<br />

data from the models that reside in the building analysis model layer. The pull<br />

approach allows for a directed search of relevant information that resides on the<br />

upper layers of the workbench. Whenever building information is present in structured<br />

format, the data exchange from upper layer to the AF Model can be automated.<br />

However, the AF Model population interface may signal missing information and<br />

trigger manual input by the simulation expert. Since the AF Model only describes the<br />

elements that are critical for a small performance analysis, both the automatic part of<br />

the interface as well as the user guided constructive part represent small and manageable<br />

programming efforts for the developers. They will benefit greatly from<br />

emerging XML-based graphical (declarative) mapping languages. Each AF drives the<br />

connection and data exchange with the neighboring workbench layers. The principle<br />

of the approach is shown in Figure 8.16.<br />

Design info<br />

layer<br />

<strong>Building</strong> analyis<br />

model layer<br />

Analysis scenario<br />

layer<br />

Tool layer<br />

structured Ideas un-structured<br />

database<br />

WFM<br />

radiance<br />

esp-r<br />

CAD<br />

XMLschema<br />

XMLdocument<br />

energy+<br />

Figure 8.16 Analysis function as central driver in the data exchange topology.<br />

Post-it memos<br />

Aspect model<br />

IAI-IFC, Combine<br />

select:<br />

AF1<br />

AF2<br />

AF3<br />

AF4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!