#  EXECUTIVE SUMMARY

The present document is a deliverable of the SatisFactory project, funded by
the European Union’s Horizon 2020 Research and Innovation programme (H2020).
It constitutes the fourth and final version of the project’s Data Management
Plan (DMP).

This version presents in detail the various datasets produced within the
project, as well as the strategy put in place around their storage, protection
and sharing among the project’s partners and beyond.

Throughout the project, the team needed to manage a large number of datasets,
generated and collected by various means, i.e. sensors, cameras, manual inputs
in IT systems and direct interactions with employees (e.g. interviews). By the
end of the project, 31 different datasets have been produced through the
SatisFactory’s technical activities, with almost all the partners being data
owners and/or producers.

All SatisFactory datasets have been handled considering the main data security
and privacy principles, respecting also the partners IPR policies. A dedicated
Data Management Portal, developed by the project, further supported the
efficient management, storage and sharing of the project’s datasets.

Finally, SatisFactory supports the Open Research Data Pilot (ORD) and believes
firmly in the concepts of open science. In this context, the team has taken
measures to ensure that the project’s results are used by other stakeholders,
such as researchers or industry actors, stimulating in this way the continuity
and transfer of the SatisFactory outputs to further research and other
initiatives, allowing others to build upon, benefit from and be influenced by
them - though this objective obviously needs to be balanced with IPR and data
privacy principles. Interested stakeholders will be able to access open
resources generated by the project, such as reports, publications and
datasets, through various platforms, even beyond the project’s duration. This
way, sustainability of the SatisFactory outcomes will be fostered.

#  INTRODUCTION

The SatisFactory project aims to enhance and enrich the manufacturing working
environment towards attractive factories of the future that encompass key
enabling technologies, such as augmented reality, wearable and ubiquitous
computing, as well as customised social communication platforms, coupled with
gamification techniques for the efficient transfer of knowledge and experience
among employees.

The purpose of the Data Management Plan (DMP) is to provide an analysis of the
main elements of the data management policy used by the consortium regarding
all the datasets generated by the project.

The DMP has not been a fixed plan since the beginning, but has evolved during
the lifespan of the project. Its fourth and final version presented in the
current document includes:

  * an updated overview of the datasets produced by the project, their characteristics and their management processes; 

  

  * additional information regarding the dissemination of the project’s open access knowledge and datasets, aiming to foster further exploitation of the SatisFactory’s results by the scientific community and industrial stakeholders. 

  

#  ACTIVITIES TIMELINE

The main activities planned and carried out during the project concerning the
SatisFactory data management are presented below, along with a high level time
plan (Figure 1):

  * M6: Preliminary analysis and production of the first version of the Data Management Plan (submitted); 

  

  * M12: Refined analysis based on the progress in the development of the tools and the definition of the case studies, described in the second version of the Data Management Plan (submitted); 

  

  * M16: Drafting of the specifications for the project Data Management Portal (first included in D6.2 v3.0); 

  

  * M17-M19: Development of the Data Management Portal (completed by CERTH); 

  

  * M20: The Data Management Portal is operational; 

  

  * M24: Third version of the Data Management Plan, updated with procedures implemented by the project towards the pilot demonstrators, and preparing the sustainability of the data storage after the end of the project (submitted); 

  

  * M36: Final Data Management Plan, describing the plans implemented by 

  

SatisFactory for sustainable storage and accessibility of the data.

**Figure 1 - Data management timeline**

#  GENERAL PRINCIPLES

##  IPR MANAGEMENT AND SECURITY

As an innovation action which is close to the market, SatisFactory covers
high-TRL technologies and aims at developing marketable solutions. The project
consortium includes many partners from the private sector, namely technology
developers (namely ABE, GLASSUP, and REGOLA) and end-users (namely COMAU and
SUNLIGHT). Those partners obviously have Intellectual Property Rights on their
technologies and data, on which their economic sustainability is at stake.
Consequently, the SatisFactory consortium protects that data and crosschecks
with the concerned partners before every data publication.

Considering the above, as well as the fact that the data collected through
SatisFactory are of high value, every measure should be taken to prevent them
from leak or being hacked. This is another key aspect of SatisFactory data
management, and therefore, every data repository used by the project is
effectively protected. A holistic security approach has been followed, in
order to protect the pillars of information security, i.e. confidentiality,
integrity and availability.

Security measures include the implementation of PAKE protocols, such as the
SRP protocol, and protection from bots, such as CAPTCHA technologies.
Moreover, the industrial demo sites apply monitored and controlled procedures
related to the data collection, their integrity and protection. The data
protection and assurance of privacy of personal information include protective
measures against infiltration, as well as physical protection of core parts of
the systems and access control measures.

##  PERSONAL DATA PROTECTION

SatisFactory’s activities involve the human factor, as the pilots are
conducted in real shop floors with actual workers. However, no personal data
of these workers were required nor collected during the project. The team
generally avoided to collect even basic personal data (e.g. name, background,
contact details), unless it was really necessary (e.g. for managing external
participants of workshops). This data are protected in accordance with the
EU's _Data Protection Directive 95/46/EC_ 1  “on the protection of individuals
with regard to the processing of personal data and on the free movement of
such data”. National legislations are also applicable, such as the _Italian
Personal Data Protection Code_ 2  .

The industrial pilot sites also implement health and safety management
standards (BS OHSAS 18001:2007) and are compliant with the regulations on
managing personal information of their employees.

#  DATA MANAGEMENT PLAN

##  DATASET LIST

SatisFactory partners identified and later updated the data produced in the
different project activities. The datasets list is provided in the table
below, while the nature and details for each dataset are presented in the next
sub-section. The datasets added in this version of the report are marked with
“new M36”, while the updated ones with “updated M36”.

**Table 1 - Datasets tracking**  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Dataset Name**

</th>  
<th>

**Status**

</th> </tr>  
<tr>  
<td>

1

</td>  
<td>

DS.CERTH.01.IncidentDetection

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

2

</td>  
<td>

DS.CERTH.02.ProcessField

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

3

</td>  
<td>

DS.CERTH.03.SocialCollaborationPlatform

</td>  
<td>

“New M36”

</td> </tr>  
<tr>  
<td>

4

</td>  
<td>

DS.COMAU.01.Accelerometer_jacket

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

5

</td>  
<td>

DS.COMAU.01.Gyroscope_jacket

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

6

</td>  
<td>

DS.COMAU.01.Cardio_jacket

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

7

</td>  
<td>

DS.COMAU.02.RFID_torque_wrench

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

8

</td>  
<td>

DS.COMAU.03.Work_bench_camera

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

9

</td>  
<td>

DS.COMAU.04.Glasses

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

10

</td>  
<td>

DS.COMAU.05.Digital_caliper_USB

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

11

</td>  
<td>

DS.COMAU.06.Torque_wrench_USB

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

12

</td>  
<td>

DS.COMAU.07.Dinamometer_USB

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

13

</td>  
<td>

DS.COMAU.08.Micrometer_USB

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

14

</td>  
<td>

DS.COMAU.09.Digital_dial_USB

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

15

</td>  
<td>

DS.ISMB.01.FallDetection (previously named DS.ISMB.01.incidentDetection)

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

16

</td>  
<td>

DS.ISMB.02.GestureDetection

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

