1 / 29

CETMEF-2008 - Common Shore-Based e-Navigation Architecture

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.

symona
Download Presentation

CETMEF-2008 - Common Shore-Based e-Navigation Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. 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

  3. IMO‘s e-Navigation Definition • „E-Navigation is the • harmonizedcollection, 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.”

  4. Maritime Fields Ship operation+ navigation proper ClassicalAids-to-Navigation Vessel TrafficServices (VTS) Search and Rescue /GMDSS Pilotage Maritime hazard abatement Port operations Security / ISPS The harmonization effect of IMO‘s e-Navigation concept • 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 ???? Vessel Traffic Management (VTM) ??? Complete List: Compare e.g. Annex 2 of Annex 12 of report IMO-NAV54

  5. The overarching • e-Navigation • architecture

  6. The three sides of the coin “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)

  7. E-NavAppli- cation E-NavAppli- cation E-NavAppli- cation E-NavAppli-cation E-NavAppli-cation E-Nav Appli-cation Link technology proper Data sources Data sinks Shore-based eNav services The complete picture e.g. VTS Center „External“ system(s): Position, Velocity, Timing (PNT); World Wide Radio Navigation System (WWRNS) Shore-basede-Navigation system other ships PhysicalLink (e.g. radio link) Shipborne Rx/Tx station INS otherships Application-to-application (peer-to-peer) functional connection Other shore-basede-Navigation system(s)

  8. Peer-to-peer functional connection shore-based operator  mariner Peer-to-peer functional connection(e.g. voice communications) e.g. VTS Center Link Shore-based e-Navigation system Shipboardapplication Ship- boardTrans- ceiver User InteractionService VHF Communi-cation Service Added-ValueData ProcessingServices Other sensor services ShipborneSensors Gateway Service Other sensor services Deployed and operated by shore-based competentauthority Third party users Physical path

  9. Functional connection shipboard sensors  shore-based operator Peer-to-peer functional connection(e.g. AIS monitoring) e.g. VTS Center Physical path Link Shore-based e-Navigation system Shipboardapplication Ship- boardTrans- ceiver AIS Service Added-ValueData ProcessingServices User InteractionService Other sensor services ShipborneSensors Gateway Service Other sensor services Deployed and operated by shore-based competentauthority Third party users

  10. Functional connection shipboard application  shore-based application Peer-to-peer functional connection(e.g. AIS application specific messages) e.g. VTS Center Physical path Link Shore-based e-Navigation system Shipboardapplication Ship- boardTrans- ceiver AIS Service Added-ValueData ProcessingServices User InteractionService Other sensor services ShipborneSensors Gateway Service Other sensor services Deployed and operated by shore-based competentauthority Third party users

  11. Functional connection shore-based installation  mariner Peer-to-peer functional connection(e.g. Visual Aids-to-Navigation) e.g. VTS Center Physical path Link Shore-based e-Navigation system Shipboardapplication Ship- boardTrans- ceiver Visual Aids-to-Navigation Service User InteractionService Added-ValueData ProcessingServices Other sensor services ShipborneSensors Gateway Service Other sensor services Deployed and operated by shore-based competentauthority Third party users

  12. Functional connection between shore-based applications e.g. VTS Center Link Shore-based e-Navigation system Shipboardapplication Ship- boardTrans- ceiver AIS Service Added-ValueData ProcessingServices User InteractionService Radar Service Physical path ShipborneSensors Gateway Service Other sensor services Deployed and operated by shore-based competentauthority Third party users Peer-to-peer functional connection(e.g. data exchange between authorities)

  13. The complete picture refined – user-requirement driven design Operational Requirement – Fulfillment by provision of Human Machine Interface Aids-to-Navigation Applications Including VTS Engineering modeling of shore-based e-Nav system (architecture + technologies + interfacing + life-cycle-management)

  14. Zoom-In:Developing a commonshore-based e-Navigation system architecture

  15. E-NavAppli- cation E-Nav Appli- cation E-NavAppli- cation Shore-based e-Nav service Master complexity! - How? PhysicalLink (e.g. radio link) Encapsulation of complexity for shore-based e-Navigation applications Standardised interfaces Point of view from ashore Standardised „signal-in-air“ specifications

  16. Fundamental design principles /1 shore based e-Navigation system f(x) Deployed and operated by shore-based competentauthority Thinking in user-requirement driven functionality(not technology) – What?! – instead of How?!

  17. Fundamental design principles /2 Deployed and operated by shore-based competentauthority User-requirement drivendesign - employing the object orientation and top-down functionality analysis

  18. Fundamental design principles /3 shore based e-Navigation system One holistic, common,service-oriented, and client-server shore-based e-Navigation system architecture Deployed and operated by shore-based Competentauthority

  19. Fundamental design principles /4 Deployed andoperated byshore-based competentautority HolisticLife-cyclemanagement

  20. Zoom Out:Embedding the common shore-based e-Navigation system architecture innational, regional, and global topologies

  21. Embedded in national, regional, and global topologies e.g. LRIT or IALA-NET e.g. EU-SSN e.g. HELCOM Deployed andoperated byown authority

  22. IALA‘s role • (IALA = International Association of Marine Aids-to-Navigation and Lighthouse Authorities)

  23. Development of common shore-basede-Navigation system architecture /1 IMO‘s invitation toIALA for participationin the implementationof e-Navigation Long standing mandate of IALA for mutual support ofAids-to-Navigation/VTS authorities(IALA national membership) IALA Contributionsto IMO documents (future)IALA Recommendations, IALA Guidelines +IALA Manuals on e-Navigationfor IALA National Members IALA activities fore-Navigation

  24. Development of common shore-basede-Navigation system architecture /2 • 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

  25. Development of common shore-basede-Navigation system architecture /3 • „Draft IALA Recommendation e-NAV 101 • on 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

  26. Summary and • concluding remarks

  27. Fundamental statements appliedto the „three sides of the coin“ 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 source to ultimate information sink)

  28. User requirements / peer-to-peer applications – not so much new under the sun!?“ existing definitions needs to be inter- nationally documen-ted and harmonised existing, well-known user requirements + applications: VTS, Aids-to-Navigation, AIS integration, radio navigation, shore data exchange Need to be created, evaluated and internatio-nally defined genuinely new e-Nav user-requirements + e-Nav applications

  29. Thank you for your attention!Questions?

More Related