#  EXECUTIVE SUMMARY

This deliverable shows how quality, innovation and data management aspects are
considered in a variety of processes and activities within the SEMIoTICS
project.

The interrelated quality/innovation/data management processes namely quality
management, quality control and quality assurance, innovation management, and
data management have impact on the project work from the requirements &
architectural definition to the project’s implementation in 3 different usage
scenarios.

In chapter 3, Quality Management Plan refers to reporting procedures, the
definition of roles and responsibilities, quality control & assurance policies
for deliverables and publications with a well-defined internal review process
and implementation throughout the project’s duration.

In chapter 4, Innovation Management Plan provides detailed plan for activities
and processes for identifying internal and external opportunities for and
realising innovation.

In chapter 5, Data Management Plan provides details about how to manage the
data generated within technical work-packages within the consortium. The
processes and criteria described in this document may also be updated if
additional needs arise during the execution of the project in regular WP1
deliverables (Yearly project reports and project plan updates).

#  INTRODUCTION

Global networks like IoT create an enormous potential for new generations of
IoT applications, by leveraging synergies arising through the convergence of
consumer, business and industrial Internet, and creating open, global networks
connecting people, data, and “things”. A series of innovations across the IoT
landscape have converged to make IoT products, platforms and devices
technically and economically feasible. However, despite these advancements the
realization of the IoT potential requires overcoming significant business and
technical hurdles, e.g. Dynamicity, Scalability, Heterogeneity, End-to-end
Security and Privacy.

To address these challenges, SEMIoTICS aims “ _To develop a pattern-driven
framework, built upon existing IoT platforms, to enable and guarantee secure
and dependable actuation and semi-autonomic behaviour in IoT/IIoT
applications. The SEMIoTICS framework will support cross-layer intelligent
dynamic adaptation, including heterogeneous smart objects, networks and
clouds. To address the complexity and scalability needs within horizontal and
vertical domains, SEMIoTICS will develop and integrate smart programmable
networking and semantic interoperability mechanisms. The above will be
validated by industry, using three diverse usage scenarios in the areas of
renewable energy, healthcare, and smart sensing and will be offered through an
open_

_API._ ”

An essential measure to reach the highly ambitious and challenging aim and
subsequent objectives of SEMIoTICS project is to set the appropriate quality
management processes and criteria. These processes and criteria are described
in this document in order to successfully ensure high quality project
outcomes.

This deliverable is addressed to any interested public reader. It will be
practically useful for the consortium members who can use it as a basis for
the general management of all project activities. Guidelines/criteria given in
this deliverable (Chapter 3) will ensure that all kind or project reports and
publications will follow high quality standards and will give all consortium
members a comprehensive overview on the SEMIoTICS procedures for publication
and reporting. Chapter 4 provides details about Innovation Management plan and
project’s different tasks which will lead to innovation and its assessment.
Chapter 5 gives details about project’s Data Management Plan (DMP) which for
the consortium internal usage.

This document refers to:

  1. the Description of Action (part B) [1] 

  

  2. the Consortium Agreement [2] 

  

  3. the Grant Agreement [3] 

  

  

#  QUALITY MANAGEMENT PLAN (QMP)

##  Roles and Responsibilities

Roles and responsibilities for maintaining and updating deliverables/plans are
linked to roles within SEMIoTICS. In case new personnel is assigned to a
relevant role, responsibilities with respect to previously assigned tasks are
also taken over.

The project management roles and the structure of SEMIoTICS are described, and
the following table gives a quick reference to the detailed description of
each role:  
  
<table>  
<tr>  
<th>

Project Coordinator (PC)

</th>  
<th>

The Coordinator will consolidate the input and will do the continuous
reporting (online).

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

Technical Project Manager (TPM)

</td>  
<td>

TPM, also known as Scientific, Technical and Innovation Project Manager, is
responsible of the technical and innovation management; and transparently
communicates innovation management related issues within PCC and PTC.

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

Project Coordination Committee (PCC)

</td>  
<td>

PCC approval is required for all disclosure of confidential project results
outside the consortium. PCC and PTC are responsible to take appropriate
actions according to the rules on innovation management and intellectual
property creation. PCC constitutes all the named personnel in CA [2] of
SEMIoTICS

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

Project Technical Committee (PTC)

</td>  
<td>

PTC has a strong focus on development and protection of intellectual property
and its efforts will be supported by TPM and PCC in order to create a solid
base for industrial and commercial exploitation. PTC constitutes all the WP
leads of SEMIoTICS

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

Work Package Leaders

</td>  
<td>

Work package leaders are responsible for quality control measures within their
work package and will monitor that this quality management plan is followed.

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

Task Leaders

</td>  
<td>

Task leaders have to give work package leader support in effectively
monitoring the QMP implementation. Work package leaders are responsible to
report incidents of the QMP not being followed to the PTC

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

Reviewer

</td>  
<td>

Reviewer is assigned by WP Leader/PTC who reviews the deliverable/other
material based on respective quality criteria

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

Advisory Committee (AC)

</td>  
<td>

Advisory Committee (AC) consisting of relevant external stakeholders from
research, academia and industry. The AC will follow the project development
and will provide necessary feedback in order to ensure that the scientific and
technological evolution of the project is in the direction to fulfill its
goals and provide an external global viewpoint.

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

_**TABLE 1: PROJECT MANAGEMENT ROLES** _

##  Management Bodies

SEMIoTICS has a lean management structure supporting an effective project
execution including the tasks and activities related to innovation and
innovation management.

A clear definition of roles is also given there and can be summarized as
follows:

  * During project execution, the TPM will be responsible of driving the technical and innovation management and transparently communicate innovation management related issues within PCC and PTC. 

  

  * PCC and PTC are responsible to take appropriate actions according to the rules on innovation management and intellectual property creation. 

  

  * Partners of SEMIoTICS have departments for maintaining the intellectual property portfolio and existing interfaces of consortium partners will be used to protect intellectual property developed within the project according to local law 

  

  * SEMIoTICS consortium partners have experience in the collaboration of their own legal / IP departments and projects and existing processes will support creation of intellectual property within the project (e.g., use of tools like internal/external patent databases). 

  

  * The PTC will have a strong focus on development and protection of intellectual property and its efforts will be supported by TPM and PCC in order to create a solid base for industrial and commercial exploitation. 

  

  * Different exploitation strategies were already discussed during the proposal phase and Task 6.2 and 

  

6.1 has allocated resources for work on exploitation and impact creation.

  * PCC approval is required for all disclosure of confidential project results outside the consortium and decisions will be taken according to this deliverable. 

  

  * SEMIoTICS has an interface established to interact with other projects within IOT-EPI programme in order to drive the collaborative exercise of all partners. 

  

  * Consortium partners contributing expertise on business, technologies, application domain, and research which enable innovation aligned to the business activities of the partners, and thus, will lead to either the development of a product, a service, or future research. 

  

  * Legal aspects of innovation, intellectual property being created within the project, joint ownership of results (if applicable), joint exploitation strategies, and all related confidentiality issues are clarified in the consortium agreement [2]. 

  

