1. Strategy for standardization of LIDO in ESONET
Christoph Waldmann
MARUM, Bremen
LIDO Demo Mission Meeting, Catania, Jan 2010

2. OUTLINE Rationale for Standardization Scope of the work within LIDO
Outlook

3. RATIONALE Why Standardization? It is essential for System building
Sharing infrastructures and platforms
Integrating different systems
Enabling the transition from experimental to operational phase

4. RATIONALE Differences Operational versus Research
(Parisot, OceanObs09)

5. RATIONALE Why Standardization? Concerns
Will it constraint the versatility/flexibility?
Will the integration be easier or more complex?

6. BACKGROUND
Addressing different Levels and domains
Data interoperability Data quality Standardization Service/Maintenance Intervention

7. STANDARDIZATION WITHIN LIDO
RATIONALE
STANDARDIZATION WITHIN LIDO
WP2 - Data Management
…. Existing concepts and standards like SWE (Sensor Web Enablement) will be evaluated and implemented into a prototype system.
…..management and processing of the real-time data and near to real-time data collected in the DM sites, allowing
1) ………….
2) the automatic detection, classification and tracking of biological and anthropogenic sound sources to assess long-term trends in marine ambient noise.
Public outreach

8. STANDARDIZATION WITHIN LIDO
RATIONALE
STANDARDIZATION WITHIN LIDO
….. The standardization concept that will be pursued during LIDO starts at the detailed description of each sensor and instrument inserted by the user into a standard interface control document.
….. this sensor registry an inventory of all instruments in use of the observatory can be derived and published on the Internet.
This applies in particular to the following issues, where a full description will
be given to the
• Function and operation of all observatory instruments
• Communication and power interfaces
• Time synchronisation
• Actual geographical position for mobile systems
• Safety issues
• Deployment requirements.

9. THE CONCEPT OF AN “OPEN STANDARD“
BACKGROUND
THE CONCEPT OF AN “OPEN STANDARD“
An open standard is a standard that is publicly available and has various rights to use associated with it
“Open“ means royalty-free technologies
“Standard" means technologies approved by formalized committees that are open to participation by all interested parties and operate on a consensus basis.

10. STANDARDIZATION BODIES
BACKGROUND
STANDARDIZATION BODIES
ISO International Organization for Standradisation
IEEE
OGC Open Geospatial Consortium

11. BACKGROUND
EXAMPLES
ISO/CD : Road vehicles -- Controller area network (CAN) -- Part 3: Low-speed fault tolerant medium dependent interface
IEEE 1451 Smart Transducer Interface Standard
OGC SWE Sensor Web Enbalement (SensorML)

12. BACKGROUND
Data infrastructure requirements - assimilating and supplying reliable data and data products from distributed sources in a timely and efficient way.
Service-oriented federated system is needed building on and integrating all facilities in Europe handling oceanographic or related data.

13. ESONET WP9 Data infrastructure
Knowledge Base
Sensor Registry
Sensor Observation Service
Sensor integration

14. Task 9b: Knowledge base (Lead: Robert Huber [UNI-HB] )
Objectives:
General information platform and will serve data from all ESONET institutions and observatories
Topology of observatories
Sensor registry
Data archive
ESONET data portal
Full text search engine
Mapping interfaces
Near real time access to selected demo sites (SOS)
Operational ESONET web data portal
D44 ESONET knowledge base

15. Task 9b: Knowledge base Data and information portal
This tasks deals with organisational and policy issues of the ESONET data management. Two groups have been founded already during the first year, the data management group and the data management council.
Whereas the data managment group deals with technological issues, the council acts as an advisory board.
The data management group is organised in 3 working groups: Data Archive+Interoperability,QC/Quality Assurance, Data capture
Members include WP members and demo site members. But also from partner projects such as EuroSites and Seadatanet.
The group organised 2 meetings during the last year, one in Portugal and one in Bremen
Another meeting is planned for next week at the marum in Bremen ‘the last mile of data management’
The data management council has met the first time during the General Assembly Meeting in Portugal, where also memebership was extended to members of the projects SeaDataNet and EuroSites
The data management plan was drafted by WP 1 and submitted to and reviewed by the Data Management Council and published as Deliverable 6 online in a WIKI as well as a pdf version on the ESONET homepage.
It provides detailled instructions and deals with all major aspects of the ESONET data management procedures.
In detail, the main parts are dealing with
policies with respect to relevant bordering international initiatives and programs
General aspects of sustainable data management
Detailed guidelines for demonstration cases and subsequent long-term observatoriesnetwork operation

16. Task 9b: Knowledge base Future data portal
This tasks deals with organisational and policy issues of the ESONET data management. Two groups have been founded already during the first year, the data management group and the data management council.
Whereas the data managment group deals with technological issues, the council acts as an advisory board.
The data management group is organised in 3 working groups: Data Archive+Interoperability,QC/Quality Assurance, Data capture
Members include WP members and demo site members. But also from partner projects such as EuroSites and Seadatanet.
The group organised 2 meetings during the last year, one in Portugal and one in Bremen
Another meeting is planned for next week at the marum in Bremen ‘the last mile of data management’
The data management council has met the first time during the General Assembly Meeting in Portugal, where also memebership was extended to members of the projects SeaDataNet and EuroSites
The data management plan was drafted by WP 1 and submitted to and reviewed by the Data Management Council and published as Deliverable 6 online in a WIKI as well as a pdf version on the ESONET homepage.
It provides detailled instructions and deals with all major aspects of the ESONET data management procedures.
In detail, the main parts are dealing with
policies with respect to relevant bordering international initiatives and programs
General aspects of sustainable data management
Detailed guidelines for demonstration cases and subsequent long-term observatoriesnetwork operation

17. Sensor registry COMUNITIES Plug‘n’Work sensor
Sensor Registry (Sensor ML)
registration
dissemination
Archiving, curation & control
Feature Catalogue (ISO 19110)
ESONET Portal Data & Services
automated
sensors and/or related facilites
manual
Instrument specifications
sensor controls
COMUNITIES

18. Task 9c:. Data infrastructure:
Task 9c: Data infrastructure: Sensor Registry (Lead: Eric Delory [dbscale] -> WP2)
Objectives:
Central catalogue of observatories and sensors
User friendly entry interface
Data stored in native XML database (eXist) as OGC standard SensorML (XML)
OGC CSW (Catalogue Service) as GEOSS interface.
Operational Sensor registry
D71 ESONET sensor registry

19. Sensor registry

20. Sensor registry

21. Task 9c: Data infrastructure: SOS development and implementation (Lead: Thierry Carval [IFREMER] )
SOS Client

22. Equipment tests on cabled sites
Organization of equipment tests on cabled sites with training activities
Tests of observatory equipments will be organised
to teach and demonstrate the use of equipments dedicated to long term immersion for real time measurements
to demonstrate the procedures of measurements, underwater interventions etc

23. Session on EGU General Assembly, April 2010
Towards establishing permanent infrastructures for ocean observations: instrumentation, measurement strategies and methods for ocean observatories
Convener: C. Waldmann, MARUM  Co-Conveners: I. Puillat-Felix, IFREMER
L. Beranzoli, INGV
R. Stephen, WHOI