#  Introduction

##  Summary

The vision of RECLAIM is to demonstrate technologies and strategies to support
a new paradigm for refurbishment and re-manufacturing of large industrial
equipment in factories, paving the way to a circular economy. Its ultimate
goal is to save valuable resources by reusing equipment instead of discarding
them. RECLAIM will support legacy industrial infrastructures with advanced
technological solutions with built-in capabilities for in-situ repair, self-
assessment and optimal re-use strategies. It will establish new concepts and
strategies for repair and equipment upgrade and factory layouts’ redesign in
order to gain economic benefits to the manufacturing sector.

The technological core of RECLAIM is a novel Decision Support Framework (DSF)
that guides the optimal refurbishment and re-manufacturing of
electromechanical machines and robotics systems.

Over the project period, RECLAIM will generate a large amount of R&D data.
These data come from pilot plants in various branches of the industry. From
direct and indirect sensor signals, theoretical and numerical analyses,
simulations as well as prototype device testing and validation. As a project
participating in the Open Research Data Pilot in Horizon 2020, RECLAIM will
make its research data **FAIR** , which means they are _F_ indable, _A_
ccessible, _I_ nteroperable and _R_ e-Usable.

##  Scope and structure of the deliverable

The present report is the deliverable D1.3 of the project, RECLAIM’s Data
Management Plan (DMP). The DMP’s purpose is, therefore, to provide the main
elements of the data management policy to be used by the Consortium. It
describes:

  * **types and formats of data to be generated, collected and processed,**

  

  * **the standards to be applied,**

  

  * **the data-reservation methods,**

  

  * **the data-sharing policies for re-use.**

  

The present document is the 1  st  version of RECLAIM DMP, containing a
summary of the data sets; i.e., types, formats and sources (WPs and partner
names) and specific conditions to be applied for sharing and reuse. As a
living document, the DMP will be modified and refined through updates as the
project implementation progresses and/or significant changes occur. At minimum
one more iteration will be submitted, at M42, with the corresponding updates
in the context of the normal course of the project.

The document covers the following topics:

  * **General principles for Data Management Plan**

  

  * **Necessary Information for the description of RECLAIM Data sets**

  

  * **Conclusions and remarks**

  

#  General Principles

##  Research data types and open access policy of RECLAIM

RECLAIM participates in the Pilot on Open Research Data (ORDP) launched by the
European Commission along with the Horizon2020 program. The members of the
consortium embrace the concepts and the principles of open science and
acknowledge the benefits of reusing and evaluating already produced data for
promoting and supporting research and innovation projects at European level.
The data generated during the project activities may be available in open
access for further analysis and exploitation.

The data generated over the project lifetime can be divided into three
categories:

  * **Open Data** : Data that are publicly shared for re-use and exploitation 

  

  * **Private Data** : Data that are retained by individual partners for their own processes and tests 

  

  * **Confidential Data** : data that are available only for the members of the consortium and the EU commission services and subjected to the project nondisclosure-agreement 

  

##  IPR

As data is used as a basis for almost all activities within the RECLAIM
project, the handling of IPR (Intellectual Property Rights) related to data is
of high importance. IPR handling is explicitly addressed by Task T8.1
“Management of IPR”. Even if this task has only started this month (M6), first
activities have been started already. For example, IPR issues and activities
have been presented during the 6 months virtual meeting on 24  th  March 2020.
Within the ongoing activities, IPR management will also take the handling of
RECLAIM data into account. Detailed measures and procedures will be reported
in the updated version of this Data Management Plan.

#  Data sets

All Partners in RECLAIM have initially identified the data that will be
produced and/or used in the different WP’s and project activities. Changes

(addition/removal of data sets) and later updates resulting from the progress
of the project are marked accordingly in the next versions of the DMP. The
type of data set and corresponding details are given in the following
sections.

##  Data sets overview

The following table provides an overview of the different data sets used and
produced during the RECLAIM project.  
  
<table>  
<tr>  
<th>

**No. Data set name**

</th>  
<th>

**Responsible**

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

**1**

</td>  
<td>

DS.HWH.01.FRICTION_WELDING_MACHINE

</td>  
<td>

HWH

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

**2**

</td>  
<td>

DS.HWH.02.MAINTENANCE_DATA

</td>  
<td>

HWH

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

**3**

</td>  
<td>

DS.FEUP.01.PREDICTIVE_MAINTENANCE

</td>  
<td>

FEUP

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

**4**

</td>  
<td>

DS.FEUP.02.DEGRADATION_DATA_SET

</td>  
<td>

FEUP

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

**5**

</td>  
<td>

DS.FEUP.03.ANOMALY_DETECTION

</td>  
<td>

FEUP

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

**6**

</td>  
<td>

DS.FEUP.04.QUALITY_PREDICTION

</td>  
<td>

FEUP

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

**7**

</td>  
<td>

DS.ASTON.01.REMANUFACTURING_PROCESS

</td>  
<td>

