Develop and anchor standards and guidelines.

A standard voyage exchange format is established to be used in different services using parts of voyage exchange format in its realization. The voyage exchange format builds further on the route exchange format.

Standard IEC 61174 ed 4 needs to complemented with a format for the exchange of a route segment in AIS ASM compatible format.

Add procedure in IALA VTS operating procedures

Specification and standard of the initial Voyage object.

Directive 2010/65/EU of the European Parliament and the Council Decision of 20 October 2010 on reporting formalities for ships arriving in and/or departing from ports of the Member States and repealing Directive 2002/6/EC: It should be noted that this Directive aims to simplify and harmonise the administrative procedures applied to maritime transport by establishing a standard electronic transmission of information and by rationalising reporting formalities for ships arriving in and ships departing from European Union (EU) ports. EU countries shall accept electronic reports via a single window as soon as possible and, at the latest, by 1 June 2015. The single window will be the place where all information is reported once and made available to various competent authorities and the EU countries. EU countries must ensure that information received in accordance with reporting formalities is made available in their national SafeSeaNet systems and make available parts of such information to other EU countries via the SafeSeaNet system.

The establishment of SeaSWIM has to address the creation of an appropriate organisational structure for the implementation and operation SeaSWIM; legal basis for the implementation of SeaSWIM would be made possible by the Rule Book or the SeaSWIM contract. The Rule Book would ensure a clear environment ensuring the trust of the involved stakeholders.

IMO Convention provisions tailored to accommodate the new concepts, namely SOLAS Reg V/28+ IMO FAL convention.

Port call synchronization and green / right steaming requires a change in existing contract templates (charter parties) providing incentives for just-in-time approaches and establishing / communicating / committing to port of readiness.

A standardised port call format is to be established supporting the ship-to-shore, shore-to-ship, and shore-to-shore interaction supporting port call synchronization.

This is a new area that needs to be specified
Could be part of IHO S 121

Functional requirement for displaying safety information

A liability regime, possibly through a contractual arrangement, needs to be established. The liability questions is anticipated to be similar to liability issues for existing VTS and pilotage services.

The national competent authority, NCA, issues authorization to service provider following the standardised procedures and values.

The standard is a subset of the Voyage Information format standard. Covers all facts and specefications of the vessel needed for carrying out STM services (e.g Voyage Optimisation, Port call Synchronisation, etc). Exisisting services like Q88.com, SIRE, FairPlay.

Nautical information of an area should be available in a standard format. Today, it is in paper form or not standard format.

All manufacturers of ECDIS and NAV systems have their own format elaborating and presenting routes. In order to eliminate errors and misinterpretations a new standardized format (IEC 61174 ed 4) has been developed within the Monalisa Project and can now freely be used by any vendor.

Definition of roles, consider VTS TOS

A common format for voyage id�s is essential to ensure that relevant actors share information about the same unit of analysis, the voyage, and to enable that information associated with the voyage can be bundled to one and the same voyage. Such common format must be established and acknowledged by key actors in the maritime sector.

Establish organisation that will have the overall responsibility of governing voyage IDs from time of registering the voyage till the end of that voyage.

The establishment of SeaSWIM has to address the creation of an appropriate organisational structure for the implementation and operation of SeaSWIM function. Careful consideration must be given regarding the SeaSWIM organisation’s mission, actions, structure and performance. All the indicated aspects are important for the organisation to be viewed as trustworthy and reliable, which contribute to it being accorded legitimacy for it to be trusted by businesses and authority.

Identify or establish organisation(s) that is responsible of issuing Voyage ID’s.

The issuer of voyage ID�s is the one that associate a certain ID to the voyage. The preferred way is to allow the actor that initiate a voyage to have his/her own number serie of voyage ID�s granted by the governance body (see EN-130).

Quality standards indicating requirements, specifications, guidelines or characteristics must be identified to ensure that the SeaSWIM services are fit for each of their purpose. Such standards are generally referred to as the evaluative standards that enable the users to assess service providers and their service quality. The discussion on quality standards also leads to the process of certification that is used to demonstrate compliance with the standards. It has been defined as �the successful conclusion of a procedure to evaluate whether or not an activity actually meets a set of requirements�. Certification simply refers to quality assurance which can either be provided by the service provider itself or by an assessment by a third party.

For providing historical data, regulations for third party usage must be established, e.g. commercial sensitive data.

The specification of SeaSWIM services, core and STM-compliant services, builds upon a standardized service specification language. The language constitutes the ontology of how to describe a service.

Guidelines for liability and responsibility to ensure voyage information correctness need to be established. The source of voyage information, and thereby the one that regulates the management of voyage information by others, is the shipping company. The shipping company is the owner of voyage information why there needs to be routines established to ensure that the information associated with the voyage is managed in a correct way (see EN-109).

IMO to issue standards for this cross-check protocol and to be implemented in IMO 893(21).

To share routes or route segments is a cornerstone in enhancing several services described in STM. To increase incentives for route exchange it is important that ships/shipping companies receives benefits from sharing their route. Examples of incentives could be reduced need for manual reporting, or coastal/port states discount on fairway, pilotage or port fees. Also insurance companies, getting benefits from increases safety, may offer incentives for ships.that take part in route exchange and associated services like enhanced monitoring and route cross-checking.

Dynamic separation of traffic, when traffic density is low and safety precautions allows it, requires revision of IMO regulations for TSS and possibly other ships routeing sytems

Established federation for the definition of which data to share and to quality assure that information sharing is made in a trustworthy way,

Guideline, procedures and criterias needs to be developed with regards to number of waypoints to be exchanged, etc. The procedures and criterias needs to tested and validated in testbeds and simulator trials.