##  Quality Management

###  REPORTING PROCEDURES

All project reporting procedures have to follow the terms and conditions as
stated in the Grant Agreement. In general, SEMIoTICS facilitates quality
management by regular project reporting of all partners being used as input
for the project reports for the EC and the Project Officer. SEMIoTICS will use
continuous reporting to the EC via the web-based project management portal.
Therefore, WP leads have to give short reports on WP related activities and
achievements to the Coordinators at the end of each quarter (March, June,
September, and December). The Coordinator will consolidate the input and will
do the continuous reporting (online). Reporting includes progress report
(against baseline), achievements, resources, and risks. Content for the
reporting deliverables, namely yearly reports (D1.3, D1.4, and D1.5) is
created based on information from continuous reporting, as well as specific
information on closed, active and upcoming WPs directly given by corresponding
WP leads.

Detailed technical content and detailed progress information of each WP is
reported from Task leads towards WP lead and to Project Technical Committee
(PTC) via WP lead.

Monthly PTC meetings/calls are used to review progress, review/update the risk
register, updates of DMP, and dissemination plan, inter-WP collaboration, as
well as for reporting towards PCC. PTC call minutes will be forwarded to PCC
within 5 working days after each PTC call.

###  QUALITY CONTROL – GENERAL

Work package leaders are responsible for quality control measures within their
work package and will monitor that this quality management plan is followed.
Task leaders have to give them support in effectively monitoring the QMP
implementation. Work package leaders are responsible to report incidents of
the QMP not being followed to the PTC. PTC will decide on mitigation actions,
if possible. In case mitigation is not possible through PTC, PTC will inform
PCC for further actions.

Detailed quality control measures for different types of results are described
in the following sections.

##  Quality control for publications

###  RULES FOR PUBLICATION

The following procedure ensures a high quality of joint publications related
to SEMIoTICS and take care that IPR of other parties is not infringed. Timing
is aligned so that each project partner can also complete mandatory internal
approval procedures.  
  
<table>  
<tr>  
<th>

At least 4 weeks before deadline

</th>  
<th>

Venue is registered in the Dissemination Plan. Author will send notification
to Task 6.1 lead and PTC will start tracking the status of that publication.
This includes planned authors, title, abstract, and planned venue.

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

At least 3 weeks before deadline

</td>  
<td>

Outline of presentation is ready, and authors start partner internal approval
processes.

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

At least 1 week before deadline

</td>  
<td>

Work package internal (authors / subject matter experts) review started,
authors are responsible to integrate / discuss comments with reviewers.

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

Before submission

</td>  
<td>

Authors declare successful (internal) review and all authors agree to the
submission of that final version (e.g., via email). PTC will store that
information on the repository together with the submitted version.

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

After submission / dissemination / acceptance of publication

</td>  
<td>

Authors ensure that status of publication is tracked and updated in
Dissemination Plan (update notifications to Task 6.1 lead).

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

####  TABLE 2A: PROCEDURE FOR JOINT PUBLICATION

For publications with only one partner being involved, the procedure is
simplified:  
  
<table>  
<tr>  
<th>

At least 4 weeks before deadline

</th>  
<th>

Venue is registered in the Dissemination Plan and PTC will start tracking the
status of publication and submission.

This includes planned authors, title, abstract/outline, and planned venue.

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

After submission / dissemination / acceptance of publication

</td>  
<td>

Authors ensure that status of publication is tracked and updated in
Dissemination Plan (update notifications to Task 6.1 lead).

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

_**TABLE 2B: PROCEDURE FOR PUBLICATION OF ONE PARTNER** _

Objections will be handled according to the procedures given in the Grant
Agreement.

###  ACKNOWLEDGEMENT

Acknowledgement to the EC for its funding must be clearly indicated on every
publication and presentation for which project funding will be claimed.
Typical text is as follows:

This [paper/presentation/...] has received funding from the European Union's
Horizon 2020 research and innovation programme
H2020-IOT-2016-2017/H2020-IOT-2017, under grant agreement No. 780315\.

###  DISCLAIMER

It is recommended to include a disclaimer on every publication and
presentation. Typical text is as follows:

This [paper/presentation/...] reflects only the authors' views and the
European Commission is not responsible for any use that may be made of the
information it contains.

##  Quality control for deliverables

The project coordinator, together with PCC and Technical Manager will closely
coordinate technical quality checks for all deliverables. All deliverables
will be subject to a review within the work package before forwarding them to
PCC for final review and approval. Where necessary, the Project Coordinator
could request further work of the partners on a deliverable, to ensure that it
complies with the project’s contractual requirements. All deliverables will
include the names of the editor (responsible person), the authors of the
content, the reviewers, as well as the approvers. After PCC approval,
deliverables are submitted to the EC by the coordinator. Escalations in case
of quality concerns will follow the procedures given in the “Conflict
Resolution” of Grant Agreement [3].

To ensure that this process can be followed through, the following time plan
has been agreed:  
  
<table>  
<tr>  
<th>

Start of tasks contributing to a deliverable

</th>  
<th>
##  Quality control for other material

###  DISSEMINATION ACTIVITIES (INCL. IOT-EPI PROGRAMME LEVEL TOPICS)

Detailed procedures on dissemination activities are given in the Dissemination
Plan (e.g., event description, activity description, and timing). Quality
control related actions for dissemination activities are:

  * Dissemination activities have to be coordinated with the WP6 lead 

  

  * For “standard” dissemination activities, a SEMIoTICS project presentation slide deck is available in the project repository. 

  

  * For all additional technical content in dissemination activities a project internal peer review is foreseen, and PCC has to give approval for dissemination after peer review is done. Peer review is initiated by the author by sending a request to PTC. PTC will assign a reviewer. After review is finished PTC will give a recommendation for approval to PCC. 

  

