Presentation is loading. Please wait.

Presentation is loading. Please wait.

The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit Presented by : Yves Hardy 17 March 2004.

Similar presentations


Presentation on theme: "The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit Presented by : Yves Hardy 17 March 2004."— Presentation transcript:

1 The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit Presented by : Yves Hardy 17 March 2004

2 The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit 1.General context and objectives 2.SafeSeanet Concept & Architecture

3 To set-up an electronic network between the maritime administrations of Member States in order to facilitate the implementation of EC maritime safety legislation SSN – Basic initial Concept Directorate General for Energy and Transport Maritime Safety Unit

4 (1) - Updating and improving the EU-Hazmat concept - make use of modern IT solutions : Internet and XML - elaborate a simple and flexible solution coping with the diversity of IT systems in place SSN – Legal background Directorate General for Energy and Transport Maritime Safety Unit

5 Types of notifications Port Notifications ( 24 H prior to entry into EC ports) Ship reporting Ships to have AIS in operation MS to monitor compliance with MRS (mandatory reporting systems), VTS (Vessel Traffic Services) and routeing systems Minimum requirements for contents of ships’ reports Hazmat notifications - from ship’s agent to CA on departure from loading port - static, voyage and DG cargo information to be transferred “electronically whenever practicable” SSN – The “Traffic monitoring Directive” Directorate General for Energy and Transport Maritime Safety Unit

6 Obligations for Member States : Hazmat to cooperate to ensure the interconnection and interoperability of the national systems on the basis of the minimum following system requirements (a)use of electronic data exchange (b)be able to transmit information 24 hours a day; (c)be able, upon request, to forward information on the ship and the dangerous or polluting goods on board without delay to the CA of another MS SSN – The “Traffic monitoring Directive” Directorate General for Energy and Transport Maritime Safety Unit

7 Obligations for Member States : Hazmat Message requirements (Annex III of Directive 2002/59) 1.MS shall develop and maintain the necessary infrastructure to enable transmission, reception and conversion of data between their IT systems. –2. The Commission shall develop and maintain, in consultation with the MS, an "Interface Control Document" which describes the system facilities, including the description of the messages. –3. These procedures and infrastructure should incorporate, whenever practicable, reporting and information exchange obligations resulting from other Directives, such as Directive 2000/59/EC on port reception facilities SSN – The “Traffic monitoring Directive” Directorate General for Energy and Transport Maritime Safety Unit

8 General Objective: provide the Member States and the Commission with technical assistance for implementing EC maritime safety legislation Specific objective : to develop and operate any information system necessary for attaining the objectives of the Directive SSN – EMSA Directorate General for Energy and Transport Maritime Safety Unit

9 SSN was launched in January 2002 2 phases until now: –Feasibility Phase : January 2002 – April 2003 + pilot-group of MS –Development Phase : started in May- June 2003 ongoing –Testing Phase: launched in January 2004 till June 2004 SSN – Timetable Directorate General for Energy and Transport Maritime Safety Unit

10 Main criticism from Member States (during feasibility phase ) : - The scope of SafeSeaNet is too narrow, being only focused on a legal objective (implementation of EU directives) - Reporting through AIS needs to be considered Therefore, SSN needs a broader long-term objective : the setting-up of a European platform for maritime data exchange making available to a large number of maritime users all relevant information concerning ships, their movements and their cargoes SSN – Evolution of concept Directorate General for Energy and Transport Maritime Safety Unit

11 SafeSeaNet should aim at: - improved emergency response in case of incidents or pollution at sea (eg : transmission of DG information) - early detection of “ships posing a risk” - increased efficiency of port logistics (accurate ETAs, waste handling…) - produce statistics for EMSA, Member States and the Commission European Commission - Directorate-General for Energy and Transport Maritime Safety Unit Directorate General for Energy and Transport Maritime Safety Unit SSN – main objectives identified

12 6 Generic messages Voyage : –Port Reporting –Ship Reporting –AIS Hazmat Security Alert messages SITREP POLREP WASTE CONTAINERS LOST/FOUND OTHERS ? : DEFREP, INFRINGEMENT TRAFFIC RULES, etc. Directorate General for Energy and Transport Maritime Safety Unit BALTIC NS-CH ATL MED-W MED-E 3 - AREA SEARCH 2 - PORT SEARCH Provides the list of all ships bound to a given port with their ETAs 1 - SHIP SEARCH SSN – Types of requests

