ontology of a heating system - dtu research database · “room o1-01.02” subclassof owner...

Post on 23-Jun-2020

2 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

+ =

SEAS FlowSystemOntology of a heating system

Mads Holten Rasmussen

NIRAS | DTU

May 4th 2017

Photo creds: Laymik, Nounproject

2 / 48 May 2017 mhra@niras.dk

About me

2011 B.Sc. Architectural engineering, DTU

2013 M.Sc. Architectural Engineering, DTU

20132016

HVAC-engineer, NIRAS (former ALECTIA) ~2100 employees, 6 offices in Denmark + more worldwideConsulting on construction and infrastructure projects

2016 Industrial PhD

”Digital Infrastructure and Building Information Modeling in the design and planning of building services”

3 / 48 May 2017 mhra@niras.dk

Disposition

01 Professional Background

02 Research Scope

03 SEAS FlowSystems

04 Overall Vision

05 Final Words

01Professional Background

Research Scope

02

8 / 48 May 2017 mhra@niras.dk

3x BIM-PhD

Construction Commissioning OperationDesign Planning

PhD 1 PhD 2 PhD 3

9 / 48 May 2017 mhra@niras.dk

3x BIM-PhD

Construction Commissioning OperationDesign Planning

PhD 1 PhD 2 PhD 3

Pil Brix Purup

10 / 48 May 2017 mhra@niras.dk

3x BIM-PhD

Construction Commissioning OperationDesign Planning

PhD 1 PhD 2 PhD 3

Pil Brix Purup

Mads Holten Rasmussen

11 / 48 May 2017 mhra@niras.dk

3x BIM-PhD

Construction Commissioning OperationDesign Planning

PhD 1 PhD 2 PhD 3

Pil Brix Purup My new colleague

Mads Holten Rasmussen

12 / 48 May 2017 mhra@niras.dk

“Digital infrastructure and Building Information Models in the design and planning of building services”

15 / 48 May 2017 mhra@niras.dk

The overall challenge

Architecturaldrawing

Heat losscalculation

16 / 48 May 2017 mhra@niras.dk

The overall challenge

Architecturaldrawing

Heat losscalculation

areaslenghts

room IDs

thermal requirements room usages

17 / 48 May 2017 mhra@niras.dk

The overall challenge

Architecturaldrawing

Heat losscalculation

18 / 48 May 2017 mhra@niras.dk

The overall challenge

Architecturaldrawing

Heat losscalculation

19 / 48 May 2017 mhra@niras.dk

The overall challenge

Architecturaldrawing

Heat losscalculation

20 / 48 May 2017 mhra@niras.dk

The overall challenge

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

21 / 48 May 2017 mhra@niras.dk

How to go from inter-linked documents to interlinked data?

solutionsemantic web technology

SEAS FlowSystems

03

23 / 48 May 2017 mhra@niras.dk

“A system, modeled by class seas:System, is part of the universe that is virtually isolated from the environment”

D2.2 SEAS Deliverable v1.0, 2016

24 / 48 May 2017 mhra@niras.dk

Heating systemssystems of systems

Supp

lyHea

t

Excha

nger

Mixin

g

Plant

Radia

tor

DHW

Tank

Radia

tor

Radia

tor

Radia

tor

Radia

tor

Radia

tor

Mixin

g

Plant

25 / 48 May 2017 mhra@niras.dk

“A system can be a sub-system of a unique other system”

D2.2 SEAS Deliverable v1.0, 2016

26 / 48 May 2017 mhra@niras.dk

Heating systemssystems of systems

Supp

lyHea

t

Excha

nger

Mixin

g

Plant

Radia

tor

DHW

Tank

Radia

tor

Radia

tor

Radia

tor

Radia

tor

Radia

tor

Mixin

g

Plant

Radiator System 1Main distribution systemDistrict heating

Radiator System 2subSystemOfsubSystemOf

27 / 48 May 2017 mhra@niras.dk

“A system may be connected to other systems that are part of its environment”

D2.2 SEAS Deliverable v1.0, 2016

28 / 48 May 2017 mhra@niras.dk

Overall connections

seas:conne

ctsAt

seas:conne

ction

