=Paper= {{Paper |id=Vol-3081/04paper |storemode=property |title=TUBES system ontology: Digitalization of building service systems |pdfUrl=https://ceur-ws.org/Vol-3081/04paper.pdf |volume=Vol-3081 |authors=Nicolas Pauen,Dominik Schlütter,Jérôme Frisch,Christoph van Treeck |dblpUrl=https://dblp.org/rec/conf/ldac/PauenSFT21 }} ==TUBES system ontology: Digitalization of building service systems== https://ceur-ws.org/Vol-3081/04paper.pdf
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




Copyright 2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0)




                                          43
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          44
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          45
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          46
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          47
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          48
  Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




   Connections between Systems which are capable of a bi-directional flow can be de­
scribed using the tso:exchange[J properties on the level of components. Depending on
the use of functional and technical systems a bi-directional flow may not affect the
definition of directed flows of energy, mass or data between them.
   The data property tso:hasDataPointKey defines a relationship which assigns a ref­
erence designation to a system. The domain is defined as tso:System. The functional
concept is shown in Fig. 3.


      tso:exchange[J
                                                                       #Literal                        tso:subStateOf   tso:hasSubState

            «synmetric»


                                                                            tso:hasDataPointKey
                          rdfs:subPropertyOf


                                   1
                                                                                                  t
                                       tso:[ ]SuppliedBy                                     tso:stateOf


                                                                                                  i '""""�'"
                            rdfo:nr111•                                             rdfo:nr111•
                                           :

  ,     tso:System                         � «·nvors..o:               tso:System                               tso:State
  I                         rdfs:dom•in    :               rdfs:nnge
  I
  I                I                      tso:supplies[J                                    tso: hasState
  I   ----         I
  l, ____________ .J
        rdfs:subPropertyOf



                                                    Fig. 3. Functional concept of TSO

Sources and Sinks. Systems can be defined as a source or a sink. Since this classifica­
tion is depending on the perspective, e.g. a heat exchange or a tank can be a sink for a
downstream component and a source for an upstream component, it needs to be defined
with regard to the considered system. Hence, the object properties tso:hasSource and
tso:hasSink define relationships identifying the source, respectively the sink of a sys­
tem. tso:sourceOf and tso:sinkOf are defined as their inverse properties identifying the
corresponding system of a source or a sink. All of these object properties have their
domain and range defined as tso:System.

Linking systems and zones. As shown in Fig. 1, tso:Zone and tso:System can be linked
via tso:se-rves and tso:servedBy. To further detail what is served by a system, 10 sub­
properties are defined for tso:serves and tso:servedBy, respectively. Tue same classifi­
cation scheme as for the sub-properties of tso:connects is implemented. tso:serves is
distinguished into serving mass, solid, fluid, gas, liquid, energy, thermal energy, me­
chanical energy, electrical energy or data The domain is defined as tso:System and the
range as tso:Zone. Tue corresponding inverse property tso:servedBy is detailed into
mass, solid, fluid, gas, liquid, energy, thermal energy, mechanical energy, electrical
energy or data. The domain is defined as tso:Zone and the range as tso:System.

Classification of systems. Systems can be either classified by their overall function
(tso:FunctionalSystem) or the technical solution by which the function is fulfilled
(tso:TechnicalSystem) [20]. The technical solution can be specified by taking the Input
(X), the Output (Y) as well as the time and space of the input (TX/SX) and output




                                                                           49
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          50
  Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                                                 ___         ,.   ...........   .............   ............ .
                                     HeatingSystem
                                                                                       FloorHeating




                                           el□Block

                                                                        DTE-Dis tr




                                     ThermalSupply




                                Fig. 4. Application example

The testbed contains a heating system using various components and subsystems. A
stratified tank (Solvis Strato) is used to buffer the heat generated by the electric heater
(eloBlock) in the Thermal Supply system and make it available to the DTE-Distr and
Main-Distr systems. The tank can be defined as a tso:Component. It has a label Solvis
Strato linked via rdfs:label and a reference designation key linked via tso:hasData­
PointKey. It is hierarchically structured as part of the ThermalSupply, DTE-Distr and
Main-Distr systems using the tso:subSystemOfrelation. Each of these systems can be
further characterized as tso:EnergyConversionSystem for the Thermal Supply system
or tso:DistributionSystem for the DTE-Distr, Main-Distr and FloorHeating systems as
well as tso:subSystemOJof the HeatingSystem. The tank is defined as tso:sinkOJof the
ThermalSupply system and tso:sourceOfthe Main-Distr and DTE-Distr systems. It ex­
changes a liquid to the connected components described by the relationships tso:ex­
changeliquid. The pump can be defined as a tso:Component as well and is linked to
the upstream pipe segment (tso:Component) by tso:suppliesliquid and to the down­
stream pipe segment (tso:Component) via tso:liquidSuppliedBy. To describe the supply
of mechanical energy by the pump, it can be linked to the Main-Distr system via
tso:suppliesMechanicalEnergy. The supply of thermal energy between the components
and systems is represented via the tso:suppliesTherma!Energy relationship. It links for
example the ThermalSupply system to the DTE-Distr system and subsequently to the
PWH system, which is defined as a tso:SanitarySystem. The PWH system is serving a
zone in which some of the components are located. A brief representation of the appli­
cation example using the TSO is presented in Fig. 5. The whole representation of the
testbed in the turtle syntax and the following SPARQL queries can be found in the
documentation of TSO [18].




                                            51
        Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                    tso: Energy                  tso:Distribution
                                                                      System                                      tso:Sanitary
                                 ConversionSystem
                                                                                                                     System
    '                            '                                               '                   '
                                 i                                                                                               ,-
                                                                                                                                                 '''
                                                                                                                                                 '
                                                                                                                                 ,''
    : ThermalSupply                                                              :   DTE-Distr        :
    I------       _______I                                                       I------ _______I                                         PWH
                                                                                                                                  "------ -------'
                      rdfs: label                                              rdfs: label
                                                                                                                        inst:   rdfs :label
                                                                                                _ T-he- rm-a1-,-,,- - - GUID
                                                                              --,,-, ,-so-ppl_ l,-,               rg y

                                                                             tso: subSystemOf
                                                                                                             tso: serves




                                                                                                          tso: located In



f
,,_ -+AB01.BC03              '
                             °

                             '<1 1--------                     1---------
                                                                 tso: exchangeLiquid

                                                               _________,. GUID
                                                                                     inst:
                                                                                           ___
                                                                                              __,
      - - - - - - - - - - - _,
                                                                tso: exchangeliquid




                                 ,         -----,
                                 : SolvisStrato  i
                                 I ______________I   tso: Component                      tso: Component



                                                 Fig. 5. Application example using the TSO

Example SPARQL queries which were implemented are described below. To select the
planned states of a system, the following query can be used:
SELECT ?state WHERE {inst:GUID tso:hasState ?state}
   The location of the first valve, which is located downstream of the component serv­
ing thermal energy to a zone can be selected by this query:
SELECT ?z WHERE {inst:GUID tso:thermalEnergyServedBy ?c •
                 ?c tso:liquidSuppliedBy+ ?c2 .
                 ?c2 a ifc:IfcValve •
                 ?c2 tso:locatedin ?z •
                 ?z a tso:Zone }
                 LIMIT 1
   The following query to be used to select the location of the source of the electrical
system, which supplies electrical energy to this valve:
SELECT ?z WHERE {inst:GUID tso:subSystemOf ?s •
                 ?s a tso:ElectricalSystem .
                 ?s tso:hasSource ?c •
                 ?c tso:locatedin ?z •
                 ?z a tso:Zone}
   This shows that TSO is capable of describing complex interconnected building ser­
vice systems and to link these with the spatial structure. The SPARQL queries visualize
the accessibility of this information, which can be used to gain a deeper understanding
of the underlying system.




                                                                        52
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          53
Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021




                                          54