17

</td>  
<td>

DS.ISMB.03.PresenceDetection

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

18

</td>  
<td>

DS.ISMB.04.VideoRecordingEvent

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

19

</td>  
<td>

DS.ISMB.05.VideoRecording

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

20

</td>  
<td>

DS.ISMB.06.LocalizationManager_VirtualFencing

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

</td>  
<td>

(previously named DS.ISMB.06.UWB_VirtualFencing)

</td>  
<td>

</td> </tr>  
<tr>  
<td>

21

</td>  
<td>

DS.ISMB.07.UWB_Localization

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

22

</td>  
<td>

DS.ISMB.08.Ergonomics_Data

</td>  
<td>

“new M36”

</td> </tr>  
<tr>  
<td>

23

</td>  
<td>

DS.ABE.01.IntegratedDSS

</td>  
<td>

“updated M36”

</td> </tr>  
<tr>  
<td>

24

</td>  
<td>

DS.FIT.01.UserRequirements

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

25

</td>  
<td>

DS.Regola.01.ARModels

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

26

</td>  
<td>

DS.Regola.02.TrainingData

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

27

</td>  
<td>

DS.Sunlight.01.MotiveBatteriesAssembly

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

28

</td>  
<td>

DS.Sunlight.02.Training&SuggestionsPlatform

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

29

</td>  
<td>

DS.Sunlight.03.TempMonitoringInJarFormation

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

30

</td>  
<td>

DS.Sunlight.04.MalfunctionIncidentManagement

</td>  
<td>

“no change”

</td> </tr>  
<tr>  
<td>

31

</td>  
<td>

DS.Sunlight.05.Handwashing

</td>  
<td>

“new M36”

</td> </tr> </table>

##  PLANS PER DATASET  
  
<table>  
<tr>  
<th>

**DS.CERTH.01.IncidentDetection**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset for incident detection, along with high-level activities and business
processes monitoring (e.g. activities occurring at the shop-floor, etc.),
obtained with thermal and depth cameras mounted at specific locations in the
shop-floor.

In particular, depth cameras will detect the following incidents: 1) human
falls, 2) falling items, 3) collisions between moving objects, 4) intrusions
to forbidden areas, while thermal cameras will detect overheated areas within
the shop-floor.

The depth and thermal images will be processed and not saved anywhere, while
only the metadata of the incident detection process will be stored. These data
will be comprised by anonymized alarms that will include the type of the
occurring incident (e.g. human fall, collision, sudden heating of an
electrical component etc.) accompanied by the corresponding timestamp and
exact location of the event (specific room and exact coordinates on the
architectural map of the building). Similar information (metadata of the
processed depth and thermal images) do not exist or provided freeware for
shop-floor environments.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected using thermal and depth cameras located at the
areas under interest.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by the industrial plant (CERTH/CPERI, COMAU,
SUNLIGHT), where the data collection is going to be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and more
specifically within activities of T3.3 and T4.3.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The dataset will be accompanied by a detailed documentation of its contents.
Indicative metadata include:

(a) description of the experimental setup (e.g. location, date, etc.) and
procedure that led to the generation of the dataset; (b) annotated incident,
activity, business process, state of the monitored activity and the involved
humans per time interval, etc.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be stored at XML format (CIDEM compatible) and are estimated to
be 35 MB per day.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected data will be used for the development of the activities analysis
and incident detection methods of the SatisFactory project and all the tasks,
activities and methods that are related to it.

Furthermore, the different parts of the dataset could be useful in the
benchmarking of a series of human detection and tracking methods, activity
detection focusing either on pose and gestures analysis and tracking, on high-
level activity recognition, on affect related human activity analysis and on
incident analysis and detection.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it.

Furthermore, if the dataset or specific portions of it (e.g. metadata,
statistics, etc.) are decided to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The full dataset will be shared with the consortium using a data management
portal that created and maintained by CERTH. The public version of the data
will be shared within the portal as well. Of course, the data management
portal will be equipped with authentication mechanisms, so as to handle the
identity of the persons/organizations that download them, as well as the
purpose and the use of the downloaded dataset.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Both full and public versions of the dataset will be accommodated at the data
management portal created and maintained by CERTH, while links to the portal
will exist at the SatisFactory website. Furthermore, in order to avoid data
losses, RAID and other common backup mechanism will be utilized ensuring data
reliability and performance improvement. The dataset will remain at the data
management portal for the whole project duration, as well as for at least 2
years after the end of the project. The volume of data is estimated to be
about 10 GB for all pilots.

Finally, after the end of the project, the portal is going to be accommodated
with other portals at the same server, so as to minimize the needed costs for
its maintenance.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.CERTH.02.ProcessField**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset for shop-floor information related to the status and condition of the
involved machinery and production-process system (e.g. field data related to
the status of a device, such as a pump, a motor etc.) that workers interact
with at the shopfloor, etc.).

The dataset will also include the human actions and the logging of commands
and activity during different conditions and states, to be used for the
decision support system and procedures. The dataset will include real-time
data and archived historical data of the involved process plants.

Similar raw information at the detail level that the project needs, neither
exist nor are provided freeware in the literature for shop-floor environments.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected through the automation systems that acquire the
signals from the respective field network of interest. The device managers
will communicate with the automation systems in order to transfer the selected
data to the Satisfactory repository.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by CERTH/CPERI, where the data collection is going to
be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Initially the static and persistent data along will a set of dynamic data will
be collected within activities of WP3 and more specifically within activities
of T3.3 and T3.5. The dynamic data will be updated during WP5 and more
specifically in T5.3.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The dataset will be accompanied with the respective documentation of its
contents. Indicative metadata include: (a) description of the experimental
setup (e.g. process system, date, etc.) and procedure which is related to the
dataset (e.g. proactive maintenance action, unplanned event, nominal
operation. etc.),

(b) scenario related procedures, state of the monitored activity and involved
workers, involved system etc.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be stored in XML format and are estimated to be 200-1000 MB per
month.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The raw field layer data will be enriched with semantics by the middleware
components and will be used for the sharing of information between the process
system and the involved actors at the shop-floor.

The collected data will be used by the integrated decision support system and
the event manager, in order to represent the input for the operation and the
maintenance procedures, along with the identification of unplanned incidents
at the shopfloor and to analyse the response and behaviour of the workers
through their interaction with the Satisfactory platform.