13 Advantages of the proposed solution Flexible – built on existing national structures –can integrate new users (customs, Schengen, etc.), new messages – Internet-based solution (XML), Cost-effective –No unnecessary movements of data : the bulky data remains close to the source Simple : one single contact point : the European Index Server SSN – Conclusion : Added Value Directorate General for Energy and Transport Maritime Safety Unit

14 The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit 1.General context and objectives 2.SafeSeanet Concept & Architecture

15 3 Main Actors -The SSN European Index Server (EIS) : is able to locate and retrieve in a MS the information required by another MS and forward it to the requesting MS The Data Provider: the authority which locally handles the information has to notify the EIS that it possesses such information but retains the detailed information (in particular cargo information). On request the Data provider forwards the detailed information to the EIS The Data Requester : the authority which needs the information sends a request and receives the reply from the EIS SSN – The Actors Directorate General for Energy and Transport Maritime Safety Unit

16 Who are the actors -At EU level : -The European Index Server (EIS) : hosted by the Informatics Directorate of the Commission (LUX) -The Commission (DG TREN) : general monitoring and statistics -EMSA : will take over the operation of SSN At national level: –The NCA will assume the overall responsibility of the proper functioning of the system at national level –Local authorities or bodies will act as data providers or requesters : coastal VTS, MRCC, ports… SSN – The Actors Directorate General for Energy and Transport Maritime Safety Unit

17  SSN provides 2 different types of interfaces 1. A default browser-based web interface 2. An XML message-based interface SafeSeaNet Functional Services Overview Directorate General for Energy and Transport Maritime Safety Unit

18  SafeSeaNet Browser-Based Web User Interface Manually send notifications to SSN (by filling in web forms). The Member State acting as Data Provider Manually request detailed information (by filling in web forms and viewing results). The Member State acting as Data Requester  SafeSeaNet XML Message-Based Interface Communicate programmatically with the SafeSeaNet system SafeSeaNet Functional Services Overview Directorate General for Energy and Transport Maritime Safety Unit

19 1. Data Providers XML Message-based Interface Browser-based Web User Interface 2.Data Requester SafeSeaNet Functional Services Overview

20 Directorate General for Energy and Transport Maritime Safety Unit Port Authority:AAA Port Authority:ABB Member State x National Contact Point NCA Web Server SafeSeaNet Central Server Data Centre MS2SSN_Port_Not Port Reporting SentAt: 23/09/2003 10:00 From: AAA To: SSN Port Reporting Notification IMO : 1234567 MMSI : …. NextPortOfCall : … Hazmat Reporting MS2SSN_Haz_Not SentAt: 23/09/2003 12:00 From: AAB To: SSN Hazmat Reporting Not. IMO : 1234567 MMSI : …. NextPortOfCall: … SafeSeaNet Web Server Data Provider – XML Message-Based Interface

21 Directorate General for Energy and Transport Maritime Safety Unit Port Authority:AAA Member State x National Competent Authority SafeSeaNet Central Server EC Data Centre https://ssn.emsa.eu.int/… SafeSeaNet Web Server Data Provider – Browser-Based Web User Interface Web form IMO : ……………….. MMSI : ……………….. Call Sign : ……………….. Ship Name : ……………….. NextPortOfCall : …………….. ETA : …………………………. ETD : …………………………. TotalPersonsOnBoard: ……… Submit 1234567 2145678901 FN382910 Albator FIHEL 2003-10-04 10:00 2003-10-06 18:00 15 MS Web Statistics Not. sent / authority: ……….. Name of authorities: ………... Nb. of request : ……………… Nb. of replies : ……………… …… 40 10 X 4

22 1. Port Reporting Notifications SafeSeaNet Generic Messages Directorate General for Energy and Transport Maritime Safety Unit

23 13/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission Port Notification message Scenario 1 : Port Reporting within the Community Notification message 15/11/2003 11:00 Hamburg Next Port of Call Port Notification’s Header Version: 1.4 MSRefId: 151120031101 SentAt: 2003-11-15 1101 From : DEHAM To: SSN Port Notification’s Body Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : DEHAM ETA : 17/11/2003 15:00 ETD : 18/11/2003 07:00 PersonsOnBoard : 10

