#  Data summary

The main objective of the SPICE project is to realize a novel integration
platform that combines photonic, magnetic and electronic components. To align
with the objective of the project, all Partners have been asked to provide
their inputs to this DMP document on what data are going to be collected, in
which format, how they are going to be stored, how they are going to be
deposited after the project and finally what is the estimated size.

Data management is essential for SPICE due to the synergistic approach taken
in this project. In a hierarchical manner, data from each Partner and/or WP
will be required by another Partner and/or WP to build on. For example,
material characterization data from WP1 will be used in the magnetic tunnel
junction design in WP2. These data will also be used in the development of
theoretical models and simulation tools in WP5. All these data will be
required to support the development of an architecture-level simulation and
assessment and an experimental demonstrator in WP4. Since the various WPs are
managed by various Partners, interaction and data exchange is of key
importance. The following main data types and formats are identified,
alongside their origin, expected size and usefulness:

  * Laboratory experimental characterization data will typically be stored in ascii or binary format, in a (multidimensional) array. These include the characterization of magneto-optic materials, magnetic tunnel junction (MTJ) elements, photonic circuits, and the demonstrator. Data _originate_ from laboratory instrumentation, including lasers, optical spectrum analyzers, electrical source meters, thermos-electric control elements, power meters, etc. Data _size_ depends on the resolution, the amount of devices measured, etc., but does typically not exceed the ~1MB level per dataset and the ~TB level overall. The _usefulness_ is the validation and quantification of performance, which in turn can validate models. 

  

  * Simulation data will be stored in simulation-tool specific formats. This includes the QW Atomistix tool, the Verilog tool and the Lumerical tool, for example. Some tools use an open file format, others are proprietary. In all cases, final simulation results can be exported to ascii or binary, if required for communication and documentation. The data _originate_ from running the simulation algorithms, with appropriate design and material parameters. Data _size_ depends, again, on resolution of parameter sweeps, and varies a lot, although is overall not expected to exceed the ~TB level. The _usefulness_ is to provide a quantified background for the design of materials, devices, and circuits, as well as helping with the interpretation and validation of experimental results. 

  

  * Process flows are used to describe the fabrication process in detail, of either material growth/deposition, MTJ fabrication and/or PIC fabrication. These are foundry and toolspecific and are stored in either a text document, e.g., “doc(x)”, – or similar – or a laboratory management tool. These typically _originate_ from a set of process steps, which are toolspecific, e.g., dry etching, wet etching, metal sputtering or evaporation, oxide deposition, etc., and are compiled by process operators and process flow designers. The _size_ is limited to a list of process steps in text, possibly extended with pictures to illustrate the cross-sections, i.e., not exceeding ~10MB per file. The _usefulness_ is to store process knowledge and to identify possible issues when experimental data indicate malfunction. Existing knowledge in processing, including process flows, will be _reused_ . 

  

  * Mask design data are stored in design-tool specific format, but are eventually exported to an open format like “gds”. Their _origin_ depends on how these masks are designed. These can be drawn directly by the designer, or the designer can use a process-design kit (PDK) to use pre-defined building blocks. Data _size_ depends on mask complexity, but typically does not exceed ~100MB per mask set. The _usefulness_ is the identification of structures on a mask, during experimental characterization, also by other Partners and in other WPs, as well as – obviously – providing the necessary input for lithography tools. Together with a mask design, a design report, showing details on the structures and designs and a split chart, should be included. This should also refer to the used process flow. The format is typically text based, e.g., “doc(x)”, and its size does not exceed 10MB. 

  

  * Dissemination and communication data take the form of reports, publications, websites and video, using the typical open formats, like “pdf” and “mpeg”. The _origin_ is the effort of the management and dissemination WPs, i.e., these are written or taped by the consortium Partners. The _usefulness_ is the communication between Partners, between the Consortium and the EC, and with the various target audiences outside the Consortium, including students, peers and general public. 

  

A summary of the data types with SPICE is shown in table 1. More detailed data
description related to the tasks within SPICE are tabulated at the end of this
document.

Table 1. Summary of the data types in SPICE project  
  
<table>  
<tr>  
<th>

**Description of data**

</th>  
<th>

**Responsible organization**

</th>  
<th>

**Type** 1  
</th>  
<th>

**Related WP**

</th>  
<th>

**To whom might it be useful**