The initial set of dynamic data will be analysed during the development of the
Satisfactory platform and the nominal dynamic data will be used during the
deployment phase at the shop-floor.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if specific portions of it (e.g.
metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential correlation and identification of
the ethical issues with their publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The created dataset will be shared with the consortium using a data management
portal created and maintained by CERTH. The public version of the data will be
shared within the portal as well. Of course, the data management portal will
be equipped with authentication mechanisms, so as to handle the identity of
the persons/organizations that download them, as well as the purpose and the
use of the downloaded dataset.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Both full and public versions of the dataset will be accommodated at the data
management portal created and maintained by CERTH, while links to the portal
will exist at the SatisFactory website. Furthermore, in order to avoid data
losses, RAID and other common backup mechanism will be utilized ensuring data
reliability and performance improvement. The archiving system of CERTH/CPERI
will contain the initial data as sent to the Satisfactory repository.

The dataset will remain at the data management portal for the whole project
duration, as well as for at least 2 years after the end of the project.

The volume of data is estimated to be about 50 GB for all pilots. Finally,
after the end of the project, the portal is going to be accommodated with
other portals at the same server, so as to minimize the needed costs for its
maintenance.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.CERTH.03.SocialCollaborationPlatform**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Data produced by the use of the platform such as a) posted text, images,
videos, b) posted questions and answers on the forum, c) notifications
generated by shop floor incidents, social activities, gamification events and
d) chat messages exchanged between users.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The data are generated in the device where users access the Social platform
front-end and are stored in the back-end of the platform.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by the industrial plant (CERTH/CPERI, COMAU,
SUNLIGHT), where the data collection is going to be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP2, WP3, WP4, WP5 and
more specifically within activities of T2.3, T2.4, T3.4, T4.5, T5.1, T5.3 and
T5.4.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that are being used are the appropriate details for each type of data
(e.g. title, description, date, access qualifier for videos ).

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data are stored in a MySQL database with the exception of multimedia
content (images, videos) that are stored in the filesystem of the server.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected data will be used for performing analytics through the Social
Platform’s dashboard view.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it.

Furthermore, if the dataset or specific portions of it (e.g. metadata,
statistics, etc.) are decided to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data is not currently shared

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data from Social Collaboration Platform are stored in a database where the
administrator of the platform can decide if and how often a back-up needed as
well as the time period that back-ups should be saved too.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.01.Jacket**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Data for ergonomic parameters monitoring, coming from sensors installed on a
jacket worn by the operators. This dataset will comprise several distinct sub-
datasets corresponding to each type of sensor, in order to simplify its
maintainability. Those sub-datasets, named

DS.COMAU.01.Accelerometer_jacket,

DS.COMAU.01.Gyroscope_jacket,

DS.COMAU.01.Cardio_jacket etc., will follow similar procedures but will be
managed independently.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected by different sensors installed on jackets worn
by operators, namely: an accelerometer, a gyroscope, and a temperature sensor.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and WP4.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Indicative metadata include worker's posture, e.g., trunk bending
forward/backward and time stamp.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data format has not been defined yet. Approximately, the estimated volume
of data is less than 2MB per day per worker.

Format will be defined by the technical partners.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Benchmarking of a series of human detection and tracking methods, activity
detection focusing either on pose and gestures analysis and tracking

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The created dataset could be shared by using open APIs through the middleware.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies. Data has to be stored on a SQL
Circular Database (not yet existing) that must contain data for at least 1
year, and then each day the oldest data (today-365) should be deleted.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.02.RFID_torque_wrench**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

Format will be defined by the technical partners. Thus, a data volume
estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies. Data has to be stored on a SQL
Circular Database (not yet existing) till the end of life/warranty of the
produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.03.Work_bench_camera**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Camera installed on the workbench where the operator works. The type of camera
will be defined at a later stage based on the use-cases to be developed.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

Format will be defined by the technical partners. Thus, a data volume
estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies. Data has to be stored on a SQL
Circular Database (not yet existing) till the end of life/warranty of the
produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.04.Glasses**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

The data are collected by the sensors installed on the glasses developed by
GlassUp. Images, videos and sound create a dataset that arise from actions
triggered from them.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected by different sensors installed on the GlassUp
glasses worn by operators when they do daily activities. The actions are
supported by glasses and produce these data are remote assistance and remote
maintenance.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

GLASSUP

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with GLASSUP

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

Middleware Manager with GLASSUP

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

Middleware Manager with GLASSUP

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The dataset will be accompanied by a detailed documentation of its contents.
Indicative metadata include:

(a) description of the experimental setup (e.g. location, date and time,
serial number of the eyeglass, badge number of the user, code number of the
test that was being performed etc.) and procedure that led to the generation
of the dataset, (b) action that the operator will take using the mobile
application (i.e. recording video, sending pictures, tag the log of date for
the event + information/description of the event).

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be stored in XML format and are not estimated yet,

being dependent on the video format and the test on uses cases. At least
1GB/day is expected.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Benchmarking of a series of human detection and tracking methods, activity detection focusing either on pose and gestures analysis and tracking 

  

  * For the cameras: Support for contextual data related on the machine/devices monitored, remote support for maintenance 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The data will be stored daily on the mobile app and will be daily backed up on
the server of the Satisfactory. Furthermore, in order to avoid data losses,
RAID and other common backup mechanism will be utilized ensuring data
reliability and performance improvement.

The dataset will remain at the data management portal for the whole project
duration, as well as at least for 2 years after the end of the project.

Finally, after the end of the project, the portal is going to be accommodated
with other portals at the same server, so as to minimize the needed costs for
its maintenance.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.05.Digital_caliper_USB**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

Format will be defined by the technical partners. Thus, a data volume
estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies. Data has to be stored on a SQL
Circular Database (not yet existing) till the end of life/warranty of the
produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.06.Torque_wrench_USB**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

it will be defined by the technical partners, thus a data volume estimation
will be later provided.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data format has not been defined yet.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies.

Data has to be stored on a SQL Circular Database (not yet existing) till the
end of life/warranty of the produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.07.Dinamometer_USB**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and

WP4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data format has not been defined yet, it will be defined by the technical
partners , thus a data volume estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies.

Data has to be stored on a SQL Circular Database (not yet existing) till the
end of life/warranty of the produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.08.Micrometer_USB**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and WP4.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data format has not been defined yet. Ιt will be defined by the technical
partners, thus a data volume estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Production process recognition and help during the different production
phases, avoiding mistakes.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies.

Data has to be stored on a SQL Circular Database (not yet existing) till the
end of life/warranty of the produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.COMAU.09.Digital_dial_USB**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Sensors installed on the workbench where the operator normally works

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

RFID installed on the torque wrenches used by the operator.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

COMAU

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

COMAU with REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

REGOLA

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and WP4.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata is yet to be defined by the solution provider.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data format has not been defined yet. It will be defined by the technical
partners, thus a data volume estimation will be later provided.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

  * Production process recognition and help during the different production phases, avoiding mistakes 

  

  * Support of quality checks and production batches recalls 

  

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The sharing of this data is yet to be decided in accordance to COMAU policies
and other partners’ requirements.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

All information belongs to the industrial partner that owns the shop floor.
All data will respect the partner policies.

Data has to be stored on a SQL Circular Database (not yet existing) till the
end of life/warranty of the produced component.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.01.FallDetection**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td>  
<td>

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

This dataset contains information about Smart Assembly Station workers fall
events.

The information is obtained by Gesture & Content Recognition Manager
performing a complex set of analysis on input video streams from a composite
device, including a conventional colour camera and a time-of-flight infrared
sensor.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Gesture & Content Recognition Manager connected to a Kinect XBOX 360 depth
sensor located in the Smart Assembly Station

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td>  
<td>

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Devices are owned by the industrial partner.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

The data is not currently stored

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