24 07/11/2003 10:00 Port of Departure Outside EC European SafeSeaNet System Data Centre – European Commission Port Notification message Scenario 2 : Port of Departure outside the Community Notification message 09/11/2003 15:00 Antwerp Next Port of Call Port Notification’s Header Version: 1.4 MSRefId: 091120031501 SentAt: 2003-11-09 1501 From : BEANR To: SSN Port Notification’s Body Vessel Identification IMO : 7654321 MMSI : FN43431 Name : Alpha Voyage Information NextPortOfCall : BEANR ETA : 13/11/2003 15:00 ETD : 15/11/2003 09:00 PersonsOnBoard : 12

25 19/11/2003 08:00 Next Port of Call Outside EC European SafeSeaNet System Data Centre – European Commission Scenario 3 : Next Port of Call outside the Community Notification message 13/11/2003 15:00 Antwerp Port of Depature No Port Notification message Transmitted

26 07/11/2003 10:00 Port of Departure Outside EC European SafeSeaNet System Data Centre – European Commission Port Notification message Port Notification’s Header Version: 1.4 MSRefId: 091120031601 SentAt: 2003-11-09 1601 From : BEANR To: SSN Scenario 4 : Ports Reporting within the Community Vessel Changes Next Port of Call 14/11/2003 11:30 Dublin New Port of Call 09/11/2003 16:00 Antwerp Next Port of Call 11/11/2003 18:00 Antwerp Cancellation Port Notification’s Body Vessel Identification IMO : 7654321 MMSI : FN43431 Name : Alpha Voyage Information NextPortOfCall : BEANR ETA : 15/11/2003 16:00 ETD : 16/11/2003 12:00 PersonsOnBoard : 9 Cancellation of the previous Port Notification (Header) Header Version: 1.4 MSRefId: 111120031801 SentAt: 2003-11-11 1801 From : BEANR To: SSN Cancellation of the previous Port Notification (Body) Vessel Identification IMO : 7654321 MMSI : FN43431 Name : Alpha Voyage Information NextPortOfCall : UNKWN ETA : - ETD : - PersonsOnBoard : 9 Port Notification’s Header Sent by DUBLIN Version: 1.4 MSRefId: 141120031131 SentAt: 2003-11-14 1131 From : IEDUB To: SSN Port Notification’s Body Sent by DUBLIN Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : IEDUB ETA : 17/11/2003 15:00 ETD : 18/11/2003 07:00 PersonsOnBoard : 10

27 10/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission Port Notification messages Scenario 5 : Ports Reporting within the Community Short Next Port Of Calls 11/11/2003 15:02 Antwerp Next Port of Call Port Notification’s Header Bordeaux Version: 1.4 MSRefId: 111120031500 SentAt: 2003-11-11 1500 From : FRBOR To: SSN Port Notification’s Body Bordeaux Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : FRBOR ETA : 13/11/2003 15:00 ETD : 13/11/2003 18:00 PersonsOnBoard : 12 11/11/2003 15:00 Bordeaux Next Port of Call 11/11/2003 15:01 Nantes Next Port of Call Port Notification’s Header Nantes Version: 1.4 MSRefId: 111120031501 SentAt: 2003-11-11 1501 From : FRNTR To: SSN Port Notification’s Body Nantes Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : FRNTR ETA : 14/11/2003 09:00 ETD : 14/11/2003 12:00 PersonsOnBoard : 12 Port Notification’s Header Antwerp Version: 1.4 MSRefId: 111120031502 SentAt: 2003-11-11 1502 From : BEANR To: SSN Port Notification’s Body Antwerp Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : BEANR ETA : 15/11/2003 07:00 ETD : 15/11/2003 12:00 PersonsOnBoard : 12

28 Directorate General for Energy and Transport Maritime Safety Unit SafeSeaNet Port Reporting Message

29 2. Ship Reporting Notifications MRS : Mandatory Reporting System AIS : Automatic Identification System SafeSeaNet Generic Messages Directorate General for Energy and Transport Maritime Safety Unit