Develop procedures on how the nomination of collaborators are to be executed.

All actors within the STM needs to be identified in order for the collaborators to �discover� them and for the STM information system to know where and to who the information is to be distributed.

Operating procedures for shore based personnel.

Add procedure in IALA VTS operating procedures

Modernise todays procedures

Procedures for onboard, shore and ship shore interaction. Use and update IALA VTS TOS procedures

The identity registry needs to be structured in accordance with actor characteristics. The role of a certain actors in the Sea Traffic Management ecosystem forms the basis of such characterization (as e.g. port, port actor, etc.) and then further appropriate specialisations.

A commonly accepted process for including a service in the service registry of a particular service as it has been approved for being provided in the STM eco-system.

Develop procedures and rules on how to issue and use Voyage ID�s.

Procedures and rules for EN-134 as well as regulating the use of voyage IDs (such as e.g. for how long voyage ID�s should be possible to access after the voyage has been conducted).

Services constitute the core of the service-oriented-architecture applied in SeaSWIM allowing possible [peer-to-peer] interactions between information providers and information consumers. In order to allow for the provisioning and consumption of services, as carriers of the information being exchanged/shared, processes/procedures of how to publish and discover services need to be defined (as e.g. how does the process look for including a service in the service registry and for discovering a particular service).

In order to allow changes of the service specification language and keep the language up-to-date, there has to be processes/procedures for how to change the service specification language

For each area of operations, i.e. in the coverage of the different concepts, there needs to be service approval processes established in which proposed services need to be met by certain criteria agreed among the members of the federation (such as the Port CDM council).

Established routines for how to feedback reviews, based primarily on use, to the service provider

In order to drive continual quality development and continuous improvement of services there will be tools associated with STM that allow for validating/assessing the used services. This both concern the possibility for �letting the crowd� give their remarks on used services as well as statistics for usage. The result of the validation is an important input for the process of improving existing services (service lifecycle management) by the service provider.

Establishing a set of specefications of how SeaSWIM enabled information services shall perform, in order to qualify as SeaSWIM service (availability, performance, data quality etc).

Route cross-check is a new service made possible by route exchange and new procedures for ship and shore interaction is needed.

To develop a common model for understanding the effects of delays on available resources and efficiency in the process of arrival and departure in ports.

New roles or organisations providing shore based assistance (e.g. VTS) or monitoring services.

As a complement to the Identity management services described in EN-125, SeaSwim will support the possibility to digitally sign the receiving or publication of a certain set of information. This will enable the digitalisation of documents which today needs a physical signature, and also provide digitally signed acknowledgements of crucial data (warnings, nautical updates etc.)

Functionality in SeaSwim (connectors) to add option of Auto-nomination of geo-location based actors (e.g. VTS, Ports, SRS, reporting areas).

The identity registry need to be kept up-to-date and have such a status that it becomes used. This requires services for provisioning and consuming actor identities. To identify and qualify a certain actor as an identity in the identity registry existing registries, as managed by diverse associations, forms an important basis.

This is a new area that needs to be specified.
Could be part of IHO S 121

A framework supporting the implementation of SeaSWIM access management for SeaSWIM enabled information services (who, what, when, with what usage rights)

A list of what information services (types) are available in SeaSWIM

A generic functionality in SeaSwim enabling the discovery of a service as the carrier of the information that is requested. E.g a port will be able through its SeaSwim connector, subscribe for VoyageID�s with planned destination to the port, without knowing anything about logical or physical address where the information can be retrieved. That information is provided by the service discovery mechanism.

An univeseral service registry provides a list of all services possible to access when certain criteria are met � such as e.g. geographical region.

The identity registry constitute one of the core enablers in the information sharing environment. High accessability is therefore required enabled by a good technical infrastructure.

The term Automated Single Windows refer to when the national reporting infrastructures (today referred as Single Window, NSW), have the capability to subscribe for the required information directly from SeaSwim. A route published by a ship, with a destination in any port state, would (if the option of Auto-nominate is set, give automatic notification to the NSW of the destination port state, enabling them to retrieve the information needed.

Actual implementation of Route Exchange Format in various equipment on board and on shore.

The nautical information, today broadcasted, in non-machine readable format, will be digitised in standardised formats, so that the information can be automatically imported in any bridge system supporting these standards.

Status: IHO ongoing work

Standards and technology for store/publish/share information valid for a specific area or place. There should be a possibility to match any route or location, and use as an index or key for obtaining data in the service providing the geo-located information.

To reach full benefits from the STM concept both ships and shore centres need to have systems that are STM and Route exchange compatible

Interoperable platforms for sharing information between different transportation systems

The objective is to provide unique voyage identity.

The objective is to manage an identity registry of maritime actors providing access rights to services.

The objective is a lifecycle approach to the facilitation of the development, publishing, maintenance, use and liquidation of services necessary for the functionality of SeaSWIM.

The objective is to provide functionality to access services and information sources based on the desires of the service provider to enable trusted information exchange.

The objective is to establish a single page for updated:
– Legal and environmental requirements,
– Nautical information, which is today contained in Pilot books,
– Environmental information e.g weather, ice, currents, tidal water, and
– Safety warning.

The objective is to enhance the situational awareness by providing surrounding vessels routes and displaying them on onboard ECDIS or shore based equipment.

A common route exchange format for route sharing between ship and shore.

A set of services within SeaSWIM or other providers will have to be developed for the full implementation of the nomination process, including automatic nomination. Geo-location of; reporting lines, regulation, entering- or leaving, depth restrictions and so on, in addition to time-regulations (ETA-dependent) will need to be established in order for the full implementation of the nomination process.