cetmef-2008 - common shore-based e-navigation architecture dipl.-ing. jan-hendrik oltmann deputy...
TRANSCRIPT
CETMEF-2008 -Common Shore-Based e-Navigation Architecture
Dipl.-Ing. Jan-Hendrik Oltmann
Deputy Head of Traffic Technologies and Telematics Division German Federal Waterways and Shipping Administration+Chair, Architecture Technical Working Group of IALA e-Navigation Committee
Presentation Overview
• What is e-Navigation?
• The full picture: The overarching e-Navigation architecture
• Zoom-In: Developing a common shore-based e-Navigation system architecture
• Zoom-Out: Embedding the common shore-based e-Navigation system architecture in national, regional, and global topologies
• IALA‘s role
• Summary and concluding remarks
IMO‘s e-Navigation Definition
„E-Navigation is the
harmonized collection, integration, exchange, presentation and analysis of maritime information
onboard and ashore
by electronic means
to enhance berth to berth navigation and related services
for safety and security at sea and protection of the marine environment.”
Vessel Traffic Management (VTM) ???
The harmonization effect of IMO‘s e-Navigation concept
Sh
ip o
per
atio
n+
nav
igat
ion
pro
per
Cla
ssic
alA
ids-
to-N
avig
atio
n
Ves
sel
Tra
ffic
Ser
vice
s (V
TS
)
Sea
rch
an
d R
escu
e /
GM
DS
S
Pil
ota
ge
Sec
uri
ty /
IS
PS
Po
rt o
per
atio
ns
Mar
itim
e h
azar
d a
bat
emen
t
e-Navigation
Globalharmonization
„common globallanguage“
defined levels offunctionality
defined levels of service quality
quality improve-ment by error avoidance
look-ahead:auditing, certification,(V)IMSAS ????
Maritime Fields
Complete List: Compare e.g. Annex 2 of Annex 12 of report IMO-NAV54
The three sides of the coin
ComputerComputer
Domäne
“harmonized collection, integration, exchange, presentation and analysis of maritime information
onboard”
“harmonized collection, integration, exchange, presentation and analysis of maritime information
ashore”
“exchange”
= virtual/ physical link(s)
Other shore-basede-Navigation system(s)
Shore-basede-Navigation system
„External“ system(s): Position, Velocity, Timing (PNT); World Wide Radio Navigation System (WWRNS)
Shipborne Rx/Tx station
Datasources
Datasinks
INS
Shore-based eNavservices
PhysicalLink (e.g. radio link)
otherships
otherships
Link technology proper
E-NavAppli-cation
E-NavAppli-cation
E-NavAppli-cation
E-NavAppli-cation
E-NavAppli-cation
E-NavAppli-cation
Application-to-application (peer-to-peer) functional connection
The complete picturee.g.
VTS
Center
Shore-based e-Navigation system
User InteractionService
LinkVHF Communi-cation Service
Ship-boardTrans-ceiver
ShipborneSensors
Shipboardapplication
Other sensor services
Added-ValueData ProcessingServices
Peer-to-peer functional connection shore-based operator mariner
Peer-to-peer functional connection(e.g. voice communications)
Physical path
Other sensor services
Gateway Service
Deployed and operated by shore-based competentauthority
e.g. VTS Center
Third party users
Functional connection shipboard sensors shore-based operator
Shore-based e-Navigation system
User InteractionService
Link AIS Service
Ship-boardTrans-ceiver
ShipborneSensors
Shipboardapplication
Other sensor services
Added-ValueData ProcessingServices
Peer-to-peer functional connection(e.g. AIS monitoring)
Physical path
Other sensor services
Gateway Service
Deployed and operated by shore-based competentauthority
e.g. VTS Center
Third party users
Functional connection shipboard application shore-based application
Shore-based e-Navigation system
User InteractionService
Link AIS Service
Ship-boardTrans-ceiver
ShipborneSensors
Shipboardapplication
Other sensor services
Added-ValueData ProcessingServices
Peer-to-peer functional connection(e.g. AIS application specific messages)
Physical path
Other sensor services
Gateway Service
Deployed and operated by shore-based competentauthority
e.g. VTS Center
Third party users
Functional connection shore-based installation mariner
Shore-based e-Navigation system
User InteractionService
LinkVisual Aids-to-Navigation Service
Ship-boardTrans-ceiver
ShipborneSensors
Shipboardapplication
Other sensor services
Added-ValueData ProcessingServices
Peer-to-peer functional connection(e.g. Visual Aids-to-Navigation)
Physical path
Other sensor services
Gateway Service
Deployed and operated by shore-based competentauthority
e.g. VTS Center
Third party users
Functional connection between shore-based applications
Shore-based e-Navigation system
User InteractionService
Link AIS Service
Ship-boardTrans-ceiver
ShipborneSensors
Shipboardapplication
Other sensor services
Added-ValueData ProcessingServices
Physical pathRadar Service
Gateway Service
Deployed and operated by shore-based competentauthority
e.g. VTS Center
Third party users
Peer-to-peer functional connection(e.g. data exchange between authorities)
Shore-based competent authority
„third party“ requesting data = information sink
Shipboard technical
equipmentsupporting
eNAV
Shipboard user
HMI
Stated operational / userrequirement
Operational PresentationSurface provided by shipboard technical equipment
Shore-based e-Navigation system(including technical maintenance)
VTS Operator
HMI
Stated operational / userrequirements
Operational PresentationSurfaces provided by shore-based e-Nav System
VTMIS Operator
HMI
MRCC Operator
HMI
Individualtechnical
eNAV services
Technical maintenance
personnel
Individualtechnical
eNAV services
Individualtechnical
eNAV services
Shore-based Operator X
HMI
etc
etc
Physical links
(various technologies)
Other shore-basedSystem
Operatorof Third Party
HMI
M2M
requested data from „third party“ = information source
Other shore-based
System
M2M Stated operational requirements
Inter-systemdata exchange(machine-to-machine)
Ship-side Links Shore-Side
Peer-to-Peer e-Nav applications
The complete picture refined – user-requirement driven design
Operational Requirement – Fulfillment by provision of Human Machine Interface
Aids-to-Navigation ApplicationsIncluding VTS
Engineering modeling of shore-based e-Nav system
(architecture + technologies + interfacing + life-cycle-management)
Point of viewfrom ashore
Encapsulation of complexity for shore-based e-Navigation applications
Master complexity! - How?
Shore-based e-Navservice
PhysicalLink (e.g. radio link)
E-NavAppli-cation
E-NavAppli-cation
E-NavAppli-cation
Standardisedinterfaces
Standardised„signal-in-air“ specifications
Value-addedData
ProcessingServices
User Interaction
Service
Gateway Service
DataCollectionand DataTransferServices
Maritime Traffic Technology System
Traffic objects,including
ships
Primaryusers
Shore based„third party“ users
f(x)
shore based e-Navigation system
Fundamental design principles /1
Deployed and operated by shore-based competentauthority
Thinking in user-requirement driven functionality (not technology) – What?! – instead of How?!
User Interaction
Service
Gateway Service
DataCollectionand DataTransferservices
eNAV-Concept’s common shore based architecture
Traffic objects,including
ships
PrimaryUsers
Shore based„third party“ users
User Interaction
Service
Gateway Service
DataCollectionand DataTransferservices
Traffic objects,including
ships
PrimaryUsers
Shore based„third party“ users
Service X
laws;regulations;
policies
Business Processesof the Administration
Systemlevel requirements
Services
Shipping
Component requirements
Componentof Service X
Otherexternalusers
Service requirements of Service X
Essential Systemlevel requirements
Shore-based e-Navigation system
Fundamental design principles /2
User-requirement driven design - employing the object orientation and top-down functionality analysis
Deployed and operated by shore-based competentauthority
Value-addedData
Processingservices
User Interaction
Service
Gateway Service
DataCollectionand DataTransferservices
Traffic objects,including
ships
PrimaryUsers
Shore based„third party“ users
Deployed and operated by shore-basedCompetentauthority
One holistic, common,service-oriented, and client-server shore-based e-Navigation system architecture
Fundamental design principles /3
shore based e-Navigation system
Fundamental design principles /4
Value-addedData
ProcessingServices
User Interaction
Service
Gateway Service
DataCollectionand DataTransferServices
Maritime Traffic Technology System
Traffic objects,including
ships
Primaryusers
Shore based„third party“ users
HolisticLife-cyclemanagement
Deployed andoperated byshore-based competentautority
Zoom Out:
Embedding the common shore-based e-Navigation system architecture innational, regional, and global topologies
Embedded in national, regional, and global topologies
International (GLOBAL)
Regional (1)
Regional(2)
Regional(3)
Regional(N)
Natio-nal (1)
Natio-nal
Natio-nal
Natio-nal
Natio-nal
Natio-nal
Local Other
Deployed andoperated byown authority
e.g. HELCOMe.g. EU-SSN
e.g. LRIT or IALA-NET
IALA‘s role
(IALA = International Association of Marine Aids-to-Navigation and Lighthouse Authorities)
Development of common shore-basede-Navigation system architecture /1
(future)IALA Recommendations,
IALA Guidelines +IALA Manuals on e-Navigation
for IALA National Members
Long standing mandate of IALA for mutual support of
Aids-to-Navigation/VTS authorities(IALA national membership)
IMO‘s invitation toIALA for participationin the implementation
of e-Navigation
IALA Contributionsto IMO documents
IALA activities fore-Navigation
IALA‘s goals regarding e-Navigation:
– To co-ordinate the implementation of e-Navigation for international, shore-based stake-holders, globally.
2. Prepare IALA itself for the implementation of e-Navigation=> „Thinking in e-Navigation on a global scale“
3. Prepare IALA (national) members for the pending implementation of e-Navigation => Recommendations, Guidelines, Manuals for IALA membership on e-Navigation
Development of common shore-basede-Navigation system architecture /2
„Draft IALA Recommendation e-NAV 101on the e-Navigation Architecture – the Shore Perspective“
Content overview:
- the double mandate of IALA
- driving forces
- fundamental principles: overarching and shore-based system architecture
- impact of e-Navigation on IALA as an organization, and its documentation
- dependencies: GNSS/WWRNS, infrastructure
Development of common shore-basede-Navigation system architecture /3
Fundamental statements appliedto the „three sides of the coin“
ComputerComputer
Domäne
Internationally agreed, holistic, flexible, and common
shore-based e-Navigation system architecture
Internationally agreed, precise and open link
descriptions („signal-in-air“)
focus on applications (Information flow peer-to-peer
= from ultimate information sourceto ultimate information sink)
User requirements / peer-to-peer applications – not so much new under the sun!?“
existing, well-knownuser requirements
+ applications:VTS, Aids-to-Navigation,
AIS integration, radio navigation,
shore data exchange
genuinely new e-Nav user-requirements + e-Nav applications
Need tobe created, evaluated
and internatio-
nally defined
existing definitions needs to be
inter-nationally documen-
ted and harmonised