ASTON

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

**8**

</td>  
<td>

DS.ASTON.02.COST_BENCHMARKING_HISTORICAL

</td>  
<td>

ASTON

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

**9**

</td>  
<td>

DS.ZORLUTEKS.01.BLEACHING_MACHINE

</td>  
<td>

ZORLUTEKS

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

**10**

</td>  
<td>

DS.CERTH.01.DECISION_SUPPORT_FRAMEWORK_OUTPUT

</td>  
<td>

CERTH

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

**11**

</td>  
<td>

DS.CERTH.02.IN_SITU_REPAIR_DATA_ANALYTICS_OUTPUT

</td>  
<td>

CERTH

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

**12**

</td>  
<td>

DS.CERTH.03.AR_MECHANISMS_OUTPUT

</td>  
<td>

CERTH

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

**13**

</td>  
<td>

DS.Gorenje.01.DW_Robot_Cells

</td>  
<td>

Gorenje

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

**14**

</td>  
<td>

DS.Gorenje.02.WHITE_ENAMELLING_LINE

</td>  
<td>

Gorenje

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

**15**

</td>  
<td>

DS.ADV-CTCR-TECNALIA.01.FORMING_MACHINE_FOR_REAR_PARTS

</td>  
<td>

ADV, CTCR, TECNALIA

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

**16**

</td>  
<td>

DS.ADV-CTCR-

TECNALIA.02.FORMING_MACHINE_FOR_REAR_PARTS_ROTOSTIR

</td>  
<td>

ADV, CTCR, TECNALIA

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

**17**

</td>  
<td>

DS.ADV-CTCR-TECNALIA.03.CUTTING_MACHINE

</td>  
<td>

ADV, CTCR, TECNALIA

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

**18**

</td>  
<td>

DS.FLUCHOS.01.FORMING_MACHINE_FOR_REAR_PARTS

</td>  
<td>

FLUCHOS

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

**19**

</td>  
<td>

DS.FLUCHOS.02.FORMING_MACHINE_FOR_REAR_PARTS_ROTOSTIR

</td>  
<td>

FLUCHOS

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

**20**

</td>  
<td>

DS.FLUCHOS.03.CUTTING_MACHINE

</td>  
<td>

FLUCHOS

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

**21**

</td>  
<td>

DS.SUPSI.01.FailuresHighLevelData_Gorenje

</td>  
<td>

SUPSI

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

**22**

</td>  
<td>

DS.SUPSI.02.FailuresHighLevelData_FLUCHOS

</td>  
<td>

SUPSI

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

**23**

</td>  
<td>

DS.SUPSI.03.FailuresHighLevelData_Podium

</td>  
<td>

SUPSI

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

**24**

</td>  
<td>

DS.SUPSI.04.FailuresHighLevelData_Zorluteks

</td>  
<td>

SUPSI

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

**25**

</td>  
<td>

DS.SUPSI.05.FailuresHighLevelData_HWH

</td>  
<td>

SUPSI

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

**26**

</td>  
<td>

DS.SUPSI.06.LCAData_Gorenje

</td>  
<td>

SUPSI

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

**27**

</td>  
<td>

DS.SUPSI.07.LCAData_FLUCHOS

</td>  
<td>

SUPSI

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

**28**

</td>  
<td>

DS.SUPSI.08.LCAData_Podium

</td>  
<td>

SUPSI

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

**29**

</td>  
<td>

DS.SUPSI.09.LCAData_Zorluteks

</td>  
<td>

SUPSI

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

**30**

</td>  
<td>

DS.SUPSI.10.LCAData_HWH

</td>  
<td>

SUPSI

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

A detailed description of each data set is given in the sections below.

##  Harms & Wende  
  
<table>  
<tr>  
<th>

**DS.HWH.01.FRICTION_WELDING_MACHINE**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during a friction welding process by a
friction welding machine

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

Source (e.g. which device?)

</td>  
<td>

Friction welding machine including the different sensors attached

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

HWH

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

Partner in charge of the data collection (if different)

</td>  
<td>

HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so,

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

</td>  
<td>

degradation models will be developed based on the data. In addition, the data
will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at HWH during the project duration.

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

**DS.HWH.02.MAINTENANCE_DATA**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is gathered and stored during the maintenance of a friction welding
machine

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

Source (e.g. which device?)

</td>  
<td>

The data is gathered by the HWH service & repair department.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

HWH

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

Partner in charge of the data collection (if different)

</td>  
<td>

HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

The data will 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 will include any data related to the repair of a machine.
This includes a) machine data such as machine type, serial number, etc. b)
customer data such as customer name, delivery time, application etc. and c)
data on repair such as repair time, components changed, etc.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in pd documents. One document for each machine/repair task.
Most of the data is text. However, pictures might be included. Thus, the data
volume can be about several Megabytes 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 data will be used for root cause analysis and for finding the maintenance
hotspots.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at HWH during the project duration.

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

##  University of Porto  
  
