1
Nordic Expert Meeting on regional
Maritime Monitoring Cooperation
SafeSeaNet and relevant monitoring
project
Haugesund 25-26 October 2011
Lazaros Aichmalotidis
Head of Unit C.2
Vessel traffic and reporting services
2
What is SafeSeaNet?
SafeSeaNet is the community vessel traffic monitoring and information system, established by Directive 2002/59/EC.
It enables the EU Member States, plus Iceland and Norway, to exchange information on vessel traffic and cargo movements (notification and Request/Response mechanism)
Initiated in October 2004 and became fully operational in 2009
Operated by EMSA at Central level, by MSs at national level, Commission and MSs responsible for the policy related matters, role of the SSN HLSG and the SSN group
Around 17,000 ships per day tracked in European waters
Over 100 millions AIS positions per month recorded
3
Objectives of SafeSeaNet
Improve prevention and response to incidents, accidents or potentially dangerous situations at sea (incl. search and rescue operations)
Contribute to improved prevention and detection of pollution by ships
Its mandate has been extended and include, broadly:
maritime safety
marine environment protection
port and maritime security
efficiency of maritime traffic and maritime transport
4
Users of SSN
National Competent Authorities (NCA) in the MSs decide which national users can access the system
Users (Local competent Authorities: LCAs) include:
Maritime administrations
Ports
Vessel traffic monitoring centres
Maritime Rescue Coordination Centres (MRCC)
Coast Guards
Pollution survey centres
Other national users may be added under specific conditions
– Customs, border control, fisheries authorities, navies, etc.
currently more than 2000 users
5 5
AIS shore stations connected to SSN
Baltic
Region North Sea Region
727+ AIS shore stations Coverage across all coastal Member States
Mediterranean Sea Region
North Atlantic Region
6
SSN Graphical interface
7
To identify a specific ship
8
Hazmat details
9
SSN Pilots projects
• SSN/VMS synergies
• Exchange of VTS/Radar data through
SSN • BlueBelt
• IMDatE (Integrated Maritime Data
Environment)
I. SafeSeaNet /VMS Pilot Project
• General objective
– maritime safety, security, counter-pollution
– fisheries management
• Specific objective of Phase A “preparatory phase”
Explore the available synergies between VMS and SSN
Define the operational concept of a pilot project
Draft technical specifications
• Phase A participants - 3 Member States (FR, ES, IT)
– Meetings - Paris (29/6/09), Lisbon (9/9/09), Vigo 4/12/09), Madrid (31/5/10)
Legal background
• Directive 2009/17/EC (new carriage requirement, requiring fishing vessels above 15 m - to be equipped by 2013/2014)
• Council regulation No.1224/2009 “establishing a Community control system for ensuring compliance with the rules of the Common Fisheries Policy” provides a sound legal basis. Article 10 states that “MSs may use AIS data when such data are available for the purpose of cross-checking with other available data …. For that purpose MSs shall ensure that AIS data for fishing vessels flying their flag are available to their national fisheries control authorities”.
• Framework of “integrated maritime policy”
11
Benefits for exchanging VMS/SSN data
• AIS SSN messages more comprehensive than VMS
• High update rate (6 min)
• Free of charge (provided to the FMC via SSN without additional communication costs)
• The identity/position of a fishing vessel can be fully verified through two different „sensors‟
• A fishing vessel monitoring will be maintained even without VMS transmissions
• Benefits/ synergies should be further analyzed
12
13
SSN
Operational concept
Phase B - Operational Testing Phase
• Phase A concluded - all significant issues of the preparatory phase have been resolved. Technical implementation completed in Oct 2011
• EMSA is offering the correlation mechanism software (proxy)
• 5th SafeSeaNet High-Level Steering Group (Brussels, 14 April 2011) Commission invited the MSs to express their interest in Phase B “operational pilot phase”
• For the MSs, their participation creates no technical impacts on their systems, nor any financial implications
• Italy, Spain, Malta, Poland (tbc) and Norway participate in the “VMS/SSN synergies” pilot project Phase B “operational pilot”
• Phase B kick off meeting (Rome 11 Oct 2011)
14
Timetable
15
II. Exchange of radar data pilot project
Purpose of the SSN/VTS pilot project : test the potential for exchange of radar-based, VTS-type information between MSs with the objective to serve:
maritime safety,
security,
counter-pollution,
border surveillance and
fisheries management
Operational concept
• Radar images will be exchanged between MSs via SSN (in request/response mode);
• The SSN architecture/philosophy will be used to exchange radar traffic images between various coastal areas;
• Internationally accepted standards should be used (as far as possible, for the protocols and the message contents, suitably adapted to SSN).
17
Communication standards
• The IALA draft standard (called IVEF), which deals with point-to-point communications between VTSs. The IVEF standard used for radar exchange via SSN after certain modifications to the SSN Core and MS systems.
18
• The IEC standard, deals with the exchange of AIS data. Italy has developed a software interface for providing radar data to SSN using the IEC format. Started tests with EMSA using the IEC solution on the 14th of September 2010.
• Benefit of the IVEF: can be used for the exchange of radar data between any VTSs. IEC works only within SSN .
• EMSA is ready to support other MSs willing to apply the IEC solution
Sample of Italy VTS/SSN tests
Follow up actions
• IEC solution: all significant issues of the preparatory phase have been resolved. There are technical impacts on MSs systems and financial implications. No impact at EMSA.
• EMSA is ready to support MSs the IEC solution.
• IVEF solution: at national level, the manufacturer-specific server software need to be installed in VTS centres. There are costs associated to the development of server software to provide/receive VTS/radar data in the IVEF format. Consultation with each of the manufacturers would be required for each VTS involved in the pilot project.
• IVEF solution not ripe enough (from the MSs side and EMSA). Further developments on hold (activated when MSs willing to invest).
20
Internal
market
International
voyage
III. Blue Belt pilot project
Objective
General Stimulate Short Sea Shipping and contribute to facilitating vessels operating on intra-EU trading routes. Ships to be able to operate freely within the internal market with a minimum of administrative burden. Specific Provide custom authorities with vessel voyage information with an added degree of certainty regarding the ship whereabouts.
22
EU Custom Authorities Represented for all matters related to the implementation of the pilot project. The customs offices in those ports where the participating vessels will call are involved in the project. Shipping Industry – participating vessels The ECSA participates with 251 vessels („Blue Ships‟), Aim The project automatically monitors the participating ships and informs the customs authorities, before arrival, of the actual voyages followed and the last ports visited.
Participation
23
Delivers a notification report by e-mail to port customs authorities of the EU Member States for the participating vessels (251) Is divided into two phases: Phase 1 (2nd May – 30th June)
• Report is sent via email to custom authorities concerned in the port
of call, 2 hours before arrival. The report contains information about the vessel, its voyage and any status applicable (if any) under existing customs legislation
Phase 2 (1st July – 3rd November), in addition to the above
• Customs authorities receive information on ship behaviour (e.g. call
at third port, encounter at sea etc.) • Satellite-AIS will become available for additional ship tracking
information
Pilot Project
24
E-mail dispatch of Blue Belt report
25
E-mail report content
List of ship calls
Voyage summary Bremerhaven to Felixstowe
26
Conclusions /follow up actions
• System currently configured to provide warnings for all ships in the ECSA list. System sends e mail to the defined customs authorities list.
• Terrestrial AIS will be complemented by Satellite-AIS in case of gaps in the coverage of SSN or when a vessel is out of the range of coastal AIS receiving stations
• Satellite-AIS can be used as back-up of terrestrial AIS. Data will become available to SSN
• Upon successful assessment of the pilot
project, due at the beginning of 2012,
existing procedures may be reviewed
and adjusted in favor of a permanent
blue belt reporting system.
27
28
IV. IMDatE (Integrated Maritime Data Environment)
Main objectives:
To integrate existing maritime services (LRIT, SSN, CSN, THETIS) to fully exploit their cross-platform capabilities
To develop added-value services – on top of the integrated framework
Integrating Maritime Data
SafeSeaNet CleanSeaNet
THETIS LRIT DC
IMDatE
Combining data from different sources to provide a more complete maritime picture
29
30
Conceptual view
SSN maritime information
reporting
LRIT DC
long range tracking
CSN DC
oil spill detection
THETIS
port state control
Enterprise Bus – Structured Data Exchange
Exte
rnal
inte
rfac
es t
o a
pp
licat
ion
use
rs
IMDatE Configurable User Services
Vessel behaviour analysis
Vessel tracks and positions
Common User Management & Single
Sign-On
Service 1 : Ship Profile
Service 2 : Area Centric
Service 3 : Maritime Surveillance
Service n
Sat-AIS processing
Vessel validation
Data Fusion
Data Storage
Sys-to-sys interfaces
31
Combining position
32
33
Project Execution Timeline
18/11/2010 18/11/2013
2011 2012 2013
18/01/2012 - 18/11/2013
Maintenance
18/11/2010 - 18/01/2012
1 BOP V1
18/05/2011 - 18/03/2012
2 Satellite AIS
18/01/2012 - 18/11/2013
5 Enhancements
18/01/2012 - 18/11/2012
3 Added Value Services
18/03/2012 - 18/11/2012
4 Innovative Display