1. 1 CleanSeaNet DREAM PRESENTATION

2. Content Short introduction to EMSA EMSA Objectives and expected main results from DREAM EMSA Activity/Processes to which the project is applicable 2

3. EMSA ACTIVITIES 3

4. Acquisition and Processing Oil Spill Analysis Product Processing and Alert Generation T0 = End of scene acquisition T = T0 + 30 min FeedbackFeedback CleanSeaNet : Near Real Time service – 30 min* 4 CleanSeaNet Service providers EMSA CleanSeaNet Data Centre Analysis Results (Oil spills and vessel detection) Phone and email alert (Alert Report) Data dissemination Met-ocean & ancillary data * Satellite images are acquired in segments up to 1400 km long. 30 min are for a 400 km length image Planning

5. CleanSeaNet Data Centre EMSA data broker, quality control, operational monitoring 5 CleanSeaNet service architecture >>> 27 Coastal States <<< ENVISAT Radarsat (1 and 2) Satellites (synth. aperture radar) Cosmo Skymed, TerraSAR, Worldview … Service providers Procurement EDISOFT KSAT E-GEOS CLS >>> EU / EC <<<

6. CleanSeaNet User Interface 6

7. 27 Coastal States 2000 Satellite images per year and image metadata such as acquisition date, geographic coordinates, etc… Oil spill identification - alert report Vessel detection information Modeling data Forward modeling Backward modeling Electronic Nautical Charts AIS information via EMSA SafeSeaNet service Associated ancillary data: meteorological wind and wave data, SAR derived wind and swell data Products delivered by CleanSeaNet

8. 8 ESA MDA CLS KSAT EGEOS EDISOFT … … … FTP FTPS HTTPS ? Common ICD Single Interface CLEANSEANET DELIVERY CHAIN EMSA GEST CHAIN CSN DATA DELIVERY Fully automatic Manual

9. 9 CSN INFORMATION EXCHANGE Budget? … 1.- Planning tool files are generated 2.- Data is ingested in POR 3.- SP and LP confirm in POR 4.- CS confirms in POR 5.- E-mails are sent to SP and LP with the tasking forms (data purchase) 6.- Acquired data is available in the GIS viewer (400x400 Km scene + oil + vessel detection available in 30 minutes) 7.- Budget constantly monitored For Emergency a couple of phone calls are added to this procedure Single Interface 1.- SPERF is compiled and sent to GEST 2.- SRT is sent to EMSA 3.- Confirmation is sent to GEST 4.- Reporting obligations 5.- No Real time Budget (quota) management 6.-Cancellation information sometimes arrives after acquisition time 7.- Sometimes information is received from GCM Single Interface E-mail

10. EMSA OBJECTIVES 10

11. 1.Multi Satellite Swath Propagation tool: Coverage requirement import and tasking areas Propagation of GCMs Acting as format integrator (many output formats for the different satellite operators, one unified format for EMSA) Cloud stats 2.Catalogue access 3.Ordering tool Definition of products to be delivered (e.g. mode/pol, processing level) Definition of timeliness requirements Order status summary (e.g. confirmed (feasible), tasked, delivered, cancelled, anomaly, error) 4.Delivery gateway 5.Integration with EMSA CSN DC 11 Expected results

12. 1.Multi Satellite Swath Propagation tool: Coverage requirement import and tasking areas Format used in EMSA is shapefiles Propagation of GCMs The propagation shall be done using the elements the Satellite Operator is using. E.g. Envisat propagation based on TLEs and not in nominal orbit would lead to an incorrect planning of the satellite. Acting as format integrator (many output formats for the different satellite operators, one unified format for EMSA) Eoli shopcart, APT, Swath Planner,… all the tools use different formats, if available an HMA interface shall be implemented, otherwise mission native tool format. Towards EMSA an unified format shall be created. Optimization of the acquistions coverage Shifting/resizing shall be available for each mission Cloud stats/Ingestion of cloud masks in real time For planning optical missions 12 Expected results

13. 2.Catalogue access To assess what is available during an emergency or can be used for a project 13 Expected results

14. 3.Ordering tool Definition of products to be delivered (e.g. mode/pol, processing level) Definition of timeliness requirements Order status summary (e.g. confirmed (feasible), tasked, delivered, cancelled, anomaly, error) 14 Expected results

15. 4.Delivery gateway Unified pick up interface (e.g. clicking download to get the product independently of provided) CSN DC products are packaged containing: an XML package descriptor, followed by the native EO product file (referred as File in figure 5), the EO Product metadata and the browse image file in JPEG format. 15 Expected results Figure.- Data Delivery to EMSA

16. 5.Integration with EMSA CSN DC Integration of planning tools Coverage requirements Tasking Areas Integration with POR Unified format/Multiple formats Status updates Integrated Delivery GCMs Integrated Catalogue accessible via CleanSeaNet or via the tool 16 Expected results

17. APPLICABLE PROCESSES 17

18. 18 ESA MDA CLS KSAT EGEOS EDISOFT … … … FTP FTPS HTTPS ? Common ICD Single Interface CLEANSEANET DELIVERY CHAIN EMSA GEST CHAIN IMPACT IN DELIVERY CHAIN Fully automatic Manual

19. 19 CSN INFORMATION EXCHANGE Budget? … 1.- Planning tool files are generated 2.- Data is ingested in POR 3.- SP and LP confirm in POR 4.- CS confirms in POR 5.- E-mails are sent to SP and LP with the tasking forms (data purchase) 6.- Acquired data is available in the GIS viewer (400x400 Km scene + oil + vessel detection available in 30 minutes) 7.- Budget constantly monitored For Emergency a couple of phone calls are added to this procedure Single Interface 1.- SPERF is compiled and sent to GEST 2.- SRT is sent to EMSA 3.- Confirmation is sent to GEST 4.- REPORT TO ESA? 4.- No Real time Budget (quota) management 5.-Cancellation information sometimes arrives after acquisition time 6.- Sometimes information is received from GCM Single Interface E-mail

20. Focal Point: Jorge Del Rio – CleanSeaNet project officer jorge.DELRIO-VERA@emsa.europa.eu Backup: Pedro Lourenço – CleanSeaNet project officer Pedro.LOURENCO@emsa.europa.eu 20 EMSA point of contact