<table>  
<tr>  
<th>

**DS.FEUP.01.PREDICTIVE_MAINTENANCE**

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

Data Identification

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

Data set description

</td>  
<td>

Data that will be used and produced by the Predictive Maintenance models

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

Source (e.g. which device?)

</td>  
<td>

Friction Welding machine and Predictive Maintenance Algorithm for failure

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

</th>  
<th>

prediction, and maintenance action recommendation.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FEUP

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

Partner in charge of the data collection (if different)

</td>  
<td>

FEUP, HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

Inputs: time-series sensor and process data from components and / or
equipment; Maintenance actions (name, duration and components involved);
errors; malfunctions; production schedule.

Output: Which component will fail, when it will fail and recommendation of
maintenance actions and when to perform it (Component; Duration; Maintenance
Action).

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

Standards, Format, Estimated volume of data

</td>  
<td>

Since maintenance actions do not occur often, the space required is very low.
The historical data (input) might take several Gb of space.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The input data will be used for model training and testing of several PM
strategies, as the data output of the model will be used for decision making,
resulting in a database of recommendations and further refinement of the
model.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only, and the inputs
and outputs will be anonymized.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in FEUP server or in any RECLAIM repository available

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

**DS.FEUP.02.DEGRADATION_DATA_SET**

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

Data Identification

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

Data set description

</td>  
<td>

Data that will be used and produced by the Degradation Model

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

Source (e.g. which device?)

</td>  
<td>

Friction Welding and Degradation Algorithm for failure degradation prediction
based on further machine use and current condition.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FEUP

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

Partner in charge of the data collection (if different)

</td>  
<td>

FEUP, HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

WP4, T4.2

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

Standards

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

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

</td>  
<td>

Inputs: time-series sensor and process data from components and / or
equipment; Time from last repair; Amount of time used; Current machine
conditions (Throughput, machine parameters).

Output: Mean time to failure (or similar KPI) according the future
parameterization and use of the machine.

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

Standards, Format, Estimated

</td>  
<td>

Since degradation predictions that are critical and pertinent will be stored,
the

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

volume of data

</td>  
<td>

space required is very low. The historical data (input) might take several Mb
of space.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The input data will be used for model training and testing, as the data output
of the model will be used for decision making, resulting in a database of
important predictions and further refinement of the model.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only, and the outputs
will be anonymized.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in FEUP server or in any RECLAIM repository available

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

**DS.FEUP.03.ANOMALY_DETECTION**

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

Data Identification

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

Data set description

</td>  
<td>

Data that will be used and produced by the Anomaly Detection algorithm

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

Source (e.g. which device?)

</td>  
<td>

Friction Welding and Anomaly Detection for observed misbehaviours that might
require attention, raise alarms / notifications, or machine shutdown.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FEUP

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

Partner in charge of the data collection (if different)

</td>  
<td>

FEUP, HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

WP3, T3.3, WP4 T4.2

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

Standards

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

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

</td>  
<td>

Inputs: time-series sensor and process data of normal (or abnormal) behaviour
from components and / or equipment.

Output: Based on the identified patterns, classify data into anomaly or normal
data.

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

Standards, Format, Estimated volume of data

</td>  
<td>

Since anomalies might not be so often, the space required will be low (Mb).
The historical data (input) might take several Mb of space.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The input data will be used for pattern recognition and testing, as the data
output of the model will be used for decision making, as input for more
complex models like Predictive Maintenance or Degradation, and further
refinement of the model.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only, and the outputs
will be anonymized.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in FEUP server or in any RECLAIM repository available

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

**DS.FEUP.04.QUALITY_PREDICTION**

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

Data Identification

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

Data set description

</td>  
<td>

Data that will be used and produced by the Process Quality model for further
process parameter estimation when a new product

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

</th>  
<th>

needs to be produced, or an existing one needs to be calibrated.

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

Source (e.g. which device?)

</td>  
<td>

Friction Welding and Process Quality prediction.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FEUP

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

Partner in charge of the data collection (if different)

</td>  
<td>

FEUP, HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

FEUP

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

WP4 T4.2

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

Standards

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

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

</td>  
<td>

Inputs: 1) Machine parameters; 2) Product / process quality; 3) Product specs.

Output: Quality Prediction and recommended parameters based on a quality
target.

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

Standards, Format, Estimated volume of data

</td>  
<td>

Since calibrations might not be so often, the space required will be low (Mb).
The historical data (input) might take several Mb of space.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The input data will be used for model training and testing, as the data output
of the model will be used for decision making and further refinement of the
model.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only, and the outputs
will be anonymized.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in FEUP server or in any RECLAIM repository available

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

##  Aston University  
  
<table>  
<tr>  
<th>

**DS.ASTON.01.REMANUFACTURING_PROCESS**

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

Data Identification

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

Data set description

</td>  
<td>

Data will be used for estimating the cost of remanufacturing/refurbishment
etc. Endof-Life (EoL) options.

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

