Guidelines for joining ORFEUS EIDA becoming an EIDA node

Last revision June 2018


To be considered as an EIDA node, an institution must fulfil all of the following requirements:

1. General Requirements

An EIDA node should:

  • be an institution from a member country of ORFEUS.
  • be committed to an open data policy.
  • ideally represent the seismological community at national level or beyond. In practice this means they should serve as a data repository for other seismic networks in the region.
  • commit human resources to contribute to the maintenance and development of the system and associated software.
  • commit to active participation in the EIDA Management Board and the EIDA Technical Committee. Note: the additional workload to run an EIDA node as compared to an independent data center is by most nodes evaluated to approximately 0.3 FTE.
  • meet a minimum technical level as defined in the ETC Technical Requirements for an EIDA Node. This includes requirements on both data quality (waveform and metadata) and service (server uptime, reaction time for problems, data security, e.g. redundancy, backups).
  • contribute at least 50 permanent operational stations, with back archive, not previously distributed by other EIDA nodes and maintain a permanent data management center.
  • meet requirements set by EPOS. At present, this means ensuring all owners of the networks distributed from the node 1) provide a formal agreement for data distribution (following EIDA templates), 2) agree to attach an open data licence to the data, and 3) have a DOI for each network code.
Any prospective nodes that cannot meet all these requirements are encouraged to inform the EMB Chair. Depending on the difficulty encountered, the EIDA Management Board and ETC will help the applicant to meet the criteria or, if no solution is found, inform the ORFEUS Execom.

2. Technical Requirements

All EIDA nodes must offer access to:

  • Waveform data: through FDSN-Dataselect, Arclink*
  • Inventory: through FDSN-Station
  • Routing Information: through the Routing Service(s) @ ODC, GFZ, etc,
  • Quality metrics of the data: through WFCatalog.

Mandatory services are:

  • Arclink*
  • FDSN-Dataselect
  • FDSN-Station
  • WFCatalog
  • Webreqlog (daily report for statistics)
  • Extension to Dataselect for AAI (“auth” method)
* Arclink is a mandatory service until it is retired in 2019

3. Target Requirements*

An EIDA node should dedicate resources and make an effort to provide:

  • High data quality for archives including:
    • Waveforms (miniSEED format)
    • Inventory (any of StationXML, datalessSEED, InventoryXML).
  • Service availability: >95%
  • Contact person for technical issues and maintenance
  • Reaction time for problems within 48 hours
  • At least one backup copy of all data
  • Infrastructure should be able to serve all EIDA inventory and significant data requests in a reasonable time
* Specifications for ideal operational hardware and expected performance is dynamic and can be discussed with ETC

Roadmap for becoming an EIDA Node

A. Preparation

Any agency interested in becoming an EIDA node should be technically prepared:

  • all waveform datasets are in mini-SEED and organized in a manner already accessible to EIDA software, e.g. SDS structure. If not there must be a willingness to create an interface to access the data
  • all datasets have metadata in dataless SEED, StationXML or inventoryXML format.
  • Discuss intention to join EIDA with EIDA EMB. Current contact point is the EMB Chair (see the EIDA Management & Structure page). The EIDA EMB brings the discussion to the attention of ORFEUS.
  • The EMB Chair sends a message to the applicant with specific recommendations for the application.

B. Formal Steps

From this stage, Technical and Management steps can proceed in parallel:

Technical
  • interaction with EIDA Technical Committee in order to prepare the technical integration with the EIDA system, including the implementation of EIDA related services (e.g. web portal, fdsnws)
Management
  • A formal written application is submitted.
  • EMB will evaluate the request based on the fulfillment of the above requirements.
  • EMB will make a formal recommendation and inform the ORFEUS ExeCom.
  • The ORFEUS Board decides on the inclusion of the node, based on the EMB recommendation, input from the Execom, and any other consideration the Board considers relevant.

C. Final Steps

  • The new member must sign an EIDA MoU, with ORFEUS.
  • Technical readiness is monitored for a few weeks
  • Operational integration of the data center

Note: the process to become an EIDA node typically lasts 1-2 years between initial contacts and signature of the MoU / full operational integration within EIDA.