WP3: T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td>  
<td>

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The fall dataset includes:

  * the identifiers of both Smart Assembly Station and shop floor where the event occurred 

  

  * the date when the event occurred 

  

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The dataset XML format is defined by the Common Information Data Exchange
Model XML Schema Definition (see WorkAlertInformationType). Each event size is
normally about 2 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td>  
<td>

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The events triggered are used by SatisFactory ecosystem components to improve
actors’ reaction times in safety related situations and to activate procedures
to avoid recurrence of accidents.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The dataset is confidential and all information belongs to the industrial
partner that owns the shop floor.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset is distributed using the LinkSmart middleware MQTT broker.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The data is not currently stored

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.02.GestureDetection**

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Through a continuous monitoring of the Smart Assembly Station the Gesture &
Content Recognition Manager can spot predefined worker gestures.

This dataset contains information about the detected gestures.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Gesture & Content Recognition Manager connected to a Kinect

XBOX 360 depth sensor located in the Smart Assembly

Station.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Devices are owned by the industrial partner.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

The data is not currently stored

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

WP3: T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The gesture data set include:

  * the identifiers of both Smart Assembly Station and shop floor where the event occurred 

  

  * the date when the event occurred 

  

  * the type of gestures (LeftHandSwipeRight, 

  

RightHandSwipeLeft, BothHandsRaised,

RightArmRaisedLeftArmPointOut,

LeftArmRaisedRightArmPointOut)

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The dataset XML format is defined by the Common Information Data Exchange
Model XML Schema Definition (see

GestureType). Each event size is normally about 2 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The events triggered are used to feed management toolkits and to manage
contactless applications where users don't have easy access to standard input
devices due to safety gear.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The dataset is confidential and all information belongs to the industrial
partner that owns the shop floor.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset is distributed using the LinkSmart middleware MQTT broker.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The data is not currently stored

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.03.PresenceDetection**

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Through a continuous monitoring of the Smart Assembly Station the Gesture &
Content Recognition Manager can spot worker presence.

This dataset contains information about the number of workers detected.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Gesture & Content Recognition Manager connected to a Kinect

XBOX 360 depth sensor located in the Smart Assembly

Station.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Devices are owned by the industrial partner.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

The data is not currently stored

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

WP3: T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The presence data set include:

  * the identifiers of both Smart Assembly Station and shop floor where the event occurred 

  

  * the date when the event occurred 

  

  * the people count and previous people count 

  

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data set XML format is defined by the Common Information Data Exchange
Model XML Schema Definition (see PresenceType). Each event size is normally
about 2 KB of data..

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The events triggered are used to monitor the presence of workers in the Smart
Assembly Stations.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The dataset is confidential and all information belongs to the industrial
partner that owns the shop floor.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset is distributed using the LinkSmart middleware MQTT broker.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data is not currently stored.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.04.VideoRecordingEvent**

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

When specific events such as fall alarms are triggered by the Gesture &
Content Recognition Manager, the Multiple Media Manager server encodes
automatically the video and uploads it to the central unit.

The data set gives information about the current phase of the encoding
process.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Multiple Media Manager installed on Smart Assembly Station core hardware (an
Intel Next Unit of Computing)

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Devices are owned by the industrial partner.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

Data is not used

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

WP3: T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The video recording data set include:

  * the identifiers of both Smart Assembly Station and shop floor where the event occurred 

  

  * the date when the event occurred 

  

  * the referred alert event id 

  

  * the path of the produced video 

  

  * the information of the current phase about the encoding process 

  

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data set XML format is defined by the Common Information Data Exchange
Model XML Schema Definition (see RecordingType). Each event size is normally
about 2 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Data can be used by supervisors to correctly retrieve stored video
information.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The dataset is confidential and all information belongs to the industrial
partner that owns the shop floor

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset is distributed using the LinkSmart middleware MQTT broker.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The data is not currently stored.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.05.VideoRecording**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

When specific events such as fall alarms are triggered by the Gesture &
Content Recognition Manager, the Multiple Media Manager server encodes
automatically the video and uploads it to the central unit.

The data set is the encoded video containing the recording of the last minutes
before the fall event.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Multiple Media Manager installed on Smart Assembly Station core hardware (in
current deployment an Intel Next Unit of Computing)

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Devices are owned by the industrial partner.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

WP3: T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The video contained in the data set is enriched using auxiliary data form the
Gesture & Content Recognition Manager.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The videos in the dataset have the following characteristic:

  * MP4 format 

  

  * H264 video encoding 

  

  * Overlay metadata 

  

  * The video size for each incident is about 15Mb. 

  

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data could allow the visual detection and isolation of specific conditions
and factors which could have contributed to an incident in order to address
the necessary actions to avoid its recurrence.

Furthermore, the data analysis can provide mechanisms to search for incident
occurred previously in similar circumstances (e.g. workers without protective
equipment or with the same skills or at the same process time) to measure the
effects of preventive procedures.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The dataset is confidential and all information belongs to the industrial
partner that owns the shop floor.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The videos are distributed by the Multiple Media Manager Central Unit using
HTTPS progressive download.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The videos are stored by the Multiple Media Manager Central Unit for a
configurable period of time (currently 7 days). The size of the data is
strictly dependent on the number of incidents occurred in the configured
period.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.06.LocalizationManager_VirtualFencing**

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset reporting potential incidents based on workers location in the shop
floor. A virtual fencing approach based on a point in polygon algorithm is
adopted. The localization manager (LM) detects whether a worker is approaching
a dangerous area or whether he/she is inside of it. Moreover, LM reports when
new dynamic dangerous areas are generated when abnormal measurements from
sensors at the shop floor are detected. In addition, it reports also whether
there is no more any potential incident as well as when the dynamic dangerous
area has been deleted.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The data is generated by the localization manager which it is running on the
UWB GW device.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The developed software is owned by ISMB whilst the stored data will be owned
by the industrial partners.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Industrial partners (CERTH, SUNLIGHT, COMAU)

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data has been be collected within activities of WP3 (T3.3) and WP5.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Indicative metadata include: device Id, state of the worker (e.g., inside or
outside a dangerous area), name of the dangerous area, current location of the
worker in relative coordinates, alert Id, time stamp and event id.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The geofencing events can be accessed through MQTT APIs. The data is XML
formatted and it is compliant with the CIDEM specifications. The volume of
data generated per worker depends on the number of incidents detected. One
single event generates 2 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected is used for the development of the proactive incident detection
functionalities of the SatisFactory platform and for pilots demonstration.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset is confidential and only the members of the consortium have
access on it. Furthermore, if the dataset or specific portions of it (e.g.
metadata, statistics, etc.) are to become of widely open access, these could
be shared through the CIDEM. Of course, the data would be anonymized, so as
not to have any potential ethical issues with their publication and
dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The LocalizationManager VirtualFencing dataset could be shared using the APIs
of CIDEM. The public version of the data could be shared by using a suitable
authentication mechanism, so as to handle the identity of the
persons/organizations that access them.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data is stored in the CIDEM by the LinkSmart middleware.

