Unverified Commit ca94b1a4 authored by Maxime Lefrançois's avatar Maxime Lefrançois
Browse files

documentation generated from TS

parent da0d1c76
Loading
Loading
Loading
Loading
+35 −0
Original line number Diff line number Diff line

For the purposes of the present document, the following abbreviations apply:

* BIC: Brainport Industries Campus
* BS: British Standard
* EAN: European Article Number
* EN: European Norm
* GS1: Global Standards One
* GTIN: Global Trade Item Number
* GUID: Globally Unique IDentifier 
* ID: Identifier
* IEC: International Electrotechnical Commission
* IRDI: International Registration Data Identifier
* ISO: International Organisation for Standardization 
* ITF: Interleaved 2 of 5
* ITU-T: International Telecommunication Union - Telecommunications sector
* OWL: Web Ontology Language
* OWL-DL: Web Ontology Language - Description Logic
* QR: Quick Response code
* RAMI: Reference Architectural Model Industry 4.0
* RFID: Radio Frequency Identification
* RPC: Remote Procedure Call
* SAREF: Smart Applications REFerence ontology
* SAREF4BLDG: SAREF extension for buildings
* SAREF4INMA: SAREF extension for industry and manufacturing domains
* TR: Technical Report
* TS: Technical Specification
* UCC: Uniform Commercial Code
* UPC: Universal Product Code
* UPC-A: Universal Product Code 

!!! alert-info "NOTE:"
    UPC-A is an 11 digit variation of UPC, as opposed to UPC-E which is the 6 digit variation.

* UUID: Universally Unique Identifier
 No newline at end of file
+21 −7
Original line number Diff line number Diff line
<div class="alert-warning">NOTE: The text in this section is extracted from ETSI TS 103 410-5 (V2.1.1) <a href="#[0]">[0]</a>, and therefore falls inside the <a href="https://www.etsi.org/intellectual-property-rights">ETSI IPR Policy</a></div>
# SAREF4INMA ontology and semantics


## Introduction and overview


The present document is a technical specification of SAREF4INMA, an extension of SAREF [1] that was created for the industry and manufacturing domain. SAREF4INMA was created to be aligned with related initiatives in the smart industry and manufacturing domain in terms of modelling and standardization, such as the Reference Architecture Model for Industry 4.0 (RAMI), which combines several standards used by the various national initiatives in Europe that support digitalization in manufacturing. These initiatives include, but are not limited to, the platform Industrie 4.0 in Germany, the Smart Industry initiative in the Netherlands, Industria 4.0 in Italy, the 'Industrie du future initiative' in France and more.