For publications to go to public, prior written notice with abstract of any
planned publication (irrespective if for scientific journals, conferences,
online publications, or the like) needs to be given to the consortium members
at least forty-five (45) days before the planned publication date ((i.e. the
day the journal will be published, the day the conference is scheduled for,
etc.). Any objection from PTC/PCC members as specified in consortium agreement
to the planned publication shall be made in writing to all the consortium
members within thirty (30) days after receipt of the written notice. If no
objection is made within the time limit stated above, the publication is
permitted. The internal approval process is mentioned earlier in Table 1A and
Table 1B.

###  DEMONSTRATION ACTIVITIES (INCL. IOT-EPI PROGRAMME LEVEL TOPICS)

Demonstration activities will follow the same procedure as dissemination
activities with technical content (e.g., peer review of technical content).
All demonstration activities have to be coordinated with PTC well in time -
due to extended visibility, partners might have to follow internal approval
procedures which need lead time. Demonstrations will be coordinated by
dedicated (internal) workgroups and these workgroups will directly report to
PTC. Quality assurance will follow the procedures given in the Grant Agreement
[3].

##  Quality assurance

Quality assurance will follow the procedures given in the Grant Agreement,
namely: Quality assurance will be performed in all project phases through WP1
by PCC that will undertake to secure SEMIoTICS quality and relevant
documentation at all development stages of the project. SEMIoTICS is adopting
the Plan-Do-CheckAct (PDCA) principle to achieve proper monitoring of all
project activities. With PDCA all work done within the WPs and tasks will be
closely monitored on a continuous basis resulting in PCC/PTC initiated
corrective actions and changes to the project plan when necessary.

###  QA FOR DELIVERABLES

QA recommends and expects certain Quality levels / Quality Assurance levels
for project deliverables, as well as the criteria and processes for assessing
them, including responsible project internal stakeholders (Task leader/Editor,
Contributor, Reviewer, WP Leader, PTC, TPM, PCC, PC).

The title page of the SEMIoTICS deliverables clearly identifies authors,
reviewers, and approvers. This gives a transparent view on the persons
involved in quality control and deliverables can only be released after the
quality assurance levels (e.g., internal reviews/processes) are successfully
passed.

Each Task leader/editor will follow the criteria such as:

  1. The deliverable Table of Contents are prepared according to PERT chart (see section 6.5) of the project. 

  

  2. Incorporating suggestions from PTC, TPM, PCC and PC for continuous improvement of the deliverable 

  

  3. Making sure timely inputs from the contributors of the task. 

  

  4. Checking and managing the flow of information in the technical contents as per task objectives fulfilling the WP objectives. 

  

  

Each contributor of the deliverable will follow the criteria such as:

  1. Timely contribution of the technical contents to the Editor of the deliverable. 

  

  2. Checking the flow of information in the technical contents. 

  

  

Each WP lead will follow the criteria such as:

  1. Monitor technical progress w.r.t. WP objectives in comparison to resource consumption each of its tasks within WP. 

  

  2. Check each of WP’s deliverable as per PERT chart (see section 6.5) of the project and ask for corrections from the Editor, if necessary. 

  

  3. Assign a reviewer/s which will check the consistency of the deliverable from the information flow point of view. 

  

  

The deliverable reviewer assigned by WP lead will follow the criteria such as:

  1. Check whether each deliverable starting from high level concepts, and then presents technologies and details in separate sections. 

  

  2. Check for English grammatical errors, broken links. 

  

  3. Check the layout of the deliverables w.r.t. the reporting template 

  

  

After the deliverable is properly reviewed internal to the WP, TPM sends it to
PTC for their review and checking for any obvious artifacts which may affect
other tasks in their respective WPs. After their approval TPM sends it to PCC
for final approval. After PCC approval, PC uploads the deliverable on EC
portal.

###  QA FOR PUBLICATIONS

All SEMIoTICS publication activities will be captured in the Dissemination
Plans of WP6 and also information quality control gates are recorded there.
This includes proper documentation that the quality control gates are
successfully passed, as well as the status of external peer reviews (e.g.,
publication submitted to double blind peer review and was accepted for
publication on the conference).

###  QA FOR OTHER MATERIAL

All internal reviews for other SEMIoTICS dissemination material will be
documented in the dissemination plan (per dissemination activity). This
includes information on authors, reviewers, and approvers.

##  Risk Management

The overall risks, considering the project to be technically too broad and
ambitious, is controlled by the excellence and experience of the consortium
partners. It is important that the consortium identify the risks that may
originate from the approaches used to achieve the project goals, as well as
the measures that the consortium could take to minimize them. The potential
project risks can be classified into the following groups: i. Execution risks,

  1. Partner related, 

  

  2. Planning problems 

  

  3. Consortium Collaboration Issues ii. Technological risks, iii. External risks. 

  

  

SEMIoTICS’s major risks, including description, possible impacts, and related
contingency plans are described in the Risk register which is regularly
updated in monthly PTC meetings.

In case a serious issue arises in any deliverable, deliverable responsible
person/reviewer/PTC/Technical Project Manager/PCC/Project Coordinator can
raise that issue directly with the involved persons in the project directly or
indirectly through Technical Project Manager/Project Coordinator.

##  Deliverable tracking process

Transparency of roles and responsibilities has a big impact on the project
success. Uncertainty can dramatically affect individual, organisational as
well as the consortium performance. Therefore, responsible persons for each
organisation and per WP were defined. The tables below show initial
assignments of the Deliverables, its reviewers and Milestones of the project;
and detailed tacking incl. reasons for delay (if any) will be done throughout
the WP1 activities. While Deliverable leading organisations were already
defined within the DoA [1], the concrete editor responsible for requesting and
guiding partner inputs towards a punctual and high-quality submission, were
named at the project start till Milestone 2 (MS2). The later assignments will
be mentioned in subsequent deliverables of WP1 (Yearly and half-yearly project
plan updates). In line with the quality control process for deliverables
(described in chapter 3.4) at least one specific internal reviewer for each
deliverable was defined and clear deadlines for the draft version, internal
review as well as for the pre-final version and final version submission were
established.

Note: For simplicity, Table 4A is filled till Milestone MS2 and Table 4B is
filled till Milestone MS1. In the forthcoming WP1 deliverables this table will
be updated continuously.

This table is linked to file “Deliverables_tracking_Editors and
reviewers.xlsx”

_https://overseer1.erlm.siemens.de/repository/Document/downloadWithName/Deliverables_tracking_

_Editors%20and%20reviewers.xlsx?reqCode=downloadWithName&id=24675185  
  
<table>  
<tr>  
<th>

Deliverables for Project 780315

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

Deliverables

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

WP No

</td>  
<td>

Del No

</td>  
<td>

Title

</td>  
<td>

Editor

</td>  
<td>

Reviwer/s

</td>  
<td>

Comments

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

WP1

</td>  
<td>

D1.1

</td>  
<td>

Project web site and internal communication platform

</td>  
<td>

Andreas Miaoudakis (FORTH)

</td>  
<td>

Nikolaos Petroulakis (FORTH), Vivek Kulkarni (SIEMENS)

</td>  
<td>

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

WP2

</td>  
<td>

D2.1

</td>  
<td>

Analysis of IoT value drivers

</td>  
<td>

Prof. Georgios Spanoudakis (Sphynx)

</td>  
<td>

Vivek Kulkarni (SIEMENS)

</td>  
<td>

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

WP2

</td>  
<td>

D2.2

</td>  
<td>

SEMIoTICS usage scenarios and requirements

</td>  
<td>

Vivek Kulkarni (SIEMENS)

</td>  
<td>

Use case wise peer-reviewers

</td>  
<td>

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

WP1

</td>  
<td>

D1.2

</td>  
<td>

Initial Quality, Innovation and Data Management Plan

</td>  
<td>

Volkmar Döricht (SIEMENS)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

WP1

</td>  
<td>

D1.7

</td>  
<td>

Periodic project plan updates (M6)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

Vivek Kulkarni (SIEMENS)

</td>  
<td>

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

WP2

</td>  
<td>

D2.3

</td>  
<td>

Requirements specification of SEMIoTICS framework

</td>  
<td>

Mirko Falchetto (ST-I)

</td>  
<td>

Peer-reviewers of each section

</td>  
<td>

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

WP6

</td>  
<td>

D6.1

</td>  
<td>

Impact creation, dissemination and exploitation plan

</td>  
<td>

Christos Verikoukis (CTTC)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

MS1

</td>  
<td>

</td>  
<td>

Finalization of the Requirements

</td>  
<td>

Danilo Pau (ST-I)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

Approxmiate 1 month delay in completion of the milestone was agreed with the
PO at that time.

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

WP1

</td>  
<td>

D1.3

</td>  
<td>

Year 1 project report and project plan updates

</td>  
<td>

Vivek Kulkarni (SIEMENS)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

WP3

</td>  
<td>

D3.5

</td>  
<td>

Field-level middleware & networking toolbox (first draft)

</td>  
<td>

Prodromos Vasileios Mekikis (IQUADRAT)

</td>  
<td>

Ermin Sakic (SIEMENS)

</td>  
<td>

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

WP2

</td>  
<td>

D2.4

</td>  
<td>

SEMIoTICS high level architecture (first draft)

</td>  
<td>

Mirko Falchetto (ST-I)

</td>  
<td>

Łukasz Ciechomski (BlueSoft)

</td>  
<td>

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

WP3

</td>  
<td>

D3.1

</td>  
<td>

Software defined programmibilty for IoT devices (first draft)

</td>  
<td>

Ermin Sakic (SIEMENS)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

WP3

</td>  
<td>

D3.2

</td>  
<td>

Network Functions Virtualization for IoT (1st draft)

</td>  
<td>

Luis Sanabria Russo (CTTC)

</td>  
<td>

Ermin Sakic (SIEMENS)

</td>  
<td>

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

WP3

</td>  
<td>

D3.3

</td>  
<td>

Bootstrapping and interfacing SEMIoTICS field level devices (1st draft)

</td>  
<td>

Darko Anicic (SIEMENS)

</td>  
<td>

Kostas Ramantas (IQUADRAT)

</td>  
<td>

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

WP3

</td>  
<td>

D3.4

</td>  
<td>

Network-level Semantic Interoperability (first draft)

</td>  
<td>

Iason Somarakis (Sphynx)

</td>  
<td>

Ermin Sakic (SIEMENS)

</td>  
<td>

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

WP4

</td>  
<td>

D4.1

</td>  
<td>

SEMIoTICS SPDI Patterns (first draft)

</td>  
<td>

Konstantinos Fysarakis (Sphynx)

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

MS2

</td>  
<td>

</td>  
<td>

First version of SEMIoTICS architecture, End of 1st Field and Network level
mechanisms development cycle

</td>  
<td>

SIEMENS

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

WP4

</td>  
<td>

D4.2

</td>  
<td>

SEMIoTICS Monitoring, prediction and diagnosis mechanisms (first draft)

</td>  
<td>

ENG

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.3

</td>  
<td>

Embedded Intelligence and local analytics (first draft)

</td>  
<td>

ST-I

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.4

</td>  
<td>

Semantic interoperability mechanisms for IoT (first draft)

</td>  
<td>

FORTH

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.5

</td>  
<td>

SEMIoTICS Security and privacy mechanisms (first draft)

</td>  
<td>

UNI PASSAU

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.6

</td>  
<td>

Implementation of SEMIoTICS BackEnd API (Cycle 1)

</td>  
<td>

BlueSoft

</td>  
<td>

</td>  
<td>

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

MS3

</td>  
<td>

</td>  
<td>

End of 1st Pattern-driven smart behavior of IIoT mechanisms development cycle
and the 1st backend implementation cycle

</td>  
<td>

Sphynx

</td>  
<td>

Nikolaos Petroulakis (FORTH)

</td>  
<td>

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

WP1

</td>  
<td>

D1.8

</td>  
<td>

Periodic project plan updates (M18)

</td>  
<td>

FORTH

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.2

</td>  
<td>

Interim report on impact creation, dissemination activities

</td>  
<td>

CTTC

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.3

</td>  
<td>

Interim report on exploitation activities (M18)

</td>  
<td>

ENG

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.4

</td>  
<td>

Interim report on standardization activities

</td>  
<td>

SIEMENS

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.6

</td>  
<td>

Field-level middleware & networking toolbox (second draft)

</td>  
<td>

IQUADRAT

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.1

</td>  
<td>

SEMIoTICS KPIs and Evaluation Methodology

</td>  
<td>

UNI PASSAU

</td>  
<td>

</td>  
<td>

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

WP2

</td>  
<td>

D2.5

</td>  
<td>

SEMIoTICS high level architecture (final)

</td>  
<td>

BlueSoft

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.7

</td>  
<td>

Implementation of SEMIoTICS BackEnd API (Cycle 2)

</td>  
<td>

BlueSoft

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.2

</td>  
<td>

Software system integration (Cycle 1)

</td>  
<td>

BlueSoft

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.3

</td>  
<td>

IIoT Infrastructure set-up and testing (Cycle 1)

</td>  
<td>

IQUADRAT

</td>  
<td>

</td>  
<td>

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

MS4

</td>  
<td>

</td>  
<td>

Final version of SEMIoTICS architecture, end of 2nd implem.cycle, End of setup
and testing 1st cycle, Evaluation methodology defined

</td>  
<td>

FORTH

</td>  
<td>

Vivek Kulkarni (SIEMENS)

</td>  
<td>

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

###  TABLE 4A: DELIVERABLE INITIAL ASSIGNMENTS (EDITOR/RESPONSIBLE PERSON,
REVIEWER)  
  
