#  1 Introduction

##  1.1 About PICs4All

PICS4All is a project in support of a European network of excellence in
Photonic Integrated Circuit (PIC) technology, having the task to bring this
technology to a broad European community of potential applicants of the PIC-
technology being SMEs, large companies and research institutes. Dissemination,
communication and outreach are the pivotal activities of the PICs4All project,
since these are the essential first steps in bringing the knowledge of the
PICS4All Application Support Centers and the photonic IC-community to such
parties for application of the technology in their products or use it for
further research and development:

To enable know-how sharing, the PICs4All Coordination and Support Action has
set up a European Network of experts in photonics comprising nine so called
Application Support Centres (ASCs) distributed around Europe, whose main task
is to stimulate the development of novel applications based on PICs for
various application fields and enhance the cooperation between universities
and other research centres, technology clusters and industry. The ASCs provide
such parties access to the advanced PIC technology.

The PICs4All experts offer their knowledge and hands-on support to academia,
research institutes, SMEs and larger companies to:

  1. assess whether their ideas or products can be better realized using PICs; 

  

  2. determine whether the application of PICs is economically viable in their products; and 

  

  3. access PIC design, manufacturing and evaluation facilities. 

  

  

In this way, PICs4All aims to increase the impact of integrated photonics by
bridging the gap between technology and market. The PIC development cycle, as
presented in Figure 1, is supported entirely by the expertise of PICs4All
ASCs.

**Figure**

**1**

**PIC development cycle supported by the PICs4All consortium.**

Actions of PICs4All also aim on bringing together the PIC value chain for
Europe’s key players in the field of photonic integration, including
manufacturing and packaging partners, photonic CAD software partners, R&D labs
and PIC design houses. Currently a gap exists between understanding the
technology (its capabilities and potential) and market – industrial demands.
ASCs will bridge this gap between potential users, especially those who have
limited knowledge of PICs and PIC technology, and the community of PIC-
specialized parties. As such ASCs act as PICtechnology ambassadors in their
local/regional network, supporting dissemination and outreach which are so
pivotal in seeking of new connections.

Apart from this support action, within PICS4All the effectiveness of this
support action is being studied as a separate item within the project. The
main question here is whether the knowledge gap between specialists on PIC-
technology, currently largely concentrated in academia like the organizations
hosting the PICS4All ASCs and an increasing amount of companies active in
designing, manufacturing and testing PICs and user organizations who are less
familiar with PIC-technology can indeed be bridged by initiatives like
PICS4All.

#  2 Clusters of activities and the related management of data

Within the PICS4All project in effect three types of activities are carried
out, each have their own characteristics concerning data generation,
preservation and accessibility. These clusters are:

  * support activities in which aid is offered to (potential) users of PIC-technology. 

  

These activities can comprise o technical and economic feasibility
assessments, early support in concept design (and for a limited amount of
cases: actual PIC-design);

  * testing and evaluation of PIC-prototypes and subsequently advice on potential improvements and application boundaries; 

  

  * advice in finding the right support in the PIC-creation and application process by third parties (e.g. design houses, PIC-foundries, PIC-packaging manufacturers and packagers and PIC test facilities) when required. 

  

  * a study for the effectiveness of the PICS4All approach in the product innovation process entered by PIC-users 

  

  * documents generated within the project in the context of enabling and managing the PICS4All project. 

  

In the next section a more extensive description of data management structures
as applied within these separate clusters of activities are provided.

##  2.1 Support activities

###  2.1.1 _Scope_

The key activities of the PICS4All ASCs are directed at supporting potential
applicants of PIC-technology in innovative new products, or for the use in
further applied or scientific research in various technical and scientific
fields. PIC-technology, although it basic principles exist for over 30 years,
has always been of subordinate interest as compared to (silicon) electronic
integrated circuits due to the complexity of manipulating photons.
Additionally, electronic IC-technology has evolved during the last 4 or 5
decades at an enormous pace pushed by Moore’s law of ever increasing capacity
of electronic IC’s; virtually all problems could be solved using electronic
IC’s. However, recently PIC’s have shown profound advantages in various areas
of technology as compared to electronic IC’s in terms of energy efficiency,
operation speed and functionality. These advantages have boosted, and will
keep boosting, the use of PIC’s in new applications. Clear advantages of the
use of photons instead of electrons have been shown in telecom and sensing
applications in particular.