[The technical specification ETSI TS 103 410-5](#[0]) is a technical specification of SAREF4INMA, an extension of SAREF [[1]](#[1]) that was created for the industry and manufacturing domain. SAREF4INMA was created to be aligned with related initiatives in the smart industry and manufacturing domain in terms of modelling and standardization, such as the Reference Architecture Model for Industry 4.0 (RAMI), which combines several standards used by the various national initiatives in Europe that support digitalization in manufacturing. These initiatives include, but are not limited to, the platform Industrie 4.0 in Germany, the Smart Industry initiative in the Netherlands, Industria 4.0 in Italy, the 'Industrie du future initiative' in France and more.

SAREF4INMA is an OWL-DL ontology that extends SAREF with 21 classes, 16 object and 10 data type properties. In addition, SAREF4INMA reuses SAREF and SAREF4BLDG ontologies by importing them. SAREF4INMA focuses on extending SAREF for the industry and manufacturing domain to solve the lack of interoperability between various types of production equipment that produce items in a factory and, once outside the factory, between different organizations in the value chain to uniquely track back the produced items to the corresponding production equipment, batches, material and precise time in which they were manufactured.

The full list of use cases, standards and requirements that guided the creation of SAREF4INMA are described in the associated ETSI TR 103 507 [[i.2]](#[i.2]). The "zero defect manufacturing" use case has been used as basis for the creation of SAREF4INMA in [the technical specification ETSI TS 103 410-5](#[0]). This use case is concerned with improving the manufacturing process in terms of flexibility to timely change from one manufactured product to another, generating as little yield loss as possible. Also the "smart services for product in use" and "smart product lifecycle" use cases are acknowledged in the associated ETSI TR 103 507 [[i.2]](#[i.2]) as especially relevant for SAREF4INMA, as they pose semantic interoperability issues for, respectively:

1. the manufacturing companies that remain responsible for the proper functioning of a product during its entire lifecycle, also when the product has left the factory; and
2. the various, interacting parties involved in the value chain (e.g. manufacturer, user, servicing organization, parts supplier, etc.) that need to refer to a common digital footprint of a product to allow for its management during its entire lifecycle.
The full list of use cases, standards and requirements that guided the creation of SAREF4INMA are described in the associated ETSI TR 103 507 [i.2]. The "zero defect manufacturing" use case has been used as basis for the creation of SAREF4INMA in the present document. This use case is concerned with improving the manufacturing process in terms of flexibility to timely change from one manufactured product to another, generating as little yield loss as possible. Also the "smart services for product in use" and "smart product lifecycle" use cases are acknowledged in the associated ETSI TR 103 507 [i.2] as especially relevant for SAREF4INMA, as they pose semantic interoperability issues for, respectively:


!!! indent-1 ""
    1)	the manufacturing companies that remain responsible for the proper functioning of a product during its entire lifecycle, also when the product has left the factory; and


!!! indent-1 ""
    2)	the various, interacting parties involved in the value chain (e.g. manufacturer, user, servicing organization, parts supplier, etc.) that need to refer to a common digital footprint of a product to allow for its management during its entire lifecycle.


Note that SAREF4INMA specified in the present document provides a second version of the SAREF extension for the industry and manufacturing domain, based on the (limited set of) use cases mentioned above and an initial list of standards for digitalization, communication, engineering and life-cycle, covering relevant concepts such as factory, production equipment, item, material and batch, as described in ETSI TR 103 507 [i.2]. However, as all the SAREF ontologies, SAREF4INMA is a dynamic semantic model that should be used, validated and improved over time with and by the stakeholders in the industry and manufacturing domain in an iterative and interactive manner to accommodate more use cases, standards and generate new requirements as needed.

