Skip to content
GitLab
Commits (2)
Hide whitespace changes
Inline Side-by-side
.saref-repositories.yml
View file @ c7363cc3
forge.etsi.org/rep/:
labs.etsi.org/rep/:
repos:
- saref/saref-core
- saref/saref4syst
......
documentation/abstract.md
View file @ c7363cc3
SAREF4LIFT is an OWL-DL ontology that extends SAREF for the Smart Lifts domain. This SAREF extension is based on a limited set of use cases and existing data models identified within available initiatives that was detailed in previous documents ETSI TR 103 546 [[i.1]](#[i.1]) and ETSI TS 103 735 [[i.2]](#[i.2]). The work conducted in the present document has been developed in the context of the <a href="https://portal.etsi.org/STF/STFs/STF-HomePages/STF602">STF 602</a>, which was established with the goal of creating SAREF extension for the domain mentioned above, i.e. Smart Lifts. This work has been developed in close collaboration with the industrial world and alliances.
SAREF4LIFT is an ontology that extends SAREF for the Smart Lifts domain. This SAREF extension is based on a limited set of use cases and existing data models identified within available initiatives that was detailed in previous documents ETSI TR 103 546 [[i.1]](#[i.1]) and ETSI TS 103 735 [[i.2]](#[i.2]). The development of SAREF4LIFT has been conducted in the context of the <a href="https://portal.etsi.org/STF/STFs/STF-HomePages/STF602">STF 602</a>, which was established with the goal of creating SAREF extension for the domain mentioned above, i.e. Smart Lifts. This work has been developed in close collaboration with the industrial world and alliances.
One of the tasks of STF 602 consists of specifying and producing the extension of SAREF for the aforementioned domain based on the requirements resulting from previous initiatives. The related initiatives and use cases considered for the development of the SAREF4LIFT extension are the ones reported previously in ETSI TR 103 546 [[i.1]](#[i.1]) and ETSI TS 103 735 [[i.2]](#[i.2]). Such related initiatives and use cases are not repeated in this document. Hence, the reader can rely on those references for further details.
......
documentation/description.html
View file @ c7363cc3
......@@ -29,7 +29,7 @@
<li>Individuals are denoted by rectangles in which the identifier is underlined.</li>
</ul>
<p>SAREF4LIFT is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 510 <a href="#[i.1]">[i.1]</a>) and can thus be mainly described by the following self-contained knowledge modules:</p>
<p>SAREF4LIFT is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 510 <a href="#[i.4]">[i.4]</a>) and can thus be mainly described by the following self-contained knowledge modules:</p>
<ul>
<li><strong><a href="#Systems_and_connections">Systems and connections</a>.</strong> This module defines the different systems modelled within a smart lift environment. A system is described as a component virtually isolated from the environment, whose behaviour and interactions with the environment are specifically defined. Systems can be connected to other systems. Connected systems interact in some ways. Systems can also have subsystems. Properties of subsystems somehow contribute to the properties of the supersystem.</li>
......@@ -38,16 +38,16 @@
<li><strong><a href="#Signals">Signals</a>.</strong> This module describes the types of signals supported by a smart lift. Four type of signals have been identified:, car signal (<a href="#s4lift:AlarmSignal">s4lift:AlarmSignal</a>), fault signal (<a href="#s4lift:FaultSignal">s4lift:FaultSignal</a>), status signal (<a href="#s4lift:StatusSignal">s4lift:StatusSignal</a>), and statistic signal (<a href="#s4lift:StatisticSignal">s4lift:StatisticSignal</a>). The <a href="#Signal">section on Signals</a> provides a complete taxonomy of supported signals with respect to the ones reported in <a href="#Figure_1">Figure 1</a>.</li>
</ul>
<p>Beside the four module described above, the SAREF4LIFT extension defines also two new property types (<a href="#s4lift:Load">s4lift:Load</a> and <a href="#s4lift:Voltage">s4lift:Voltage</a>) defining the load in the smart lift car and the electric voltage of some electric power system.</p>
<p>Besides the four module described above, the SAREF4LIFT extension defines also two new property types (<a href="#s4lift:Load">s4lift:Load</a> and <a href="#s4lift:Voltage">s4lift:Voltage</a>) defining the load in the smart lift car and the electric voltage of some electric power system.</p>
<h3 id="Systems_and_connections">Systems and connections</h3>
<p>This module specializes the SAREF4SYST ontology pattern for the Smart Lift domain.</p>
<p>A Smart Lift system can be defined as a <a href="https://saref.etsi.org/saref4syst/System">s4syst:System</a> made by different components. This module defines the subcomponents that are part of Smart Lift. In particular, we denoted two subcomponents: the <a href="#s4lift:SmartLiftEdgeComponent">s4lift:SmartLiftEdgeComponent</a> and the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>. The former is dedicated to the hosting of smart lift additional modules in the case that they are not hosted directly in the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>.
<p>A Smart Lift system can be defined as a <a href="https://saref.etsi.org/saref4syst/System">s4syst:System</a> made by different components. This module defines the subcomponents that are part of Smart Lift. In particular, two subcomponents are denoted: the <a href="#s4lift:SmartLiftEdgeComponent">s4lift:SmartLiftEdgeComponent</a> and the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>. The former is dedicated to the hosting of smart lift additional modules in the case that they are not hosted directly in the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the <a href="#s4lift:SmartLiftEdgeControlUnit">s4lift:SmartLiftEdgeControlUnit</a>.
The latter is the main element of a Smart Lift installation and it is typically associated with the lift control cabinet.</p>
<p>A <a href="#s4lift:SmartLiftInstallation">s4lift:SmartLiftInstallation</a> corresponds to a single lift, with all its elements. Such a concept is equipped with the list of properties shown in Figure 2. Seven types of installations are considered relevant for this extension: namely s4lift :AccessibleGoodsOnlySmartLift as per [EN 81-31], s4lift: FirefightersSmartLift as per [EN 81-72], <a href="#s4lift:GoodsSmartLift">s4lift:GoodsSmartLift</a>, and <a href="#s4lift:MachineRoomLessSmartLift">s4lift:MachineRoomLessSmartLift</a>, <a href="#s4lift:PassengerAndGoodsPassengerSmartLift">s4lift:PassengerAndGoodsPassengerSmartLift</a> as per [EN 81-20], <a href="#s4lift:SmartLiftWithoutEmergencyCallSupport">s4lift:SmartLiftWithoutEmergencyCallSupport</a>, <a href="#s4lift:VerticalSmartLiftingPlatform">s4lift:VerticalSmartLiftingPlatform</a> as per [EN 81-41]. All these concepts represent a type of smart lift that can be instantiated by the ontology.</p>
<p>A <a href="#s4lift:SmartLiftInstallation">s4lift:SmartLiftInstallation</a> corresponds to a single lift, with all its elements. Such a concept is equipped with the list of properties shown in Figure 2. Seven types of installations are considered relevant for this extension: namely <a href="#s4lift:AccessibleGoodsOnlySmartLift">s4lift:AccessibleGoodsOnlySmartLift</a> as per EN 81-31 <a href="[2]">[2]</a>, <a href="#s4lift:AccessibleGoodsOnlySmartLift">s4lift:AccessibleGoodsOnlySmartLift</a> as per EN 81-72 <a href="[3]">[3]</a>, <a href="#s4lift:GoodsSmartLift">s4lift:GoodsSmartLift</a>, and <a href="#s4lift:MachineRoomLessSmartLift">s4lift:MachineRoomLessSmartLift</a>, <a href="#s4lift:PassengerAndGoodsPassengerSmartLift">s4lift:PassengerAndGoodsPassengerSmartLift</a> as per EN 81-20 <a href="[4]">[4]</a>, <a href="#s4lift:SmartLiftWithoutEmergencyCallSupport">s4lift:SmartLiftWithoutEmergencyCallSupport</a>, <a href="#s4lift:VerticalSmartLiftingPlatform">s4lift:VerticalSmartLiftingPlatform</a> as per EN 81-41 <a href="[5]">[5]</a>. All these concepts represent a type of smart lift that can be instantiated by the ontology.</p>
<p>A <a href="#s4lift:SmartLiftGroup">s4lift:SmartLiftGroup</a> represents the correlation of multiple Smart Lifts Installation and it is supported by the introduction of a Smart Lift Group identifier common each Smart Lifts Installation belonging to the same Smart Lift Group. Such kind of installations usually presents control units connected one each other to coordinate the movement and position of the different lifts, where the common commands (e.g. the call buttons) are given to one of these control units that acts as a principal master and coordinates the other installations or is composed by peer installations that coordinates one each other.</p>
......@@ -64,7 +64,7 @@ The latter is the main element of a Smart Lift installation and it is typically
<h3 id="Devices_and_commands">Devices and commands</h3>
<p>This model specifies the list of commands that we considered relevant for the smart lift domain. We defined six new commands that are subsumed by the saref:Command concept that can be triggered, in turn, by a <a href="https://saref.etsi.org/core/Function">saref:Function</a> as presented in <a href="#Figure_3">Figure 3</a>:</p>
<p>This model specifies the list of commands that is considered relevant for the smart lift domain. Six new defined commands that are subsumed by the saref:Command concept that can be triggered, in turn, by a <a href="https://saref.etsi.org/core/Function">saref:Function</a> as presented in <a href="#Figure_3">Figure 3</a>:</p>
<ul>
<li><a href="#s4lift:MainBoardResetCommand">s4lift:MainBoardResetCommand</a> defines the command for resetting the main board of a smart lift;</li>
......@@ -105,7 +105,7 @@ The latter is the main element of a Smart Lift installation and it is typically
<li><a href="#s4lift:StatusSignal">s4lift:StatusSignal</a>: these are signals that convey (<a href="#s4lift:conveys">s4lift:conveys</a>) a saref:State of a feature of interest.</li>
</ul>
<p>Descendants of the <a href="#s4lift:Signal">s4lift:Signal</a> inherit the <a href="https://saref.etsi.org/core/hasTimestamp>saref:hasTimestamp</a> , <a href="https://saref.etsi.org/core/isAbout>saref:isAbout</a>, and <a href="#s4lift:conveys">s4lift:conveys</a> properties defining the timestamp when the signal has been generated, the features of interest that the signal is about, and the states or measurements conveyed, respectively.</p>
<p>Descendants of the <a href="#s4lift:Signal">s4lift:Signal</a> inherit the <a href="https://saref.etsi.org/core/hasTimestamp">saref:hasTimestamp</a>, <a href="https://saref.etsi.org/core/isAbout">saref:isAbout</a>, and <a href="#s4lift:conveys">s4lift:conveys</a> properties defining the timestamp when the signal has been generated, the features of interest that the signal is about, and the states or measurements conveyed, respectively.</p>
<figure>
<a href="diagrams/TS103735_Clause_6_2_5_Signals.png"><img src="diagrams/TS103735_Clause_6_2_5_Signals.png" alt="Signals model."/></a>
......
documentation/examples.html
View file @ c7363cc3
<p>This clause shows different examples of how to instantiate the SAREF4LIFT extension of SAREF.</p>
<p>The example presented in Figure 6 demonstrates how to represent information from group name SLIdentification as described in ETSI TS 103 735, Clause 6.2a.</p>
<p>The example presented in Figure 6 demonstrates how to represent information from group name SLIdentification as described in ETSI TS 103 735 <a href="[i.2]">[i.2]</a>, Clause 6.2a.</p>
<p>We defined two new global identifiers of respective smart lifts installations (<code>mailto:lift.1415@company1.com</code> and <code>mailto:lift.1416@company1.com</code>) and the global identifier of the associated group (<code>mailto:group.10354@company1.com</code>).</p>
<p>There are two new global identifiers of respective smart lifts installations defined (<code>mailto:lift.1415@company1.com</code> and <code>mailto:lift.1416@company1.com</code>) and the global identifier of the associated group (<code>mailto:group.10354@company1.com</code>).</p>
<p>Through the object properties s4lift:isMasterInGroup and s4lift:isSecondaryinGroup it is possible to define the importance level of each identifier.</p>
......@@ -13,7 +13,7 @@
</figure>
<p>The example presented in <a href="#Figure_7">Figure 7</a> demonstrates how to represent administrative information associated with a s4lift:SmartLiftInstallation as described in ETSI TS 103 735, Clause 6.3.</p>
<p>The example presented in <a href="#Figure_7">Figure 7</a> demonstrates how to represent administrative information associated with a s4lift:SmartLiftInstallation as described in ETSI TS 103 735 <a href="[i.2]">[i.2]</a>, Clause 6.3.</p>
<p>The individual <code>mailto:lift.1415@company1.com</code> is subclass of both s4lift:SmartLiftInstallation and s4lift:PassengerAndGoodsPassengerSmartLift concepts in order to specify precisely the type of smart lift. Then, data properties describing the installation are provided and associated with it.</p>
......@@ -25,7 +25,7 @@
</figure>
<p>Finally, the example presented in Figure 8 demonstrates how to represent information from group name SLInstallation as described in ETSI TS 103 735, Clause 6.4.</p>
<p>Finally, the example presented in Figure 8 demonstrates how to represent information from group name SLInstallation as described in ETSI TS 103 735 <a href="[i.2]">[i.2]</a>, Clause 6.4.</p>
<p>As shown in Figure 6 and Figure 7, the installation labelled as <code>mailto:lift.1415@company1.com</code> is associated with the respective group and the related administrative information are defined.</p>
<p>Here we show how the load capacity is defined through the definition of a the s4lift:carloadlimit property (linked through the s4lift:hasCarLoadLimit object property) that is associated with the related saref:Measurement (s4lift:CarLoadLimitMeasurement).<p>
<p>Then, both the main power supply and the standard power supply are defined.</p>
......
documentation/references.html
View file @ c7363cc3
<h3>Normative references</h3>
<ul>
<li id="[1]">[1] ETSI TS 103 264 (V3.1.1) (02-2020): "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".</li>
<li id="[1]">[1] ETSI TS 103 264 (V3.1.1): "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".</li>
<li id="[2]">[2] EN 81-31:2010: "Safety rules for the construction and installation of lifts - Lifts for the transport of goods only - Part 31:Accessible goods only lifts" (produced by CEN).</li>
<li id="[3]">[3] EN 81-72:2020: "Safety rules for the construction and installation of lifts - Particular applications for passenger and goods passenger lifts - Part 72: Firefighters lifts" (produced by CEN).</li>
<li id="[4]">[4] EN 81-20:2020: "Safety rules for the construction and installation of lifts - Lifts for the transport of persons and goods - Part 20: Passenger and goods passenger lifts" (produced by CEN).</li>
<li id="[5]">[5] EN 81-41:2010: "Safety rules for the construction and installation of lifts - Special lifts for the transport of persons and goods - Part 41: Vertical lifting platforms intended for use by persons with impaired mobility" (produced by CEN).</li>
<li id="[6]">[6] IETF RFC 3966: "The tel URI for Telephone Numbers".</li>
<li id="[7]">[7] EN 81-28:2018+AC:2019: "Safety rules for the construction and installation of lifts - Lifts for the transport of persons and goods - Part 28: Remote alarm on passenger and goods passenger lifts" (produced by CEN).</li>
<li id="[8]">[8] ETSI TS 145 008: "Digital cellular telecommunications system (Phase 2+) (GSM); GSM/EDGE Radio subsystem link control (3GPP TS 45.008)".</li>
</ul>
<h3>Informative references</h3>
<ul>
<li id="[i.1]">[i.1] ETSI TR 103 546 (V1.1.1) (2020-04): "SmartM2M; Requirements & Feasibility study for Smart Lifts in IoT".</li>
<li id="[i.2]">[i.2] ETSI TS 103 735 (V1.1.1) (2021-03): "SmartM2M; Smart Lifts IoT System".</li>
<li id="[i.1]">[i.1] ETSI TR 103 546 (V1.1.1): "SmartM2M; Requirements & Feasibility study for Smart Lifts in IoT".</li>
<li id="[i.2]">[i.2] ETSI TS 103 735 (V1.1.1): "SmartM2M; Smart Lifts IoT System".</li>
<li id="[i.3]">[i.3] ISO 16484-5:2017: "Building automation and control systems (BACS) -- Part 5: Data communication protocol".</li>
<li id="[i.4]">[i.4] ETSI TR 103 510: "SmartM2M; SAREF extension investigation; Requirements for Wearables".</li>
</ul>