However, many more applications (even unknown applications) could strongly
benefit from using photonic IC’s additionally to or instead of electronic
IC’s. PICS4All supports applicants who are not familiar with this technology
in the technical and economical assessment, design, manufacturing and
evaluation of PICs and PICapplications.

The basic idea of PIC-based applications can be provided by the user, but also
as a consequence of a discussion between PICS4All ASCs and users by
elaborating the technical opportunities of PIC’s, eg. in the course of solving
a particular problem. However, the basic idea or problem is proprietary to the
potential applicant, the client. For as yet, in many cases customers have a
distinct idea of the application and the underlying technology.

####  2.1.2 Data management characteristics

As a consequence, in order to provide an attractive proposition to potential
applicants and to protect the commercial interests of the client, the ASCs are
bound to a Non-Disclosure Agreement (NDA) concluded with their clients. This
NDA comprises a confidentiality clause, stating .. _’not to disclose
Confidential Information to any third party without the prior written consent
by the Disclosing Party’._

Since the daily practice up to now is that all information exchanged between
ASCs and their clients is designated as ‘Confidential’ due to (potential) IPR-
issues, the data generated by ASCs within a consulting trajectory are not
accessible to outside parties.

The current practice of ASCs is to process data generated in design and
evaluation into PIC-designs and PIC-evaluation reports, possibly resulting in
re-designs. In this way new products or components essential to new products
are devised which, in principle, are proprietary to the clients.

The ASCs however are prepared to disseminate information on new phenomena or
basic principles as encountered in their consulting trajectories to the public
domain whenever possible and allowed. The most appropriate method is to
publish relevant results in scientific articles, conference proceedings or
educational courses on PICtechnology; as university based entities, the ASCs
have ample experience in using these channels for technical information
dissemination.

Currently, the raw data generated within each consultancy trajectory are
stored at computers of the ASCs. In general, these data are also preserved at
central server facilities, where they are backed-up. Of all ASC’s the data are
not stored in any public depository. An overview of the data file typology,
metadata and application software necessary to read and interpret the data
files of the ASCs is provided in chapter 4\.

##  2.2 Effectiveness study

###  2.2.1 _Scope_

An important question to the principal of the PICS4All Coordination and
Support Action, the European Commission, and of scientific relevance is
whether activities as performed within PICS4All are effective in the creation
of new innovative products and other opportunities which have a commercial or
scientific impact. To this end the _Innovation, Technology, Entrepreneurship &
Marketing (ITEM) group _ of the coordinator TU/e is conducting a study after
this effectiveness. One of the main specialities of the ITEM-group is the
generation of understanding of the various aspects involved in ‘Technology
commercialization, incubators, and university knowledge transfer’. The global
approach of the study is based on two activities:

  1. Study of the numerical aspects of PICS4All activities, e.g. the amount of clients which were contacted by ASCs, who took the initiative, how clients became aware of the services of ASCs, how many contacts responded positively to offerings of consultancy by ASCs, etc. etc. These data are periodically analysed to track the progress of the support activities and to reveal trends and patterns in support activities that have proven to be particularly (in)efficient. Findings will be reported in the deliverables. 

  

  2. Interviews with contacted parties and clients in order to reveal motivations of contacts to accept or decline any offerings of consultancy and support, the rate of success of such support, the level of appreciation by the client of the help provided by ASCs, potential ways to improve support, etc. etc. These data serves to better understand the dynamics and effects of the support processes including challenges and best practices from an ASC and client perspective. The data will be analysed using qualitative analysis techniques such as coding, to reveal underlying dynamics of the support processes as well as common challenges and best practices. Since this data consists of highly confidential, sensitive information, reporting will mainly include aggregate, anonymized findings. 

  

  

####  2.2.2 Data management characteristics

The information needed to carry out the first activity is collected by the
ASCs in the ZOHO Project Registration System. Every contact made by ASCs with
potentially interested parties is registered in a Client/Project database.
This database is created using the cloud based on the ZOHO Customer Relations
Management tool. Details of this tool can be found in _Deliverable 5.2
‘Project Registration System’_ .

