BIM Show Live 2015: Single or Multiple Models

17
School of Architecture © Prof Arto Kiviniemi 2015 Single or Multiple Models Prof Arto Kiviniemi School of Architecture

Transcript of BIM Show Live 2015: Single or Multiple Models

School of Architecture © Prof Arto Kiviniemi 2015

Single or Multiple Models

Prof Arto Kiviniemi

School of Architecture

School of Architecture © Prof Arto Kiviniemi 2015

Information is exchanged as documents

- often even on paper - which causes non-value-

adding work, friction, data losses and errors

Traditional document-based process

Arto Kiviniemi – VERA programme 1997

School of Architecture © Prof Arto Kiviniemi 2015

Information is shared in an exploitable data format between different systems

Integrated BIM process

Arto Kiviniemi – VERA programme 1997

IAI

1999

Vision: an Integrated Project Model

Goal: Continuous maintenance of project data through to building management

Way: Building information rather than drawing data to integrate disciplines

SHARED

PROJECT

MODEL

With IFC

Structural

Engineer

Architect

Civil

Engineer

HVAC

Engineer

Building

Owner

Controls

Engineer Facilities

Manager

Constr.

Manager

Structural

Engineer

Architect

Civil

Engineer

HVAC

Engineer

Building

Owner

Controls

Engineer Facilities

Manager

Constr.

Manager

Now

School of Architecture © Prof Arto Kiviniemi 2015

Common (mis)conception of integrated BIM

Structural team

Construction team

Maintenance team

Architectural team

M&E team

Integrated BIM

Arto Kiviniemi – CIFE/Stanford University 2004

School of Architecture © Prof Arto Kiviniemi 2015

Integrated BIM

Shared data

Domain specific & integrated BIM

Structural BIM

Construction BIM

Maintenance BIM

Architectural BIM

M&E BIM

Arto Kiviniemi – CIFE/Stanford University 2004

School of Architecture © Prof Arto Kiviniemi 2015

Common databases and libraries

BIM linked to internal and external information

Structural BIM

Construction BIM

Maintenance BIM

Architectural BIM

Integrated project model

Shared data

M&E BIM

Internal databases and libraries Internal databases and libraries

Internal databases and libraries Internal databases and libraries Internal databases and libraries

School of Architecture © Prof Arto Kiviniemi 2015

What is a model?

School of Architecture © Prof Arto Kiviniemi 2015

What is a model? • A model represents reality for the given purpose; the model is an

abstraction of reality in the sense that it cannot represent all aspects of reality.

Jeff Rothenberg "AI, Simulation & Modeling” 1989

• Different domains (architectural design, structural and HVAC engineering, construction tasks, FM…) have different models because they perform different tasks.

• The shared models must cover (at least) the parts necessary for the desired purpose(s) and defining the content and representation in a homogeneous way is not a simple task.

School of Architecture © Prof Arto Kiviniemi 2015

Architects’ view of the building

Copyright © Vladimir Bazjanac / LBNL 2007

School of Architecture © Prof Arto Kiviniemi 2015

Thermal view of the building

Transformation between views is a necessity!

Copyright © Vladimir Bazjanac / LBNL 2007

School of Architecture © Prof Arto Kiviniemi 2015

Who makes the transformation?

• Authoring software producing specific views for each receiving application •Do the vendors know what is required for different purposes? •Are all thermal models similar? •Can the designer know what to export for each purpose?

or

• Authoring software producing one (or few) generic views •Receiving software makes the transformation based on its own

needs; known content. • Is all required information available in the exchange file or

should the receiving software allow additional input?

School of Architecture © Prof Arto Kiviniemi 2015

One of the challenges: Object ≠ Object • The relation between objects in different models is not one-to-

one • Multiple objects in the architectural model can be a single object in the

structural model, e.g. columns and shafts divided by floor • One object in architectural model can be multiple objects in structural and/or

production models, e.g. slab • How to create and maintain the links?

• Different ways of modelling in different domains; nominal vs. real measures

• Objects are not always easy to classify • How to handle this in the ontologies?

Wall

Roof

?

School of Architecture © Prof Arto Kiviniemi 2015

Correct understanding of the purpose of

model exchange/sharing is essential!

School of Architecture © Prof Arto Kiviniemi 2015

Round tripping between domains?

Structural BIM

Maintenance BIM

Construction BIM

Architectural BIM

MEP BIM

School of Architecture © Prof Arto Kiviniemi 2015

Round tripping inside one domain?

IFC

export

IFC

import Parametric model

working environment

Native BIM in propriatory format (Revit, ArchiCAD, Tekla, Vectorworks...)

Exchange model in IFC format

?

Static model

snapshot at

a point of time

Image courtesy Granlund

School of Architecture © Prof Arto Kiviniemi 2015

Integrated BIM

Shared data

Sharing information/data between domains

Structural BIM

Architectural BIM

MEP BIM

Construction BIM

Maintenance BIM

Data retrieval = reference information of other

models, never taking your own data back

Updates from the original models