This is done by means of the event aggregator. The Localization Manager
software has been installed in the endusers’ premises for industrial pilot
demonstrators. The approximated end volume will be 4 MB of data and it will be
stored for as long as CIDEM works at the industrial pilots.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.07.UWB_Localization**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset reporting, in real-time, the current position of workers at the shop
floor by means on UWB-based wearable devices. In particular, a wearable device
continuously performs ranging (i.e. distance) measurements from fixed UWB
anchors, at the shop floor, and estimates the worker position running a
localization algorithm.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The raw localization data is estimated by the UWB-based wearable devices which
are carried by workers. Wearable devices send workers location to an UWB GW
which is connected with the SatisFactory infrastructure. Moreover, this data
is put into CIDEM by the localization manager once per minute.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The UWB-based wearable devices are owned by ISMB.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Industrial partners (CERTH, SUNLIGHT, COMAU)

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data has been collected within activities of WP3 (T3.3) and WP5.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Indicative metadata include: event id, device Id, estimated position of the
worker in relative coordinates, shop floor Id, anchor connectivity and time
stamp.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The localization data is stored in the CIDEM by the LinkSmart middleware. The
data is XML formatted and it is CIDEM compliant. For each worker, it is
estimated one position per minute. The volume of data generated depends on the
number of workers that are localized and for how long they are localized. One
single event generates 4 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The raw data is used by the Localization Manager for the detection of
proactive incidents at the shop floor, based on current workers position.
Furthermore, localization data can be exploited by other components of
SatisFactory infrastructure such as Augmented Reality and Collaboration Tools.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset is confidential and only the members of the consortium have
access on it. Furthermore, if the dataset or specific portions of it (e.g.
metadata, statistics, etc.) are to become of widely open access, these could
be shared through the CIDEM. Of course. these data will be anonymized, so as
not to have any potential ethical issues with their publication and
dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The UWB Localization dataset could be shared using the CIDEM APIs. The public
version of the data could be shared through CIDEM by using a suitable
authentication mechanism so as to handle the identity of the
persons/organizations that access them.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data is stored in the CIDEM by LinkSmart. This is done by means of the event
aggregator. The UWB infrastructure (i.e.

UWB GW, UWB anchor nodes, UWB-based wearable devices) has been installed in
the end-users’ premises for the industrial pilot demonstrators. The
approximated end volume will be 100 MB of data and it will last until CIDEM is
working at the industrial pilots.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ISMB.08.Ergonomics_Data**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset reporting, in real-time, workers attitude referred to their back as
well as alerts related to wrong postures (ergonomics alerts) adopted during
daily activities. This data set provides support to ergonomics applications
aiming to improve wellness at shop floor.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Raw attitude data is estimated by UWB-based wearable devices which are carried
by workers. Besides, these data and the ergonomics alerts are put into CIDEM
by the UWB GW.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The UWB-based wearable devices are owned by ISMB.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Industrial partners (CERTH, SUNLIGHT, COMAU)

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ISMB

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data has been collected within activities of WP3 (T3.3) and WP5.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Indicative metadata include: shop floor id, event id, device id, data type,
time stamp, space id, short description and pitch and roll measurements
(attitude data) or alert id and priority for ergonomics data.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The ergonomics data is XML formatted and CIDEM compliant. For each worker, it
is generated one attitude data per second while the ergonomics data depends on
when the event happens. The volume of data generated depends on the number of
workers and triggered alerts per person during one working day. One single
event generates 1 KB of data.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Attitude data and ergonomics data are used by other SatisFactory components in
order to evaluate the ergonomics of workers.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset is confidential and only the members of the consortium have
access on it. Furthermore, if the dataset or specific portions of it (e.g.
metadata, statistics, etc.) are to become of widely open access, these could
be shared through the CIDEM. Of course. these data will be anonymized, so as
not to have any potential ethical issues with their publication and
dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset could be shared using the CIDEM APIs. The public version of the
data could be shared through CIDEM by using a suitable authentication
mechanism so as to handle the identity of the persons/organizations that
access them.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data is stored in the CIDEM by means of CIDEM APIs. The approximated end
volume will be 865 MB of data and it will last until CIDEM is working at the
industrial pilots.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.ABE.01.IntegratedDSS**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Input dataset of Shop Floor Feedback Engine and iDSS is obtained by Smart
Sensor Network. Thermal and Depth Cameras receive events on shopfloor.
Processed and anonymised alarms are sent to the Shop Floor Feedback Engine and
iDSS. Device Manager, Gesture Recognition

Context Manager, Semantic Manager, AR In – Factory Platform and Gamification
Adaptation Interface create events and store them in CIDEM. iDSS access data
from CIDEM though LiknSmart middleware. Output dataset of iDSS includes tasks
created on the Maintenance Toolkit and their propagation to the Shop Floor
Feedback Engine, Gesture Recognition Context Manager, Semantic Manager, AR In
– Factory Platform. Tasks are created based on input data. iDSS sends message
data to Gamification Platform in order users to gain points in Maintenance
game. Notification data such as push notifications, email etc is also the
output of iDSS. All output data is also communicated to CIDEM repository.
Output data also include data available for the Human Resourced Re –
Adaptation Toolkit and the creation of automated schedules according to tasks
on Maintenance Toolkit. Output data is used in the Visual Training Data
Analytics Toolkit to create Key Performance Indicators which will explain the
gained knowledge of the SatisFactory components. Output data is also used as
an input for the AR Glasses of the AR In – Factory Platform.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Device Manager, Event Manager, Semantic Context Manager,

AR In-Factory Platform, Gamification Adaptation Interface, Gesture Recognition
Context Manager, iDSS, CIDEM,

LinkSmart Middleware, Shop Floor Feedback Engine

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by the industry (COMAU, CERTH/CPERI, SUNLIGHT), where
the data collection is going to be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Various partners related to the specific incident and/or operation

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

Various partners related to the specific incident and/or operation

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

ABE will store data related to integratedDSS (various partners can handle the
rest of the data)

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of WP3 and WP4 and WP5

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Indicative metadata include: shop floor data, production results (including
timestamp, location), preventive maintenance schedules combined with
instruction and attachments. Metadata for Gamification platform contain
database entries such as ID, trades, taskID, task status. Notification
metadata also use database entries to create the notification.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

Data can be available in XML or JSON format. Estimation of the volume of data
cannot be expertly predicted in advance of real use of the technology on the
shop floor level, but an estimate of 25MB of data is possible. The number
contains all possible data creation including attachment files, which can be
different formats (PDF, TXT, JPEG, MPEG, etc). Http send messages are also
included in the estimate.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Collected data is used for operational purposes and real-time functionality of
iDSS. Data is used for processing, creating and publishing tasks to different
SatisFactory components and improve maintenance procedures on the shopfloors.
Real – time data should be available for continuous operation of iDSS as
defined. Data produced by the iDSS is also published and made available to
other components for real – time use. AR Glass will also use data in real –
time to show the created task on the screen.

Collected data will be used for better understanding of the processes and
activities evolving in the Shopfloor which in conjunction with pre-defined
response policies and strategies will provide actionable knowledge in the form
of a set of recommendations regarding both maintenance and manufacturing
operations. Also, new knowledge will be extracted and exploited from the
Gamification Adaptation Interface. This knowledge comes from the social
collaboration of workers outside the working environment. Visual Training Data
Analytics Toolkit (VTDAT) uses the available data to create visualisation of
KPIs and quantify the gained knowledge.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

If such a need arises, sharing of this data among consortium partners will be
decided and handled based on agreed terms with the respective industrial
partner.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data will be stored in a DB. RAID and other common backup mechanism will be
utilized to ensure data reliability and performance improvement and to avoid
data losses.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.FIT.01.UserRequirements**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Data that is collected in user workshops with the goal of understanding the
shop floor workers’ work environment and their needs

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Semi­structured interviews and other questioning techniques in user workshops

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Data not collected by device

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

