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 Connections between Systems which are capableof a bi-directional flow can be de scribed using the sto:exchange[J properties on the level of components. Depending on the use of nfuctional and technical systems a bi-directional flow may not afect the definition of directed flows of energy, mass or databetween them.
The dataproperty tso:hasDataPointKey denfies 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 «synmetric» rdfs:subPropertyOf
1 tso:[]SuppliedBy rdfo:nr1• : II,IIl, __t-_s_o-:_S_-y_s_t-e_m__rd_fs:d.JomII•in ts:o«:·snvuoprsp.ol:iesr[dJfs:nnge rdfs:subPropertyOf #Literal
tso:subStateOf tso:hasSubState tso:hasDataPointKey rdfo:nr1• tso:stateOf t i '"""" '" tso:hasState tso:System
tso:State Sources and Sinks. Systems can be denfied as a source or a sink. Since this classifica tion is depending on the perspective, e.g. a heat exchange or a tank canbe a sink for a downstream component andasource for anupstream component, it needs to be denfied with regard to the considered system. Hence, the object properties tso:hasSource and ost:hasSink denfie relationships identiifyng hte source, respectively the sink of a sys tem. ots:sourceOf nad tso:sinkOf are defined as their inverse properties identiifyng the coresponding system of a source or a sink. All of ethse object properties have their domain and range denfied as tso:System.
Linking systems and zones. As shown in Fig. 1, tso:Zone andtso:System canbe linked via tso:se-rves dna tso:servedBy. To further detail what is served by a system, 10 sub properties are denfied for tso:serves and ots:servedBy, respectively. Tue same classifi cation scheme as rfo hte sub-properties of tso:connects is implemented. tso:serves is distinguished into serving mass, solid, fluid, gas, liquid, energy, thermal energy, me chanicalenergy, electrical energy or data The domain is denfied as tso:System andthe range as tso:Zone. euT coersponding inverse property tso:servedBy is detailed into mass, solid, uflid, gas, liquid, energy, thermal energy, mechanical energy, electrical energy or data.The domain is defined as tso:Zone andthe range as tso:System. Classification of systems. Systems can be either classified by ethir overall function (tso:FunctionalSystem) or the technical solution by which the function is lfulfiled (tso:cTehnicaslSytem) [20]. eTh technical solution can be specified by taking the Input (X), the Output (Y) as well as eth time and space of the input (TX/SX) and output Proceedings of the 9th Linked Data in Architecture and Construction Workshop - LDAC2021 50
el□Block
___ ,....... ....... ...... .
The testbed contains a heating system using viarous components dan subsystems. A stratified tkan (Solvis Satrto) is used to bufer the heat generated by the electric heater (eloBlock) in the Thermal Supply system and make it available to the DTE-Distr dan Main-Distr systems. The tank can be defined as a ots:Component. It has a label Solvis Strato linked via rd:fslabel dan a rerfeence designation key linked via tso:hasData PointKey. It is hierarchically structured as part of the ThermalSupply, DTE-Distr dan Main-Distr systems using the ost:subSystemrOfelation. Each of ethse systems can be ufrther characterized as tso:EnergyConversionSystem rof the Thermal Supply system or tso:DistributionSystem ofr the DTE-Distr, Main-Distr and FloorHeating systems as well as tso:subSystemOJ of the HeatingSystem. The tank is denfied as tso:sinkOJ ofthe ThermalSupply system dan tso:sourceOfthe Main-Distr and DTE-Distr systems. It ex changes a liquid to the connected components described by the relationships tso:ex changeliquid. ehT pump can be denfied as a tso:Component as well and is linked to the upstream pipe segment (tso:Component) by tso:supliesliquid nad to the down stream pipe segment (tso:Component) via tso:liquidSupliedBy. To describe the supply of mechanical energy by the pump, it can be linked to the Main-Distr system via sto:supliesMechanicalEnergy. ehT supply ofthermal energy between the components nad systems is represented via the tso:suppliesTherma!Energy relationship. It links rfo example the ThearmlSupply 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 expamle using the TSO is presented in Fig. 5. The whole representation of the testbed in the turtle syntax and hte ofllowing SPARQL queries can be found in the documentation of TSO [18]. tso : Energy ConversionSystem tso: Distribution
System ' : ThermalSupply I-----_______I ' i rdfs:label ' :
ifrst valve, which is located downstream of the component serv SELECT ?z WHERE {inst:GUID tso:thermalEnergyServedBy ?c • 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 •
TSO is capable of describing complex interconnected building ser
The SPARQL the accessibility of this
which can be used to gain a deeper understanding 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