NCA s scope for E-nav and digital route service

Transkript

1 NCA s scope for E-nav and digital route service John Morten Klingsheim senior engineer Kystverket Region West, Senter for pilotage and VTS 17th January 2019

2 E-nav Maritime communication Maritime information Harmonization To enhance berth to berth navigation

3 E-nav Maritime communication Maritime information Harmonization To enhance berth to berth navigation Land - Sea - Air

4 National Budget Safety/security - Wealth creation - Transition to low emission society - Renewal and improvement - Welfare services - Business

5 NCA s work on e-nav - IMO/IALA - IHO - EMSA - National/international cooperation authorities/industry/academia, e- Nav conference - ITS-Norway - World ITS Copenhagen St.prp 1 (Samferdselsdepartementet)

6 Reporting and Information Services - NCA s information services for maritime users - Scope: Safe and competitive sea transport (economically and sustainable). - Based on St.prp 1, Sjøsikkerhetsmeldingen På rett kurs

7 Digitalization and digital vulnerability

8 A short and a long perspective Maritime single window 200x xx t 0 Arrival / Departure / Hazmat Maritime Stakeholders Pilot services Single Window for Authorities and Trade Collaboration & interaction Ports & Port facilities Collaboration & interaction Automation

9 - Routeinfo - New service launched 24. september 2018

10 Purpose of establishing recommended routes «Anbefalte seilingsruter» - Safety at Sea: Important information for navigation more accessible for the navigator, and better exchange of information between crew on bridge. Based on Sjøsikkerhetsanalysen , actions 1C and 1D - «Tiltak som trafikkseparasjon (TSS), anbefalte ruter, aktsomhetsområder, og forbudsområder kan bidra til å redusere kompleksiteten av arbeidsoppgavene på bro. I tillegg vil anbefalte ruter redusere sannsynligheten for en feilhandling eller feilvurdering.» (hentet fra Årsaksanalysen). - Tiltak 1C: Utveksle seilingsinformasjon mellom fartøy, los og VTS Tiltak 1D: Gjøre informasjon lettere tilgjengelig for navigatør - Also have a potential to make a more predictable traffic within VTS-areas. Sjøsikkerhetsanalysen , 015/November/Peker-ut-viderekurs-for-arbeid-med-sjosikkerhet/

11 The process to establish recommended routes Henter inn AIS-informasjon Tar mot innspill fra brukere Dataflyt - Ruter Input/brukerbehov: - nye ruter fra-til, - grensesnitt/layout - merknader til rutevalg/waypoints Quality assured by NCA Utarbeider forslag i ECDIS Kvalitetssikring av forslag i losverktøy Redaksjon (Senter for Los og VTS) Forslag til Rute (RTZ) Navigatører / brukere (referansegr uppe) Losdrift Trefikksentraltjenesten FFM/nautisk ved region Kvalitetssikret rute (RTZ) + External check: 1. Quality of charts for the route (depths) and any available depth data by Norwegian Hydrographic Service (Kartverket) 2. Users and NGOs (Rederiforbundet, Kystrederiene, Forsvaret) for any input Administrasjon av ruter Redaksjon (Senter for Los og VTS) Publiserte ruter i rutetjeneste RTZ Navigatører / brukere Ruteinformasjon (eksemepl: lokale begrensninger i lospliktforskriften)

12 Route information in Routeinfo Locations: Ports (SafeSeaNet Norway including places at sea and Anchorages Port facilities (NCA s register of ISPS port facilities) Quay s.: registered in SafeSeaNet Norway by the ports) Regulations not available in nav.chart/enc: PEC (Pilot Excemption Certificate) VTS (within service areas for Vessel Traffic Centers) Sailing distance

13 Technical solution Basic concept Ruter i Kystverkets database N.mil SQL Redaksjon (GIS (Web eller desktop software) RTZ 1.1 RTZ 1.0 / 1.1 / 1.1 ext SQL N.mil Navigatør som spør etter distanser Http server RTZ 1.0 / 1.1 / 1.1 ext RTZ 1.1 SQL RTZ 1.0 / 1.1 / 1.1 ext Redaksjon (ECDIS) RTZ 1.1 RTZ 1.0 / 1.1 / 1.1 ext Filserver / epostserver RSS, abonnement / varsling Losdrift (PPU/ECDIS)?????? Navigatør som spør etter ruteforslag Eksterne tjenester, videreforedling

14 Test September - December 2018 (navigator, pilot, VTS) Test goals: To assure the routes comes up on navigation platforms in a good way. To check any file-format issues. To assure that the service gives the wanted support to navigation. To establish grounds for seamless update of recommended routes on vessels. PS: NCA today has not infrastructure for route exchange! From the testing: File name longer than 25 signs can cause problems on some ECS. «validityperiodstart» and «validityperiodstop» seems not to mean anything in some navigation platforms. Only the file name is easily accessible for the navigator. Other route information quite hidden. Waypoints of course easy accesible.

15 Recommended routes and route information Smart distribution of recommended routes. Status and the way forward! Kystverket and Sjöfartsverket

16 Routeinfo - Infrastructure https: For secure communication over internet RTZ: Single choosen routes or all routes altogether default RTZ 1.0, RTZ 1.1 can be relevant for STM-vessels, filename includes 11 in the end, also set within the file. A log on changes: ID number as key for updates. Log to include other needed information. Valid until to assure update on vessel.

17 Routes, RTZ - Data model used in Routeinfo Datamodel for RTZ ver 1.0 (IEC 61174: Validity Period

18 The way forward and input to NCA s route service Test-results Dec 2018/Jan 2019 A version 2 of routeinfo early 2019: - ambition to have quality assured recommended routes for Skagerrak and Rogaland - with development on functionality and route information, especially for seamless distribution.

19 Demo / Video

20 Thanks!