13.02.2013 Views

Advanced Building Simulation

Advanced Building Simulation

Advanced Building Simulation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This chapter introduces the technologies to achieve interoperability on different<br />

levels. It then reviews a number of existing approaches to develop integrated systems<br />

followed by the in-depth discussion of a new initiative in design analysis integration<br />

that combines interoperability and groupware technologies. The last section draws<br />

conclusions about the state of the art and possible next steps.<br />

8.2 Technologies for interoperability<br />

Developments in interoperability 191<br />

The previous section introduced PDT as the key-enabler of interoperability. It<br />

provides the methods and tools to develop seamless connections of software applications.<br />

The connections at the application side is typically implemented as front and<br />

backend interfaces that read/write and interpret/translate data from other (upstream)<br />

applications and produce data in a format that can be interpreted by other (downstream)<br />

applications. Achieving interoperability for building simulation applications<br />

will for instance require that design information from CAD systems can be read and<br />

automatically translated to the internal native simulation model representation,<br />

whereas the simulation outputs are in some form aggregated and automatically translated<br />

back to a neutral format which can be read by the CAD system or by other software<br />

tools such as code checking procedures, HVAC layout applications, lighting<br />

fixture design tools, or simple client report generators.<br />

Achieving interoperability relies on the ability to identify, gather, structure, generalize,<br />

and formalize information that is exchanged between the variety of building<br />

design and engineering applications. Product models attempt to capture this information<br />

in static and generic representations. It is important to make the distinction<br />

between this product data-centric description and the information that describes the<br />

process context in which product data is exchanged. Process models capture the logic<br />

of the data generation and exchange processes that lead to the various states of the<br />

design. Hitherto, the focus of PDT is mainly on the first category of information.<br />

Process information becomes critical when one needs to manage the deployment of<br />

interoperable tools in a given scenario of use. Anticipating and coordinating the tasks<br />

in real-life scenarios require information about decision-making, design evolution<br />

and change management processes, assignment of roles and responsibilities of design<br />

actors, their possible, even their design rationale, etc. It enables the “orchestration”<br />

of the deployment of applications and other project tasks. In that case the suite of<br />

interoperable tools is embedded in a process managed interoperable system, that<br />

helps system users to execute the control over the exchange events. Section 8.2.1 deals<br />

with the data centric part of interoperability. Sections 8.2.2 and 8.2.3 then discuss the<br />

role of the process context and the technologies that are available to build integrated<br />

systems. It concludes with a brief overview of a prototype system built according to<br />

the ideas introduced in this section.<br />

8.2.1 Data-centric interoperable systems<br />

The area of interoperability in A/E/C has received considerable attention over the last<br />

fifteen years. An overview of projects during this period can be found in Eastman (1999).<br />

In different sectors of the A/E/C industry research and standardization initiatives were<br />

started pursuing the development of a common shared building representation. These

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

Saved successfully!

Ooh no, something went wrong!