references and resources · 01 baggrund 1 / 47 bsi | october 2017 mhraniras.dk references and...
TRANSCRIPT
01Baggrund
1 / 47 bSI | October 2017 [email protected]
References and resourcesRepository (Work in Progress - should work by mid November, and also an online demo will be available)https://github.com/MadsHolten/forge-sparql
Building Topology Ontology (BOT)https://raw.githubusercontent.com/w3c-lbd-cg/bot/master/bot.ttl
Project page on ResearchgateNew findings, presentations etc. will be shared here - please join the discussion and follow the project!https://www.researchgate.net/project/Building-Topology-Ontology-BOT
Initial paper on the Building Topology Ontology (BOT) - LC3-2017, Heraklionhttps://doi.org/10.24928/JC3-2017/0153
Paper on the recent changes in the Building Topology Ontology (BOT) - LDAC-2017, Dijonhttps://www.researchgate.net/publication/320631574_Recent_changes_in_the_Building_Topology_Ontology
Paper on the software implementation - LDAC-2017, Dijonhttps://www.researchgate.net/publication/320757039_Web-based_topology_queries_on_a_BIM_model
Linked Building DatabuildingSMART summitLondon, 2017Mads Holten Rasmussen
NIRAS | DTU
October 31st 2017
01Baggrund
3 / 47 bSI | October 2017 [email protected]
About me
2011 B.Sc. Architectural engineering, DTU
2013 M.Sc. Architectural Engineering, DTU
20132016
HVAC-engineer, NIRAS (former ALECTIA)2,100 employees - offices in 27 countries
2016 Industrial PhD
”Digital Infrastructure and Building Information Modeling in the design and planning of building services”
01Problem in Scope
01Baggrund
Slidetitel
5 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
A real life experience
Designing HVAC systems at Axel Towers, Copenhagen
Contractor
Architect
Engineer
01Baggrund
7 / 47 bSI | October 2017 [email protected]
Problem in scope
Architecturaldrawing
Heat losscalculation
01Baggrund
8 / 47 bSI | October 2017 [email protected]
Problem in scope
Architecturaldrawing
Heat losscalculation
areaslenghts
room IDs
thermal requirements room usages
01Baggrund
9 / 47 bSI | October 2017 [email protected]
Problem in scope
Architecturaldrawing
Heat losscalculation
01Baggrund
10 / 47 bSI | October 2017 [email protected]
Problem in scope
Architecturaldrawing
Heat losscalculation
01Baggrund
11 / 47 bSI | October 2017 [email protected]
Problem in scope
Architecturaldrawing
Heat losscalculation
01Baggrund
12 / 47 bSI | October 2017 [email protected]
arch-drawing heat loss calc. Heating units
U-value calc.
Regulations
Plant diagram Pumps
Valves
BMSFunctionaldescription
Vent. plants VentilationMech. plans
Heating plants
Meters
Pipe sizing Distributiondiagram
Mech. plans
Mech. plans
Motors High voltage
BMS
01Baggrund
Slidetitel
13 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
We are quite good at modeling geometry,but how about everything around it?
01Baggrund
14 / 47 bSI | October 2017 [email protected]
What do you see?
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
Space 1 Space 2 Space 3
TT
kWh
temperature transmitter PP pressure pocket TI temperature indicator filter gate valve commissioning valve
manual thermostatic valvemodulating motor valve H,flowenergy meter speed adjustable pump H,return
01Baggrund
15 / 47 bSI | October 2017 [email protected]
What the architect sees
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
Space 1 Space 2 Space 3
Office type 1
one persontwo persons
Office type 2 Copy room
01Baggrund
16 / 47 bSI | October 2017 [email protected]
What the indoor climate engineer sees
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
Thermal zone 1 Thermal zone 2 Thermal zone 3
Equipmentloads
Heat losses
Lighting demandPeople load
LoadSchedules
Solar heatgains
Cooling demand
Heating demand
01Baggrund
17 / 47 bSI | October 2017 [email protected]
What the automation engineer sees
TT
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
Control zone 1 Control zone 2
Sensor
Setpoint temp.
Actuator
Controlled device
temperature transmitter
modulating motor valve
01Baggrund
18 / 47 bSI | October 2017 [email protected]
What the automation engineer sees
TT
kWh
temperature transmitter
energy meter speed adjustable pump
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
Heated zone 1 Heated zone 2
Sensor
Actuator (frequency converter)
Energymeter Controlled device
(pump)
Setpoint temp.
Heat circulation system 1
01Baggrund
19 / 47 bSI | October 2017 [email protected]
What the HVAC engineer sees
TT
TI
TT
TI
TT
IT
PP
PP
PP
TI
kWh
TT TT
TT
kWh
temperature transmitter PP pressure pocket TI temperature indicator filter gate valve commissioning valve
manual thermostatic valvemodulating motor valve H,flowenergy meter speed adjustable pump H,return
Heated zone 1 Heated zone 2
Primary side
Shut-off for maintainance
Valve pre-setting
Pump sizeMonitoring
Mixing plant
Filter
Pressure dropFlow velocity
Terminal / consumer
Valve sizeTT TT
Secondary side
01Baggrund
20 / 47 bSI | October 2017 [email protected]
And the...
?
building owner
facility manager
carpenter
plumber
fire engineer
acoustician
structural engineer
lighting designerbank
end-user
tenant
contractor
authorities
01Baggrund
Slidetitel
21 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
Same dataDifferent interpretationsand needs
01Baggrund
22 / 47 bSI | October 2017 [email protected]
Another example
Texture, color
Hygrothermal properties
Maintainance requirements
Usage restrictionsSecondary functionHeating? cooling?
Fire resistance
Acoustic properties
Static properties
BIM and Semantic Web
02
01Baggrund
24 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
Subject
predicate
Object
A triple
01Baggrund
25 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
WallA
hasWindow
Window13
A triple
01Baggrund
26 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
WallA
hasWindow
Window13
frameC
olor
“green”
“24”
“true”openable
type
No
Subject
Subject and object
Literal (value)
Objects can be literals (simple datatypes)
01Baggrund
27 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
frameC
olor
“green”
“24”
“true”openable
type
No
<http://www.niras.dk/prj1454/Walls/A2>
<http://www.niras.dk/prj1454/Windows/13>
hasWindow
Subject
Subject and object
Literal (value)
URIs as Global Identifiers
:host/:db/:type/:id
01Baggrund
28 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
Turtle syntax
prefix:
frameC
olor
“green”
“24”
“true”openable
type
No
inst:Walls/A2 inst:Windows/13
hasWindow
Subject inst: <http://www.niras.dk/prj1454/>
Subject and object
Literal (value)
01Baggrund
29 / 47 bSI | October 2017 [email protected]
RDFResource Description Framework
predicates and datatypes also have namespaces
ont:fr
ameC
olor
ont:openable
ont:t
ypeN
o
“green”^^xsd:string
“24”^^xsd:integer
“true”^^xsd:boolean
inst:Walls/A2 inst:Windows/13
ont:hasWindow
Subject inst: <http://www.niras.dk/prj1454/>ont: <http://www.alectia.com/ontology#>
xsd: <http://www.w3.org/2001/XMLSchema#>Subject and object
Literal (value)
01Baggrund
Slidetitel
30 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
BOTA simple Ontology to modelBuilding Topology
01Baggrund
31 / 47 bSI | October 2017 [email protected]
BOTBuilding Topology Ontology
bot:Elementbot:Zone
bot:Site bot:Building bot:Storey bot:Space
An area or stretch of land having a particular characteristic, purpose, or
use, or subject to particular restrictions
Zone Subclasses
Constituent of a construction entity with a characteristic technical function,
form or position
01Baggrund
32 / 47 bSI | October 2017 [email protected]
Relationships
bot:Elementbot:Zone
bot:containsZonebot:adjacentZoneowl:symmetricProperty owl:transitiveProperty
bot:hostsElement
owl:propertyChainAxiom
( bot:containsZone bot:containsElement )
bot:containsElement
bot:adjacentElement
Zones can have adjacent zonesIF <zoneA> bot:AdjacentZone <zoneB> THEN <zoneB> bot:AdjacentZone <zoneA>
Zones can contain other zonesIF <zoneA> bot:containsZone <zoneB> AND <zoneB> bot:containsZone <zoneC> THEN <zoneA> bot:containsZone <zoneC>
Zones can contain building elementsIF <zoneA> bot:containsZone <zoneB> AND <zoneB> bot:containsElement <elA> THEN <zoneA> bot:containsElement <elA>
Zones can have adjacent building elements
Building elements can “host“ other building elements
01Baggrund
33 / 47 bSI | October 2017 [email protected]
Relationships
bot:Elementbot:Zonebot:containsElement
bot:adjacentElement
bot:containsZone
bot:hasSpacebot:hasStoreybot:hasBuilding
bot:adjacentZonerdfs:subPropertyOf
bot:hostsElement
( bot:containsZone bot:containsElement )
bot:Site bot:Building bot:Storey bot:Space
owl:symmetricProperty owl:transitiveProperty
owl:propertyChainAxiom
If <A> has the relationship: bot:hasBuilding to <B> the following can be inferred:
<A> is a and a .
<B> is a and a .
<A> bot:containsZone <B>
bot:Site
bot:Building
bot:Zone
bot:Zone
01Baggrund
34 / 47 bSI | October 2017 [email protected]
bot:Elementbot:Building
bot:Zone
<buildingA> <spaceK2>
<spaceB3>
<window1>
<wall23>
type typetypetype
bot:hasSpace
bot:Space
type typetypetype
subClassOfsubClassOf
type
bot:adjacent Element
bot:adjacentElement
bot:hostsElementbot:adjacentZone
<heaterT3>
bot:containsElement
bot:containsElement
bot:hasSpacebot:containsZone
bot:containsZone
bot:containsZonebot:hasSpace
subPropertyOfproperty
ChainAxiom
bot:hostsElement
bot:adjacentZonesymmetric transitive
bot:adjacentElementbot:containsElement
( bot:containsZone bot:containsElement )
TERMINOLOGY
DATA
01Baggrund
Slidetitel
35 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
DEMO
Distributed Knowledge
03
01Baggrund
Slidetitel
37 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
Isn’t bot:Spaceand bot:Element too generic?
01Baggrund
38 / 47 bSI | October 2017 [email protected]
bot:Space bot:Element
fso:Heater
rdfs:subClassOf
bot:Zone
rdfs:subClassOf
rdfs:subClassOf
sco:WCRoomTERMINOLOGY
DATA
SCO Space Classification OntologyFSO Flow Systems Ontology
Aligning with BOT
Sub-classes
01Baggrund
39 / 47 bSI | October 2017 [email protected]
Sub-classes
rdf:type
<spaceA12> <heater33>
rdf:type
rdf:type
bot:Space
rdf:type
bot:Element
fso:Heater
rdfs:subClassOf
bot:Zone
rdfs:subClassOf
rdfs:subClassOf
sco:WCRoomTERMINOLOGY
DATA
A WC Room is a ZoneIF <spaceA12> rdf:type sco:WCRoom THEN <spaceA12> rdf:type bot:Zone
A Heater is a Building ElementIF <heater33> rdf:type fso:Heater THEN <heater33> rdf:type bot:Element
01Baggrund
40 / 47 bSI | October 2017 [email protected]
Sub-properties
rdf:type
<spaceA12> <heater33>
rdf:typefso:heatedBy
rdf:type
bot:Space
fso:heatedBy
bot:containsElement
bot:containsElement
rdfs:subPropertyOf
rdfs:range
rdfs:range
rdfs:domain
rdf:type
bot:Element
fso:Heater
rdfs:subClassOf
bot:Zone
rdfs:subClassOf
rdfs:subClassOf
sco:WCRoomTERMINOLOGY
DATA
Zones can be heated by a HeaterIF <spaceA12> fso:heatedBy <heater33> THEN <spaceA12> bot:containsElement <heater33>
IF <spaceA12> fso:heatedBy <heater33> THEN <heater33> rdf:type fso:HeaterIF <heater33> rdf:type fso:Heater THEN <heater33> rdf:type bot:Element
01Baggrund
41 / 47 bSI | October 2017 [email protected]
etc. etc.
rdf:type
<spaceA12><hd1> <heater33>
rdf:type
“600 W” “500 W”
fso:heatedByice:heatingDemand
fso:heatOutput
prop:Value prop:Value
rdf:type
bot:Space
fso:heatedBy
bot:containsElement
bot:containsElement
rdfs:subPropertyOf
rdfs:range
rdfs:range
rdfs:domain
rdf:type
bot:Element
fso:Heater
rdfs:subClassOf
bot:Zone
rdfs:subClassOf
rdfs:subClassOf
sco:WCRoom
rdf:type
prop:Property
rdf:type
prop:Property
TERMINOLOGY
DATA
<ho1>
01Baggrund
42 / 47 bSI | October 2017 [email protected]
Architect
<http://some-arch.com/projects/100100/Walls/123>
bot:Element
rdf:type
prod:Wall
rdf:type
ifc:IfcWall“20.3 m2” “360 mm”
rdf:type
props:areabsdd:area
props:thickness
01Baggrund
43 / 47 bSI | October 2017 [email protected]
Energy
<http://some-arch.com/projects/100100/Walls/123>
<http://some-eng.com/projects/100222/Interfaces/23>
bot:Element
rdf:type
bot:Interface
props:uValuebsdd:heatTransfer
prod:Wall
rdf:type
ifc:IfcWall“20.3 m2” “360 mm”
“0.21 W/m2K”
“10.5 m2”
rdf:type
props:areabsdd:area
props:thickness
rdf:type
ds418:heatTransmissionAreaprops:heatTransmissionArea
“0.13 m2K/W”props:surfaceResistance
bot:interfaceOf
01Baggrund
44 / 47 bSI | October 2017 [email protected]
Statics
<http://some-arch.com/projects/100100/Walls/123>
<http://other-eng.com/projects/123211/Reinf/23>
<http://some-eng.com/projects/100222/Interfaces/23>
bot:Element
rdf:type
bot:Interface
props:uValuebsdd:heatTransfer
prod:Wall
rdf:typerdf:type
ifc:IfcWall“20.3 m2” “360 mm”
“0.21 W/m2K”
props:concreteStrengthbsdd:strength
stat:reinforcementDefinition
“20 MPa”
stat:verticalBars
“10.5 m2”
rdf:type
props:areabsdd:area
props:thickness
rdf:type
stat:ReinforcementDefinition
ds418:heatTransmissionAreaprops:heatTransmissionArea
“0.13 m2K/W”props:surfaceResistance
bot:interfaceOf
“5 bars/m”
01Baggrund
Slidetitel
45 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
No need to discuss“one model” vs. “multiple models”
- different data sources togethercompose the model
01Baggrund
Slidetitel
46 / 47 bSI | October 2017 [email protected] / 47 bSI | October 2017 [email protected]
DEMO
01Baggrund
47 / 47 bSI | October 2017 [email protected]
Final words
- Modular schema
- Some schemas are there already. Some will need to be developed - Reuse as much as possible and align with what is already there
- Queries possible through standardised language: SPARQL
- Distributed datasets combined to a whole
- As a service solutions needed for smaller companies to get started