<table>  
<tr>  
<th>

Deliverables for Project 780315

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

Deliverables

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

WP No

</td>  
<td>

Del No

</td>  
<td>

Title

</td>  
<td>

Lead Beneficiary

</td>  
<td>

Nature

</td>  
<td>

Dissemination Level

</td>  
<td>

Est. Del. Date (annex I)

</td>  
<td>

Receipt Date

</td>  
<td>

Status

</td>  
<td>

Reasons for delay, if any

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

WP1

</td>  
<td>

D1.1

</td>  
<td>

Project web site and internal communication platform

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Confidential

</td>  
<td>

30-Jan-18

</td>  
<td>

28-May-18

</td>  
<td>

Submitted

</td>  
<td>

Project start happened 1 month earlier than consortium's expected start, Web
site was already operational and internal communication was in operation. The
delay was agreed with the PO at that time.

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

WP2

</td>  
<td>

D2.1

</td>  
<td>

Analysis of IoT value drivers

</td>  
<td>

Sphynx

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Mar-18

</td>  
<td>

03-May-18

</td>  
<td>

Submitted

</td>  
<td>

The deliverable submission delay was agreed with the PO at that time.

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

WP2

</td>  
<td>

D2.2

</td>  
<td>

SEMIoTICS usage scenarios and requirements

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-18