The interviews will be conducted by COMAU, SUNLIGHT, CERTH/CPERI and FIT.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

FIT

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The requirements engineering is focus of WP1.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The data collection process will be described as well as there will be minutes
of the workshops.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

Semi­structured interviews, Questionnaires, Shadowing, Think Aloud Prototypes,
Velcro Modelling

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected data builds the foundation for all activities in the project.
The analysis will determine what the SatisFactory shall achieve and thus it
will determine the actions for all WPs.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. The results of the analysis will be accessible in the
public deliverables D1.1 and partly in D1.2. For this, all data will be
anonymized.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset will be stored in a restricted folder of the BSCW and will be only
shared with the partners.

It cannot be made available due to confidentiality agreements with the
interviewees themselves.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

Forever

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Included in the normal BSCW backup strategy

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Regola.01.ARModels**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset containing information captured at low-level and representing human
activities in the shop floor context; graphic model describing objects
processed during the activities; video and audio recorded during actions (e.g.
activities occurring at the shop-floor, etc.) obtained with AR cameras mounted
on specific wearable devices; executable script containing stepby-step
instructions, dynamic help visualized trough the glasses, etc.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected using cameras integrated in the wearable device
and cameras located at the areas of interest.

The recordings will be colour and HR.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by the industry (COMAU, CERTH/CPERI, SUNLIGHT), where
the data collection is going to be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Regola

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

Regola

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

Regola

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of T2.5 and of T4.3.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The dataset will be accompanied by a detailed documentation of its contents.
Indicative metadata include: (a) description of the working phase (e.g.
location, date, etc.) SOP and procedure that led to the generation of the
dataset, (b) description of involved objects.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

3D Formats: 3DM, 3DS, DXF, DWG, IGES, Collada DAE, FBX, OBJ, PLY, ASC, RAW,
SKP, SLDPRT, STP, STEP, STL, WRL, VRML, SGF e SGP (proprietary scenegraph file
formats). Image Formats: BMP, DIB, JPG, TGA, PNG, DDS, HDR Audio Formats: WAV,
MID, MP3 Video Formats: AVP,

MPG Motion Capture Formats: BVH, C3D, HTR, GTR Original SOP Formats: PDF,
DOCX, XLS, XLSX, etc. R3D RT SOP Formats: RTS (proprietary XML-Based file
format). The data will be stored at XML format and are estimated to be 40 GB
per day.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected data will be used for analysis of operator's behaviour and the
development of the scripts containing stepby-step instruction and the controls
of correctness of activities.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. Furthermore, if the dataset or specific portions of it
(e.g. metadata, statistics, etc.) are to become of widely open access, a data
management portal will be created that should provide a description of the
dataset and link to a download section. Of course, these data will be
anonymized, so as not to have any potential ethical issues with their
publication and dissemination.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The full dataset will be shared using a data management portal. The data
management portal will be equipped with authentication mechanisms, so as to
handle the identity of the persons/organizations that download them, as well
as the purpose and the use of the downloaded dataset.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Both full and public versions of the dataset will be accommodated at the data
management portal; RAID and other common backup mechanism will be utilized
ensuring data reliability and performance improvement.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Regola.02.TrainingData**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Dataset containing audit data captured by the Presentation Tool. The dataset
includes execution instances of the Training Procedures in the shop floor
context. The data are described in the Annex B of the deliverable: D2.5. They
are parameters identifying the trainee and the procedure; the procedure under
execution; the time spent for the execution of the procedure’s steps; the
survey data submitted at the end of the procedure; etc.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

The dataset will be collected using the platform where the Presentation tool
is under execution: Smartphones; Smartglass; Tablets.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

The device will be owned by the industry (COMAU, CERTH/CPERI, SUNLIGHT), where
the data collection is going to be performed.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

Regola

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ABE

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

The industry (COMAU, CERTH/CPERI, SUNLIGHT), where the data collection is
going to be performed.

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

The data are going to be collected within activities of T2.5.

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

The dataset is stored in XML format, so the metadata specifying it are already
part of the dataset.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The dataset is stored in XML format. The overall volume of the data depends on
the amount of training sessions completed. A possible value could be compute
ad: 10Kb * N, where N is the number of training sessions.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The collected data will be used for further analysis by the Training Data
Analytics Tool currently under development by ABE. The aim of the analysis is
to assess the skills of the trainee and to gather training statistics, in
order to provide feedback able to improve the training procedures.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

The full dataset will be confidential and only the members of the consortium
will have access on it. If the dataset or portions of it are going to become
of widely open access, the data **must** be anonymized, in order to avoid A)
privacy issues, according to the applicable laws of the country where the data
are gathered, B) issues with the trade unions.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

The dataset is not intended to be shared using a data management portal;
instead, it is intended to be managed by the Training Data Analytics tool.
Nevertheless, the dataset could be easily accessed / reused for further
applicable needs, taking in account how easily statistics about working steps
could be built from the bulk of the individual data gathered.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

The dataset will be stored in the CIDEM. The data lifetime is determined by
the applicable policies specified by the shop floors.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Sunlight.01.MotiveBatteriesAssembly**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Technical data for battery assembly and working instructions for assembly and
quality control.

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Technical data for battery assembly will be provided from SAP. Working
instructions will be available from a database which will be accessed through
the internal company network.

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Sunlight will be the owner of the device.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

SUNLIGHT/CERTH

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Data will be collected for WP3, T3.4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that will be used are SAP codes, order numbers and drawing numbers.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be in text format including drawings and photos. The estimated
total volume will not exceed 1TB.

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be used only for the development of the Satisfactory
application.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

Data will be confidential. Data that cannot be shared because it includes
Customer order details and technical know-how details.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data can not be shared.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data are stored in SAP but an intermediate storage unit will be used in order
to avoid data loses and provide a data backup.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Sunlight.02.Training &SuggestionsPlatform **

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

  1. Battery assembly training data (e.g. assembly instructions, drawings, quality check instructions, procedures etc.). 

  

  2. Workers’ suggestions data 

  

  

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Data are stored in an internal database which will be accessed through
internal LAN

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Sunlight will be the owner of the device.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

SUNLIGHT/CERTH/FIT

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Data will be collected for WP3, T3.3 and T3.4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that will be used are battery assembly procedures and instructions,
assembly drawings. For suggestions from users, metadata will be the timestamp
of the suggestion, and, if the user has submitted it, the identification of
the user.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be in text format

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be used only for the development of the Satisfactory
application.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

Data will be confidential because it includes technical knowhow details.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data will be shared by using a data management portal.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data are stored in a storage device of a server or computer. A back up will be
stored in an external storage device.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Sunlight.03.TempMonitoringInJarFormation**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Battery Temperature measurements

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Thermal cameras

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Sunlight will be the owner of the device.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

SUNLIGHT/CERTH/FIT

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Data will be collected for WP3, T3.3

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that will be used are production dates and the Jar formation
equipment code number.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be in text format

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be used only for the development of the Satisfactory
application.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