The complexity of the raw data supporting this part of the study is limited.
An example of a first result can be found in Deliverable 4.1 _‘Yearly summary
report on outreach activities and their impact on new users and application
market’._ In this report, the relevant raw data underpinning the conclusions
are provided. Currently, no unaided access to the ZOHO database can be
provided to outside parties due to:

  * licensing issues; every user needs a separate license in order to use ZOHO; 

  

  * confidentiality wrt. to the contents of the ZOHO database. Especially when a consultancy trajectory is entered, the ZOHO database also contains information about the basic product/component idea of the client, approach chosen, potential solutions, etc. This information is subject to the NDA concluded between ASCs and their clients and therefore not open to third parties. 

  

The raw data of the questionnaires filled in by or interview held with
contacts and clients are currently kept in the form of text files at the TU/e
servers. TU/e does not have an approved data handling policy yet (this is
worked on) but does have a code of conduct containing some data management
elements  1  . Since this data consists of confidential, sensitive information
– which can only be interpreted in the context of the actual interviews that
took place - data will not be made public and reporting will be based on
aggregate, anonymized findings.

##  2.3 Project Management Data

###  2.3.1 _Scope_

Within the course of the PICS4All project, several types of documents are
created in support of the management and reporting of the project’s
activities:

 Project Internal Documents:

  * minutes of WP-leaders meetings and telcos 

  

  * minutes of Progress Meetings and attendance registers o internal communication of PL to Steering Committee  Project External Documents: 

  

  * Deliverables and Progress Reports o All kinds of PR-materials, Project Presentations, etc. 

  

####  2.3.2 Data management characteristics

A copy of the abovementioned documents are stored at a file exchange facility
(folder) hosted by the Project Office (Berenschot). All files are accessible
to all partners. The documents which are intended for public use are, when
appropriate, available through the project’s website (
_www.pics4all.jeppix.eu_ )  . The underlying raw data (mostly handwritten
notes or draft versions) are not kept when they have no additional value; e.g.
handwritten notes are generally not legible to others than the writer, draft
versions contain mistakes, remarks, etc. which are not relevant to any party
when the final version is complete.

For this reason, no facility to make raw data on project management documents
accessible to third parties are used or considered.

#  3 Conclusions

This report provides an overview of the various types of data as generated
within the PICS4All project. In summary:

  * support activities: various types of data are generated. The data are stored for future reference at the PC’s and backup servers of the institutes hosting the ASCs. At this moment these data are not stored on publicly accessible data repositories for two reasons: 

    * external data storage in an accessible form is not in the policy of the institutes involved; 

  

    * the data concerning support activities are subject to Non-disclosure 

  

  

Agreements with clients since they might contain IPR-sensitive material.

  * Effectiveness study: data generated within the study for the effectiveness of the PICS4All CSA in knowledge transfer and creation of new market or scientific innovations are collected and stored at the PC’s and servers of the TU/e. It will be considered at a later stage which data should be stored and archived in which type of data archive/repository and with which degree of openness. Since the majority of our data are subject to NDAs and IPR, careful selection and appraisal of the data (and the possible mode of storage/archiving) is required. Whenever beneficial, a change in data management policy is considered. 

  

  * Project management: no raw data underlying to the publicly accessible documents are relevant or available for storage in some kind of publicly accessible data repository. 

  

The currently reported status of data and data management does not preclude a
(partly) different approach in the future. The PICS4All consortium appreciates
the relevance of open data access, although it has opted-out of participation
in the Open Data Pilot as promoted by the EU. During the course of the
project, open access to data and structures to enable open data access will be
considered and applied when not intervening with the IPR-interests of the
participating parties.

#  4 Appendix; data formats, metadata and data processing tools used by ASCs

In this Appendix, an overview per ASC is given of data, file types, required
application programs to read the files and other relevant information on data
preservation are provided. This data mainly concerns data generated in the
course of a support activity (cf. section 2.1) and therefore is not open to
public publication.