Source (e.g. which device?)

</td>  
<td>

Partners and Remanufacturers’ practice

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

HWH etc. remanufacturing practitioner

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

Partner in charge of the data collection (if different)

</td>  
<td>

HWH etc. remanufacturing practitioner, ASTON

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ASTON

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH, ASTON

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

WPs and tasks

</td>  
<td>

WP4, T4.3

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

Standards

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

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

</td>  
<td>

The indicative metadata include: 1) remanufacturer name, 2) specific machine,
3) machine conditions, 4) remanufacturing activities, 5) resources required
for activities, 6) time required for activities.

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

Standards, Format, Estimated volume of data

</td>  
<td>

Numerical number and text.

</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 for estimating the cost of each End-of-Life strategy and
process.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in Aston’s server or in RECLAIM project repository

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

**DS.ASTON.02.COST_BENCHMARKING_HISTORICAL**

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

Data Identification

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

Data set description

</td>  
<td>

Data will be used for estimating the cost of remanufacturing/refurbishment
etc. Endof-Life (EoL) options.

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

Source (e.g. which device?)

</td>  
<td>

Partners and Remanufacturers’ practice, various public resources

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

ASTON

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

Partner in charge of the data collection (if different)

</td>  
<td>

ASTON

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ASTON

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

Partner in charge of the data storage (if different)

</td>  
<td>

ASTON

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

WPs and tasks

</td>  
<td>

WP4, T4.3

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

Standards

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

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

</td>  
<td>

The indicative metadata include: 1) data source 2) scenario of the data, 3)
time of the data being valid 5)

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

Standards, Format, Estimated volume of data

</td>  
<td>

Numerical number and text.

</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 for estimating the cost of each End-of-Life strategy

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data will be given to the consortium only.

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

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

</td>  
<td>

RECLAIM repository

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

Embargo periods (if any)

</td>  
<td>

No

</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 can be stored in Aston’s server or in RECLAIM project repository

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

##  Zorluteks  
  
<table>  
<tr>  
<th>

**DS.ZORLUTEKS.01.BLEACHING_MACHINE**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during a bleaching process by a bleaching
machine

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

Source (e.g. which device?)

</td>  
<td>

Bleaching machine includes different sensors attached such as temperature
sensors in washing baths and steamer, liquid level sensors in the washing
baths and bleaching chemical through, humidity sensor to measure humidity of
bleached fabric at the end of the machine. Furthermore, it is possible to
monitor velocity of the machine and recipes for different quality of feeding
fabric by PLC monitoring on the bleaching machine. PLC monitoring system also
helps determining electricity, steam and water consumptions daily. There is an
online platform which takes data from PLCs. By using this, energy
consumptions, efficiency and reasons for stops are detailed and analysed based
on each machine in the production plant.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

ZORLUTEKS

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

Partner in charge of the data collection (if different)

</td>  
<td>

ZORLUTEKS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

TEC, ADV and CTCR

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

Partner in charge of the data storage (if different)

</td>  
<td>

ZORLUTEKS

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

WPs and tasks

</td>  
<td>

The data will 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 includes production-related information and machine-related
information. Production-related information can be exemplified types of fabric
with its production amount and production time obtained by SCADA System. Data
can be handled transiently. Machine-related information be illustrated as
serial number.

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

Standards, Format, Estimated volume of data

</td>  
<td>

Stored data in proprietary format can be exported to Excel. The volume is
estimated to several Megabytes per day based on the production volume.

</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 for analysing production data, amount of energy
consumption and efficiency of the machine in order to estimate the machine’s
current state and to predict the machine’s future behaviour. So that,
degradation models will be advanced based on the data.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

Data sharing, re-use and

</td>  
<td>

The data will be shared via the RECLAIM

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

distribution (How?)

</td>  
<td>

repository and the respective data communication mechanisms.

</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 at Zorluteks during the project duration. Water, steam
and energy consumptions, efficiencies and production-related information such
as type of fabric with its production amount as well as production time in a
period of time can be stored in the on-line platform and SCADA System.
However, data obtained by sensors and recipes information used for different
types of feeding fabric do not be stored.

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

##  Center for Research and Technology Hellas  
  
<table>  
<tr>  
<th>

**DS.CERTH.01.DECISION_SUPPORT_FRAMEWORK_OUTPUT**

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

Data Identification

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

Data set description

</td>  
<td>

Based on evaluation metrics to be defined, raw data from T3.1, the output of
data analysis components from T3.2-T3.4, T4.2 and T4.3, as well as lifetime
extension strategies from T4.1, the Decision Support Framework (DSF) will
infer 1) the most suitable remanufacturing/refurbishment strategy, 2) the
preferable timeframe for the implementation of the strategy, 3) the right
components to be

remanufactured/refurbished, 4) the optimal design alternative. In contrast
with the Optimization Toolkit of T3.4, which performs only operational
optimization in single machines, T4.4 performs operational optimization
globally, i.e. in whole production lines or set of machines of each pilot use
case, considering also business aspects (financial etc.) based on T4.1 and
T4.3.

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