PointOf

seas:connectsAt

seas:connection

PointOf

seas:exchangesFluidWith

seas:exchangesFluidWithseas:connectedThrough

seas:connectsSystem seas:conne

ctedThrough

seas:conne

ctsSyste

mseas:FlowSystem seas:FlowSystem

seas:connectsSystemThrough

seas:connects

SystemThroughseas:FlowPort seas:FlowPort

seas:FlowConnection

seas:connectsSystemAtseas:co

nnects

SystemAt

29 / 48 May 2017 mhra@niras.dk

Rules

§

“IF { ?x seas:subFlowSystemOf ?ss ; seas:exchangesFluidWith ?y .}THEN { ?y seas:subFlowSystemOf ?ss .

}”^^xsd:string

“Rule #1”^^xsd:string

rule:contentrdfs:label

rdfs:comment

rule:SPARQLRulerdf:type

“If one flow system is a sub-system of a super system, all flow systems that exchange fluid with it are part of that super system”^^xsd:string

Pipe

Radiator

Tee

seas:subFlowSystemOf

seas

:exch

ange

sFluid

With

seas

:exch

ange

sFluid

With

S1

30 / 48 May 2017 mhra@niras.dk

31 / 48 May 2017 mhra@niras.dk

HeatConsumer

seas:HeatConsumer

seas:FlowPort

rdfs:label

“Radiator 2”^^xsd:string

“Out”^^xsd:string

“In”^^xsd:string

seas:connectsAt

seas:connectsAt

rdf:type

rdf:type

rdf:type

seas:flowDirection

seas:flowDirection

seas:value

seas:value

32 / 48 May 2017 mhra@niras.dk

Heating system

seas:HeatConsumer

seas:fluidSupplyTemperatureseas:fluidReturnTemperature

seas:value

“Radiator 2”^^xsd:string

“55 Cel”^^cdt:ucum

“Heating System 1”^^xsd:string

seas:connectsAt

S1

seas:HeatingSystem

rdf:type

rdf:type

rdf:type

rdf:type

rdf:type

rdf:type

seas:FluidTemperatureProperty

seas:value

“35 Cel”^^cdt:ucum

seas:FlowPort

“Out”^^xsd:string

“In”^^xsd:string

seas:flowDirection

seas:flowDirection

seas:value

seas:value

rdfs:label

rdfs:label

seas:connectsAt

33 / 48 May 2017 mhra@niras.dk

Temperature SetInherited to ports

seas:subFlowSystemOf

seas:fluidFlowTemperature

seas:fluidFlowTemperature

seas:value seas:value “55 Cel”^^cdt:ucum

“Heating System 1”^^xsd:string

“35 Cel”^^cdt:ucum

S1

seas:HeatingSystem

rdf:type

rdf:type

rdf:type

seas:FluidTemperatureProperty

seas:HeatConsumer

“Radiator 2”^^xsd:string

seas:connectsAt rdf:type

rdf:type

rdf:type

seas:fluidSupplyTemperatureseas:fluidReturnTemperature

seas:FlowPort

“Out”^^xsd:string

“In”^^xsd:string

seas:flowDirection

seas:flowDirection

seas:value

seas:value

rdfs:label

rdfs:label

seas:connectsAt

34 / 48 May 2017 mhra@niras.dk

FlowDemandCalculated from output

seas:subFlowSystemOf

seas:fluidFlowTemperature

seas:fluidFlowTemperature

seas:value seas:value “55 Cel”^^cdt:ucum

“Heating System 1”^^xsd:string

“35 Cel”^^cdt:ucum

S1

seas:HeatingSystem

rdf:type

rdf:type

rdf:type

seas:FluidTemperatureProperty

seas:HeatConsumer

“Radiator 2”^^xsd:string

seas:connectsAt rdf:type

rdf:type

rdf:type

seas:fluidSupplyTemperature

seas:fluidType

seas:consumerHeatOutput

seas:consumerFlowDemand

seas:fluidReturnTemperature

seas:FlowPort

“Out”^^xsd:string

“In”^^xsd:string

seas:flowDirection

seas:flowDirection

seas:value

seas:value

“600 W”^^cdt:ucum

