FARGIS Seminar og Work Shop 16. – 17. mars 2004 Ved Reidar Kjennbakken

History 1993 : the 93/75 “Hazmat” Directive1993 : the 93/75 “Hazmat” Directive 1995 : the MOU-Hazmat (6 MS – EDIFACT / X- 400)1995 : the MOU-Hazmat (6 MS – EDIFACT / X- 400) 2002 :2002 : June 2002 : adoption of ERIKA-II measuresJune 2002 : adoption of ERIKA-II measures the 2002/59 “Traffic Monitoring” Directivethe 2002/59 “Traffic Monitoring” Directive the 1406/2002 “EMSA” Regulationthe 1406/2002 “EMSA” Regulation January 2002 : launching of the SafeSeaNet ProjectJanuary 2002 : launching of the SafeSeaNet Project January April 2003 : Feasibility PhaseJanuary April 2003 : Feasibility Phase May/June 2003 ongoing : Development PhaseMay/June 2003 ongoing : Development Phase

Objective Short-term objective : To set-up an electronic network between the maritime administrations of Member States in order to facilitate the implementation of EC maritime safety legislation Longer-term objective : To set up 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

What is the purpose of SafeSeaNet? 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

EU legislation involved: 1.Directive 2002/59/EC “Traffic Monitoring” 2. Directive 2000/59/EC “Port Reception Facilities” 3. Directive 1999/35/EC “Ro-Ro surveys” 4.Directive 95/21/EC “Port State Control” 5.Regulation 1406/2002 “European Maritime Safety Agency” (6.Future EU Security Regulation)

Directive 2002/59/EC “Traffic Monitoring” Requires ships to notify in advance various information (identity/voyage/DG on board/incidents...) Requires Member States to set-up appropriate shore- based infrastructure by the end of 2007 and to interconnect their national communication systems (as from February 2004) Requires Member States and the Commission to cooperate: to develop specifications for the data exchange, telematic links between ports/coastal stationsto develop telematic links between ports/coastal stations to improve links between coastal stationsto improve links between coastal stations to extend/improve ships’ identification and monitoring by MRS, VTS and routing systemsto extend/improve ships’ identification and monitoring by MRS, VTS and routing systems

I - Clarification on SafeSeaNet functions A clear distinction must be done between the information transmitted by the ships to the shore (Ship to Shore notification) and the information transmitted by the shore to the "European Index Server" (Member States to E.I.S).

II - Notification functions (Shore to SSN) Member States shall notify to the E.I.S: Port Notifications Hazmat Notifications Ship reports AIS and VTS Alert messages (waste, polrep, sitrep) received or emitted by their operational services

III - Request functions Ship Search Port search and Area search will give the possibility to obtain all the information transmitted by the vessels / operational services in the reporting and notification process (Port notification, VTS/AIS reports, and Hazmat notification) that have been notified by the MS.

SafeSeaNet Functional Services Overview SafeSeaNet will provide two different interfaces to help the Member States communicate with the central SafeSeaNet system: A default browser-based web interface An XML message-based interface

SafeSeaNet Functional Services SafeSeaNet will provide a default browser- based web interface Manually send notifications to SafeSeaNet (by filling in web forms) – the Member State acting as Data Provider Manually request detailed information about previously sent notifications (by filling in web forms and viewing results) – the Member State acting as Data Requester Nevertheless, this browser based web interface will internally use the XML message-based interface.

SafeSeaNet XML Message-based Interface SafeSeaNet will also provide an XML message-based interface to enable the NCA applications of the Member States to communicate programmatically with the SafeSeaNet system. The Member States are responsible for developing their NCA application in a way that it provides implementation for the sending, receiving and processing of the messages

Definition of a Data Provider In SafeSeaNet, a Data Provider is a Member State owning some information about vessels and incidents, and making it available to Data Requesters by sending notifications to SafeSeaNet and responding to requests for detailed information.

The responsibility of a Data Provider The Data Provider have to: Send notifications to SafeSeaNet about vessels and incidents, indicating that the Provider owns some detailed information about these notifications, which is made available on request. Respond to SafeSeaNet’s requests (on behalf of Data Requesters) for detailed information about notifications.

Notifications can be of 5 different types: Port Used to notify SafeSeaNet that a given vessel is bound for a particular port with an estimated time of arrival and with a number of persons aboard. Note that the destination port can be ‘unknown’ (then canceling a previous port notification).

