WG 17 - TC 80/WG 17

IEC 63173-2:2022 the scope of secure communication between ship and shore (SECOM) includes interfaces (APIs) for data exchange (information services), information security measures to enable secure communication and interfaces for service discoverability. SECOM provides technical interoperability, where the same service interface is used for exchanging the information regardless of its operational use, up to the level of exchanging information securely online. Although designed for IHO S-100 based products, SECOM is technically payload agnostic and applicable also for other types of data.
Communication between SECOM information services for data exchange relies on IP based web services. The "last mile" links between a SECOM information service and the end-user application is not defined in this document, thus the communication technology between the vendor API and a ship/shore system can be non-IP based as well as IP based. The informative Annex D describes one such implementation of this. This allows different solutions between the service and shore/ship’s system/applications.
SECOM does not define physical layer or link layer for transport of data between SECOM information services, but requires that the transport supports IP communication. SECOM is applicable for both public (governmental) and private (business) services. SECOM is applicable for ship-shore and shore-ship communication, and can be used for ship-ship communication.

IEC 63173-1:2021 specifies an S-100 compliant product specification for route plan intended for exchange of information. It specifies the content, structure, and metadata needed for creating fully S-100 compliant route plan information and its portrayal within an S-100-based application. The IHO manages all numbers for S-100 compliant product specifications and has assigned S-421 for this route plan IEC standard.
This document specifies only a data format for the route plan exchange. This document does not specify a data format of vessel monitoring and logging information. This information can be provided by other mechanisms or be specified in other standards.
The format of the route plan exchange includes some limited vessel static information. When more static information is required, it can be obtained by other methods such as AIS.