Source (e.g. which device?)

</td>  
<td>

Decision Support Framework (T4.4)

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

CERTH

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

Partner in charge of the data collection (if different)

</td>  
<td>

  * **pilots** 1  **(as end users)**

  

  * **ICE (as responsible for data storage in RECLAIM Repository)**

  

  * **partners from T3.1 (as responsible for communication)**

  

  * **CERTH (as responsible for integration)**

  

  * **partners from T5.1, T5.5, T7.4 (for meta-analysis)**

  

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

Partner in charge of the data analysis (if different)

</td>  
<td>

partners from T5.1, T5.5, T7.4

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

Partner in charge of the data storage (if different)

</td>  
<td>

ICE, pilots

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

WPs and tasks

</td>  
<td>

  * **data generation: T4.4**

  

  * **data storage: T3.2, T6.3-T6.7**

  

  * **data meta-analysis: T5.1, T5.5, T7.4**

  

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will be properly documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

  * **JSON/CSV/XLSX/TXT format**

  

  * **The volume cannot be estimated yet. If it is too high, temporal aggregation may take place.**

  

</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 directly visualized by the pilots.**

  

  * **T5.1 will have input from T4.4 and will export the inference of refurbishment and re-manufacturing plan.**

  

  * **The real-time 3D annotation module of the AR Mechanisms (T5.5) will**

  

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

</th>  
<th>

**receive proposed actions & parts IDs. **

• **T7.4 will use WP4 outputs, among other data, to develop reliable and
robust digital replica of the physical machines.**

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

This depends on the pilots’ policy.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

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

Embargo periods (if any)

</td>  
<td>

Same as embargo periods for the DSF input data

</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 on the Cloud and/or the respective pilot plant. The
storage duration will depend on the policy of the storage manager.

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

**DS.CERTH.02.IN_SITU_REPAIR_DATA_ANALYTICS_OUTPUT**

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

Data Identification

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

Data set description

</td>  
<td>

This data set is the output of the component corresponding to T5.2 and
building block 8. The exact role of it will depend on the pilot needs. In any
case, it will consist of algorithms and visual analytics. One possible option
is that a camera or laser sensor that will be taking 3D data from the product
is installed, and an image processing algorithm (supervised or unsupervised,
depending on the presence or absence of ground truth data respectively) will
be comparing it with the ideal form of the product and based on that will be
inferring (in the supervised case) what action should be taken on the
equipment producing it. If 3D data cannot be acquired, process data from
machinery data collectors may be used as input instead.

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

Source (e.g. which device?)

</th>  
<th>

In-situ repair data analytics for situational awareness (T5.2)

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

CERTH

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

Partner in charge of the data collection (if different)

</td>  
<td>

  * **pilots (as end users)**

  

  * **ICE (as responsible for data storage in RECLAIM Repository)**

  

  * **partners from T3.1 (as responsible for communication)**

  

  * **CERTH (as responsible for integration)**

  

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

Partner in charge of the data analysis (if different)

</td>  
<td>

None (no meta-analysis)

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

Partner in charge of the data storage (if different)

</td>  
<td>

ICE, pilots

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

WPs and tasks

</td>  
<td>

  * **data generation: T5.2**

  

  * **data storage: T3.2, T6.3-T6.7**

  

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

  * **The format is still unknown.**

  

  * **The volume cannot be estimated yet. If it is too high, temporal aggregation may take place.**

  

</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 directly visualized by the pilots.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

This depends on the pilots’ policy.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data

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

</td>  
<td>

communication mechanisms.

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

Embargo periods (if any)

</td>  
<td>

same as embargo periods for the In-Situ Repair Data Analytics Toolkit input
data

</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 on the Cloud and/or the respective pilot plant. The
storage duration will depend on the policy of the storage manager.

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

**DS.CERTH.03.AR_MECHANISMS_OUTPUT**

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

Data Identification

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

Data set description

</td>  
<td>

AR User Interface, contextual interaction.

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

Source (e.g. which device?)

</td>  
<td>

AR Mechanisms (T5.5)

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

CERTH

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

None (no meta-analysis)

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

T5.5

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

  * **JSON format & others **

  

  * **volume cannot be estimated**

  

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

Data exploitation and sharing

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

Data exploitation (purpose/use of

</td>  
<td>

The data will be directly visualized by the

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

the data analysis)

</td>  
<td>

pilots.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

This depends on the pilots’ policy.

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

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

</td>  
<td>

AR devices (glasses, tablets etc.) will display the part of the machine that
needs repair and then a sequence of disassembly steps of the engine parts will
be displayed with images and videos.

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

Embargo periods (if any)

</td>  
<td>

same as embargo periods for the AR input data

</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 on the Cloud and/or the respective pilot plant. The
storage duration will depend on the policy of the storage manager.

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