Data will be available only for members of the Consortium and the Commission
Services

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data will be shared by using a data management portal.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data will be stored in the storage device of the developed system (computer).
A back up will be stored in an external storage device.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Sunlight.04.MalfunctionIncidentManagement**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Malfunction Incidents

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Malfunction Incidents are logged manually in xls file or via the Shop Floor
Feedback Engine

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Sunlight will be the owner of the device.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

ABE

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

ABE

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

SUNLIGHT/ABE

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Data will be collected for WP3, T3.5

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that will be used are the incident details (date, hour, place, etc.)

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be in text format

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be used only for the development of the Satisfactory
application.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

Data will be available only for members of the Consortium and the Commission
Services

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data will be shared by using a data management portal.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data will be stored in the storage device of the developed system (computer).
A back up will be stored in an external storage device.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**DS.Sunlight.05.Handwashing**

</th>  
<th>

</th> </tr>  
<tr>  
<td>

**Data Identification**

</td> </tr>  
<tr>  
<td>

Data set description

</td>  
<td>

Handwashing frequency data

</td> </tr>  
<tr>  
<td>

Source (e.g. which device?)

</td>  
<td>

Data are stored in an internal database which will be accessed through
internal LAN

</td> </tr>  
<tr>  
<td>

**Partners activities and responsibilities**

</td> </tr>  
<tr>  
<td>

Partner owner of the device

</td>  
<td>

Sunlight will be the owner of the device.

</td> </tr>  
<tr>  
<td>