Currently, the raw data are stored at the computers or servers in accordance
with the data preservation and storage policies of the various institutes
hosting the ASCs.

The available data and data formats of Milan, Cambridge and Paris have not
been provided yet.

##  4.1 Aarhus University  
  
<table>  
<tr>  
<th>

**Data set reference / name**

</th>  
<th>

**Dataset description / goal of the data**

</th>  
<th>

**Standards and metadata incl. required software**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Way of archiving (incl. storage and back-up)**

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

</th>  
<th>

freely accessible?

</th>  
<th>

Is sharing of data between project partners possible/useful/carried out?

</th>  
<th>

Is sharing with external parties possible/useful/carried out?

</th>  
<th>

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

</th>  
<th>

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

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

ZOHO database

</td>  
<td>

Client data (company name, contact persons, address), project data (questions,
ideas and concepts, project progress).

</td>  
<td>

Zoho CRM software

</td>  
<td>

No

</td>  
<td>

Yes, data is shared. Most importantly the company name and contact person.
Secondly the

most promising fields/applications are identified.

</td>  
<td>

Project data is not shared when explicitly prohibited by bilateral

NDA.

</td>  
<td>

.

</td>  
<td>

No, sharing company/person data is not considered relevant. Data on support
projects is subject to NDA and thus not shared.

</td>  
<td>

Backup automatically taken care of by cloudbased ZOHO application.

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

Personal contact database

</td>  
<td>

Overview and history of all potential users that have bene contacted and/or
will be contacted.

</td>  
<td>

The datasets are stored in an Excel database

(personal logbook)

</td>  
<td>

Excel reader software is freely accessible.

</td>  
<td>

Data can be shared based on a per-case basis, though not the full database at
once.

</td>  
<td>

</td>  
<td>

</td>  
<td>

Data sharing in data repository is at this stage not considered, the large
majority of the data cannot be disclosed because of

</td>  
<td>

AU backup server.

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

Feasibility studies

</td>  
<td>

Feasibility studies contain conceptual ideas but, sometimes, also quantified
simulations. These studies can also take the form of actual grant proposals.

</td>  
<td>

These reports are typically compiled into a textbased document, for
readability. Raw datasets could be produced too.

</td>  
<td>

Documents are typically in pdf or doc format. Raw datasets can be in ascii or
binary, and are ofton only - or most conveniently - accisible through the
software in which it was generated. These packages can be very expensive, and
the data are hence not freely accessible.

</td>  
<td>

Yes, on a per-case basis. (Potential) IP needs to be addressed, as feasibility
studies might contain novel ideas.

</td>  
<td>

</td>  
<td>

</td>  
<td>

No, unless in the form of an official report or publication. Novel and
concepts will remain confidential and will not be shared..

</td>  
<td>

AU backup server.

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

##  4.2 National Technical University of Athens  
  
<table>  
<tr>  
<th>

**Data set reference / name**

</th>  
<th>

**Dataset description / goal of the data**

</th>  
<th>

**Standards and metadata incl. required software**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Way of archiving (incl. storage and back-up)**

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

</th>  
<th>

freely accessible?

</th>  
<th>

Is sharing of data between project partners possible/useful/carried out?

</th>  
<th>

Is sharing with external parties possible/useful/carried out?

</th>  
<th>

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

</th>  
<th>

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

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

Mask Engineer Data Files

</td>  
<td>

Script files used to prepare and generate mask layout files. The script files
are processed using the Phoenix Software compiler in order to convert them
into mask layout files (gds)

</td>  
<td>

The file format is .spt and the software needed to execute them is Phoenix
MaskEngineer Software. Simple visualization of the files can be done using a
text editor.

</td>  
<td>

No

</td>  
<td>

Sharing of data between project partners is possible and useful. It can be
readily done either by e-mail or through NTUA's ftp server

</td>  
<td>

</td>  
<td>

Sharing of data with external parties is possible if the data is not protected
by NDA with the respective customer. It can be readily done either by e-mail
or through

</td>  
<td>

</td>  
<td>

The data are permanently stored in NTUA servers, while they are regularly
backed-up in order to ensure prolongued preservation and protection against
mistakes or malicious actions.

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

OptoDesigner Data Files