##  Gorenje  
  
<table>  
<tr>  
<th>

**DS.Gorenje.01.DW_Robot_Cells**

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

Data Identification

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

Data set description

</td>  
<td>

DW Robot Cell set for making tubs consists of: A-cell, B-cell, C-cell, D-cell,
E-cell, outer bottom cell.

Data is generated and stored during different processes as spot welding,
punching, double bending, seam welding and other support processes by robot
cells set equipment.

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

Source (e.g. which device?)

</td>  
<td>

6 robot cells: different robots, punching and welding machines and other
equipment with different sensors and control units.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Gorenje Velenje

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

Partner in charge of the data

</td>  
<td>

Gorenje Velenje

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

collection (if different)

</th>  
<th>

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

Partner in charge of the data analysis (if different)

</td>  
<td>

Roboteh, ADV

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

Partner in charge of the data storage (if different)

</td>  
<td>

Gorenje Velenje

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

WPs and tasks

</td>  
<td>

WP2, WP3, WP4

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

Standards

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

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

</td>  
<td>

Indicative metadata will include:

  * **machine-related information such as serial number.**

  

  * **production related information such as production site, tool/appliance or components appliances.**

  

Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format – program SAP and PIS (MES) system
but can usually exported to Excel. Depending on the machine and the production
volume, the volume is estimated to several Megabytes 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 data will be used for analysing production data in order to estimate the
machine’s and product current state and to predict future behaviour. To do so,
degradation models will be developed based on the data. In addition, the data
will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
eReports or WEB.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms. (WEB

applications)

</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 at Gorenje during the project duration or lifespan of
appliances.

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

**DS.Gorenje.02.WHITE ENAMELLING LINE**

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

Data Identification

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

Data set description

</td>  
<td>

White enamelling line with 3 main processes: spraying booth, furnace and
process parameter traceability. Data is stored by PLC monitoring units of
individual subsystems of the line.

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

Source (e.g. which device?)

</td>  
<td>

Equipment for identification of parts (f.e.camera) is envisaged to identify
different semi-finished products in the process at different locations of the
production process. On-line measurement of air temperature and relative
humidity at different locations, measuring the applied thickness of the enamel
powder layer on semi-finished products and measuring the speed of the enamel
conveyor is envisaged.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Gorenje Mora

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

Partner in charge of the data collection (if different)

</td>  
<td>

Gorenje Mora

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ADV

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

Partner in charge of the data storage (if different)

</td>  
<td>

Gorenje Mora

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

WPs and tasks

</td>  
<td>

WP2, WP3, WP4

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

Standards

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

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

</td>  
<td>

Indicative metadata will include:

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

documentation?

</td>  
<td>

  * **machine-related information such as serial number.**

  

  * **production related information such as production quantities of parts, records of enamel thickness)**

  

  * **environmental data (temperature, humidity,…)**

  

Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format – program SAP and PIS (MES) system
but can usually be exported to Excel. Depending on the production volume, the
volume is estimated to several Megabytes 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 data will be used for analysing production data, keeping history.
Environmental data will be used for simulations or process parameters. In
addition, the data can be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

If possible we prefer NO access to our local data

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

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

</td>  
<td>

No sharing data

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

Embargo periods (if any)

</td>  
<td>

</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 on MORA servers

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

##  Advanticsys-Tecnalia-CTCR  
  
<table>  
<tr>  
<th>

**DS.ADV-CTCR-TECNALIA.01.FORMING_MACHINE_FOR_REAR_PARTS**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the forming operation of the rear
parts of

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

</th>  
<th>

the shoes.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data collection (if different)

</td>  
<td>

ADV, CTCR, TECNALIA, FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM)

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

</td>  
<td>

Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

**DS.ADV-CTCR-TECNALIA.02.FORMING_MACHINE_FOR_REAR_PARTS_ROTOSTIR**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the forming operation of the rear
parts of the shoes in the machine called ROTOSTIR.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data collection (if different)

</td>  
<td>

ADV, CTCR, TECNALIA, FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated

</td>  
<td>

The data is stored in proprietary format,

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

volume of data

</td>  
<td>

but can usually exported to Excel. Depending on the machine and the production
volume, the volume is estimated to several Kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

**DS.ADV-CTCR-TECNALIA.03.CUTTING_MACHINE**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the cutting operation of the
components for the upper part of the footwear.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data

</td>  
<td>

ADV, CTCR, TECNALIA, FLUCHOS

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

collection (if different)

</th>  
<th>

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

Partner in charge of the data analysis (if different)

</td>  
<td>

ADV, CTCR, TECNALIA

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

##  Fluchos  
  
<table>  
<tr>  
<th>

**DS.FLUCHOS.01.FORMING_MACHINE_FOR_REAR_PARTS**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the forming operation of the rear
parts of the shoes.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FLUCHOS

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

Partner in charge of the data collection (if different)

</td>  
<td>

FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

CTCR, TECNALIA, ADV

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