Note that SAREF4INMA specified in [the technical specification ETSI TS 103 410-5](#[0]) provides a second version of the SAREF extension for the industry and manufacturing domain, based on the (limited set of) use cases mentioned above and an initial list of standards for digitalization, communication, engineering and life-cycle, covering relevant concepts such as factory, production equipment, item, material and batch, as described in ETSI TR 103 507 [[i.2]](#[i.2]). However, as all the SAREF ontologies, SAREF4INMA is a dynamic semantic model that should be used, validated and improved over time with and by the stakeholders in the industry and manufacturing domain in an iterative and interactive manner to accommodate more use cases, standards and generate new requirements as needed.

The prefixes and namespaces used in SAREF4INMA and in [the technical specification ETSI TS 103 410-5](#[0]) are listed in [the Namespace Declarations section](#namespacedeclarations).
The prefixes and namespaces used in SAREF4INMA and in the present document are listed in Table 1.

{{table_1}}
+8 −0
Original line number Diff line number Diff line

# Bibliography

* ETSI TS 103 267: "SmartM2M; Smart Appliances; Communication Framework".
* ETSI TS 102 689: "Machine-to-Machine communications (M2M); M2M Service Requirements".


+311 −28

File changed.

Preview size limit exceeded, changes collapsed.

+24 −19
Original line number Diff line number Diff line
<div class="alert-warning">NOTE: The text in this section is extracted from ETSI TS 103 410-5 (V2.1.1) <a href="#[0]">[0]</a>, and therefore falls inside the <a href="https://www.etsi.org/intellectual-property-rights">ETSI IPR Policy</a></div>
## Instantiating SAREF4INMA

This example instantiation is referred to using the ex prefix. This prefix is different from the s4inma prefix, which indicates the SAREF4INMA ontology on which the ex example instantiation is built upon.

The example is shown in [Figure 4](#Figure_4) and represents an instance of a shaver (i.e. the ex:Shaver10023) of the [s4inma:Item](#s4inma:Item) class, which is an item created in a certain batch (represented by the ex:PhilBrau_S40_Premium_Gold_Shaver_ItemBatch392 instance), which in turn belongs to a category of items called PhilBrau S40 Premium Gold Shaver ItemCategory. This item category is represented by the ex: PhilBrau_S40_Premium_Gold_Shaver _ItemCategory instance of the [s4inma:ItemCategory](#s4inma:ItemCategory) class, it has model number ex:nr98647656 and manufacturer PhilBrau, and is produced using a certain production equipment category, namely the ex:Lazor_Series_8030_ProdEquipCategory instance of the [s4inma:ProductionEquipmentCategory](#s4inma:ProductionEquipmentCategory) class.
This example instantiation is referred to using the `ex` prefix. This prefix is different from the `s4inma` prefix, which indicates the SAREF4INMA ontology on which the `ex` example instantiation is built upon.

The ex:Lazor_Series_8030_ProdEquipCategory instance is the general category of a specific production equipment, namely the ex:Laser_Cutting_Machine_1 instance of a laser cutting machine created specifically for this example (i.e. the ex:LaserCuttingMachine class created in this example as a subclass of the [s4inma:ProductionEquipment](#s4inma:ProductionEquipment) class).

The example is shown in Figure 4 and represents an instance of a shaver (i.e. the `ex:Shaver10023`) of the `s4inma:Item` class, which is an item created in a certain batch (represented by the `ex:PhilBrau_S40_Premium_Gold_Shaver_ItemBatch392` instance), which in turn belongs to a category of items called _PhilBrau S40 Premium Gold Shaver ItemCategory_. This item category is represented by the `ex`: `PhilBrau_S40_Premium_Gold_Shaver` `_ItemCategory` instance of the `s4inma:ItemCategory` class, it has model number `ex:nr98647656` and manufacturer `PhilBrau`, and is produced using a certain production equipment category, namely the `ex:Lazor_Series_8030_ProdEquipCategory` instance of the `s4inma:ProductionEquipmentCategory` class.


The `ex:Lazor_Series_8030_ProdEquipCategory` instance is the general category of a specific production equipment, namely the `ex:Laser_Cutting_Machine_1` instance of a laser cutting machine created specifically for this example (i.e. the `ex:LaserCuttingMachine` class created in this example as a subclass of the `s4inma:ProductionEquipment` class).

<figure>
    <img src="diagrams/S4INMA Item example.png" alt="Item example"/>
    <figcaption id="Figure_4">Figure 4: Item example</figcaption>
    <img data-docx-width="14.26cm" src="diagrams/S4INMA Item example.png" alt="Item example"/>
    <figcaption>Figure 4: Item example</figcaption>
</figure>

[Figure 5](#Figure_5) further shows that the Shaver10023 item recursively consists of other three items, namely the ShaverHead3002, StepMotor083 and ShaverBody9440 items. In other words, SAREF4INMA allows to describe an item as a whole (i.e. the shaver) or in its parts (i.e. the shaver head, motor and body). The ShaverBody9440 item is created in the PhilBrau_S40-S50_Generic_Body_ItemBatch3290 item batch, which in turn consists of material from other batches, namely the Torx screws_D2mm_L8mm MaterialBatch323 and ABS_Plastic_Role_8mm_MaterialBatch742. These material batches belong to two different material categories classes created specifically for this example, respectively the ex:Screw class (with its ex:Torx_screws_D2mm_L8mm_MaterialCategory instance) and the ex:Plastic class (with its ex:ABS_Plastic_Role_8mm_MaterialCategory instance), which are both subclasses of [s4inma:MaterialCategory](#s4inma:MaterialCategory). In other words, the body of a shaver is an item created in a batch that is made of other materials such as screws and plastic.

Figure 5 further shows that the _Shaver10023_ item recursively consists of other three items, namely the _ShaverHead3002_, _StepMotor083_ and _ShaverBody9440_ items. In other words, SAREF4INMA allows to describe an item as a whole (i.e. the shaver) or in its parts (i.e. the shaver head, motor and body). The _ShaverBody9440_ item is created in the _PhilBrau_S40-S50_Generic_Body_ItemBatch3290_ item batch, which in turn consists of material from other batches, namely the _Torx_ _screws_D2mm_L8mm MaterialBatch323_ and _ABS_Plastic_Role_8mm_MaterialBatch742_. These material batches belong to two different material categories classes created specifically for this example, respectively the `ex:Screw` class (with its `ex:Torx_screws_D2mm_L8mm_MaterialCategory` instance) and the `ex:Plastic` class (with its `ex:ABS_Plastic_Role_8mm_MaterialCategory` instance), which are both subclasses of `s4inma:MaterialCategory`. In other words, the body of a shaver is an item created in a batch that is made of other materials such as screws and plastic.

<figure>
    <img src="diagrams/S4INMA Material example.png" alt="Material example "/>
    <figcaption id="Figure_5">Figure 5: Material example </figcaption>
    <img data-docx-width="13.46cm" src="diagrams/S4INMA Material example.png" alt="Material example "/>
    <figcaption>Figure 5: Material example </figcaption>
</figure>

The example instantiation further defines two types of production equipment categories, namely the Lazor_Series_8030_ProdEquipCategory and the WandI_Welding_Series_1000_ProdEquipCategory. These categories represent a certain model of production equipment and not the individual machines, since an organization might have multiple machines of the same model. In particular, there is one laser cutting machine of type Lazor_Series_8030_ProdEquipCategory, namely the Laser_Cutting_Machine_1, and two welding machines, namely Welding_Machine_1 and Welding_Machine_2, which are shown in [Figure 6](#Figure_6).

These machines are instances of the ex:WeldingMachine and the ex:LaserCuttingMachine classes created for this example, which are both subclasses of the [s4inma:ProductionEquipment](#s4inma:ProductionEquipment) class, which is in turn a subclass of [saref:Device](https://saref.etsi.org/core/Device), which is in turn a subclass of [s4bldg:PhysicalObject](https://saref.etsi.org/saref4bldg/PhysicalObject). The subclass relation of [saref:Device](https://saref.etsi.org/core/Device) ensures that a [s4inma:ProductionEquipment](#s4inma:ProductionEquipment) can reuse SAREF functionality by inheritance, such as the possibility to perform functions, be composed by other devices such as sensors (e.g. temperature sensors), control properties (e.g. welding temperature) and make observations. For example, the Welding_Machine_2 production equipment can perform a JoiningFunction (ex:JoiningFunction instance), controls the WeldingTemperature property, and further consists of the WeldingMachineTemperatureSensor1.
The example instantiation further defines two types of production equipment categories, namely the _Lazor_Series_8030_ProdEquipCategory_ and the _WandI_Welding_Series_1000_ProdEquipCategory_. These categories represent a certain model of production equipment and not the individual machines, since an organization might have multiple machines of the same model. In particular, there is one laser cutting machine of type _Lazor_Series_8030_ProdEquipCategory_, namely the _Laser_Cutting_Machine_1_, and two welding machines, namely _Welding_Machine__1 and _Welding_Machine_2_, which are shown in Figure 6.


These machines are instances of the `ex:WeldingMachine` and the `ex:LaserCuttingMachine` classes created for this example, which are both subclasses of the `s4inma:ProductionEquipment` class, which is in turn a subclass of `saref:Device`, which is in turn a subclass of `s4bldg:PhysicalObject`. The subclass relation of `saref:Device` ensures that a `s4inma:ProductionEquipment` can reuse SAREF functionality by inheritance, such as the possibility to perform functions, be composed by other devices such as sensors (e.g. temperature sensors), control properties (e.g. welding temperature) and make observations. For example, the _Welding_Machine_2_ production equipment can perform a _JoiningFunction_ (`ex:JoiningFunction` instance), controls the _WeldingTemperature_ property, and further consists of the _WeldingMachineTemperatureSensor1_.

<figure>
    <img src="diagrams/S4INMA ProductionEquipm example.png" alt="Production Equipment example"/>
    <figcaption id="Figure_6">Figure 6: Production Equipment example</figcaption>
    <img data-docx-width="11.42cm" src="diagrams/S4INMA ProductionEquipm example.png" alt="Production Equipment example"/>
    <figcaption>Figure 6: Production Equipment example</figcaption>
</figure>

The Welding Machine Temperature Sensor 1 makes some temperature observation during the production of Shaver10023 in intervals of ten seconds. [Figure 7](#Figure_7) shows some example observations related to the production of the Shaver10023 item and the reuse of the SAREF model for observations. For example, the ex:Welding_Machine_2_Observation_W101520 instance is observed by the WeldingMachineTemperatureSensor1, relates to the WeldingTemperature property, has value 223 and unit of measure degree Celsius, has timestamp 2019-01-28T12:11:10 and has the item Shaver10023 as feature of interest.

The _Welding Machine Temperature Sensor 1_ makes some temperature observation during the production of _Shaver10023_ in intervals of ten seconds. Figure 7 shows some example observations related to the production of the _Shaver10023_ item and the reuse of the SAREF model for observations. For example, the `ex:Welding_Machine_2_Observation_W101520` instance is observed by the _WeldingMachineTemperatureSensor1_, relates to the _WeldingTemperature_ property, has value _223_ and unit of measure _degree Celsius_, has timestamp _2019-01-28T12:11:10_ and has the item _Shaver10023_ as feature of interest.

<figure>
    <img src="diagrams/S4INMA Observation example.png" alt="Observation example "/>
    <figcaption id="Figure_7">Figure 7: Observation example </figcaption>
    <img data-docx-width="14.92cm" src="diagrams/S4INMA Observation example.png" alt="Observation example "/>
    <figcaption>Figure 7: Observation example </figcaption>
</figure>

Since a [s4inma:ProductionEquipment](#s4inma:ProductionEquipment) is a subclass of a [saref:Device](https://saref.etsi.org/core/Device) and consequently of [s4bldg:PhysicalObject](https://saref.etsi.org/saref4bldg/PhysicalObject), it is possible to assign each production equipment instance to a physical location within the factory. [Figure 8](#Figure_8) shows an instance of a [s4inma:Factory](#s4inma:Factory) class, which in turn is defined in SAREF4INMA as a [s4bldg:Building](https://saref.etsi.org/saref4bldg/Building) subclass. This instance (ex:Eindhoven_BIC) represents a factory that can be decomposed into Site and Area, building spaces, which are all subclasses of [s4bldg:BuildingSpaces](https://saref.etsi.org/saref4bldg/BuildingSpaces). Moreover, the welding machines and the laser cutting machine are part of the Welding_WorkCenter, which is a WorkCenter located in the Area BIC_Site_A_Area_19, which is in its turn located in the Site BIC_Site_A in the Eindhoven BIC building.

Since a `s4inma:ProductionEquipment` is a subclass of a `saref:Device` and consequently of `s4bldg:PhysicalObject`, it is possible to assign each production equipment instance to a physical location within the factory. Figure 8 shows an instance of a `s4inma:Factory` class, which in turn is defined in SAREF4INMA as a `s4bldg:Building` subclass. This instance (`ex:Eindhoven_BIC`) represents a factory that can be decomposed into _Site_ and _Area_, building spaces, which are all subclasses of `s4bldg:BuildingSpaces`. Moreover, the welding machines and the laser cutting machine are part of the _Welding_WorkCenter_, which is a _WorkCenter_ located in the _Area BIC_Site_A_Area_19_, which is in its turn located in the _Site BIC_Site_A_ in the _Eindhoven_ _BIC_ building.

<figure>
    <img src="diagrams/S4INMA Factory example.png" alt="Factory example"/>
    <figcaption id="Figure_8">Figure 8: Factory example</figcaption>
    <img data-docx-width="11.65cm" src="diagrams/S4INMA Factory example.png" alt="Factory example"/>
    <figcaption>Figure 8: Factory example</figcaption>
</figure>


Loading