</td>  
<td>

Script files used to perform mode (FMM, FD) and propagation simulations (BPM,
BEP, FDTD). The script files are processed using the Phoenix Software compiler
in order to run the parameterize, run the simulation engine and organize and
save the respective results.

</td>  
<td>

The file format is .spt and the software needed to execute them is Phoenix
MaskEngineer Software. Simple visualization of the files can be done using a
text editor while the results are saved either in .txt or .bmp format.

</td>  
<td>

No

</td>  
<td>

Sharing of data between project partners is possible and useful. It can be
readily done either by e-mail or through NTUA's ftp server

</td>  
<td>

</td>  
<td>

Sharing of data with external parties is possible if the data is not protected
by NDA with the respective customer. It can be readily done either by e-mail
or through

NTUA's ftp server

</td>  
<td>

</td>  
<td>

The data are permanently stored in NTUA servers, while they are regularly
backed-up in order to ensure prolongued preservation and protection against
mistakes or malicious actions.

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

ASPIC Data Files

</td>  
<td>

Data files used to perfrom circuit level simulation on integrated photonic
circuits. The files are used to view, edit and simulate the desired
structures, as well as save and access the simulation results.

</td>  
<td>

The file format is .apc and the software needed to execute them is ASPIC
Filarete. The results can be saved in either .txt, .mat or .csv format.

</td>  
<td>

No

</td>  
<td>

Sharing of data between project partners is possible and useful. It can be
readily done either by e-mail or through NTUA's ftp server

</td>  
<td>

</td>  
<td>

Sharing of data with external parties is possible if the data is not protected
by NDA with the respective customer. It can be readily done either by e-mail
or through

</td>  
<td>

</td>  
<td>

The data are permanently stored in NTUA servers, while they are regularly
backed-up in order to ensure prolongued preservation and protection against
mistakes or malicious actions.

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

Lumerical FDTD Data Files

</td>  
<td>

Data files used to perfrorm 2D and 3D FDTD simulations of photonic structures.
The files are used to view edit and simulate the desired structures, as well
as save and access the simulation results. Furthermore, since the software
offers a scripting environment, script files can be also developed and
executed.

</td>  
<td>

The file format of the layout and the script files is .fsp and .lsf
respectively, while the software needed to execute them is Lumerical 3D-FDTD
Software. The results can be saved in either .txt or .csv format.

</td>  
<td>

No

</td>  
<td>

Sharing of data between project partners is possible and useful. It can be
readily done either by e-mail or through NTUA's ftp server

</td>  
<td>

</td>  
<td>

Sharing of data with external parties is possible if the data is not protected
by NDA with the respective customer. It can be readily done either by e-mail
or through

NTUA's ftp server

</td>  
<td>

</td>  
<td>

The data are permanently stored in NTUA servers, while they are regularly
backed-up in order to ensure prolongued preservation and protection against
mistakes or malicious actions.

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

Lumerical MODE Solutions Data

Files

</td>  
<td>

Data files used to perfrorm 2D and 3D-EigenMode Expansion simulations of
photonic structures. The files are used to view edit and simulate the desired
structures, as well as save and access the simulation results. Furthermore,
since the software offers a scripting environment, script files can be also
developed and executed.

</td>  
<td>

The file format of the layout and the script files is .lms and .lsf
respectively, while the software needed to execute them is Lumerical MODE
Solutions Software. The results can be saved in either .txt or .csv format.

</td>  
<td>

</td>  
<td>

Sharing of data between project partners is possible and useful. It can be
readily done either by e-mail or through NTUA's ftp server

</td>  
<td>

</td>  
<td>

Sharing of data with external parties is possible if the data is not protected
by NDA with the respective customer. It can be readily done either by e-mail
or through

NTUA's ftp server

</td>  
<td>

</td>  
<td>

The data are permanently stored in NTUA servers, while they are regularly
backed-up in order to ensure prolongued preservation and protection against
mistakes or malicious actions.

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

##  4.3 Technical University of Berlin  
  
<table>  
<tr>  
<th>

**Data set reference / name**

</th>  
<th>

**Dataset description / goal of the data**

</th>  
<th>