**DS.FLUCHOS.02.FORMING_MACHINE_FOR_REAR_PARTS_ROTOSTIR**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the forming operation of the rear
parts of the shoes in the machine called ROTOSTIR.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FLUCHOS

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

Partner in charge of the data collection (if different)

</td>  
<td>

FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

CTCR, TEC, ADV

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

**DS.FLUCHOS.03.CUTTING_MACHINE**

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

Data Identification

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

Data set description

</td>  
<td>

Data that is generated and stored during the cutting operation of the
components for the upper part of the footwear.

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

Source (e.g. which device?)

</td>  
<td>

Rear parts forming machine including the different sensors attached.

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FLUCHOS

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

Partner in charge of the data collection (if different)

</td>  
<td>

FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

CTCR, TEC, ADV

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will 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 will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Kilobytes 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 data will be used for analysing production data in order to estimate the
machine’s current state and to predict the machine’s future behaviour. To do
so, degradation models will be developed based on the data. In addition, the
data

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

</td>  
<td>

will partially be used for visualization.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Prognostic and Health Management (PHM) Toolkit.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 at FLUCHOS and CTCR during the project duration.

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

##  Scuola Universitaria Professionale della Svizzera Italiana

###  Data sets related to Task 2.5  
  
<table>  
<tr>  
<th>

**DS.SUPSI.01.FailuresHighLevelData_Gorenje**

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

Data Identification

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

Data set description

</td>  
<td>

Demonstration scenario data related to failure occurrences, **l** abour hours
spent on maintenance, number of breakdowns, operational time, OEE, etc.

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Gorenje

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

Partner in charge of the data collection (if different)

</td>  
<td>

Gorenje

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Gorenje

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP2 and the analysis will be
carried out within task 2.5.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes per day.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

To design, develop and validate a methodology/tool to support companies in
structuring and perform a high-level analysis of the state and life expectancy
of the machines in the company, providing preliminary insight into the most
meaningful approaches to maintenance execution.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Reliability Analysis Tool.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.02.FailuresHighLevelData_FLUCHOS**

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

Data Identification

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

Data set description

</td>  
<td>

Demonstration scenario data related to failure occurrences, **l** abour hours
spent on maintenance, number of breakdowns, operational time, OEE, etc.

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FLUCHOS

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

Partner in charge of the data collection (if different)

</td>  
<td>

FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP2 and the analysis will be
carried out within task 2.5.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes per day.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

To design, develop and validate a methodology/tool to support companies in
structuring and perform a high-level analysis of the state and life expectancy
of the machines in the company, providing

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

</td>  
<td>

preliminary insight into the most meaningful approaches to maintenance
execution.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Reliability Analysis Tool.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.03.FailuresHighLevelData_Podium**

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

Data Identification

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

Data set description

</td>  
<td>

Demonstration scenario data related to failure occurrences, **l** abour hours
spent on maintenance, number of breakdowns, operational time, OEE, etc.

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Podium

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

Partner in charge of the data collection (if different)

</td>  
<td>

Podium

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Podium

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP2 and the analysis will be
carried out within task 2.5.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes per day.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

To design, develop and validate a methodology/tool to support companies in
structuring and perform a high-level analysis of the state and life expectancy
of the machines in the company, providing preliminary insight into the most
meaningful approaches to maintenance execution.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Reliability Analysis Tool.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.04.FailuresHighLevelData_Zorluteks**

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

Data Identification

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

Data set description

</td>  
<td>

Data related to failure occurrences, **l** abour hours spent on maintenance,
number of

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

</th>  
<th>

breakdowns, operational time, OEE, etc.

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Zorluteks

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

Partner in charge of the data collection (if different)

</td>  
<td>

Zorluteks

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Zorluteks

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP2 and the analysis will be
carried out within task 2.5.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes per day.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

To design, develop and validate a methodology/tool to support companies in
structuring and perform a high-level analysis of the state and life expectancy
of the machines in the company, providing preliminary insight into the most
meaningful approaches to maintenance execution.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM

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

the Commission Services) / Public

</td>  
<td>

Reliability Analysis Tool.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.05.FailuresHighLevelData_HWH**

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

Data Identification

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

Data set description

</td>  
<td>

Demonstration scenario data related to failure occurrences, **l** abour hours
spent on maintenance, number of breakdowns, operational time, OEE, etc.

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

HWH

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

Partner in charge of the data collection (if different)

</td>  
<td>

HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP2 and the analysis will be
carried out within task 2.5.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include a) machine-related information such as serial
number and b) production related information such as production site or charge
ID. Data will properly be documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is stored in proprietary format, but can usually exported to Excel.
Depending on the machine and the production volume, the volume is estimated to
several Megabytes per day.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

To design, develop and validate a methodology/tool to support companies in
structuring and perform a high-level analysis of the state and life expectancy
of the machines in the company, providing preliminary insight into the most
meaningful approaches to maintenance execution.

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only. Anonymized and consolidated data can be provided to the public via the
RECLAIM Reliability Analysis Tool.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

