Presented in buildingSMART Summit (Jeju, Korea, 28 Sept. 2016) In the Technical Room Session #5

1. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Tarcisio Mendes de Farias, Ana Roxin, Christophe Nicolle
ana-maria.roxin@u-bourgogne.fr

2. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Agenda
Motivation
• General context presentation
• Model View Definition (MVD)
IFC DynamicIFC Dynamic
Views
• A rule-based system for defining user views
• Case study: COBieMVD
Case studies
• Institut Var
• Medical Clinic
• High-school
2

3. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
MOTIVATION
3

4. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Combining ifcOWL and MVD
4
ifcOWL
MVD
How to
combine
them ?

5. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Related Problem
5
◼ Model View Definitions (MVDs) can be serialized in mvdXML format
mvdXML 1.0
mvdXML 1.1 - outcome of the buildingSMART International Project S1015
"Enabling trust in BIM deliveries"
◼ Main drawbacks of mvdXML for extracting building views:
Lack of logical formalisms
MVD solely considers the IFC schema
MVD-based view constructors aren't very flexible and dynamic

6. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
DEFINING IFC DYNAMIC VIEWS
6

7. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Types of Views
7
An abstract view can
be pre-defined as a set
of logical rules by using
ifcOWL vocabulary
• Those rules can be stored
with building data and
schema
A concrete view can be
automatically
generated based on
rules and the ifcOWL
ontology (populated)
Users can easily define rule-
based views !

8. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Defining Views through Rules
8
Abstract views
• Pre-defined, stored and
exchanged
Concrete views
• Built from IFC data
• Using abstract view
definitions (i.e. rules).
Easily configurable
• Set of concepts (C)
• Set of GUIDs (G)
• Set of IFC relationships (R)
A rule-based system to construct
building views

9. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
View Definition Process
9

10. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Defining a building envelope view
Horn-like rules
•Specify which
elements are part
of the view
Horn-like rules
•Definition of new
concepts
pertaining to the
considered view
Horn-like rules
•Map the newly
defined concepts
to the view
10
∧ ∧ ∧
∧
∧ ∧ ∧
∧
ifcowl:IfcObject(X1) ∧ ifcowl:IfcRelDefines(X2) ∧ ifcowl:relatedObjects…(X2 , X1) ∧ ifcowl:relatingPropertyDefinition… (X2
, X3) ∧ ifcowl:IfcPropertySet(X3) → :hasPropertySet(X1 ,X3)
aei:hasPropertySet(X1 , X2) ∧ ifcowl:hasProperties… (X2 , X3) ∧ ifcowl:IfcProperty(X3) → :hasProperty(X1 , X3)
aei:hasProperty(X1 , X3) ∧ ifcowl:name_IfcProperty(X3, X4) ∧ expr:hasString(X4 , "IsExternal”) ∧ ifcowl:nominalValue…
(X3, X5) ∧ expr:hasBoolean(X5 , X6)→ :isExternal(X1 , X6)
∧
∧
aei:isExternal(X , true) ∧ ifcowl:IfcWall(X) → :ExternalWall(X)
aei:isExternal(X , true) ∧ ifcowl:IfcDoor(X) → :ExternalDoor(X)
aei:isExternal(X , true) ∧ ifcowl:IfcWindow(X) → :ExternalWindow(X)
:ExternalDoor(X) → :BuildingEnvelope(X)
:ExternalWall(X) → :BuildingEnvelope(X)
:ExternalWindow(X) → :BuildingEnvelope(X)
For simplicity's sake, we consider as a building
envelope all external doors, windows and walls

11. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
APPLICATION CASE STUDIES
11

12. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
The Duplex building project
◼ Produced in Weimar (Germany) for a design competition
12

13. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Export phase inputs
13
C = {BuildingEnvelope}
G = { }
R = { IfcRelDecomposes, IfcRelContainedInSpatialStructure,
IfcRelVoidsElement, IfcRelFillsElement, IfcRelDefinesByProperties }.

14. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Additional case studies
Institute Var Medical clinic High-school
14

15. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Project: Institute Var
File sizes Original SPF file : 6 MB
Generated TTL file (with all original data): 35 MB
Building
view
Format: STEP Physical file
Query: All building doors
SPF size : 2.11 MB
15
C = {IfcDoor}
R = { IfcRelDecomposes,
IfcRelContainedInSpatialStructure,
IfcRelVoidsElement, IfcRelFillsElement,
IfcRelDefinesByProperties }.

16. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Project: Medical clinic
File sizes Original SPF file : 107 MB
Generated TTL file (with all original data): 689 MB
Building view Query: All building doors and windows
SPF size : 1.64 MB
16
C = {IfcDoor, IfcWindow}
R = { IfcRelDecomposes,
IfcRelContainedInSpatialStructure,
IfcRelVoidsElement, IfcRelFillsElement,
IfcRelDefinesByProperties }

17. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Project: High-school
File sizes Original SPF file : 111 MB
Generated TTL file (with all original data): 762 MB
Building
view
Query: All building doors and stairs
SPF size : 21.5 MB
17
C = {IfcDoor, IfcStair}
R = {IfcRelDecomposes,
IfcRelContainedInSpatialStructure,
IfcRel-VoidsElement,
IfcRelFillsElement,
IfcRelDefinesByProperties }

18. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Conclusions
Benefits of using MVD with
semantic web technologies
Less or no code needed
Storage of abstract view along with data and
schema
Users can easily define building views:
• GUIDs, IFC concepts or personalized concepts (rules)
Benefits of semantic web
rule syntax
Automatic generation of concrete views
Easier exchange and implementation of
abstract views
No need to develop an mvdXML parser
Everything is already coded in the semantic
graph database
18

19. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
Tarcisio Mendes de Farias, Ana Roxin, Christophe Nicolle
ana-maria.roxin@u-bourgogne.fr
Thank you for your attention !

20. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
20
Model 1 Model 2 Model 3 … Model N
e.g IFC e.g. bSDD
(extra data than IFC)
Exchange requirement = Subset of information from the different considered models ?
e.g. {subset of Model1} ∩ {subset of Model2} ∩ {subset of ModelN}
e.g. Energy model
if YES, 2 solutions with Semantic Web Technologies:
- either SPARQL query
- either define a rule (IF -> THEN )

21. AnaROXIN–ana-maria.roxin@u-bourgogne.fr
21
IFCOWL bSDD
IfcWindow Window^^@EN
Fenêtre^^@FR
Fenster^^@DE
http://server_name_IfcWindow_#GUID http://bsdd_server_window_EN_trans
http://bsdd_server_window_FR_trans
hasTransEN
hasTransFR