30 European SafeSeaNet System Data Centre – European Commission Ship Notification Messages (MRS or AIS) Directorate General for Energy and Transport Maritime Safety Unit 25/08/2003 00:00 Lisbon Port of Departure 26/08/2003 12:00 Cap Finist. AIS Dest = Hamburg ETA = 29/08/03 20:00 27/08/2003 09:00 Ushuant Isl. AIS Dest = Hamburg ETA = 29/08/03 20:00 28/08/2003 06:00 Dover MRS Dest = Hamburg ETA = 29/08/03 21:30 28/08/2003 18:00 Amsterdam MRS Dest = Hamburg ETA = 29/08/03 22:30 27/08/2003 08:00 Hamburg Next Port of Call Port Notification’s Header Cap Finisterre (AIS) Version: 1.4 MSRefId: 260820031200 SentAt: 2003-08-26 1200 From : ESMAD (*) To: SSN * LoCode NCA Madrid Port Notification’s Body Cap Finisterre (AIS) Vessel Identification IMO : 7654321 MMSI : FN43431 Voyage Information NextPortOfCall : DEHAM ETA : 29/08/2003 20:00 Ship’s Position Longitude : 49° 41’ N Latitude : 01° 55’ W Timestamp: (UTC format) Port Notification’s Header Ushuant Island (AIS) Version: 1.4 MSRefId: 270820030900 SentAt: 2003-08-27 0900 From : FRJOB (*) To: SSN * LoCode NCA Jobourg Port Notification’s Body Ushuant Island (AIS) Vessel Identification IMO : 7654321 MMSI : FN43431 Voyage Information NextPortOfCall : DEHAM ETA : 29/08/2003 20:00 Ship’s Position Longitude : 51° 22’ N Latitude : 04° 24’ W Timestamp: (UTC format) Ship Notification’s Header Dover (MRS) Version: 1.4 MSRefId: 280820030600 SentAt: 2003-08-28 0600 From : GBDVR To: SSN Ship Notification’s Body Dover (MRS) Vessel Identification IMO : 7654321 MMSI : FN43431 Voyage Information NextPortOfCall : DEHAM ETA : 29/08/2003 21:30 Ship’s Position Longitude : 54° 02’ N Latitude : 03° 04’ W PersonsOnBoard: 10 Ship Notification’s Header Dunkirk (AIS) Version: 1.4 MSRefId: 280820030700 SentAt: 2003-08-28 0700 From : FRJOB (*) To: SSN * LoCode NCA Jobourg Ship Notification’s Body Dunkirk (AIS) Vessel Identification IMO : 7654321 MMSI : FN43431 Voyage Information NextPortOfCall : DEHAM ETA : 29/08/2003 22:30 Ship’s Position Longitude : 58° 32’ N Latitude : 09° 14’ W Timestamp: (UTC format) Ship Notification’s Header Amsterdam (MRS) Version: 1.4 MSRefId: 280820031800 SentAt: 2003-08-28 1800 From : NLAMS To: SSN Ship Notification’s Body Amsterdam (MRS) Vessel Identification IMO : 7654321 MMSI : FN43431 Voyage Information NextPortOfCall : DEHAM ETA : 29/08/2003 22:30 Ship’s Position Longitude : 45° 11’ N Latitude : 08° 14’ W PersonsOnBoard: 10 28/08/2003 07:00 Dunkirk AIS Dest = Hamburg ETA = 29/08/03 22:30

31 Directorate General for Energy and Transport Maritime Safety Unit SafeSeaNet Ship Reporting Messages

32 3. Hazmat Reporting SafeSeaNet Generic Messages Directorate General for Energy and Transport Maritime Safety Unit

33 13/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission Hazmat Notification message Scenario 1 : Hazmat Reporting - Port of Departure Notification message 15/11/2003 11:00 Hamburg Next Port of Call Hazmat Notification’s Header : Lisbon Version: 1.4 MSRefId: 131120031000 SentAt: 2003-11-13 1000 From : DEHAM To: SSN Hazmat Notification’s Body : Lisbon Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : DEHAM ETA : 17/11/2003 15:00 ETD : 18/11/2003 07:00 PersonsOnBoard : 10 Notification Details XML or URL or Phone/Fax

34 07/11/2003 10:00 Port of Departure Outside EC European SafeSeaNet System Data Centre – European Commission Hazmat Notification message Scenario 2 : Hazmat Reporting - Next Port Of Call Notification message 09/11/2003 15:00 Antwerp Next Port of Call Hazmat Notification’s Header : Antwerp Version: 1.4 MSRefId: 091120031500 SentAt: 2003-11-09 1500 From : BEANR To: SSN Hazmat Notification’s Body : Antwerp Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : BEANR ETA : 13/11/2003 15:00 ETD : 15/11/2003 10:00 PersonsOnBoard : 10 Notification Details XML or URL or Phone/Fax

