Merge branch 'html' into 'develop-v2.1.1'

SAREF4INMA is an OWL-DL ontology that extends SAREF with 24 classes (in addition to a number of classes directly reused from the SAREF ontology and the SAREF4BLDG extension), 20 object properties (in addition to a number of object properties reused from the SAREF ontology and the SAREF4BLDG extension) and 11 data type properties. 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.

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 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]](#[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.

Note that SAREF4INMA specified in the present document provides a first 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.

Note that SAREF4INMA specified in the present document provides a second version of 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 present document are listed in [the Namespace Declarations section](#namespacedeclarations)

 No newline at end of file

- Alba Fernandez Izquierdo ([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/))

- [Mike de Roode](https://www.linkedin.com/in/mderoode) ([TNO](https://tno.nl/))

- [Maria Poveda-Villalon](https://w3id.org/people/mpoveda/) ([Universidad Politécnica de Madrid](http://www.oeg-upm.net/))

<h3>Item and Batch</h3>

<p>This clause focuses on the classes of SAREF4INMA that describe an item produced in a factory. The classes of interest, which are <a href="#s4inma:Item">s4inma:Item</a>, <a href="#s4inma:ItemCategory">s4inma:ItemCategory</a>, <a href="#s4inma:MaterialCategory">s4inma:MaterialCategory</a>, <a href="#s4inma:Batch">s4inma:Batch</a>, <a href="#s4inma:ItemBatch">s4inma:ItemBatch</a>, <a href="#s4inma:MaterialBatch">s4inma:MaterialBatch</a> and <a href="#s4inma:ID">s4inma:ID</a>, are shown in <a href="#Figure_3">Figure 3</a>.</p>

<p>This clause focuses on the classes of SAREF4INMA that describe an item produced in a factory. The classes of interest, which are <a href="#s4inma:Item">s4inma:Item</a>, <a href="#s4inma:ItemCategory">s4inma:ItemCategory</a>, <a href="#s4inma:MaterialCategory">s4inma:MaterialCategory</a>, <a href="#s4inma:Batch">s4inma:Batch</a>, <a href="#s4inma:ItemBatch">s4inma:ItemBatch</a>, <a href="#s4inma:MaterialBatch">s4inma:MaterialBatch</a> and <a href="#s4inma:ID">s4inma:ID</a>, are shown in <a href="#Figure_2">Figure 2</a>.</p>

<p>An Item is a tangible object that represents either the goods produced by an organization's production process or individually traced supplies (i.e. sub-assemblies of supplies). An item can be individually traced using an ID. SAREF4INMA allows to use several types of IDs, such as the Global Trade Item Number (GTIN) defined by GS1 (<a href="https://www.gs1.org/">https://www.gs1.org/</a>), used by organizations to uniquely identify their trade items as products or services that are priced, ordered or invoiced at any point in the supply chain. There are four GTIN formats (GTIN-8, GTIN-12, GTIN 13, GTIN-14) and SAREF4INMA defines classes and properties for each of them. SAREF4INMA defines also classes and properties to associate items to the International Registration Data Identifier (IRDI), which is based on the international standards ISO/IEC 11179-6 <a href="#[i.4]">[i.4]</a>, ISO 29002 <a href="#[i.5]">[i.5]</a> and ISO 6532 <a href="#[i.6]">[i.6]</a>. An example of relevant standard that uses IRDIs is the eCl@ss specification (<a href="https://www.eclass.eu/en/">https://www.eclass.eu/en/</a>) for grouping materials, products and services. Other types of IDs are defined in SAREF4INMA, such as the Universally Unique Identifier (UUID), or can be further defined ad-hoc by the ontology users by creating new classes as subclasses of the <a href="#s4inma:ID">s4inma:ID</a> class.</p>

<p>An Item can recursively consist of other items (e.g. a shaver consists of a shaver head, motor and body) and can be the feature of interest of a measurement (e.g. a shaver can be the feature of interest of a temperature measurement made by a welding machine used to join different parts in the production of the shaver). An item is created exactly in one ItemBatch, which describes a uniform collection of items produced at a certain time using a certain production equipment. An ItemBatch consists of a set of items with similar properties (e.g. a certain brand and model of sensors made using a certain production line). An ItemBatch is a specialization of the more general Batch, which can be further specialized in a MaterialBatch. The difference between ItemBatch and MaterialBatch is that individual items can be traced in an ItemBatch (e.g. it is possible to trace an individual metal sheet in an ItemBatch), whereas it is not possible to exactly trace material in a MaterialBatch, (e.g. it is not possible to trace the exact piece of raw plastic material from a MaterialBatch, as the raw plastic is a volume, not identifiable in a specific sheet like in the case of metal sheets).</p>

<p>An Item can recursively consist of other items (e.g. a shaver consists of a shaver head, motor and body) and can be the feature of interest of a observation (e.g. a shaver can be the feature of interest of a temperature observation made by a welding machine used to join different parts in the production of the shaver). An item is created exactly in one ItemBatch, which describes a uniform collection of items produced at a certain time using a certain production equipment. An ItemBatch consists of a set of items with similar properties (e.g. a certain brand and model of sensors made using a certain production line). An ItemBatch is a specialization of the more general Batch, which can be further specialized in a MaterialBatch. The difference between ItemBatch and MaterialBatch is that individual items can be traced in an ItemBatch (e.g. it is possible to trace an individual metal sheet in an ItemBatch), whereas it is not possible to exactly trace material in a MaterialBatch, (e.g. it is not possible to trace the exact piece of raw plastic material from a MaterialBatch, as the raw plastic is a volume, not identifiable in a specific sheet like in the case of metal sheets).</p>

<p>Material batches can be equipped with quality certificates, such as the BS EN 10204:2004 <a href="#[i.7]">[i.7]</a> category 3.1 steel quality certificate (<a href="https://standardsdevelopment.bsigroup.com">https://standardsdevelopment.bsigroup.com</a>). These certificates provide additional information about the material in the batch. Furthermore, MaterialBatches belong to some MaterialCategory, which describes a certain type of material (e.g. a certain type of steel sheets). Analogously, item batches belong to some ItemCategory, which describes a single type of Items (e.g. a certain type of sensor). An ItemCategory is in turn produced by some ProductionEquipmentCategory. The essential properties of each Item in all ItemBatches are the same. However, each ItemBatch might use different MaterialBatches and/or different ProductionEquipment. Therefore, small deviations between batches might occur, while the essential properties of all Items related to an ItemCategory are similar. Finally, the time that a batch is produced can be recorded using the time:hasBeginning and time:hasEnd properties.</p>

<h3>Production Equipment and Factory</h3>

<p>This clause focuses on the classes that describe how a production equipment is organized and how it can exchange information within the factory. The classes of interest are: <a href="#s4inma:ProductionEquipment">s4inma:ProductionEquipment</a>,<a href="#s4inma:ProductionEquipmentCategory">s4inma:ProductionEquipmentCategory</a>,<a href="#s4inma:WorkCenter">s4inma:WorkCenter</a>, <a href="#s4inma:Area">s4inma:Area</a>, <a href="#s4inma:Site">s4inma:Site</a>, and <a href="#s4inma:Factory">s4inma:Factory</a>, and are shown in <a href="#Figure_4">Figure 4</a>. </p>

<p>This clause focuses on the classes that describe how a production equipment is organized and how it can exchange information within the factory. The classes of interest are: <a href="#s4inma:ProductionEquipment">s4inma:ProductionEquipment</a>,<a href="#s4inma:ProductionEquipmentCategory">s4inma:ProductionEquipmentCategory</a>,<a href="#s4inma:WorkCenter">s4inma:WorkCenter</a>, <a href="#s4inma:Area">s4inma:Area</a>, <a href="#s4inma:Site">s4inma:Site</a>, and <a href="#s4inma:Factory">s4inma:Factory</a>, and are shown in <a href="#Figure_3">Figure 3</a>. </p>

<figure>

  <a href="diagrams/ProductionEquipmentAndFactory.png"><img src="diagrams/ProductionEquipmentAndFactory.png" alt="Production Equipment, Factory and related classes"/></a>

</figure>

<p>A ProductionEquipmentCategory describes the kind of production equipment required for producing a certain item, i.e. a category of machine. An organization might have multiple instances of the same category of machines. Each individual machine is represented by a ProductionEquipment, which is a subclass of <a href="https://saref.etsi.org/core/Device">saref:Device</a>, which is in turn a subclass of <a href="https://saref.etsi.org/saref4bldg/PhysicalObject">s4bldg:PhysicalObject</a>. The latter is part of the SAREF for Building extension <a href="#[i.3]">[i.3]</a>, which defines the <a href="https://saref.etsi.org/core/Device">saref:Device</a> class as a subclass of the more general <a href="https://saref.etsi.org/saref4bldg/PhysicalObject">s4bldg:PhysicalObject</a> class, following a pattern that allows to locate devices within the building. Analogously, SAREF4INMA reuses the same pattern to locate a production equipment in the factory.</p>

<p>In order to locate the ProductionEquipment, a factory layout can be created. A factory is represented by the <a href="#s4inma:Factory">s4inma:Factory</a> class (which is subclass of the <a href="https://saref.etsi.org/saref4bldg/Building">s4bldg:Building</a> class) and can be further divided into smaller spaces using the <a href="https://saref.etsi.org/saref4bldg/BuildingSpace">s4bldg:BuildingSpace</a> class. For the scope of SAREF4INMA, two types of BuildingSpaces are defined, namely Site and Area. A Factory can be further divided in sites, which according to IEC 62264 <a href="#[i.11]">[i.11]</a> are identified physical, geographical, and/or logical component groupings of a manufacturing enterprise. A Site can be divided in areas which are defined by IEC 62264 <a href="#[i.11]">[i.11]</a> as physical, geographical or logical groupings of resources determined by the site. An Area contains one or multiple work centers, which are a subclass of the <a href="#s4inma:ProductionEquipment">s4inma:ProductionEquipment</a> class and are defined according to IEC 62264 <a href="#[i.11]">[i.11]</a> as equipment elements under an area in a role-based equipment hierarchy that performs production, storage or material movement.</p>

<p>Note that as a subclass of <a href="https://saref.etsi.org/core/Device">saref:Device</a>, a production equipment in SAREF4INMA inherits all the properties of devices defined in SAREF. This includes the possibility to associate a device (and therefore a production equipment) with a number of functions. For the purpose of SAREF4INMA, a new class of functions is created, namely the <a href="#s4inma:ProductionEquipmentFunction">s4inma:ProductionEquipmentFunction</a> class, which can be populated with subclasses that describe relevant functions, depending on the use case under consideration.</p>

<h3>Measurement</h3>

<h3>Observation</h3>

<p>An important aspect of SAREF4INMA is the ability to trace back production process measurements to individual items or batches. The modelling of measurements in SAREF4INMA totally relies on the measurement model proposed in SAREF. This modelling include the <a href="https://saref.etsi.org/core/FeatureOfInterest">saref:FeatureOfInterest</a> class that provides the means to refer to the real world phenomena that is being observed in the given measurement (e.g. a shaver is an item resulting from a certain production process and it can be defined as the feature of interest of a temperature measurement made by a welding machine used to join different parts in the production of the shaver). The reader shall refer to the SAREF specification for details about the modelling of measurements. The following properties are reused in SAREF4INMA to complete the model of measurements:</p>

<p>An important aspect of SAREF4INMA is the ability to trace back production process observations to individual items or batches. The modelling of observations in SAREF4INMA totally relies on the observations model proposed in SAREF. This modelling include the <a href="https://saref.etsi.org/core/FeatureOfInterest">saref:FeatureOfInterest</a> class that provides the means to refer to the real world phenomena that is being observed in the given observation (e.g. a shaver is an item resulting from a certain production process and it can be defined as the feature of interest of a temperature observation made by a welding machine used to join different parts in the production of the shaver). The reader shall refer to the SAREF specification for details about the modelling of observations. The following properties are reused in SAREF4INMA to complete the model of observations:</p>

<ul>

 <li><a href="https://saref.etsi.org/core/isPropertyOf">saref:isPropertyOf</a> (and its inverse <a href="https://saref.etsi.org/core/hasProperty">saref:hasProperty</a>) to link the property being observed with the feature of interest.</li>

 <li><a href="https://saref.etsi.org/core/hasFeatureOfInterest">saref:hasFeatureOfInterest</a> (and its inverse <a href="https://saref.etsi.org/core/isFeatureOfInterestOf">saref:isFeatureOfInterestOf</a>) to link a given measurement with the feature of interest being observed.</li>

 <li><a href="https://saref.etsi.org/core/measurementMadeBy">saref:measurementMadeBy</a> has been included as complement of the <a href="https://saref.etsi.org/core/makesMeasurement">saref:makesMeasurement</a>, as its inverse, to link a measurement and the device that produces it.</li>

 <li><a href="https://saref.etsi.org/core/observes">saref:observes</a> (and its inverse <a href="https://saref.etsi.org/core/isObservedBy">saref:isObservedBy</a>) to link a given observation with the feature of interest being observed.</li>

 <li><a href="https://saref.etsi.org/core/madeBy">saref:madeBy</a> has been included as complement of the <a href="https://saref.etsi.org/core/madeExecution">saref:madeExecution</a>, as its inverse, to link a measurement and the device that produces it.</li>

</ul>

<p>Note that the present document includes details only for the new concepts created in SAREF4INMA, such as the <a href="#s4inma:Measurement">s4inma:Measurement</a> class. The classes of interest for measurements are shown in <a href="#Figure_5">Figure 5</a>.</p>

<p>The <a href="#s4inma:Measurement">s4inma:Measurement</a> class is defined as a subclass of the more general <a href="https://saref.etsi.org/core/Measurement">saref:Measurement</a> class. The <a href="#s4inma:Measurement">s4inma:Measurement</a> class is further specialized in the <a href="#s4inma:ActualMeasurement">s4inma:ActualMeasurement</a> and <a href="#s4inma:ExpectedMeasurement">s4inma:ExpectedMeasurement</a> classes to describe whether a certain measurement is planned (i.e. expected) or is actually measured during the production process (i.e. actual measurement). This enables the calculation of deviations between planned and actual production process measurements.</p>

<p>As a <a href="https://saref.etsi.org/core/Device">saref:Device</a> can recursively consists of devices, a ProductionEquipment in SAREF4INMA can also consist of other devices, such sensors and actuators. A device (e.g. production equipment and its sensors) can make measurements. These measurements can be related to a specific <a href="#s4inma:Batch">s4inma:Batch</a> or <a href="#s4inma:Item">s4inma:Item</a> (which are both subclasses of the <a href="https://saref.etsi.org/core/FeatureOfInterest">saref:FeatureOfInterest</a> class) via thehasFeatureOfInterest relation. Moreover, according to the measurement model in SAREF, measurements are related to the property they observe (e.g. welding temperature) and its unit of measure (e.g. degrees Celsius).</p>

<figure>

  <a href="diagrams/Measurement.png"><img src="diagrams/Measurement.png" alt="Measurement"/></a>

  <figcaption id="Figure_4">Figure 4: Measurement</figcaption>

</figure>

<p>Within the SAREF4INMA use cases there is a need to distinguish between actual measurements and expected ones. For the former could be represented by stating a property value for a <a href="https://saref.etsi.org/core/FeatureKind">saref:FeatureKind</a>, while the latter could be stated stating the value of a <a href="https://saref.etsi.org/core/FeatureKind">saref:FeatureKind</a>that related to the saref:FeatureKind, or by stating an <a href="https://saref.etsi.org/core/Observation">saref:Observation</a>. This enables the calculation of deviations between planned and actual production process observations.</p>

<p>As a saref:Device can recursively consists of devices, a ProductionEquipment in SAREF4INMA can also consist of other devices, such sensors and actuators. A device (e.g. production equipment and its sensors) can make observations. These observation scan be related to a specific <a href="https://saref.etsi.org/core/Batch">saref:Batch</a> or <a href="https://saref.etsi.org/core/Item">saref:Item</a>(which are both subclasses of the <a href="https://saref.etsi.org/core/FeatureOfInterest">saref:FeatureOfInterest</a> class) via the hasFeatureOfInterest relation. Moreover, according to the observations model in SAREF, observations are related to the property they observe (e.g. welding temperature) and its unit of measure (e.g. degrees Celsius).</p>