Domain name and links to environments are new for Navelink (
Hence, URL to search for service instances and get Organizations are changed
SSL Certificates for Navelink servers are new and need to be trusted
Let’s Encrypt SSL certificate on Navelink servers.
Root certificate in Identity Registry are new for Navelink instances.
Each issued certificate for identity will have the new Navelink self-signed certificate in its trust chain
MRN identities are changed from urn:mrn:stm to urn:mrn:mcp
Identity on VIS Technical Design is changed to:
Navelink DEV: urn:mrn:mcp:service:navelink-dev:navelink:design:vis:rest:2.2
Navelink TEST: urn:mrn:mcp:service:navelink-test:navelink:design:vis:rest:2.2
Navelink OPS: urn:mrn:mcp:service:navelink:navelink:design:vis:rest:2.2
  1. Logon to MCP and Download XML for Service Instance
  2. Change id on service instance to correct MRN for Navelink
  3. MCP: urn:mrn:stm:service:instance:sma:[service]
    Navelink: urn:mrn:mcp:service:navelink:instance:sma:[service]
    For Test or Development environment add "-test" or "-dev" to "navelink".
  4. Change id for implementsServiceDesign
  5. MCP: urn:mrn:stm:service:design:sma:vis-rest-2.2
    Navelink: urn:mrn:mcp:service:design:navelink:naveling:vis:rest:2.2
    For Test or Development environment add "-test" or "-dev" to the first "navelink".
  6. Logon to Navelink and select VIS Technical Design
  7. Create new instance
  8. Upload XML
  9. Upload Document
  10. Issue Certificate

You choose your own short name. This will be part of the organization identity Maritime Resource Naming. All MRN identities created within the organization (users, vessels etc). Allowed characters are: a-z (lower case) 0-9 (3-10 characters).

  • Higher SLA with 24/7 technical monitoring of the system.
  • Higher level of support to users.
  • Higher stability and longterm availability means more stability of investments.
  • Closer cooperation with end users; A system provided by the Users. Ownership of Navelink are themselves big users of Navelink.

The change of MRN in Identity Registry concerns the identities, hence the service book and possibly authorization data needs to be updated/reloaded.
The UVID (Unique Voyage Number) in the RTZ (vesselVoyage) is not affected by the change from MCP to Navelink. In UVID the MRN urn:mrn:stm will continued to be used.
The MRN identity has also been changed for the VIS Technical Design, so please ensure that this change is reflected in e.g. filter in Find Service.

No. We will send you a Service Agreement proposal. You commit to Navelink when signing the Service Agreement.

There is a procedure defined in Navelink for releasing service instances in OPERATIONAL environment that includes a special protocol and request before set to status=released. The procedure and guideline will soon be available for download on Navelink. Release in DEV and TEST does not require protocol to be released.

Service registrations will be automatically monitored in Navelink against the guidelines. Deviations will be reported directly to the registered person.

To change the password you have to use the "forgot password" function on the selected environment. This will send a email to the email account associated to your Navelink user with a temporary password. Use this password to log in and then you will be prompted to set a new password.

Navelink REST API documentation as OpenAPI (swagger) can be found here:

Identity Registry: |
Service Registry:

The error has been reported and an Issue Task is created.

The status on Service Instance can be changed by the following procedure:
  • Download XML
  • Change status in the XML
  • Update Instance and upload the new XML

The error has been reported and an Issue Task is created.

The Document can be uploaded with the following procedure:
  • Create the instance
  • Update the instance and Upload the Document.

The error has been reported and an Issue Task is created.

The Service Instance can be created with the following procedure:
  • Move over to the Acting for organisation
  • Create a temporary user as Agent where you can enter your email address with the following format; name+agent@xxx.yy. The +agent enables you to use the same email again)
  • Log out and log in with the newly created user in the Acting for organisation, alternatively issue a certificate for the newly created user
  • Create the Service Instance logged in with the newly created User or the new certificate
  • Remove the User when done