#  Long term preservation plan

Retained documents will be stored for at least 10 years. The long term
preservation plan needs to be decided by the end of this project.

#  Sharing policy

Deliverables and milestone documents are openly shared, unless specifically
determined to be confidential. The stored project documents such as tendering
documents, manufacturing contracts, etc., are shared with EISCAT associates.
The archive emails are not shared.

#  Responsible person

Deliverables, milestone documents and other general project documents are
prepared and managed by Dr. Sathyaveer Prasad from EISCAT Scientific
Association.

#  Resources used

The resources of EISCAT Scientific Association such as the project website,
the project staff are used to some extent in this project. This project also
plans to hire employees within this project and thus, to establish project
office for implementing the EISCAT_3D system.

**2\. ENGINEERING LEVEL SOFTWARE**

#  Data Collected

A low level engineering software will be developed to operate and control the
sub-array, process the data from individual antennas and generate the phased-
array data products. The developed software will be as similar as possible to
that to be used for EISCAT_3D system. This software is considered data in the
general sense in this document.

#  Collection method

The data collection will be done during the project and mostly in work package
(WP) 5 of this project. The data (software codes) are collected using web-
based systems.

**Metadata and documentation**

Documented by in-line comments and documentation principles of each IT partner
in question.

**Ethical and privacy issues**

None

#  IPR issues

All produced software will stay as the ownership of the EISCAT scientific
association. However, it has to be licensed using an open software license, as
described in the grant agreement.

**Storage and backup project time**

A computer will be used for storage with a regular internal backup system.

#  Access management

The developed software can be openly accessed by project staff and EISCAT
associates via project website whereas a controlled access will be provided to
the outside users. However, the access practicalities depend on the software
platform.

#  Retention and preservation

Draft and final versions of the developed software codes are stored and
preserved for usage in the EISCAT_3D system.

#  Long term preservation plan

A method will be defined by the end of this project for long term preservation
of the developed software.

**Sharing policy**

All the final versions of the developed software products will be shared
publicly.

#  Responsible persons

Software engineer is responsible on version control, documentation and initial
storage. Chief engineer is responsible for the overall software produced in
the WP5 of this project and to control that the final versions are made
available.

#  Resources used

Project staff and other resources (computers, software and hardware) from
EISCAT scientific association will be used to develop the software products.

**3\. SUB-ARRAY TEST DATA**

The testing of the sub-array will produce low-level data product of the
digitized signal voltages and it is comparable to the data products at the
beginning of the scientific data chains used by incoherent scatter radar
facilities around the world. Hence, the data processing and storage
requirements of this project are much less compared to the full EISCAT_3D
system.

#  Data Collected

Data sets collected from sub-array testing and system calibration are of only
engineering interest, and do not have much additional value.

#  Collection method

The data is collected by performing internal interference testing of various
subsystems and radar system performance testing. A detailed test data
collection method will be defined during the WP6 of this project.

#  Metadata and documentation

The local metadata i.e. the results of the subsystem tests are only reported
in deliverables, but the actual testing data sets are not specifically
documented.

**Ethical and privacy issues**

None

**IPR issues**

EISCAT scientific association has ownership to all the test data produced.

**Storage and backup project time**

Individual storage options will be considered during testing with regular
backup of test data.

**Access management**

Only to WP in question.

#  Retention and preservation

The director of EISCAT scientific association will make the final decision on
storing such test data. If the data is determined to be stored, it will then
be included in the documentation process and will be stored according to
standard EISCAT data storage policy as defined in the “Blue Book” [2].

#  Long term preservation plan

The test data is usually not retained and if it is retained then it will be
done according to the standard EISCAT data storage policy as defined in the
“Blue Book” [2].

#  Sharing policy

The sharing will be done only within the WP. However, the retained test data
is openly available and will be shared according to EISCAT scientific
association's sharing policy.

#  Responsible persons

Electrical engineer, software engineer and chief engineer will be the
responsible persons for subarray testing. The decision about data retention
will be taken by the director of EISCAT scientific association.

#  Resources used

The procured hardware from vendors, developed low-level engineering software
in WP5 of this project and the project staff of EISCAT scientific association
will be used to perform the sub-array testing.

**CONCLUSIONS**

The DMP has impact on both the project and the stakeholders.

#  Impact on Project

This is the initial version of the DMP and it is clear from this document that
it needs to be further developed, detailed and updated during the project
period. However, it gives the overall data management plan in EISCAT3D_PfP
project and also, the most likely data types collected.

#  Impact on Stakeholders

Data management plan actions are important for research infrastructures
because such document will guide the project personnel to access the produced
documents, software and key data sets in a standard manner.