**Standards and metadata incl. required software**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Way of archiving (incl. storage and back-up)**

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

</th>  
<th>

freely accessible?

</th>  
<th>

Is sharing of data between project partners possible/useful/carried out?

</th>  
<th>

Is sharing with external parties possible/useful/carried out?

</th>  
<th>

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

</th>  
<th>

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

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

Measurement Data

</td>  
<td>

Data generated in characterization of PICs

</td>  
<td>

Textfiles, hdf5 files

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

TUB Internal backup system

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

Simulation Data

</td>  
<td>

Rough data generated by/serving as a data file for PIC-simulation programmes.

</td>  
<td>

Textfiles, hdf5 files

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

TUB Internal backup system

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

Layout Data

</td>  
<td>

Rough data generated by/serving as a data file for PIC-design and layout
programmes.

</td>  
<td>

Textfiles, GDSII files

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

</td>  
<td>

Confidential with client

</td>  
<td>

TUB Internal backup system

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

ZOHO Questionaire

</td>  
<td>

Client data (company name, contact persons, address), project data (questions,
ideas and concepts, project progress).

</td>  
<td>

HTML

</td>  
<td>

yes

</td>  
<td>

ZOHO System

</td>  
<td>

</td>  
<td>

</td>  
<td>

ZOHO contains confidential information

</td>  
<td>

Stored online in a cloud facility.

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

Conference Talks, Posters

</td>  
<td>

Elaborated data meant for publishing

</td>  
<td>

PDF

</td>  
<td>

yes

</td>  
<td>

Published via conference proceedings

</td>  
<td>

</td>  
<td>

Published via conference proceedings

</td>  
<td>

</td>  
<td>

TUB Internal backup system

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

##  4.4 Eindhoven University of Technology  
  
<table>  
<tr>  
<th>

**Data set reference / name**

</th>  
<th>

**Dataset description / goal of the data**

</th>  
<th>

**Standards and metadata incl. required software**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Way of archiving (incl. storage and back-up)**

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

</th>  
<th>

freely accessible?

</th>  
<th>

Is sharing of data between project partners possible/useful/carried out?

</th>  
<th>

Is sharing with external parties possible/useful/carried out?

</th>  
<th>

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

</th>  
<th>

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

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

PICs4All project documentation

</td>  
<td>

Project minutes, deliverables, milestones, communication kit, promotional
materials

</td>  
<td>

text, pdf, presentation, mail

</td>  
<td>

yes

</td>  
<td>

Yes, it is essential. Berenschot server is used.

</td>  
<td>

</td>  
<td>

Part of the documents are shared using public PICs4All website or

</td>  
<td>

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

ZOHO database

</td>  
<td>

Database of scouted insitutions; keep track of the ASC activities

</td>  
<td>

</td>  
<td>

</td>  
<td>

Yes, database is shared among ASCs.

Each ASC has an account to ZOHO system.

</td>  
<td>

</td>  
<td>

distributed via mailing.

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Cloud based software and data file.

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

Techno-economic feasibility

</td>  
<td>

Conceptualization of ideas and assesment of using PICs

</td>  
<td>

text, pdf, presentation, mail, spreadsheet

</td>  
<td>

yes

</td>  
<td>

Yes, case-by-case scenario, as exchange of the confidential information is an
issue. Sharing of the information shall be approved by parties involved.

</td>  
<td>

</td>  
<td>

Sharing is possible, after approval of the parties, but unlikely to happen (IP
issues). Most likely in the form of summary for formal deliverable reports.

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

Simulation data

</td>  
<td>

System/device performance assesment

</td>  
<td>

simulation files, presentation, images

</td>  
<td>

yes (simulation software might be required)

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

PIC layout

</td>  
<td>

Device layout ready for fabrication

</td>  
<td>

gds/cif file; scripting languange file

</td>  
<td>

yes (PIC layout software might be required)

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

Measurements data

</td>  
<td>

Funcionality and device operation assesment

</td>  
<td>

txt, pdf, combined into report - pdf or presentation

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

Application notes

</td>  
<td>

Application notes that origin from the successful PIC implementation

</td>  
<td>

text, pdf

</td>  
<td>

yes