</td>  
<td>

14-Jun-18

</td>  
<td>

Submitted

</td>  
<td>

The deliverable submission delay was agreed with the PO at that time.

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

WP1

</td>  
<td>

D1.2

</td>  
<td>

Initial Quality, Innovation and Data Management Plan

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-18

</td>  
<td>

23-Jul-18

</td>  
<td>

Submitted

</td>  
<td>

The deliverable submission delay was agreed with the PO at that time.

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

WP1

</td>  
<td>

D1.7

</td>  
<td>

Periodic project plan updates (M6)

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Confidential

</td>  
<td>

30-Jun-18

</td>  
<td>

02-Aug-18

</td>  
<td>

Submitted

</td>  
<td>

The previously delayed deliverables brought additional delay.

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

WP2

</td>  
<td>

D2.3

</td>  
<td>

Requirements specification of SEMIoTICS framework

</td>  
<td>

ST-I

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-18

</td>  
<td>

07-Aug-18

</td>  
<td>

Submitted

</td>  
<td>

The previously delayed deliverables brought additional delay.

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

WP6

</td>  
<td>

D6.1

</td>  
<td>

Impact creation, dissemination and exploitation plan

</td>  
<td>

CTTC

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-18

</td>  
<td>

03-Jul-18

</td>  
<td>

Submitted

</td>  
<td>

The previously delayed deliverable esp. D2.1 and D2.2 brought additional
delay.

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

MS1

</td>  
<td>

</td>  
<td>

Finalization of the Requirements

</td>  
<td>

ST-I

</td>  
<td>

</td>  
<td>

</td>  
<td>

30-Jun-18

</td>  
<td>

07-Aug-18

</td>  
<td>

Submitted

</td>  
<td>

Approxmiate 1 month delay in completion of the milestone was agreed with the
PO at that time.

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

WP1

</td>  
<td>

D1.3

</td>  
<td>

Year 1 project report and project plan updates

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-18

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.5

</td>  
<td>

Field-level middleware & networking toolbox (first draft)

</td>  
<td>

IQUADRAT

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

31-Dec-18

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP2

</td>  
<td>

D2.4

</td>  
<td>

SEMIoTICS high level architecture (first draft)

</td>  
<td>

ST-I

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.1

</td>  
<td>

Software defined programmibilty for IoT devices (first draft)

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.2

</td>  
<td>

Network Functions Virtualization for IoT (1st draft)

</td>  
<td>

CTTC

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.3

</td>  
<td>

Bootstrapping and interfacing SEMIoTICS field level devices (1st draft)

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.4

</td>  
<td>

Network-level Semantic Interoperability (first draft)

</td>  
<td>

Sphynx

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.1

</td>  
<td>

SEMIoTICS SPDI Patterns (first draft)

</td>  
<td>

Sphynx

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS2

</td>  
<td>

</td>  
<td>

First version of SEMIoTICS architecture, End of 1st Field and Network level
mechanisms development cycle

</td>  
<td>

SIEMENS

</td>  
<td>

</td>  
<td>

</td>  
<td>

28-Feb-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.2

</td>  
<td>