seas:value

“0.0258 m3/h”^^cdt:ucum

seas:value

rdfs:label

rdfs:label “Water”^^xsd:string

rdfs:label

seas:connectsAt

35 / 48 May 2017 mhra@niras.dk

Distribution system

Pipe

Mixing Plant

Pipe

Pipe

Radiator

Radiator

Pipe

Bend

Tee

exchanges fluid with

consumer flow demand

“0.026 m3/h”^^cdt:ucum

“0.043 m3/h”^^cdt:ucum

seas:consumerFlowDemand

seas:consumerFlowDemand

seas:consumerHeatOutput

seas:consumerHeatOutput

“600 W”^^cdt:ucum

“1000 W”^^cdt:ucum

36 / 48 May 2017 mhra@niras.dk

Inferencing volume flows

Pipe

Mixing Plant

Pipe

Pipe

Radiator

Radiator

Pipe

Bend

Tee

exchanges fluid with

consumer flow demand

“0.026 m3/h”^^cdt:ucum

“0.043 m3/h”^^cdt:ucum

seas:consumerFlowDemand

seas:consumerFlowDemand

seas:consumerHeatOutput

seas:consumerHeatOutput

“600 W”^^cdt:ucum

“1000 W”^^cdt:ucum

distribution volume flow

Distribution systems have an “indirect consumption”= consumption further out in the distribution tree

seas:distributionVolumeFlow a owl:ObjectProperty ; owl:propertyChainAxiom ( seas:exchangesFluidWith seas:consumerFlowDemand ) .

37 / 48 May 2017 mhra@niras.dk

Pipe

Mixing Plant

Pipe

Pipe

Radiator

Radiator

Pipe

Bend

Tee

exchanges fluid with

consumer flow demand

“0.026 m3/h”^^cdt:ucum

“0.043 m3/h”^^cdt:ucum

seas:consumerFlowDemand

seas:consumerFlowDemand

seas:consumerHeatOutput

seas:consumerHeatOutput

“600 W”^^cdt:ucum

“1000 W”^^cdt:ucum

distribution volume flow

inner pipe diameter

fluid velocity

“20 mm”

“0.15 m/s”

“0.11 m/s”“0.26 m/s”

Inferencing fluid velocities

Overall Vision

04

39 / 48 May 2017 mhra@niras.dk

Distributed knowledge

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

40 / 48 May 2017 mhra@niras.dk

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A”

“Storage room”

Something is a Room and it must have a physical connection to another Room

41 / 48 May 2017 mhra@niras.dk

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A”

“Storage room”

It must have an Area of minimum 12 m2 and fulfill Indoor Climate Class A

42 / 48 May 2017 mhra@niras.dk

“Room O1-01.02”subClassOf

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A”

The architect draws a Room that meets the owner’s requirements

43 / 48 May 2017 mhra@niras.dk

“Room O1-01.02”subClassOf

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A”

It gets assigned geometrical properties and a 2D- and 3D-representation

44 / 48 May 2017 mhra@niras.dk

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A” “Room O1-01.02”“Rum K1-01.02”

sameAs

The engineer further developes his own representation of the room, inheriting properties from the other parties

45 / 48 May 2017 mhra@niras.dk

Owner Architect Engineer Contractor

Building topology

Facilities ManagementTime ProvenanceStatics

AcousticsSensors3D-geometry2D-geometry

HVAC-symbols

Quantities

Units Commissioning

Fire safety

Geography

Functional requirements

Indoor Climate and Energy

Flow systems

“Office type A” “Room O1-01.02”“Rum K1-01.02”

sameAs

...and further assigns Requirements for the System to meet the Indoor Climate Requirements etc.

Final Words

05

47 / 48 May 2017 mhra@niras.dk

UI example

HR - heating, return

HF - heating, flow

Office 2.1 Corridor

Office 2.2

Storage KitchenCanteen

Office 1.1

Office 3.1

WC1

WC2

48 / 48 May 2017 mhra@niras.dk

Summary

• Today: static calculations• Future: on the fly reasoning

Explicit knowledge model of a flow system• Response on design changes• Consequence analysis• Better system control• Transparency

top related