Partner in charge of the data collection (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data analysis (if different)

</td>  
<td>

CERTH/FIT

</td> </tr>  
<tr>  
<td>

Partner in charge of the data storage (if different)

</td>  
<td>

SUNLIGHT/CERTH/FIT

</td> </tr>  
<tr>  
<td>

WPs and tasks

</td>  
<td>

Data will be collected for WP3, T3.3 and T3.4

</td> </tr>  
<tr>  
<td>

**Standards**

</td> </tr>  
<tr>  
<td>

Info about metadata (Production and storage dates, places) and documentation?

</td>  
<td>

Metadata that will be used are handwash frequencies and highest number of
handwashes for the past days. No personal data are included.

</td> </tr>  
<tr>  
<td>

Standards, Format, Estimated volume of data

</td>  
<td>

The data will be in text format

</td> </tr>  
<tr>  
<td>

**Data exploitation and sharing**

</td> </tr>  
<tr>  
<td>

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be used only for the development of the Satisfactory
application.

</td> </tr>  
<tr>  
<td>

Data access policy / Dissemination level

(Confidential, only for members of the Consortium and the Commission Services)
/ Public

</td>  
<td>

Data will be confidential.

</td> </tr>  
<tr>  
<td>

Data sharing, re-use and distribution (How?)

</td>  
<td>

Data will not be shared.

</td> </tr>  
<tr>  
<td>

Embargo periods (if any)

</td>  
<td>

None

</td> </tr>  
<tr>  
<td>

**Archiving and preservation (including storage and backup)**

</td> </tr>  
<tr>  
<td>

Data storage (including backup): where? For how long?

</td>  
<td>

Data are stored in a storage device of a server or computer. A back up will be
stored in an external storage device.

</td> </tr> </table>

#  DATA MANAGEMENT PORTAL

This section provides an analysis with regards to the specifications of the
SatisFactory Data Management Portal, a web based portal, developed within the
SatisFactory project for the purposes of the management of the various
datasets that will be produced by the project, as well as, for supporting the
exploitation perspectives for each of those datasets.

Based on the information provided in the previous sections, the Data
Management Portal needs to manage a large number of datasets, collected by
various devices, such as sensors and cameras, but also manually inserted in IT
systems and collected through direct interactions with employees (e.g.
interviews).

Furthermore, the Data Management Portal will need to be flexible in terms of
the parts of datasets that are made publicly available. Special attention is
going to be given on ensuring that the data made publicly available violates
neither IPR issues related to the project partners, nor the regulations and
good practices around personal data protection. For this latter point,
systematic anonymization of personal data will be made.

##  DATA MANAGEMENT PORTAL FUNCTIONALITIES

The DMP offers a variety of functionalities in order to facilitate the
management of the data produced within the purposes of the SatisFactory
Project.

The Data Management Portal is implemented through a **web based platform**
which enables its users to easily access and effectively manage the various
datasets created throughout the development of the project. The portal **is
connected to the SatisFactory datasets,** as stored in CIDEM, through the
CIDEM API (RESTful services) providing access to static (i.e. shop floor
gbXML), as well as dynamic (i.e. Events) information.

Regarding the **user authentication** , as well as the respective permissions
and access rights, the following three user categories are foreseen:

  * **Admin**

  

The Admin has access to all of the datasets and the functionalities offered by
the DMP and is able to determine and adjust the editing/access rights of the
registered members and users (open access area). Finally, the Admin is able to
access and extract the analytics, concerning the visitors of the portal.

  * **Member**

  

When someone successfully registers to the portal and is given access
permission by the Admin, she/he is then considered as a “registered Member”.
All the registered members will have access to and be able to manage most of
the collected datasets.

  * **User**

  

SatisFactory project is dedicated to knowledge sharing and for this reason, it
aims at providing a platform for the assessment of project outcomes and the
publication of material related to the understanding of smart factory
environments. As a result, apart from the admin and the registered members’
areas, an open access area will be available for users who will not need to
register and they will have access to some specific datasets, as well as to
project outcomes (e.g. demo datasets).

**Figure**

**2**

**-**

**Login Page of the**

**Data Management Portal**

Each dataset available in the DPM is accompanied by a short description. The
users are able to download the datasets in specific formats (e.g. xml, csv,
etc.) for further analysis. Security measures will be applied to avoid data
exposure (e.g. CAPTCHA technologies).

**Figure 3 - Data access page of the Data Management Portal**

Great emphasis will be given on properly visualizing the various data
collected within the project, so that the members can easily and effectively
manage them. A variety of graphs, pie charts etc. is going to be employed for
helping members to easily understand and elaborate the data.

##  DATA MANAGEMENT PORTAL ARCHITECTURE & DESIGN

**Architecture**

The overall system architecture is shown in the figure below, presenting all
individual interfaces developed for the Data Management Portal, in a 3-tier
schema (database layer, application layer, client layer) where each layer
performs a specific function.

**Figure**

**4**

**-**

**Data Management Portal**

**Architecture**

**Data Tier**

The Data Tier includes the databases, the data management tools (CIDEM), as
well as the data access layer that encapsulates the recovery mechanisms for
historical data (CIDEM API). Through an Application Programming Interface
(API), the methods of data storage management are exposed to the Application
Tier, ensuring robust communication and continuous unobtrusive data flow.

**Application Tier**

The Application Tier checks the functionality of an application by performing
detailed editing. It constitutes the intermediate level and also the heart of
the analysis tool for extracting useful knowledge. It should be noted that
this level goes beyond simply presenting the data but mainly into processing
and analysing them (parallel simulation scenarios implementation), towards
extracting a variety of useful and meaningful indicators and graphs.

**Client Tier**

This is the highest level of the application, with which the end user
interacts via the user interface elements. The way of presenting the
information is very important, given that the tool will be used by people who
may not have be familiar with technology. In this context, the development of
the application is designed in such a way that ensures the user-friendliness
and quick adaptation to the end-users.

#  DISSEMINATION AND EXPLOITATION OF OPEN RESEARCH DATA

Data constitutes a strong asset of the SatisFactory project, since the several
applications developed and tested in real industrial environments throughout
the project have led to the production of a considerable volume of 31
different datasets. On top of that, considerable new applied knowledge has
been produced during the project, captured in the several SatisFactory reports
and scientific publications.

The consortium believes firmly in the concepts of open science and the large
potential benefits the European innovation and economy can draw from allowing
reusing research data at a larger scale. By ensuring that the project’s
results are used by other research stakeholders, we will stimulate the
continuity and transfer of Satisfactory outputs to further research and other
initiatives, allowing others to build upon, benefit from and be influenced by
them.

To this end, SatisFactory participates in the **Open Research Data Pilot
(ORD)** launched by the European Commission along with the Horizon 2020
programme. In this context, certain data produced by the project will be
published with open access – though this objective will obviously need to be
balanced with IPR and data privacy principles.

##  SATISFACTORY OPEN RESEARCH DATA

The main openly exploitable data assets of the project take the following
forms:

  * Open datasets;  Public deliverables;  Scientific publications. 

  

_**Open datasets** _

Through the SatisFactory Social Collaboration Platform which is piloted in the
three pilot industries (namely Comau, CERTH/CPERI and Sunlight), several data
around the shopfloor activity is recorded, relating to the following:

  * Posted content (image, text, video); 

  

  * Training sessions; 

  

  * AR glasses usage; 

  

  * Forum participation; 

  

  * Gamified procedures;  Incidents that may occur;  Ergonomics. 

  

Such data can be anonymised and shared with open access in the form of
statistics, which could be analysed for evaluating activity happening in a
workplace and possibly extracting knowledge from them. Each dataset can be
accompanied by several metadata e.g. type, gender, age, etc., which could
support multiple kinds of analysis on the historical data. Examples of how
this kind of data is currently analysed and presented through the SatisFactory
Social Collaboration Platform are shown in the following figure:

**Figure 5 - Statistics of the activity on the SatisFactory Social
Collaboration Platform**

_**Public deliverables** _

The project has produced and updated more than 20 public reports which
incorporate public data and knowledge produced and integrated during the
3-year duration of the grant. This knowledge revolves around multiple research
fields and disciplines, such as:

  * End-user needs analysis; 

  

  * Industrial application scenarios/use cases; 

  

  * ICT systems architecture; 

  

  * HR management; 

  

  * User experience optimisation 

  

  * Gamification for industrial environments; 

  

  * On-the-job training; 

  

  * Semantics modelling; 

  

  * Social collaboration and information sharing in the workplace; 

  

  * Data aggregation/integration techniques; 

  

  * Evaluation methodologies; 

  

  * Industrial pilots; 

  

  * Dissemination and exploitation of results; 

  

  * etc. 

  

An indicative relevant example of the open and re-usable models disseminated
by the project is the SatisFactory data exchange model itself – namely CIDEM
(Common Information Data

Exchange Model). CIDEM defines a shared and common vocabulary enabling to
address the information needs not only of the SatisFactory project, but of the
modern factory in general. It considers both static information (e.g. shop
floor maps, assets, procedures, etc.) and dynamic data (e.g. alerts,
measurements, several events) and translates them to a common understandable
format, allowing storing and retrieving heterogeneous information, while
supporting interoperability with common industry standards. Deliverable 1.3
describes the model in detail, allowing its further re-use and exploitation.

_**Scientific publications** _

Multiple open access scientific publications have been produced in the
framework of the project, published either in conferences or relevant
journals/books. These publications summarise main achievements of the project
that can be further exploited by the scientific community.

##  OPEN DATA DISSEMINATION PLATFORMS

Visibility of the above mentioned assets is the key for allowing other
stakeholders to get inspired by the project and re-use the produced data and
knowledge, so as to fuel the open data economy. To ensure visibility of open
SatisFactory resources, several platforms have been employed by the team,
where other researchers and the general public can find information on the
project’s results, but also to download project’s data and documents. These
platforms are listed below:

_**SatisFactory website and social media** _

The project’s website is regularly updated not only with news about the
project, but also with the project’s outputs themselves, i.e. SatisFactory
public reports and publications, which are freely accessible to visitors.

In addition, the project’s social media pages support the wide communication
of the project’s outcomes. In particular, through the SatisFactory YouTube
channel several demo videos are promoted, showcasing what the SatisFactory
solutions are able to do and how these can be implemented and utilised in real
industrial settings.

**Figure 6 - Project resources accessible on the website**

_**Zenodo** _

Zenodo is a widely used research data repository, allowing research
stakeholders to search and retrieve open data uploaded by other researchers.
The project team ensures that open project resources are regularly uploaded on
Zenodo, such as public deliverables, scientific papers and datasets.

**Figure**

**7**

**-**

**SatisFactory open data on Zenodo**

_**EFFRA Innovation Portal** _

The European Factories of the Future Research Association (EFFRA) is a non-
for-profit, industry-driven association promoting the development of new and
innovative production technologies. It is the official representative of the
private side in the 'Factories of the Future' public-private partnership. The
EFFRA Innovation Portal is a unique resource combining a project database with
community building and ‘mapping’ functions, allowing users to map projects on
our ‘Factories of the Future 2020’ priorities.

The project team makes sure the EFFRA database is updated with information
about the latest project outputs, including reports and demo material.

**Figure 8 - SatisFactory page on the EFFRA Innovation Portal**

_**The OpenAIRE platform** _

Dissemination and exploitation of the project’s open data is supported through
the EC’s OpenAIRE platform, where visitors can access all types of
SatisFactory data, searching by various keywords and metadata.

**Figure 9 - SatisFactory recourses available on OpenAIRE**

_**The SatisFactory Data Management Portal** _

As explained in section 4, in order to promote exploitation of the
SatisFactory open data, the project has developed a dedicated Data Management
Portal, which, among others, allows visitors to access certain open datasets
uploaded by the project team.

#  CONCLUSION

The present report constitutes the fourth and final version of the
SatisFactory Data Management Plan and provided an updated description of the
datasets produced throughout the project, the strategy put in place for their
storage, protection and sharing, as well as the infrastructure implemented to
efficiently manage them. In addition, it presented the project’s measures for
ensuring visibility, sustainability and dissemination of the SarisFactory open
research data.

Throughout the project, the consortium needed to manage a large number of
datasets, collected by various means, i.e. sensors, cameras, manual inputs in
IT systems and direct interactions with employees (e.g. interviews). Almost
all the project partners have become SatisFactory data owners and/or
producers. Similarly, all the technical work packages of the project produced
data. All datasets have been handled considering the main data security and
privacy principles, respecting also the partners IPR policies.

As part of the Open Research Data Pilot (ORD), the project has taken measures
to promote the open data and knowledge produced by the project. Interested
stakeholders, such as researchers or industry actors, will be able to access
open resources generated by the project, through various platforms, even
beyond the project’s duration. This way, sustainability of the SatisFactory
outcomes will be fostered. However, particular attention needs to be paid on
ensuring that the data made openly available violates neither IPR of the
project partners, nor the regulations and good practices around personal data
protection. For this latter point, systematic anonymization of data is
necessary.