Notifications can be of 5 different types: Ship Used to notify SafeSeaNet about a ship’s voyage and cargo information. A ship notification is essentially based on MRS or AIS message.

The complete AIS coverage in Norway 2004.

Notifications can be of 5 different types: HAZMAT Used to notify SafeSeaNet that a given vessel carries dangerous goods and that the sender owns some detailed information about these dangerous goods.

Notifications can be of 5 different types: Security Used to notify SafeSeaNet that the sender holds some security information about a given vessel.

Notifications can be of 5 different types: ALERT Used to notify SafeSeaNet that the sender holds some information about specific incidents like SITREP, POLREP, Waste, lost/found containers. An alert can be linked or not to a particular vessel.

Send Notifications Types of notifications: Port Notification (yet detailed) Ship Notification AIS MRS Hazmat Notification Security Notification Alert Notification SITREP POLREP Waste Lost/Found Containers Others

Data Provider SafeSeaNet Global Architecture – Send Notifications (Browser-based) Data RequesterCentral SafeSeaNet System Send Notifications (Browser-based)

Data Provider SafeSeaNet Global Architecture – Send Notifications (XML message-based) Data RequesterCentral SafeSeaNet System Send Notifications (XML-based)

Information Request Types Port Used to get detailed information about a given port notification. As SafeSeaNet holds the complete information of a port notification, there’s no need to ask more information to the Member State (data provider) having originally sent the port notification. Therefore, SafeSeaNet will also act as data provider for the port notification information request.

Information Request Types Ship Used to get detailed information about a given ship notification. As SafeSeaNet holds the complete information of a ship notification, there’s no need to ask more information to the Member State (data provider) having originally sent the ship notification. Therefore, SafeSeaNet will also act as data provider for the ship notification information request.

Information Request Types HAZMAT Used to get detailed information about a given Hazmat notification. Upon receiving such request, SafeSeaNet will ask the actual data provider to send him the detailed information. SafeSeaNet will then send it back to the data requester.

Information Request Types Security Used to get detailed information about a given Security notification. Upon receiving such request, SafeSeaNet will ask the actual data provider to send him the detailed information. SafeSeaNet will then send it back to the data requester.

Information Request Types Alert Used to get detailed information about a given Alert notification. Upon receiving such request, SafeSeaNet will ask the actual data provider to send him the detailed information. SafeSeaNet will then send it back to the data requester.

Information Request Types Cargo Manifest Used to get detailed information about the cargo manifest of a given vessel. Upon receiving such request, SafeSeaNet will ask the actual data provider to send him the detailed information. SafeSeaNet will then send it back to the data requester.

Get Port Notification details Get Ship Notification details AIS MRS Get Hazmat Notification details Get Security Notification details Get Alert Notification details SITREP POLREP Waste Lost/Found Containers Others Get Cargo Manifest details Types of Information Requests:

Central SafeSeaNet System Data Provider SafeSeaNet Global Architecture – Information Requests (Browser-based) Data Requester Information Requests (Browser-based) S1: download file S2: XML-based

Central SafeSeaNet System Data Provider SafeSeaNet Global Architecture – Information Requests (XML message-based) Data Requester S1: download file S2: XML-based Information Requests (XML-based)

Notification Message (XML message-based) Port Authority:ABB Member State x National Contact Point NCA Web Server Data Centre Port Reporting LoCode: MSABB MS2SSN_Port_Not.xml SafeSeaNet Web Server SSN Certificate SSN Server Certificate 3. MS2SSN_Port_Not.xml Transactions Encrypted with SSN Certificate Connection Secured

Central SafeSeaNet Server Data Centre SSN Web Server SSN App. Server MSB Server Certificate 3. SSN Server Certificate Member State B Port Authority National Contact Point NCA Web Server SSN Certificate 5 MS2SSN_Haz_Res MSB Certificate SSN2MS_Haz_Req 4. SSN2MS_Haz_Req.xml 5. MS2SSN_Haz_Res.xml Information Request (Browser-based) Contd.

SafeSeaNet should aim at: a better detection of potential risk situations a better reaction in case of threat to maritime safety and the environment improved emergency response in case of incidents or pollution at sea improve controls of vessels in ports increased efficiency of port logistics (accurate ETAs, waste handling…) produce statistics for EMSA, Member States and the Commission