Periodic Activity Report/3rd Period - Ifremer
Periodic Activity Report/3rd Period - Ifremer
Periodic Activity Report/3rd Period - Ifremer
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ESONET Contract no.036851/<strong><strong>Period</strong>ic</strong> <strong>Activity</strong> <strong>Report</strong>/3 rd <strong>Period</strong><br />
The MODOO DM mainly addressed outlying and building hardware, in particular the Data<br />
Collection and Dissemination (DCD) node to be connected to the MODOO lander and<br />
mooring. This is in view of the deployment and the recovery cruise in the Porcupine Abyssal<br />
Plain off southwest Ireland scheduled for May/June 2010.<br />
The MOMAR-D is proceeding with the final definition of the observatory and the start the<br />
technological work: designing and building the sensors/nodes, adapting sensor software to<br />
SEAMON technology. The objective is to start trials in Brest by Spring 2010. The cruise to<br />
implement the observatory infrastructure on Lucky Strike (Azores), is now scheduled for<br />
September 2010 (R/V Pourquoi pas? and ROV Victor 6000).<br />
The AOEM (ESONET Arctic site), for which the Grant Agreement and Implementation Plan<br />
had to be amended, commenced in July 2009 with the preparation of the geophysical<br />
experiments for assessing the variability of the acoustic signature of the bubble plumes in the<br />
water column, monitoring the thermal signal of fluids expelled from the sediment and<br />
determining the micro-seismological expression of hydrate dissociation and fluid escape. The<br />
technical work that has started includes the identification of available technical solutions for<br />
data transfer from Fram Strait moorings to land and of feasible ocean water column<br />
deliverables that can be collected from the cabled network and meet the requirements of user<br />
community.<br />
2.4.3 Deviations from the project work programme, and corrective actions taken<br />
3. Delay in the signature of the AOEM DM Grant Agreement (2 nd Call). The delay was<br />
due to the planned participation of an institution which is not an ESONET consortium<br />
Partner. This Sub-contracting was not provided for ESONET, so the ESONET<br />
Coordinator prepared a request of contract amendment including modifications of<br />
financial information. This amendment request took a longer time than expected. .<br />
4. The delivery of Marmara-DM semester report was delayed for about 3 months. This<br />
was in part due to the overlap of the report deadline with the preparation and<br />
subsequent development of sea operations in the Sea of Marmara, which involved all<br />
the Partners of the DM. This kind of delay may be recurrent at this stage (at-sea<br />
operations) and are difficult to overcome given the large number of partners involved<br />
in DM reporting. Repeated solicitations and reminders with warnings of cutting off<br />
DM funds to Partners may be necessary to achieve punctual reporting.<br />
Note from the coordinator: the deliverable D45b is not delivered yet due to the delay of the<br />
deliverable D45a.<br />
Del.<br />
no.<br />
D45a<br />
2.4.4 Deliverables list<br />
Deliverable<br />
name<br />
Second<br />
periodical report<br />
WP<br />
no.<br />
Date<br />
due<br />
Actual/Forecasted<br />
delivery date<br />
Estimated<br />
indicative<br />
personmonths<br />
(*)<br />
Used<br />
indicative<br />
personmonths<br />
(*)<br />
Lead<br />
contractor<br />
WP4 28 31 278.5 INGV<br />
April 2010 40