Status Report Finland HelCom AIS EWG

Status Report Finland HelCom AIS EWG 4.10.2011

Agenda item 3 HELCOM AIS status in Finland 31 BS along the coastline and 8 BS in the lake Saimaa area HelCom proxy is now included into the national AIS network service contract. Maintenance response time for national network less than 6 hours Maintenance response time for HelCom proxy less than 1 day Maintenance response time for single base station less than 5 days 30.8.2011 Kaisu Heikonen 2 Liikenteenhallinta

Agenda item 4 Access to and use of AIS information EfficienSea Status of the dynamic risk analysis project; separate presentation WP6 Tommi Arola 30.8.2011 Kaisu Heikonen 3 Liikenteenhallinta

Agenda item 4 Access to and use of AIS information HELCOM AIS statistics Report from the Finnish Meteorological Institute HELCOM AIS statistics: separate presentation AIS Analysis JP Jalkanen 30.8.2011 Kaisu Heikonen 4 Liikenteenhallinta

Agenda Item 9 Maintaining and further development of HELCOM AIS - HELCOM AIS stream EUROPEAN INTEGRATED MARITIME SUVEILLANCE INITIATIVE In October 2010 the European Commission presented a draft roadmap on the establishment of a common information sharing environment for maritime surveillance (CISE), COM(2010) 584 Two parallel pilot projects has been established to test in a theatre of operations how integrating maritime surveillance can work in practice. One in the Mediterranean basin and another in the Northern European Sea Basins (MARSUNO). 30.8.2011 Kaisu Heikonen 5 Liikenteenhallinta

30.8.2011 Kaisu Heikonen 6 Liikenteenhallinta

MARSUNO project 30.8.2011 Kaisu Heikonen 10 Liikenteenhallinta

MARSUNO layer 2 (VTMIS) objectives MARSUNO layer 6 MSA expects us to provide information about: Information available in VTMIS layer information needs in VTMIS layer possibilities to share information cross sectoral and cross boarder + information available and information needs of the national single window users our own expectations to enhance safety at sea: by harmonizing operation of various reporting systems (VTS, SRS) to a level where ships navigators perceive all the systems as one by enhancing automatic information sharing and exchange between reporting systems in order to reduce administrative burden onboard

MARSUNO layer 2 VTMIS Sub-task 1 Information exchange between traffic monitoring systems Inventory of information available in existing systems and information that is already exchanged Harmonise ship reporting (content of reports) Harmonise information services to ships (from VTS/SRS) Identifying the obstacles

MARSUNO layer 2 VTMIS Sub-task 2 Harmonising VTS operations and sharing best practices VTS training, operational procedures and technical requirements Arrange operator exchange and study visits Develop joint operational procedures between authorities

MARSUNO layer 2 VTMIS Sub-task 3 Technical integration of systems Existing systems (e.g. SafeSeaNet) Concepts, (e.g e- navigation, e-maritime) Previous and ongoing projects (e.g. Marnis,Blast, EffienSea) Defining the information to be exchanged Agreeing the required technical specifications for systems integration

MARSUNO layer 2 VTMIS Sub-task 4 Results Agreeing and documenting a action plan for integration and harmonisation of VTMIS Demonstrating information exchange between some project partners Demonstrating single window Internet service for vessels Arranging conference to communicate results and to ensure positive development ENC, SENC Weather services Cargo related Service providers SSN++ SafeSeaNet Server Sirenac Equasis Navigational information National SW Port/flag state auth. Other authorities MOS Port VTM Port SW RIS Customs SW PCCS CCS Port authorities Source: MARNIS

MARSUNO layer 2 VTMIS results/findings Main cross-border information exchange systems for VTS and SRS centers in the Baltic area: SafeSeaNet HELCOM AIS Identified future information exchange need: Planned routes of the vessels Route information would be possible to exchange via HELCOM AIS using Application Specific Messages message type 8, FI 27 ref. IMO SN.1/Circ.289 Guidance on the use of application-specific messages