SEMIoTICS Monitoring, prediction and diagnosis mechanisms (first dr

</td>  
<td>

a ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.3

</td>  
<td>

Embedded Intelligence and local analytics (first draft)

</td>  
<td>

ST-I

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.4

</td>  
<td>

Semantic interoperability mechanisms for IoT (first draft)

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.5

</td>  
<td>

SEMIoTICS Security and privacy mechanisms (first draft)

</td>  
<td>

UNI PASSAU

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.6

</td>  
<td>

Implementation of SEMIoTICS BackEnd API (Cycle 1)

</td>  
<td>

BlueSoft

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS3

</td>  
<td>

</td>  
<td>

End of 1st Pattern-driven smart behavior of IIoT mechanisms development cycle
and the 1st backend implementation cycle

</td>  
<td>

Sphynx

</td>  
<td>

</td>  
<td>

</td>  
<td>

31-May-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP1

</td>  
<td>

D1.8

</td>  
<td>

Periodic project plan updates (M18)

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Confidential

</td>  
<td>

30-Jun-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.2

</td>  
<td>

Interim report on impact creation, dissemination activities

</td>  
<td>

CTTC

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.3

</td>  
<td>

Interim report on exploitation activities (M18)

</td>  
<td>

ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.4

</td>  
<td>

Interim report on standardization activities

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.6

</td>  
<td>

Field-level middleware & networking toolbox (second draft)

</td>  
<td>

IQUADRAT

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

30-Sep-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.1

</td>  
<td>

SEMIoTICS KPIs and Evaluation Methodology

</td>  
<td>

UNI PASSAU

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Oct-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP2

</td>  
<td>

D2.5

</td>  
<td>

SEMIoTICS high level architecture (final)

</td>  
<td>

BlueSoft

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Nov-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.7

</td>  
<td>

Implementation of SEMIoTICS BackEnd API (Cycle 2)

</td>  
<td>

BlueSoft

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

30-Nov-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.2

</td>  
<td>

Software system integration (Cycle 1)

</td>  
<td>

BlueSoft

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Nov-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.3

</td>  
<td>

IIoT Infrastructure set-up and testing (Cycle 1)

</td>  
<td>

IQUADRAT

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Nov-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS4

</td>  
<td>

</td>  
<td>

Final version of SEMIoTICS architecture, end of 2nd implem.cycle, End of setup
and testing 1st cycle, Evaluation methodology defined

</td>  
<td>

FORTH

</td>  
<td>

</td>  
<td>

</td>  
<td>

30-Nov-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP1

</td>  
<td>

D1.4

</td>  
<td>

Year 2 project report and project plan updates

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.8

</td>  
<td>

Interim report on exploitation activities (M24)

</td>  
<td>

ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-19

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.7

</td>  
<td>

Software defined programmability for IoT devices (final)

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

29-Feb-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.8

</td>  
<td>

Network Functions Virtualization for IoT (final)

</td>  
<td>

CTTC

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

29-Feb-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.9

</td>  
<td>

Bootstrapping and interfacing SEMIoTICS field level devices (final)

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

29-Feb-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.10

</td>  
<td>

Network-level Semantic Interoperability (final)

</td>  
<td>

Sphynx

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

29-Feb-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP3

</td>  
<td>

D3.11

</td>  
<td>

Field-level middleware & networking toolbox (final)

</td>  
<td>

IQUADRAT

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.8

</td>  
<td>

SEMIoTICS SPDI Patterns (final)

</td>  
<td>

Sphynx

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.9

</td>  
<td>

SEMIoTICS Monitoring, prediction and diagnosis mechanisms (final)

</td>  
<td>

ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.10

</td>  
<td>

Embedded Intelligence and local analytics (final)

</td>  
<td>

ST-I

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.11

</td>  
<td>

Semantic interoperability mechanisms for IoT (final)

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.12

</td>  
<td>

SEMIoTICS Security and privacy mechanisms (final)

</td>  
<td>

UNI PASSAU

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Apr-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP1

</td>  
<td>

D1.9

</td>  
<td>

Periodic project plan updates (M30)

</td>  
<td>

FORTH

</td>  
<td>

Report

</td>  
<td>

Confidential

</td>  
<td>

30-Jun-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP4

</td>  
<td>

D4.13

</td>  
<td>

Implementation of SEMIoTICS BackEnd API (Final Cycle)

</td>  
<td>

BlueSoft

</td>  
<td>

Other

</td>  
<td>

Confidential

</td>  
<td>

30-Jun-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.9

</td>  
<td>

Interim report on exploitation activities (M30)

</td>  
<td>

ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

30-Jun-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS5

</td>  
<td>

</td>  
<td>

End of all development and imlementation

</td>  
<td>

BlueSoft

</td>  
<td>

</td>  
<td>

</td>  
<td>

30-Jun-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS8

</td>  
<td>

</td>  
<td>

Feedback from local ethical board on ethical guidlelines

</td>  
<td>

ENG

</td>  
<td>

</td>  
<td>

</td>  
<td>

30-Jun-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.4

</td>  
<td>

Demonstration and validation of IWPC-Energy (Cycle 1)

</td>  
<td>

SIEMENS

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Jul-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.5

</td>  
<td>

Demonstration and validation of SARA-Health (Cycle 1)

</td>  
<td>

ENG

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Jul-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.6

</td>  
<td>

Demonstration and validation of IHES-Generic IoT (Cycle 1)

</td>  
<td>

ST-I

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Jul-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.7

</td>  
<td>

Software system integration (Cycle 2)

</td>  
<td>

BlueSoft

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Aug-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.8

</td>  
<td>

IIoT Infrastructure set-up and testing (Cycle 2)

</td>  
<td>

IQUADRAT

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Aug-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS6

</td>  
<td>

</td>  
<td>

End of 2nd setup and testing cycle, End of 1st demonstation cycle

</td>  
<td>

IQUADRAT

</td>  
<td>

</td>  
<td>

</td>  
<td>

31-Aug-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP1

</td>  
<td>

D1.5

</td>  
<td>

Year 3 project report and project plan updates

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP1

</td>  
<td>

D1.6

</td>  
<td>

Final project report

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Confidential

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.9

</td>  
<td>

Demonstration and validation of IWPC-Energy (Cycle 2)

</td>  
<td>

SIEMENS

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.10

</td>  
<td>

Demonstration and validation of SARA-Health (Cycle 2)

</td>  
<td>

ENG

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP5

</td>  
<td>

D5.11

</td>  
<td>

Demonstration and validation of IHES-Generic IoT (Cycle 2)

</td>  
<td>

ST-I

</td>  
<td>

Demonstrator

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.5

</td>  
<td>

Final report on impact creation, dissemination activities

</td>  
<td>

CTTC

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.6

</td>  
<td>

Final report on exploitation activities

</td>  
<td>

ENG

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

WP6

</td>  
<td>

D6.7

</td>  
<td>

Final report on standardization activities

</td>  
<td>

SIEMENS

</td>  
<td>

Report

</td>  
<td>

Public

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS7

</td>  
<td>

</td>  
<td>

Completion of Demonstration and Evaluation

</td>  
<td>

SIEMENS

</td>  
<td>

</td>  
<td>

</td>  
<td>

31-Dec-20

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

MS9 Selection and consent of Users ENG 30-Dec-20

**TABLE 4B: DELIVERABLE DETAILED TRACKING**

#  INNOVATION MANAGEMENT PLAN (IMP)

##  Innovation Management

SEMIoTICS has a consortium agreement [2] in place which covers ownership, and
access / usage rights of foreground and background IP, during and after
project.

High-profile academic partners, as well as strong involvement of the IP
departments of industry partners will ensure that IP is identified and
appropriately protected.

The Description of Action (Section 3.2.3) [1] also defines the implementation
of Innovation Management in SEMIoTICS as described below:

Beyond the advancements to the state of the art in individual technology and
scientific areas, the overarching groundbreaking objective of SEMIoTICS is to
deliver a framework, available through an open API that will enable and
guarantee secure and dependable actuation and intelligent semiautonomous
adaptation of IIoT and IoT applications involving heterogeneous smart objects.
SEMIoTICS approach is characterized by three pillars:

i. SPDI patterns-based development of IIoT/IoT application to ensure SPDI
properties [WP4 deliverables] ii. Semi-autonomic behaviour and evolution based
on cross-layer embedded intelligence [WP3, WP4 and WP5 deliverables] and iii.
Supporting interoperability across heterogeneous IIoT/IoT platforms and
vertical domains [WP3 (esp. Task 3.3, Task 3.4), WP4 (esp. Task 4.4) and WP5
deliverables].

which during the course of the project may lead to following innovations:

  1. Platform innovation stemming from security driven design foundations empowering SEMIoTICS to become a basis for building secure and trustworthy IoT ecosystems. 

  

  2. Application and Systems innovation stemming from the development of a SPDI-centric layered infrastructure involving network, software and device innovations integrated to form the SEMIoTICS framework. 

  

  3. Service innovation stemming from the deployment of the SEMIoTICS framework in lab trials, the procedures and applications developed through this process as well as lessons learned from the lab trials of SEMIoTICS. 

  

  

Innovation Management will be effectively performed by the leader of Task 6.2
Exploitation of results with the support of the Technical Project Manager
(Scientific and Technical Project Manager (STIPM)) and ultimately of the
Project Coordination Committee (PCC). The innovation collection process will
be managed by the consortium in the context of relevant WPs and will be
integrated in the overall project results. The Task 6.2 leader will assist the
WP leaders and the Technical Project Manager in handling all matters
concerning Intellectual Property protection for the produced innovations as
well as their inclusion in the project’s exploitation plan in D6.1.

###  INNOVATION SUPPORTING TASKS AND PROCESSES

Driving Research and Innovation is an integral part of SEMIoTICS and deeply
anchored inside the work structure. Following tasks and deliverables are
directly related to support, enable, or drive innovation in SEMIoTICS (for
detailed descriptions of tasks and deliverables see [6]):

Task 6.1: Impact Creation and Dissemination

Task 6.2: Exploitation of results

Task 6.3: Standardization  
  
<table>  
<tr>  
<th>

Related Task

</th>  
<th>

Created Output

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

**Task 2.2:** Specification of use case scenarios & applications and their
requirements

**Task 2.3:** Specification of infrastructure requirements

**Task 2.4:** SEMIoTICS architecture design

</td>  
<td>

**D2.3:** Requirements specification of SEMIoTICS framework (M6)

**D2.5:** SEMIoTICS high level architecture (M26)

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

**Task 3.3:** Semantics-based bootstrapping & interfacing

**Task 3.4:** Network-level semantic Interoperability **Task 3.5:**
Implementation of Field-level middleware & networking toolbox.

</td>  
<td>

**D3.9:** Bootstrapping and interfacing SEMIoTICS field level devices (final)
(M26)

**D3.10:** Network-level Semantic Interoperability

(final) (M26)

**D3.11:** Field-level middleware & networking toolbox (final) (M28)

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

**Task 4.1:** Architectural SPDI patterns

**Task 4.2:** Monitoring, prediction and diagnosis

**Task 4.3:** Embedded Intelligence and local analytics

**Task 4.4:** End-to-End Semantic Interoperability

**Task 4.5:** End-to-End Security and Privacy

**Task 4.6:** Implementation of SEMIoTICS backend

API

</td>  
<td>

**D4.8:** SEMIoTICS SPDI Patterns (final) (M28) **D4.9:** SEMIoTICS
Monitoring, prediction and diagnosis mechanisms (final) (M28)

**D4.10:** Embedded Intelligence and local analytics (final) (M28)

**D4.11:** Semantic interoperability mechanisms for

IoT (final) (M28)

**D4.12:** SEMIoTICS Security and privacy mechanisms (final) (M28)

**D4.13:** Implementation of SEMIoTICS BackEnd API (final) (M30)

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

**Task 5.3:** IIoT Infrastructure set-up and testing

**Task 5.4:** Demonstration and validation of IWPC- Energy scenario

**Task 5.5:** Demonstration and validation of SARAHealth scenario

**Task 5.6:** Demonstration and validation of IHES-

Generic IoT scenario

</td>  
<td>

**D5.4/5.9; D5.5/5.10; D5.6/5.11:** Demonstration and

Validation of respective usage scenarios (M31/M36)

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

**Task 6.1:** Impact Creation and Dissemination

**Task 6.2:** Exploitation of results

**Task 6.3:** Standardization

</td>  
<td>

**D6.1:** Impact creation, dissemination and exploitation plan (M6)

**D6.3:** Interim report on exploitation activities (M18)

**D6.4:** Interim report on standardization activities (M18)

**D6.8:** Interim report on exploitation activities(M24)

**D6.9:** Interim report on exploitation activities (M30)

**D6.6:** Final report on exploitation activities (M36)

**D6.7:** Final report on standardization activities

(M36)

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

####  TABLE 5: INNOVATION RELATED TASK AND OUTPUT

After M28, SEMIoTICS will be in a position to understand both market and
technical problems at hand, with a goal of successfully implementing
appropriate creative ideas demonstrated by WP3 and WP4. Following
classification shows different phases of Innovation management as per (Specht,
2002).

_Source: Classification of technology, R &D and innovation management (Specht,
2002) _

Being a RIA project, SEMIoTICS focusses on Technology management in the
technical work packages WP2, WP3, WP4 and WP5. In Task 6.2 of WP6, SEMIoTICS
consortium plans to come up with leaner business model canvas for SEMIoTICS
depicting a new or improved product or service or process from each partner
perspective. This may empower SEMIoTICS consortium to respond to an external
(e.g. testing Business Models in different scenarios) or internal opportunity
(e.g. use SEMIoTICS for internal product development). This will be
checked/pursued by the consortium members from time to time during the project
or even after the project end. The exact proceedings and decisions will be
taken directly in Task 6.2 of WP6.

##  Exploitation Management

SEMIoTICS presented already a draft exploitation strategy at proposal stage
(see Section 2.2.3 in [1]) and elaborations of further details on the
exploitation plan are subject to WP6.

Each partner delivered a high-level exploitation plan (Section 2.2.3) [1] at
proposal stage and these exploitation plans will be detailed further within
work of WP6.

Task 6.2 will address exploitation of the project results via e.g. commercial
and scientific exploitation strategies, plans and implementation. SEMIoTICS
will investigate different routes to be used for exploitation (e.g. use for
further research, developing and selling own products/services, spin-off
activities, and standardization activities/new standards/ongoing procedures)

Exploitation of project results will be a topic on the agenda of consortium
meetings in order to support exploitation of results on consortium level.
Results are documented in Deliverables D6.3, D6.8, D6.9 and D6.6.

##  Communication / Dissemination Management

All aspects of communication and dissemination management are captured in the
Dissemination Plan [5] and will not be covered here.

##  Capturing and handling IPR

IPR handling is covered in SEMIoTICS consortium agreement [2] (CA) and allows
each partner the exploitation of their own results. Also joint IPR is covered
by the CA and will ensure proper exploitation of the project results.

The SEMIoTICS consortium is composed in a way that each partner has strong
expertise in a certain technical/business domain and is responsible for
driving this domain forward. This ensures that the essential elements of
successful Innovation management are contributed by experts in the field (good
research practice by high profile academic partners, technologies, industrial
research, business aspects, and industry domain knowledge by leading industry
partners).

Capturing of IPR is supported by close interaction of technical and
exploitation tasks throughout the project.

Awareness of proper IPR capturing and handling will be raised by regular
sessions on this topic at all SEMIoTICS consortium meetings and PTC meetings.
For avoiding additional overhead in the project, PTC meeting is serving as
Intellectual Property Rights Committee (IPRC) to deal with intellectual
property that either is introduced to the project by a partner or produced as
a work package outcome. IPRC will be responsible for the definition of access
rights and licensing (if required so) of the project results as guided by
section 9.4 of consortium agreement [2] (CA), which provide details on access
rights for exploitation especially regarding exploitation of project outcomes
as a whole.

The table in the annex will give the overview of IPR filed within SEMIoTICS
and each partner is responsible to keep that list up to date (see also terms
in [2]). Data recorded in that table will also be used to update information
for the periodic reports in the EC project management web portal.

##  Standards & Regulations

SEMIoTICS has a dedicated task on Standardization (Task 6.3) with resources of
leading industry partners being allocated. This task will use the
“Standardization and Open Source Engagement” namely, AIOTI, W3C, ETSI, IEEE,
ISO as baseline and will continuously refine and update involvement of
SEMIoTICS. Task 6.3 is also used to monitor progress and activities or related
these standardization activities, as well as for creating input for
standardization bodies if possible. More details and a summary on related
standardization activities will be given in the deliverables D6.4 and D6.7.

##  Innovation Assessment

Assessment of SEMIoTICS result will be done on three levels.

  1. Project level objectives: SEMIoTICS has a clear definition of its objectives (see Section 1.1.2. in [1]). These definitions include a description of the objective and the corresponding measures of success. 

  

  2. SEMIoTICS as Research and Innovation Action (RIA) is clearly targeting only lab trials which corresponds to a TRL 4-6 (according to definition by EC) as stated in section 1.3.2 of [1]. 

  

  3. Lab Trial evaluation on technical level is foreseen in WP5 and uses defined requirements and KPIs as a result from respective D2.3 and D5.1 deliverable. 

  

  

In addition, SEMIoTICS also establishes an advisory committee during runtime
in order to get external views and assessment results of the achievements as
well.

#  DATA MANAGEMENT PLAN (DMP)

##  Expected data

SEMIoTICS is a three-year project and will produce a number of technical
results relevant for IoT networks, specifically in WP5. This includes data
created in lab experiments and demos for Wind turbine use case, healthcare use
case and Generic IoT use case. Wind energy use case related data used in
SEMIoTICS will be related to critical infrastructures data and therefore will
not be publicly accessible. For the healthcare use case, there will be no
person-related data which will be generated/stored/transferred by that use
case. Moreover, based on the GA 29.3 Open access to research data "Not
applicable" for SEMIoTICS. Following sections provide detailed description of
the specific data sets in 3 different use cases which will be handled only
within the consortium and the data will be classified as per use case.

##  Data formats and Metadata

###  DATA FORMATS

Following table gives initial version of the data formats in the consortium-
level DMP which will be handled only within the consortium. There are no real-
world field trials in SEMIoTICS’s 3 use cases. The data generated in all the 3
use cases will only be in lab-environment.

Detailed descriptions of the expected information of each cell are given at
the end of this section.  
  
<table>  
<tr>  
<th>

**Data set reference**

</th>  
<th>

**Data set name**

</th>  
<th>

Data Set Description

</th>  
<th>

Standards and metadata

</th>  
<th>

Data sharing

</th>  
<th>

Archiving and preservation (including storage and backup)

</th>  
<th>

Contact Person/ source of data

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

SEMIoTICS_UC1

</td>  
<td>

Test Data

</td>  
<td>

Test Data

</td>  
<td>

NA

</td>  
<td>

confidential

</td>  
<td>

_Link_

</td>  
<td>

Ermin Sakic

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

SEMIoTICS_UC2

</td>  
<td>

Test Data

</td>  
<td>

Test Data

</td>  
<td>

NA

</td>  
<td>

confidential

</td>  
<td>

_Link_

</td>  
<td>

Domenico Presenza

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

SEMIoTICS_UC3

</td>  
<td>

Test Data

</td>  
<td>

Test Data

</td>  
<td>

NA

</td>  
<td>

confidential

</td>  
<td>

_Link_

</td>  
<td>

Mirko Falchetto

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

####  TABLE 6: DATA FORMATS

Note:

This table is linked to file “SEMIoTICS DMP.xlsx”

**_https://overseer1.erlm.siemens.de/repository/Document/downloadWithName/SEMIoTICS%20DMP.xlsx_
** **_?reqCode=downloadWithName &id=12740979 _ **

The following table gives a detailed description of the fields used in the
data formats table of Section 5.2.1.  
  
<table>  
<tr>  
<th>

Data set reference and name

</th>  
<th>

Identifier for the data set to be produced

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

Data set description

</td>  
<td>

Origin (in case it is collected), scale and to whom it could be useful, and
whether it underpins a scientific publication. Information on the existence
(or not) of similar data and the possibilities for integration and reuse.

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

Standards and metadata

</td>  
<td>

Reference to existing suitable standards of the discipline. If these do not
exist, an outline on how and what metadata will be created

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

Data sharing

</td>  
<td>

The dataset cannot be shared publicly as GA 29.3 - Open access to research
data is not applicable to SEMIoTICS

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

Archiving and preservation (including storage and backup)

</td>  
<td>

In general, the procedure described in Section 5 will be applied. This cell
gives a data specific description of the procedures that will be put in place
for longterm preservation of the data (if required).

Indication of how long the data should be preserved, what is its approximated
end volume, what the associated costs are and how these are planned to be
covered (if required).

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

_**TABLE 7: FIELDS USED IN THE DATA FORMATS** _

###  METADATA

SEMIoTICS plans to create and share data in relation to project deliverables
or publications. Deliverables and publications will give all relevant
information, including the meaning of data sets, the methods of data
acquisition/processing, as well as specific methods/algorithms for usage (if
required). Thus, deliverables and publication can be considered as main piece
of metadata for all data sets created within the project.

##  Data sharing and access

Project related documents (release version of document – not raw format) with
dissemination level “public” will be accessible via the project website
_http://www.SEMIoTICS-project.eu_ .

Registration (free of charge) is required to get access. The dissemination
level is initially proposed by the corresponding author and will be reviewed
and approved by PTC and PCC (details see Section 6.2).

As far as possible depending on the publishers’ policy pre-prints of the
publications will be made available open access via the project website, as
well as ARXIV/OpenAIRE or other means. In case embargo periods (e.g., given by
publishers) have to be considered, open access will be given after the embargo
period expires. In particular, an open-access policy is foreseen for all
scientific publications in the context of SEMIoTICS, which is in-line with the
EC open access policy (see:  _https://www.openaire.eu/how-do-i-make-my-
publicationsopen-access-to-comply-with-the-ec-s-open-access-policy_ )  .

##  Data archiving and preservation

All project related documents (raw formats), deliverables, reports,
publications, data, and other artifacts will be stored in a repository
accessible during project duration for all partners. This repository is hosted
(with backup) by the Coordinator and the link is/was distributed at the first
consortium meeting. Access to the repository is given to registered persons
from project partners only. The folder structure of the repository is managed
by the coordinator and changes of the structure need to be coordinated with
the Coordinator. Corresponding partners will keep the above-mentioned
repositories operational during the project lifetime. After project closure,
repositories will be maintained for at least one more year. After project
closure the administrating partner can change access policies (e.g.,
restricted access / access on demand) in order to keep maintenance costs at a
minimum.

The Data Management Plan is maintained by the Project Coordination Committee
(PTC). Although SEMIoTICS is not liable for “Open Access to Research Data” as
Article 29.3 is not applicable to the project, PTC members reviews of the DMP
are a regular agenda item of PTC meetings, conference calls, and work package
(WP) results will be checked with respect to relevant information for the DMP.
The sole purpose of the DMP is how to handle the research data within the
consortium.

WP leads (WP3, WP4 and WP5) are responsible that results of tasks within their
work package are aligned with the definitions in the DMP. WP leads are also
responsible that the table in DMP is updated as soon as data is created within
their WP (for details on the update procedure see Section 7.2). Updates of the
tables in DMP are communicated from the Project Technical Committee (PTC) to
the PCC together with the minutes of the monthly PTC calls (see also section
on update procedures).

In order to ensure that this DMP is implemented and followed, reviews (by PCC
and/or PTC) of all kinds of project related documents (e.g., reports,
deliverables, publications) will include also a check for used data and the
proper documentation and use in-line with this DMP.

In case the contact person for data is leaving the project, the affiliation of
the original contact person will take over the responsibility and will assign
a new contact person.

#  CONCLUSION

This deliverable presented the initial quality management plan of SEMIoTICS
where the different roles and bodies are presented. Moreover, the different
levels of quality controls and assurance are also described. In addition, the
different innovation plans regarding the exploitation plans and innovation,
standards and the innovation management are also detailed. Furthermore, the
data management plan is also provided by analyzing the different expected
data, data formats and sharing strategies, Finally, the deliverable provides,
in the Annex, links on the different procedures followed and the IPR as well
as the PERT diagram with interaction between the Tasks.