###  Data sets related to Task 7.3  
  
<table>  
<tr>  
<th>

**DS.SUPSI.06.LCAData_Gorenje**

</th>  
<th>

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

Data Identification

</td>  
<td>

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

Data set description

</td>  
<td>

Raw materials, auxiliary materials, other natural resources, energy (in its
various forms), waste, products, co-products, emissions (air, water and soil)

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines, MRP, ERP, energy and waste bills; Ecoinvent

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

</td>  
<td>

database

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Gorenje

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

Partner in charge of the data collection (if different)

</td>  
<td>

Gorenje

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Gorenje

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP5 and 7 and the analysis
will be carried out within task 7.3.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include production dates. Data will properly be
documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is exported to Excel. The volume is estimated to several Megabytes.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Real-time assessment of the sustainability performances and generation of
sustainability oriented use scenarios

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.07.LCAData_FLUCHOS**

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

Data Identification

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

Data set description

</td>  
<td>

Raw materials, auxiliary materials, other natural resources, energy (in its
various forms), waste, products, co-products, emissions (air, water and soil)

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines, MRP, ERP, energy and waste bills; Ecoinvent
database

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

FLUCHOS

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

Partner in charge of the data collection (if different)

</td>  
<td>

FLUCHOS

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

FLUCHOS

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP5 and 7 and the analysis
will be carried out within task 7.3.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include production dates. Data will properly be
documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is exported to Excel. The volume is estimated to several Megabytes.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Real-time assessment of the sustainability performances and generation of
sustainability oriented use scenarios

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.08.LCAData_Podium**

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

Data Identification

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

Data set description

</td>  
<td>

Raw materials, auxiliary materials, other natural resources, energy (in its
various forms), waste, products, co-products, emissions (air, water and soil)

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines, MRP, ERP, energy and waste bills; Ecoinvent
database

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Podium

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

Partner in charge of the data collection (if different)

</td>  
<td>

Podium

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Podium

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP5 and 7 and the analysis
will be carried out within task 7.3.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include production dates. Data will properly be
documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is exported to Excel. The volume is estimated to several Megabytes.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Real-time assessment of the sustainability performances and generation of
sustainability oriented use scenarios

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.09.LCAData_Zorluteks**

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

Data Identification

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

Data set description

</td>  
<td>

Raw materials, auxiliary materials, other natural resources, energy (in its
various forms), waste, products, co-products, emissions (air, water and soil)

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines, MRP, ERP, energy and waste bills; Ecoinvent
database

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

Zorluteks

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

Partner in charge of the data collection (if different)

</td>  
<td>

Zorluteks

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

Zorluteks

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP5 and 7 and the analysis
will be carried out within task 7.3.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include production dates. Data will properly be
documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is exported to Excel. The volume is estimated to several Megabytes.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Real-time assessment of the sustainability performances and generation of
sustainability oriented use scenarios

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

**DS.SUPSI.10.LCAData_HWH**

</th>  
<th>

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

Data Identification

</td>  
<td>

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

Data set description

</td>  
<td>

Raw materials, auxiliary materials, other natural resources, energy (in its
various forms), waste, products, co-products, emissions (air, water and soil)

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

Source (e.g. which device?)

</td>  
<td>

Use-cases’ Equipment and machines, MRP, ERP, energy and waste bills; Ecoinvent

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

</td>  
<td>

database

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

Partners activities and responsibilities

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

Partner owner of the device

</td>  
<td>

HWH

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

Partner in charge of the data collection (if different)

</td>  
<td>

HWH

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

Partner in charge of the data analysis (if different)

</td>  
<td>

SUPSI

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

Partner in charge of the data storage (if different)

</td>  
<td>

HWH

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

WPs and tasks

</td>  
<td>

The data will be collected within activities of WP5 and 7 and the analysis
will be carried out within task 7.3.

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

Standards

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

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

</td>  
<td>

Indicative metadata will include production dates. Data will properly be
documented.

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

Standards, Format, Estimated volume of data

</td>  
<td>

The data is exported to Excel. The volume is estimated to several Megabytes.

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

Data exploitation and sharing

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Real-time assessment of the sustainability performances and generation of
sustainability oriented use scenarios

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

Data access policy / Dissemination level (Confidential, only for members of
the Consortium and the Commission Services) / Public

</td>  
<td>

Full access to the data sets will be given to the members of the consortium
only.

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

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

</td>  
<td>

The data will be shared via the RECLAIM repository and the respective data
communication mechanisms.

</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 in the project repository during the project duration.

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

#  Conclusion

This report describes the RECLAIM Data Management Plan in its first version.
Herein, and the data sets identified until project month 6 are illustrated. Up
to now, 30 data sets reported by 9 project partners are available. IPR related
activities with respect to data management have already been started. Those
activities will be continued within Task T8.2 “Management of IPR”.