Cosas susceptibles de posesión.

The BIM model server platform used in the case study was EDMmodelServer™, which supports functions of user control and access, model and data management. Octaga Modeller is used in conjunction with EDMmodelServer™ for 3D model viewing. Solibri Model Viewer and DDS-CAD Viewer were also used in conjunction for viewing specific models and checking object information and relationships in the model. Solibri Model Checker is used in model checking for data verification. Design review of the construction for different discipline- specific models provides data verification to ensure the accuracy of the BIM model. Figure 3.17 shows the integrated BIM model in EDMmodelServer™ that enable building information integration and sharing across disciplines.

Figure 3.17 The integrated BIM model

EDMmodelServer™ as a Collaboration Platform

Issues regarding the integration of IFC files of different discipline-specific models into an integrated BIM model in EDMmodelServer™ include:

• IFC name settings

• Security management (e.g. user control and authority settings) • Model management

• User interface

• Data management (e.g. object properties and IDM - Information Delivery Management)

64 Spatial Containment Identity: The spatial containment model of IFC is a hierarchy: project, site, building and building storey(s). For successful model synchronisation the GUID (….) must match. For example when the hydraulic sub-model from DDS-CAD was uploaded to the model server, in order to merge it with the architectural model, the GUID of each spatial entity must match.

IFC name settings: Before merging different IFC files, it is very important to confirm the consistency of IFC names in each discipline-specific models. Normally, IFC names are set in the modelling applications for each discipline. They can also be modified by editing the IFC files. The following IFC name settings were used for the Seawater Chamber case study:

ifcProject : CRC Project 1 ifcSite : CRC

ifcBuilding : CRC Building ifcBuildingStorey : Basement

Security management functions control the access settings of repositories, users and groups. Figure 3.18 shows user, group and access maintenance controls in EDMmodelServer™. Different access rights to the building information can be set including the rights to create, delete, execute, private, write, read and none.

Figure 3.18 User, group and access maintenance controls in EDMmodelServer™ as applied in the Seawater Chamber case study

To login to EDMmodelServer™, users must provide information such as user name, user group, password and settings of Host and Port (Figure 3.19), which provides controlled access to the database.

65 Figure 3.19 Login control of EDM Model Server

Model management supports different means for managing the BIM model and data sets. The main features in this category are listed in Figure 3.20.

Figure 3.20 Managing models in EDMmodelServer™ (image taken from EDM Model Server User Guide)

User interface of EDMmodelServer™ consists of two main parts, including text-based information windows and a 3D model viewer (Figure 3.21). Octaga Modeller is the plug-in software that enables viewing of the 3D model. Text-based information windows present information for:

• Repositories with different models.

• IFC Tree with different hierarchies, such as Project, Site, Building and Story. • Report for Project, Site, Building and Story.

66 • IFC Browser

Figure 3.21 User interface of EDMmodelServer™

Data management of EDMmodelServer™ include features for managing object properties and information delivery management (IDM). These details can be applied for further applications, for instance, cost estimation and construction management.

67 Figure 3.22 Presentation of building information in different views for data management

Information delivery management (IDM) defines processes and user specifications to audit model data and server transactions. IDM in EDMmodelServer™ is defined by a script and stored in the Admin Menu of EDMmodelServer™. Figure 3.23(a) shows three IDMs of EDMmodelServer™. Exchange requirement definitions and individual clusters of IDM are written in ExpressX and are editable. An IDM is associated with an import or export in the dialogue to act as a filter on the exchange (Figure 3.23(b)).

68 Figure 3.23 (a) IDM defined in EDM Model Server and (b) IDM being a filter for data exchange in

EDMmodelServer™

Figure 3.23 (a) above shows several generic collaboration processes: for example Exchange

Basic Building - an Architect sharing with engineering consultants, Exchange Structural

Design (Outline Conceptual) - a structural Engineer collaboration with an Architect and,

several other options. While many of these may be generic, it is likley there will be national and project specific versions required.

Figure 3.23 (b) shows an import of a complete building model to be checked by the

Exchange Basic Building IDM, ensuring that all information sought is provided in the IFC

69 Seawater Chamber Integrated Model in EDMmodelServer™

As discussed earlier, the Seawater Chamber case study consists of the three disciplines, architecture, hydraulics and lighting. By using different modelling applications, three discipline-specific models were constructed and then converted into IFC files. To merge IFC files of these models in EDMmodelServer™, firstly, the architectural model is uploaded into EDMmodelServer™ in a model named UNew that stands for the University of NEwcastle. In the UNew directory of repositories, the hydraulic and lighting discipline-specific models are then checked-in to UNew model and merged with the architectural model to form the Seawater Chamber integrated BIM model, as shown in Figure 3.24.

Figure 3.24 The Seawater Chamber integrated BIM model in EDMmodelServer™

In developing the Seawater Chamber integrated model, some problems were encountered. They are discussed in the following section, which become a part of the base for developing the technical requirements to be presented in the end of the report.