diff --git a/documentation/creators.md b/documentation/creators.md index 23c21ceb9d318d0134413f4bea4329805b412fd3..e13f6b7166217dc7b8d46048ab0519e9f2de2d42 100644 --- a/documentation/creators.md +++ b/documentation/creators.md @@ -1,5 +1,4 @@ -- [Mahdi Bennara](https://www.linkedin.com/in/mahdi-bennara/) ([IMT - MINES Saint-Étienne](https://www.mines-stetienne.fr/)) +- [Maxime Lefrançois](http://www.maxime-lefrancois.info/) ([IMT - MINES Saint-Étienne](https://www.mines-stetienne.fr/)) - [Mauro Dragoni](https://pdi.fbk.eu/people/profile/dragoni) ([FBK](https://pdi.fbk.eu/)) - [Alba Fernandez Izquierdo](https://www.linkedin.com/in/albafernandezizquierdo) ([Universidad Politécnica de Madrid](http://www.oeg-upm.net/)) - [Raúl Garcia-Castro](http://www.garcia-castro.com/foaf.rdf#me) ([Universidad Politécnica de Madrid](http://www.oeg-upm.net/)) -- [Maxime Lefrançois](http://www.maxime-lefrancois.info/) ([IMT - MINES Saint-Étienne](https://www.mines-stetienne.fr/)) diff --git a/documentation/description.html b/documentation/description.html index d9563523e25b6dbbb178abeb85e51bf6c860b61f..9eb7b09f3e630135d065b2e58438a44863e998b4 100644 --- a/documentation/description.html +++ b/documentation/description.html @@ -1,4 +1,4 @@ -

SAREF4LIFT has been specified and formalised by investigating related resources in the smart lifts domain, as reported in ETSI TR 103 546 [i.1] and ETSI TS 103 735 [i.2]. Therefore, SAREF4LIFT shall both: +

SAREF4LIFT has been specified and formalised by investigating related resources in the smart lifts domain, as reported in ETSI TR 103 546 [i.1] and ETSI TS 103 735 [i.2]. Therefore, SAREF4LIFT shall both:

-

SAREF4LIFT is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 510 [i.1]) and can thus be mainly described by the following self-contained knowledge modules: +

SAREF4LIFT is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 510 [i.1]) and can thus be mainly described by the following self-contained knowledge modules:

+ -

Beside the four module described above, the SAREF4LIFT extension defines also:

+

Beside the four module described above, the SAREF4LIFT extension defines also two new property types (s4lift:Load and s4lift:Voltage) defining the load in the smart lift car and the electric voltage of some electric power system.

- +

Systems and connections

+

This module specializes the SAREF4SYST ontology pattern for the Smart Lift domain.

-

Command

+

A Smart Lift system can be defined as a s4syst:System made by different components. This module defines the subcomponents that are part of Smart Lift. In particular, we denoted two subcomponents: the s4lift:SmartLiftEdgeComponent and the s4lift:SmartLiftEdgeControlUnit. The former is dedicated to the hosting of smart lift additional modules in the case that they are not hosted directly in the s4lift:SmartLiftEdgeControlUnit. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the s4lift:SmartLiftEdgeControlUnit. +The latter is the main element of a Smart Lift installation and it is typically associated with the lift control cabinet.

-

This model specifies the list of commands that we considered relevant for the smart lift domain. We defined seven new commands that are subsumed by the saref:Command concept that can be triggered, in turn, by a saref:Function as presented in Figure 2:

+

A s4lift:SmartLiftInstallation 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], s4lift:GoodsSmartLift, and s4lift:MachineRoomLessSmartLift, s4lift:PassengerAndGoodsPassengerSmartLift as per [EN 81-20], s4lift:SmartLiftWithoutEmergencyCallSupport, s4lift:VerticalSmartLiftingPlatform as per [EN 81-41]. All these concepts represent a type of smart lift that can be instantiated by the ontology.

+ +

A s4lift:SmartLiftGroup 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.

+ +

A s4lift:SmartLiftCar represents the car of a Smart Lift. A s4lift:SmartLiftInstallation usually contains different s4lift:CarStopSpaces serving different spaces of different floors at s4lift:Smart LiftCarService. A s4lift:SmartLiftCar can connect to some s4bldg:BuildingSpace through some s4lift:SmartLiftCarService at some s4lift:DoorConnectionPoint.

+ +

A s4lift:Network is the class of communication networks. Systems can connect to other networks through a potential s4lift:NetworkAccess connection.

-
- Command model. -
Figure 2: Command model.
+ Systems and connections model. +
Figure 2: Systems and connections model.
-

Device

+

Devices and commands

-

A Smart Lift system can be defined as a saref:Device made by different components. This module defines the subcomponents that are part of Smart Lift. In particular, we denoted two subcomponents: the s4lift:SmartLiftEdgeComponent and the s4lift:SmartLiftEdgeControlUnit. -The former is dedicated to the hosting of smart lift additional modules in the case that they are not hosted directly in the s4lift:SmartLiftEdgeControlUnit. An example could be the case of an additional earthquake sensor added after the lift deployment and not controlled by the s4lift:SmartLiftEdgeControlUnit.

+

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 saref:Function as presented in Figure 3:

-

The latter is the main element of a Smart Lift installation and it is typically associated with the lift control cabinet. -Both concepts are subsumed by the s4syst:System concept that, in turn, it subsumes the s4lift:SmartLiftInstallation that corresponds to a single lift, with all its elements. Such a concept is equipped with the list of properties shown in Figure 3.

- -

Finally, the s4lift:SmartLiftGroup, subsumed by the saref:FeatureOfInterest concept, 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.

+
- Device model. -
Figure 3: Device model.
+ Devices and commands model. +
Figure 3: Devices and commands model.
-

System

- -

This module expands the Device module by specifying two aspects.

+

States and measurements

-

First, the s4lift:SmartLiftInstallation concept subsumes four type of installations considered relevant for this extension, namely s4lift:SmartLiftPlatform, s4lift:GoodsSmartLift, s4lift:GoodsOnlySmartLift, and s4lift:FiremanLift. -All these concepts represents a type of smart lift that can be instantiated by the ontology.

+

This module defines states that features of interest in a smart lift installation can be found in, and measurements that can be made about features of interest in a smart lift.

-

Second, the relationship between a s4lift:SmartLiftInstallation entity and the saref:Time one. Indeed, three object properties have been defined modelling both the opening and closing time of the smart lift (s4lift:hasDoorOpenTime and s4lift:hasDoorCloseTime respectively) and the total usage time of the smart lift described by the object property s4lift:hasTraveledTime.

- System model. -
Figure 4: System model.
+ States and measurements model. +
Figure 4: States and measurements model.
-

Signal

+

Signals

This module describes the types of signals that can be read from a smart lift console. Figure 5 shows the taxonomy of the relevant types of signals foreseen within this extension.

It is possible to observe a set of four main types of signals:

-

All descendants of the s4lift:Signal inherit the saref:hasTimestamp and saref:hasValue properties defining the timestamp when the signal has been generated and its value, respectively.

- -

Then, the s4lift:PowerSupplySignal concept is associated with its power supply value through the s4lift:hasPowerSupplyValue property; while the s4lift:PositionSignal is associated with the corresponding position value through the s4lift:hasPositionValue property.

+

Descendants of the s4lift:Signal inherit the saref:isAbout, and s4lift:conveys 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.

- Signal model. -
Figure 5: Signal model.
+ Signals model. +
Figure 5: Signals model.
-