3. 3
“Shared data model” (1998)
Architect Architect
Civil Structural Civil Structural
Engineer Engineer Engineer Engineer
Building HVAC Building Shared Data HVAC
Owner Engineer Owner Engineer
Model
Facilities Energy Facilities Energy
Manager Consultant Manager Consultant
Constr. Constr.
Engineer Engineer
4. 4
Misverstand:
Shared data model is NIET gelijk aan:
Shared model
Shared data
“Shared data model” is ontstaan uit de concrete behoefte om data te
(ver)delen op een gestandaardiseerde manier.
„shared data model‟ == afspraken maken
6. 6
Waarom dan toch „centrale servers‟?
Grote bestanden delen…
Delen van data wat deel je eigenlijk? Wat heef je
ketenpartner eigenlijk van je nodig om z‟n werk te doen?
Merging / synchronisatie
Revisiebeheer
Alerts
Enz…
Kan gewoon handig zijn...
…net als schoenen met ingebouwde CD speler.
7. Wat zijn er voor „BIM Servers‟?
Closed data model:
ArchiCAD teamwork / BIM Server
Revit Server
WAFS (file synchronisatie)
Onuma
Adomi
…..
Shared data model:
EDM model server (fidumo)
EuroStep (twijfel)
Open source BIMserver.org
+ spinoffs
…..
8. Welke moet ik kiezen?
Welke is het best geschikt als „centrale‟ server?
Huh?
14. Federated, distributed infrastructuur zodat er
meerdere „centrale‟ modellen kunnen zijn.
En laten we eens gaan nadenken wat we daarvan
gaan delen met partners, waarom, en wanneer…..
20. 20
NL: Gebruikt u een modelserver?
Bijna allemaal federated/distributed gebruik….
21. 21
Observaties:
Define what data you need, and why. Don just „share everything‟.
The best choice of concept to be used as central data
repository, depends on the place in the BIM framework („little
bim‟, „BIG BIM‟, „open BIM‟). In many situations it seems favorable to
use a combination of homogeneous software environment („little BIM‟
within a single company) and plural software environment („BIG BIM‟)
in a multidisciplinary collaboration project.
Project team members should be free to choose their own software
tools in order to achieve a higher performance in the execution of their
engineering tasks.
Source: Collaborative engineering, new insights (Berlo, Beetz)
22. 22
Observaties:
The result of individual tasks has to be synchronized. The
synchronization interval depends on several factors such as: the
preferences of the project team members, the project manager and
the project phase. Users in the experiments in this research did not
prefer a so-called „live synchronization‟. The median of
synchronization time of model instances was 1 week (every Friday of
every week was a widely used practice).
In a homogeneous software environment, users felt that all team
members should have equal BIM software modeling expertise. When
using the concept of reference models, not all project team members
collaborating in a project need to have the same level of BIM
expertise.
Source: Collaborative engineering, new insights (Berlo, Beetz)
23. 23
En nog een nabrander….
Considering the previous results, the additional conclusion can be
drawn that project partners can be chosen based on competence in
performing engineering tasks. The use of a reference model concept
with IFC can lower the needed BIM competences for a project partner
to be able to collaborate in a way that is sufficiently effective for the
entire project team. All respondents in this experiment were strongly
convinced that choosing project partners based on their competence
of a specific software tool, prior to their engineering competence, is
never preferred
Source: Collaborative engineering, new insights (Berlo, Beetz)
24. 24
Werken ín een (BIG BIM) „centraal‟ model lijkt
eerder nadelen dan voordelen te geven.
(eigendom van objecten, juridische aspecten, wijzigingsverzoeken, enz..)