</td>  
<td>

Yes. To share examples and experience.

</td>  
<td>

</td>  
<td>

Yes. By publishing on the PICs4All website and consortium partners website;
realesing via newsletter.

</td>  
<td>

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

Database of potential users

</td>  
<td>

Database with contact information for outreach and scouting purpose

</td>  
<td>

spreadsheet

</td>  
<td>

yes

</td>  
<td>

On requrest.

</td>  
<td>

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will likely not allow

data sharing because of confidentiality issues.

</td>  
<td>

Backup on local PC, backup on TU/e shared drive

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

##  4.5 Universitat Politècnica de València  
  
<table>  
<tr>  
<th>

**Data set reference / name**

</th>  
<th>

**Dataset description / goal of the data**

</th>  
<th>

**Standards and metadata incl. required software**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Way of archiving (incl. storage and back-up)**

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

</th>  
<th>

freely accessible?

</th>  
<th>

Is sharing of data between project partners possible/useful/carried out?

</th>  
<th>

Is sharing with external parties possible/useful/carried out?

</th>  
<th>

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

</th>  
<th>

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

If yes, how can / is this be done?

</th>  
<th>

If no, why not?

</th>  
<th>

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

PICs Application examples

</td>  
<td>

List of applications examples where PICs can be used. This will be used to
aware potential users about PIC technololgy on their area of study or business

</td>  
<td>

application examples at areas of study/business (.doc, . Ppt, microsoft word

and powerpoint or compatible programmes)

</td>  
<td>

Yes

</td>  
<td>

e-mail, project internal document directory (Acronis) hosted by Berenschot

</td>  
<td>

</td>  
<td>

Through presentations, e-mails, conference papers, social networks,…

</td>  
<td>

</td>  
<td>

This documentation could be stored on a folder at the exchange directory in
Acronis

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

platform capabilities

</td>  
<td>

This data describes the main features and performances from different
technology platforms and will help determining the platform to be used to
reach user's application requirements

</td>  
<td>

losses, wavelengths, bandwidths, resolution, dimensions,…(.xls,

microsoft excel or compatible programmes)

</td>  
<td>

Yes

</td>  
<td>

e-mail, project internal document directory (Acronis) hosted by Berenschot

</td>  
<td>

</td>  
<td>

Through presentations, e-mails, conference papers, social networks,…

</td>  
<td>

</td>  
<td>

They are included in presentations in Acronis

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

Fabrication costs for different fab platforms

</td>  
<td>

This will help users to evaluate the techno-economic feasibility to turn their
application into a PIC.

</td>  
<td>

volumes, chip dimensions, technology platforms,… (.xls, microsoft excel or

compatible programmes)

</td>  
<td>

Yes

</td>  
<td>

e-mail, project internal document directory (Acronis) hosted by Berenschot

</td>  
<td>

</td>  
<td>

Through presentations, e-mails, conference papers, social networks,…

</td>  
<td>

</td>  
<td>

They are included in presentations in Acronis

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

Potential users database

</td>  
<td>

Companies and organizations are included in this database as potential users
of PIC's technology in order to be scouted during the project

</td>  
<td>

company/organization name, location, area of study/business, website,
email…(.xls, microsoft excel

or compatible programmes)

</td>  
<td>

No

</td>  
<td>

Shared on the project internal document directory (Acronis) hosted by
Berenschot

</td>  
<td>

</td>  
<td>

</td>  
<td>

Confidential information

</td>  
<td>

Stored on the computers from the ASCs

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

Applications of scouted users

</td>  
<td>

to help us determining the techno-economic feasibility upon user
requirements/capalilities

</td>  
<td>

new or existing, area of interest…(.doc, microsoft word or compatible
programmes)

</td>  
<td>

No

</td>  
<td>

depends on the user

</td>  
<td>

Confidential information

</td>  
<td>

</td>  
<td>

probably they want to avoid sharing them

</td>  
<td>

Stored on the computers from the ASCs

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

technical skills of users

</td>  
<td>

to evaluate if user can proceed by itself or need support

</td>  
<td>

modelling and simulation, design, packaging, characterization

</td>  
<td>

No

</td>  
<td>

