doc generated from pipeline

catalog-v001.xml

saref-pipeline.jar

target

documentation/ts_*

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

* ABS: Acrylonitrile Butadiene Styrene

* 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 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

# Approach

To create the SAREF4INMA extension specified in the present document, a combination of bottom-up and top-down approaches was followed. First, the SAREF4INMA extension has been developed bottom-up from a set of requirements extracted from standards developed in the context of various initiatives in Europe that support digitalization in manufacturing (such as, for example, 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), as explained in the associated ETSI TR 103 507 [i.2]. Additionally, following a top-down approach, the SAREF4INMA extension development has been driven by already existing ontologies (i.e. SAREF and SAREF4BLDG) which define top concepts and relationships that needed to be extended for the industry and manufacturing domain.

Following the process defined in ETSI TR 103 411 [i.1], ontological engineers analysed the existing standards in the industry domain with the support of domain experts (the complete list of the analysed standards is detailed in [i.2]). Afterwards, an initial version of the ontological requirements for SAREF4INMA was proposed, which was then refined together with domain experts in order to obtain a stable version of the requirements. This refinement was carried out by means of on-line meetings.

As mentioned, SAREF and SAREF4BLDG concepts and properties have been reused and extended when they needed to be specialized.

The following classes and properties have been directly reused from SAREF:

* saref:Device.

* saref:Function.

* saref:Measurement.

* saref:Property.

* saref:consistsOf.

* saref:hasFunction.

* saref:makesMeasurement.

* saref:relatesToMeasurement.

* saref:isMeasuredIn.

The following classes and properties have been reused in SAREF4INMA to complete the model of measurements:

* `saref:FeatureOfInterest` to define the feature of interest being observed in a certain measurement.

* `saref:isPropertyOf` (and its inverse `saref:hasProperty`) to link the property being observed with the feature of interest.

* `saref:hasFeatureOfInterest` (and its inverse `saref:isFeatureOfInterestOf`) to link a given measurement with the feature of interest being observed.

* `saref:measurementMadeBy` as complement of the `saref:makesMeasurement`, as its inverse, to link a measurement and the device that produces it.

The following classes and properties have been directly reused from SAREF4BLDG:

* s4bldg:PhysicalObject.

* s4bldg:Building.

* s4bldg:BuildingSpace.

* s4bldg:hasSpace.

* s4bldg:isSpaceOf.

* s4bldg:contains.

* s4bldg:isContainedIn.

More precisely, the following classes have been extended with new SAREF4INMA classes: 

* saref:Device and s4bldg:PhysicalObject have been extended with the s4inma:ProductionEquipment and s4inma:WorkCenter classes.

* saref:Function has been extended with the s4inma:ProductionEquipmentFunction class. Examples of these functions are defined in the SAREF4INMA instantiation in clause 4.3, i.e. ex:CuttingFunction, ex:FormingFunction and ex:JoiningFunction. Note that these functions provide only an initial example of how to reuse SAREF functions in the industry and manufacturing domain, but it is recommended that stakeholders in this domain further extend the s4inma:ProductionEquipmentFunction class as needed.

* saref:Property has been extended with s4inma:Size.

* s4bldg:BuildingSpace has been extended with s4inma:Site and s4inma:Area.

Finally, the Time ontology ([http://www.w3.org/2006/time](http://www.w3.org/2006/time)), which is already reused by SAREF, has also been reused in SAREF4INMA.

# Bibliography

* ETSI TS 103 267: "SmartM2M; Smart Appliances; Communication Framework".

* ETSI TS 102 689: "Machine-to-Machine communications (M2M); M2M Service Requirements".