35 19/11/2003 08:00 Next Port of Call Outside EC European SafeSeaNet System Data Centre – European Commission 13/11/2003 15:00 Antwerp Port of Depature Hazmat Notification message Scenario 2 : Hazmat Reporting – Port of Departure Notification message Hazmat Notification’s Header : Antwerp Version: 1.4 MSRefId: 131120031500 SentAt: 2003-11-13 1500 From : BEANR To: SSN Hazmat Notification’s Body : Antwerp Vessel Identification IMO : 1234567 MMSI : FN23424 Name : Gamma Voyage Information NextPortOfCall : USCAL ETA : 19/11/2003 08:00 ETD : 20/11/2003 07:00 PersonsOnBoard : 10 Notification Details XML or URL or Phone/Fax

36 4. Alert Reporting SafeSeaNet Alert Messages Directorate General for Energy and Transport Maritime Safety Unit

37 13/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission Waste Notification message Scenario 1 : Alert Reporting within the Community Alert Notification message 15/11/2003 11:00 Hamburg Next Port of Call Waste sent by email

38 13/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission 15/11/2003 11:00 Hamburg Next Port of Call Email to NCA SIRENAC Database Scenario 2 : Port Reporting within the Community Alert Notification message – Banned Ship Request list of banned Ships List returned to SSN Banned 15/11/2003 11:02 NCA : Bremen Email:Banned ship

39 Directorate General for Energy and Transport Maritime Safety Unit 1. Data Providers XML Message-based Interface Browser-based Web User Interface 2.Data Requester SafeSeaNet Functional Services Overview

40 Directorate General for Energy and Transport Maritime Safety Unit Member State: Netherlands Local Competent Authority SafeSeaNet Central Server EC Data Centre https://ssn.emsa.eu.int/… SafeSeaNet Web Server Data Requester – Browser-Based Web Interface Web Form Request IMO : ……………….. MMSI : ……………….. Submit 1234567 Web Form Results NextPortOfCall : …………….. ETA : …………………………. ETD : …………………………. TotalPersonsOnBoard: ……… Port of Hamburg DEHAM 2003-03-28 20:00 2003-03-30 10:00 12

41 13/11/2003 10:00 Lisbon Port of Departure European SafeSeaNet System Data Centre – European Commission Hazmat Request Data Requester – Detailed Cargo Manifest Browser-based Web User Interface 16/11/2003 11:00 Hamburg Next Port of Call SafeSeaNet Browser Web User Interface Vessel Identification IMO : ……………. MMSI : ……………. Select the type of message Port Reporting Ship Reporting Hazmat Reporting Incident Submit 14/11/2003 23:00 MRCC Jobourg Incident Reported 1234567 FN23424

42  Who are the data requesters? * Coastal stations - MRCC - VTS - Coastguards * Port authorities * National competent authorities  Types of data requested? * Port reporting (ETA, Hazmat information…) * Ship reporting (voyage information, …) * Alerts reporting (SITREP, POLREP...) SafeSeaNet : Data Requester Directorate General for Energy and Transport Maritime Safety Unit

43 Member State: Netherlands Local Competent Authority SafeSeaNet Central Server EC Data Centre https://ssn.emsa.eu.int/… SafeSeaNet Web Server Data Requester – Browser-Based Web Interface Web Form Request IMO : ……………….. MMSI : ……………….. Submit 1234567 Web Form Results NextPortOfCall : …………….. ETA : …………………………. ETD : …………………………. TotalPersonsOnBoard: ……… Port of Hamburg DEHAM 2003-03-28 20:00 2003-03-30 10:00 12

44 26/08/03 00:01 Lisbon Departure 26/08/03 12:00 Cap Finisterre AIS Dest = Hamburg ETA = 28/03/03 20:00 27/03/03 09:00 Ushant Isl. AIS Dest = Hamburg ETA = 28/03/03 20:00 European SafeSeaNet System Data Centre – European Commission 27/03/03 10:00 Port of Hamburg Request to SafeSeaNet PortOfDestination = ? ETA = ? 27/03/03 10:00 Port of Hamburg Answer from SafeSeaNet PortOfDestination = Hamburg ETA = 28/03/03 20:00 Directorate General for Energy and Transport Maritime Safety Unit

45 System available 24h/day - 365 days/year Capable of providing a rapid reply to any request Based on Internet Standard Technology (web server) Support message implementation in XML Flexible: be able to include new requirements stemming from EC legislation, new messages, new members in the network, etc. User-friendly Shall ensure security of communications SSN – Basic System Requirements Directorate General for Energy and Transport Maritime Safety Unit


Download ppt "The SafeSeaNet Project Directorate General for Energy and Transport Maritime Safety Unit Presented by : Yves Hardy 17 March 2004."

Similar presentations


Ads by Google