depends on the user

</td>  
<td>

</td>  
<td>

depends on the user

</td>  
<td>

</td>  
<td>

Stored on the computers from the ASCs

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

database with agents of PIC's value chain

</td>  
<td>

this database contains the name of the different agents concerning the PIC
value chain in order to redirect the users if needed upon their application
requirements and skills

</td>  
<td>

company name, location, area of study/business,…

(.xls, microsoft excel or

compatible programmes)

</td>  
<td>

yes

</td>  
<td>

e-mail, Acronis

</td>  
<td>

</td>  
<td>

e-mail, presentations, social networks,…

</td>  
<td>

</td>  
<td>

Acronis

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

User's details obtained through PICs4All website

</td>  
<td>

A contact details file is generated from users that download the techno-
economic template from the PICs4All website. It is used to scout the user in a
near future.

</td>  
<td>

company name, location, area of study/business,…

(.txt generated automatically, microsoft word or compatible programmes)

</td>  
<td>

No

</td>  
<td>

This information is shared between project coordinator and WP3 leader and
Spanish ASC-representative responsible for the website.

</td>  
<td>

Confidential information

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will most likely not allow sharing of their data because of

</td>  
<td>

The generated file is stored on a private folder at the website server. It is
also sent to several e-mail addresses to notify a new interest on a PIC
development. The back-up is performed at the same time as the website back-up

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

NDA between ASC and organization / end-user

</td>  
<td>

It will contain the terms of the NDA between a given user and the ASCs
concerning to the user's application.

</td>  
<td>

(.doc, microsoft word or compatible programmes)

</td>  
<td>

No

</td>  
<td>

the possibility of sharing depends on the user (confidential information)

</td>  
<td>

Confidential information

</td>  
<td>

</td>  
<td>

This document doesn't concern third parties, confidential information

</td>  
<td>

All the documentation concerning a given company/organization will be stored
on a folder named with the company/organization

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

User's application techno-economic study

</td>  
<td>

This data considers the technical and economical features of the application
requirements and it will be used to take a decission wether continue with the
integration or not.

</td>  
<td>

technical and economical features (.xls, microsoft

excel or compatible programmes)

</td>  
<td>

No

</td>  
<td>

the possibility of sharing depends on the user (confidential information)

</td>  
<td>

Confidential information

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will most

</td>  
<td>

All the documentation concerning a given company/organization will be stored
on a folder named with the company/organization name.

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

user's application design

</td>  
<td>

In some cases ASCs will help users on design's development of the application:
PIC Layout, characterization setup, packaging design.

</td>  
<td>

models and simulations, layouts, characterization setup designs, packaging
designs. (Phoenix, VPI, Lumerical software,

Filarete, Photon design,

Luceda Photonics, …)

</td>  
<td>

No

</td>  
<td>

the possibility of sharing depends on the user (confidential information)

</td>  
<td>

Confidential information

</td>  
<td>

</td>  
<td>

Data sharing is dependent on the user/client’s approval. Most users/clients
will most likely not allow sharing of their data because of
confidentiality/NDA issues.

</td>  
<td>

All the documentation concerning a given company/organization will be stored
on a folder named with the company/organization name.

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

PICs characterization measurements

</td>  
<td>

Here are included the characterization mesurements performed on the fabricated
PIC, used to validate the user's application requirements.

</td>  
<td>

characterization measurements (.doc)

</td>  
<td>

No

</td>  
<td>

</td>  
<td>

Probably, users want to keep them initially private

</td>  
<td>

</td>  
<td>

Probably, users want to keep them initially private.

</td>  
<td>

All the documentation concerning a given company/organization will be stored
on a folder named with the company/organization

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

Events contribution

</td>  
<td>

This data considers the papers and documentation published by the partners in
different events: workshops, conferences,...

</td>  
<td>

</td>  
<td>

Yes

</td>  
<td>

e-mail, project internal document directory (Acronis) hosted by Berenschot

</td>  
<td>

</td>  
<td>

E-mails, presentations, papers,…

</td>  
<td>

</td>  
<td>

This information is supposed to be published at conferences, whorkshops,… and
also it is saved on Berenschot server, of which

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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