They select the predefined IFC export called Energy Analysis MVD. For example, if an architect needs to deliver their model for energy analysis, they don’t just do a data dump of the entire model. It allows users to export specific packages of model information to meet a particular use. An MVD is essentially a filtered view of the IFC. This is achieved with Model View Definitions, or MVDs. More than this, in an openBIM workflow, we can predefine exactly what information needs to be transferred when and by whom. If changes to a model are required, these are tracked and reported on. In this setup, no-one can access or change the model content of another discipline. Secondly, we have the collaborative environment where IFC copies of these models are viewed and coordinated. So, we can divide the BIM process into two realms: Firstly, we have the native authoring environment where models are created and edited (this is the private domain of each discipline). These models, or copies of them, are then exchanged at agreed intervals. Every project participant has their own model, of which they are the sole author. In the openBIM workflow there is no single central model that everyone can access and modify as they like. openBIM standards, in particular, give us very strict controls for data exchange.

It’s about defining specific protocols and workflows. It’s not just about collaboration and sharing. BIM is actually a very structured way of working.

“How can we all possibly work on a single model?” “How do we control who does what, when?” These fears are based on a lot of misunderstandings. One of the big fears surrounding BIM is that there is a loss of control.

Allplan wiki