The recent Navelink Developer Forum provided an insightful look into our ongoing projects and future plans. Here is a detailed rundown of the key discussions and updates from the meeting. 


Current Work and Future Implementations 

SECOM Hotel Updates: 

The SECOM Hotel has successfully been added to the DEV environment, and efforts are now underway to implement it in the TEST environment. Future plans include extending SECOM Hotel to the operational environment and creating a comprehensive user guide. 



Investigation into possibly adding an MMS router to Navelink once the standard is finalized is ongoing. 


VDES Community and MCP as Identity Provider: 

There are ongoing discussions within the VDES community regarding the use of the Maritime Connectivity Platform (MCP) as an identity provider. This indicates a push towards more integrated and standardized identity management within maritime communications. 


Identity Registry Updates: 

Thomas Christensen (MCC Consortium) addressed a query about new additions to the identity registry, revealing that changes are anticipated based on the updated Maritime Identity Registry (MIR) specifications. These updates are pending approval by IALA, with an official council meeting scheduled in June. The update is expected to be released in the fall. 


EU Sanctions and MCP System: 

An in-depth analysis is being conducted on the long-term effects of EU sanctions on the MCP system. Currently, the service registry remains open for all to search, including anonymous users, with some constraints on the responses provided. Navelink is considering two options: maintaining the open search with limited information for all users and offering detailed information for members only. 


Service Registry and IALA G1128 Edition: 

The service registry currently uses service types defined in the STM Project, but this will change with the new IALA G1128 edition. The new edition will base service types on the enumeration of IMO e-Navigation services (MS1 to ~MS20). The enforcement timeline is not set but it is likely to happen this fall. Service providers in the Navelink Service registry should prepare for these changes, and more details will be shared as they become available. 


NIS2 Directive Analysis: 

Navelink is also analyzing the updated NIS directive to understand its implications on Navelink and the MCP system. 


SECOM Hotel Presentation by Mikael Olofsson 

Mikael Olofsson presented a detailed demonstration of the SECOM Hotel, highlighting several key scenarios: 

  • Scenario 0: 
    • Ping the SECOM Service. 
    • Get Capability for the SECOM Service. 
  • Scenario 1 – Download (Pull) Information: 
    • Service providing reference routes (e.g., pilot routes) for public download. 
    • Publish data on the private side. 
    • Retrieve summary and data on the SECOM side. 
  • Scenario 2 – Upload (Push) Information: 
    • Ship uploads route plan to VTS. 
    • Upload data on the SECOM side. 
    • Receive notification and uploaded message on the private side. 
  • Scenario 3 – Subscription: 
    • Service providing subscription for S-124 Nav Warnings. 
    • Create subscription on S-124 data. 
    • Publish S-124 Navigational Warning on the private side. 
    • Retrieve the uploaded S-124 Navigational Warning on the private side. 

The SECOM Hotel allows for quick and standardized data sharing through a general implementation of the SECOM Service Interface. Notably, the SECOM Hotel supports data pushing, pulling, and handling subscriptions, though it does not yet include the SECOM amendment for using subscriptions without proper endpoint URI registration. 

Additionally, the SECOM Hotel uses the ECDSA-384-SHA2 signature algorithm, aligned with the forthcoming IHO S-100 edition 5.2. A new service, “Navelink SECOM Verification Service,” provides valid test data for anyone wanting to test their SECOM instance. 

Members interested in experimenting with their own SECOM instance can contact Navelink at to set up an instance and discuss membership details. 


Looking Ahead 

The Developer Forum will take a break for the summer, with no meetings scheduled for June, July, or August. The next Developer Forum is set for September 26, 2024. 

We wish everyone a wonderful summer and look forward to reconvening in September with more exciting updates and developments.


Author: Milena Dalinaros