While the audience is gathering. During breaks etc While the audience is gathering. During breaks etc. Simple messages can be added in bold and white letters on the dark blue sea, eg. ”Welcome!”, ”Back at 15.15”

HOW-TO Use VIS Design for different operational purposes VIS = Voyage Information Service Current version is VIS Design v2.2 ed 2 (v2.2.2) This HOW-TO describes the functionality and interfaces in VIS Design and the possibility to constrain specific service instances to a limited set of allowed methods based on the operational context. The Voyage Information Service is in this context seen as the information (exchange) service that supports an operational service. Operational Service Information Service Data

WHY use VIS Design The ECDIS manufactures have implemented VIS Design (v2.2) and are interoperable with all services designed upon the VIS Design 2.2. EMS,ROS,RCS,PRS,ICE,PORTSYNCH, etc Voyage Information Service RTZ TXT S124

WHAT contains VIS Design VIS “producer” VIS “consumer” Share (send) Voyage Plan uploadVoyagePlan Send Text Message uploadTextMessage Send Area Message uploadArea subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK Receive ACK

Typical use of VIS Design Depending on the operational use of the Voyage Information Service, different sets of methods are valid. A specific service instance based on VIS Design cannot add another method and still stay compatible with VIS A specific service instance based on VIS Design can constrain the scope by returning HTTP 405 “Method not allowed” if a certain method is not valid or handled.

Typical use for a SHIP VIS “producer” Share (send) Voyage Plan Send Text Message Typically a “STM ship” allows all methods in VIS. Share (send) Voyage Plans Send Text Messages Send voyage plans on request (get) Handle subscription request on voyage plans Receive uploaded Voyage Plan Receive uploaded Text Message Receive uploaded Area (S124) Send ACK when uploaded message is forwarded to application Send Area Message subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK

Typical use for a Shore Centre (Enhanced Monitoring) VIS “producer” Share (send) Voyage Plan A shore centre is this context is a e.g. VTS providing Enhanced Monitoring Service Send Text Message Send Area Message subscribeToVoyagePlans A typical “STM Shore Centre” providing Enhanced Monitoring service have the following set of functions (interfaces) Send proposed Voyage Plans Send Text Messages Send Area (S124) messages Receive uploaded Voyage Plan Receive uploaded Text Message Receive uploaded Area (S124) Send and receive ACK removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK

Typical use for a continuous Route Optimization provider VIS “producer” In this context a “continuous” optimization provider is statefull and optimizes incoming voyage plan and regularly sends an optimized route based on contract. E.g. a optimized route every day at noon based on latest weather forecast along route. Share (send) Voyage Plan Send Text Message Send Area Message subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans A typical “STM Route Optimization” service have the following set of functions (interfaces) Send optimized Voyage Plan(s) Send Text Message Handle subscription request Receive uploaded Voyage Plan Receive uploaded Text Message Send and receive ACK getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK

Typical use for a “on request” Route Optimization provider VIS “producer” In this context a “on request” optimization provider is stateless and optimizes incoming voyage plan and then forgets it. Share (send) Voyage Plan Send Text Message Send Area Message A typical “STM “on request” Route Optimization” service have the following set of functions (interfaces) Send optimized Voyage Plan(s) Send Text Message? Receive uploaded Voyage Plan Receive uploaded Text Message? Send and receive ACK subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage Will a typical “on request” optimization provider handle Text Messages? uploadArea Send ACK Receive ACK

Typical use for a “on request” Route Check provider VIS “producer” In this context a “on request” cross check provider is stateless and checks incoming voyage plan and then forgets it. Share (send) Voyage Plan Send Text Message Send Area Message A typical “STM “on request” Route Cross Check” service have the following set of functions (interfaces) Send Text Message Receive uploaded Voyage Plan Send and receive ACK subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage Will a typical “on request” cross check send a voyage plan? uploadArea Send ACK Receive ACK

Typical use for a Route Catalogue provider VIS “producer” Share (send) Voyage Plan Send Text Message Send Area Message A typical “STM Route Catalogue” service have the following set of functions (interfaces) Receive uploaded Voyage Plan Handle subscription request on voyage plans Send voyage plan template or snippet Handle request of voyage plans (get) Send and receive ACK subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK

Typical use for a Port Call Synchronization provider VIS “producer” Share (send) Voyage Plan Send Text Message Send Area Message A typical “STM Port Synchronization” service have the following set of functions (interfaces) Receive uploaded Voyage Plan Send proposed voyage plan Send and receive ACK subscribeToVoyagePlans removeSubscriptionToVoyagePlans findSubscriptionToVoyagePlans getVoyagePlans uploadVoyagePlan uploadTextMessage uploadArea Send ACK Receive ACK

At the end – you could add text in black like ”Thank You !”