**(‘Data utility')?**

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

Mask Design Data

</td>  
<td>

AU & IMEC

(Photonic

Integrated

Circuits) and

CEA (MTJ design)

</td>  
<td>

gdsii

</td>  
<td>

2, 3 and 4

</td>  
<td>

Research

institutes

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

Process flows

</td>  
<td>

CEA & IMEC

</td>  
<td>

docs/ppt

and pdf

</td>  
<td>

1,2, and 3

</td>  
<td>

Research

institutes

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

Simulation data

</td>  
<td>

All

</td>  
<td>

Depending on the

simulation

tools (.scs,

.va, …)

</td>  
<td>

1-5

</td>  
<td>

Research

institutes and companies

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

Software

</td>  
<td>

Synopsys

</td>  
<td>

ATK commercial tools

</td>  
<td>

5

</td>  
<td>

Companies and research institutes

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

Dissemination and communication data

</td>  
<td>

All

</td>  
<td>

pdf,doc,

ppt, mpeg, mp3

</td>  
<td>

all

</td>  
<td>

Public,Companies

and research institutes

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

#  FAIR data

##  Making data findable, including provisions for metadata

Most of the SPICE datasets outlined above are not useful by itself, and depend
on context, i.e., the metadata have to be provided to interpret these data,
possibly by connecting these to other datasets. This is typically done using
logbooks or equivalent. This is necessary for experimental datasets, obtained
in the laboratory. For simulation data, obtained with commercial simulation
tools, the metadata are typically part of the data file, although not directly
visible, unless the file is opened. So, also in that case, a logbook is
required. In general, the SPICE consortium aims to provide accessible
logbooks, design reports or equivalent as a means to make datasets findable
_within_ the Consortium. These logbooks will list all relevant datasets.
Datasets and logbooks will be stored on shared folders (on a server), if
relevant for other Partners. Logbooks will have a version number to allow for
adding datasets.

A typical example is a chip design report, which will include a reference to
the process flow (including version number) and a reference to the mask file,
including a detailed description of the designs, as well as an overview of the
simulations, including, e.g., design curves, and with reference to all
simulation datasets.

To make the datasets SPICE _findable_ , we use the following naming convention
for all the datasets produced within SPICE: the naming starts with the WP
number, then the WT number within the WP and finally the dataset title is
added. These are all separated by underscore, i.e.,
<Beneficiary>_<WP#>_<WT#>_<dataset_title>). For example, if the data is
related to the dataset of WP1 (i.e. Magneto-Optic Interaction) with the WT
number of 2 with the dataset_title of “Magneto-

Optic_Interaction” from the beneficiary RU, then the naming will be
“RU_WP1_2_Magneto_Optic_Interaction”. A version number will be added to the
end of the title if required.

The Consortium recognizes that some data are confidential and cannot be shared
even within the Consortium. This should not prevent communication and
dissemination, though, and measures should be taken to allow for maximum
information flow, while protecting sensitive information. If, for example, the
exact process details of a component on a chip are confidential, some critical
gds layers can be removed from the shared dataset and/or a so-called ‘black
box’ can replace such components. The gds file can then still fulfill its main
purpose, namely the identification of relevant structures on a chip during
experiments.

The main means of communicating datasets _outside_ the Consortium is through
publications, which have a level of completeness as required by typical peer-
reviewed journals. These publications will be findable through the keywords
provided and the publication can be tracked through a digital object
identifier (DOI). If applicable and/or required, full or partial datasets will
be published alongside, as per the journal’s policy.

Specific datasets that will be shared publicly, outside the Consortium, will
have targeted approaches to make these _findable_ . For example, Verilog/spice
models, developed within SPICE, will be uploaded on, e.g., Nano-Engineered
Electronic Device Simulation Node (NEEDS) from nanohub.org, to be found and
used by others. An extensive set of magneto-optic material parameters will be
made available through the SPICE website, including context and introduction.

##  Making data openly accessible

The goal of SPICE is to make as many data and results public as possible.
However, the competitive interest of all Partners need to be taken into
account. The data that will be made _openly available_ are:

  * Reports, studies, slidesets and roadmaps indicated as ‘public’ in the GA. These will be made available through the EC website and the SPICE website, typically in pdf format. Additional dissemination is expected through social media, like LinkedIN, to further attract readership. These documents will be written in such a way that these are ‘self-explanatory’ and can be read as a separate document, i.e., including all relevant details and references. 

  

  * Verilog/spice models of the MTJs can be made available, for example, on NEEDS, including a “readme” file on how to use the models. These models can be used by commercial tools from Cadence/Synopsys, which are available to most of the universities and industry, e.g., through Europractice in Europe. Furthermore, there is a possibility to develop tools running on the nanohub.org server for the provided models. 

  

  * Novel simulation algorithms for the Atomistix toolkit of QW will be made available to the market, through this commercially available toolkit. 

  

  * Scientific results of the project, i.e., in a final stage, will be published through scientific journals and conferences. The format is typically pdf, and an open access publication format will be chosen, i.e., publications will be available from either the publisher’s website (Gold model) or from the SPICE and university websites (Green model). 

  

The data that will remain _closed_ are:

  * Simulation and characterization data sets that are generated in order to obtain major publishable results and deliverables will remain closed for as long as the major results and deliverables have not been published. This is to project the Partners and the Consortium from getting scooped. 

  

  * Detailed process flows and full mask sets will not be disclosed to protect the proprietary and existing fabrication IP of, most notably, partners IMEC and CEA. If successful, SPICE technology can be made available in line with these Partners’ existing business models. IMEC, for example, offers access to its silicon photonics technology through Europractice. 

  

  * Source code of simulation tools developed for the Atomistix toolkit. This is key IP for partner QW, as it brings these tools to the market. 

  

  * Final scientific results that have been submitted to scientific journals, but not yet accepted and/or published. This is a requirement of many journals. 

  

These _closed_ datasets will be kept on secure local servers.

**The homepage of the SPICE will be used for open-access data repository for
SPICE project. The data will kept for 5 years after the project. The budget
will be covered by SPICE project’s budget. The budget is around 500Euro.**

##  Making data interoperable

Open data formats like pdf and doc(x) (reports), gds (mask layout), ascii and
binary (experimental data) will be used as much as possible, which allows for
sharing data with other Partners. Freely available software can be used to
read such files. Design software like Atomistix, Cadence Virtuoso, PhoeniX,
Lumerical and Luceda has proprietary data formats, and it will be investigated
how these can most easily be exported to open formats, in case there is a need
for this.

##  Increase data re-use (through clarifying licences)

Experimental and simulation data sets will in principle not be re-usable by
itself, unless otherwise decided. Re-use of these data sets will be
facilitated through scientific publications, which also provide the necessary
context. Conditions for re-use are then set by the publishers’ policies. The
peer-review process, as well as adhering to academic standards, _ensures the
quality_ . These publications will remain re-usable for an indefinite time.
The underlying experimental and simulation data sets will be stored for a time
as prescribed by national and EU laws, though at least 5 years after the SPICE
project ends.

Process flows can potentially be re-used through the specific foundry
facilities, for example as a fabrication service or through a multi-project
wafer run, e.g., through Europractice. Process flows itself will not be
disclosed and cannot be re-used. This is partially to protect the foundry IP,
and partially because process flows are foundry-specific anyway. The
Consortium will discuss a policy for this when the SPICE technology is up and
running. Quality assurance will be aligned with the foundries’ existing
standards for performance, specifications, yield and reproducibility.

Mask designs, or component designs, can only be re-used when the underlying
fabrication process is made available. In that case, designs can be made part
of a PDK. Support and quality assurance, however, will be an open issue. The
Consortium will discuss this when the SPICE technology is up and running.

Simulation tools based on the Atomistix toolkit will be marketed by QW to
ensure the widest possible re-use, under the assumption that there is enough
market potential. Licenses can be obtained on a commercial base by third
parties. QW will remain responsible for their toolkit development, quality and
support and has a team in place to ensure that. The duration and scope of a
license and support will be determined between QW and their potential users at
a later stage. Simulation tools based on Verilog will be publicly shared for
widest re-use. No support is envisioned beyond the duration of SPICE, though,
so quality assurance is an open issue for the moment.

#  Allocation of resources

In the SPICE project, data management is arranged under WP6 (Dissemination and
Exploitation) and any cost related to the FAIR data management during the
project will be covered by the project budget. The homepage of the SPICE will
be used for open-access data repository; a total budget of 2000 Euro for 5
years is estimated.

The consortium has decided that a specific data manager is not required within
SPICE. In this case, each partner provides the dataset corresponding to the
tasks and the WP to the Dissemination and Exploitation WP leader and these
data will be uploaded for usability by others if applicable.

#  Data security

All data sets are backed up routinely onto the Partners’ servers, via local
network drives. Data sets are backed up on a regular basis, typically on a
daily basis. In addition, all processed data will be version controlled, which
is updated with similar frequency. No backups are stored on laptops, or
external media, nor do we use external services for backup.

The common files will be shared into a depository located under
_https://svn.nfit.au.dk/SPICE_

#  Ethical aspects

No ethical aspects have been identified.

#  Other issues

An open issue is the local, national and EU policies with respect to data
management, and of which the Consortium does not have a complete overview.

#  Appendix – partner input  
  
<table>  
<tr>  
<th>

**WP /**

**Task**

</th>  
<th>

**Responsibl e partner**

</th>  
<th>

**Dataset name**

**(for WT of X)**

</th>  
<th>

**File types**

</th>  
<th>

**Findable**

**(e.g. for WT of 1 for each WP)**

</th>  
<th>

**Accessible**

</th>  
<th>

**Inter oper**

**able**

</th>  
<th>

**Reusable**

</th>  
<th>

**Size**

</th>  
<th>

**Security**

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

1/X

</td>  
<td>

RU

</td>  
<td>

RU_WP1_X_Mag neto_Optic_Intera ction_v1

</td>  
<td>

*.xlsx , *.doc, *.pdf, *.dat, 

*.jpeg 

</td>  
<td>

All the produced data will be available in the dataset with following the
naming of

RU_WP1_1_Magn eto_Optic_Interacti

on_v1 (No meta

data)

</td>  
<td>

Available through scientific reports and publications

</td>  
<td>

N/A

</td>  
<td>

On a

depository server for 5 years after the project

</td>  
<td>

1 TB

</td>  
<td>

Confidential data will be stored and backed up continuously on a secured
server from RU and confidential reports and presentations will be uploaded on
the secured area of the website. Some reports and data will be shared on
Dropbox.

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

2/X

</td>  
<td>

SPINTEC

</td>  
<td>

SPINTEC_WP2_

X_Spintronic - Photonic integration_v1

</td>  
<td>

SEM and

TEM images

(*.jpeg), electrical data (*.xlsx, *.dat, etc.)

</td>  
<td>

SPINTEC_WP2_1_

Spintronic -

Photonic integration_v1 (No meta data)

</td>  
<td>

available through scientific reports and publications

</td>  
<td>

NA

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

500

GB

</td>  
<td>

Confidential data will be stored and backed up continuously on a secured
server at SPINTEC and confidential reports and presentations will be uploaded
on the secured area of the website. Some reports and data will be shared on
Dropbox.

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

3/X

</td>  
<td>

IMEC

</td>  
<td>

IMEC_WP3_X_

Photonic_Distribut ion_Layer_v1

</td>  
<td>

*.dat, *.docx, 

*.pdf 

</td>  
<td>

IMEC_WP3_1_

Photonic_Distributi on_Layer_v1 (No meta data)

</td>  
<td>

available through scientific reports and publications

</td>  
<td>

?

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

500

GB

</td>  
<td>

Confidential data will be stored and backed up continuously on a secured
server at AU and IMEC, and confidential reports and presentations will be
uploaded on the secured area of the website. Some reports and data will be
shared on Dropbox.

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

4/X

</td>  
<td>

AU

</td>  
<td>

AU_WP4_X_

Architecture_and_

Demonstrator_v1

</td>  
<td>

*.dat, *.docx, 

*.pdf, *.m 

</td>  
<td>

AU_WP4_1_

Architecture_and_

Demonstrator_v1

(No meta data)

</td>  
<td>

available through scientific reports and publications

</td>  
<td>

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

1 TB

</td>  
<td>

Confidential data will be stored and backed up continuously on a secured
server at AU and confidential reports and presentations will be uploaded on
the secured area of the website. Some reports and data will be shared on
Dropbox. The Verilog/spice data

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

Page 10 of 11  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

will be shared on some gateways to be used by other people

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

5/X

</td>  
<td>

QW

</td>  
<td>

QW_WP5_X_Sim

ulation_and_Desi gn_Tools_v1

</td>  
<td>

*.doc, *.pdf, *.xlsx, *.py, 

*.hdf5, *.tex 

</td>  
<td>

QW_WP5_1_Simul ation_and_Design_ Tools_v1 (No meta

data)

</td>  
<td>

available through scientific reports and publications

</td>  
<td>

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

1 TB

</td>  
<td>

Confidential data will be stored and backed up continuously on a secured
server at QW and confidential reports and presentations will be uploaded on
the secured area of the website.

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

6/X

</td>  
<td>

AU

</td>  
<td>

AU_WP6_X_Diss emination_and_E xploitation_Tools_ v1

</td>  
<td>

</td>  
<td>

AU_WP6_X_Disse mination_and_Expl oitation_Tools_v1 (No meta data)

</td>  
<td>

Available on the AU website

</td>  
<td>

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

5 GB

</td>  
<td>

The dissemination reports will be kept on a secured server at AU and also
uploaded on SyGMa as well as publicly available on the SPICE website.

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

7/X

</td>  
<td>

AU

</td>  
<td>

AU_WP7_X_Man

agement _v1

</td>  
<td>

*.xlsx , *.doc, *.pdf, *.jpeg, *.mp3, *.mpeg 
</td>  
<td>

AU_WP7_1_Mana gement _v1 (No

meta data)

</td>  
<td>

The confidential data will not be accessible to the public. The public data,
reports, presentations will be available on AU website.

</td>  
<td>

</td>  
<td>

On a

depository server (TBD) for 5 years after the project

</td>  
<td>

100

MB

</td>  
<td>

The annual reports will be confidential and so will not be available for
public. Some minutes, presentations, press release etc. will be available for
public through website.

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

Page 11 of 11