System and Interface Version Management

NEMO maintains a list of supported versions. NEMO always supports the current production version (latest stable) and the two (2) preceding versions.

Support for older versions ends after a transition period defined in EMSA's version management policy. NEMO can display information submitted using previous versions even when those versions are no longer supported.

Compatibility Assurance

• NEMO includes schema and business rule validations that ensure compliance with the Maritime National Single Window (MNSW) Migration and Integration Guidelines (MIG).
• Support for multiple versions is based on version identification at metadata level (for example, a version number included in a message or the version used in an API request).
• Historical data can be viewed for submissions made using older versions, but only the latest version provides full functionality.

Version Updates and Change Notifications

When Finland receives information about an upcoming MIG version update, Fintraffic publishes a notification announcing the forthcoming version and an initial estimate of its release schedule.

The implementation of a new MIG version is carried out in phases. Related information is communicated separately through the following channels:

• the Fintraffic Developer Portal
• email notifications sent to designated contact persons of organizations

The email address of the organization's contact person can be managed in the Organization Administration view.

Version information, including the description of the new version, message structures, and interface specifications, is published in Fintraffic's GitHub repository (JSON Schema, OpenAPI specifications, and MIG structures). A changelog is published for each version, describing the key changes compared with the previous release.

The purpose of these communications is to ensure that all third parties have sufficient time to prepare for the version update and test their implementations before deployment to the production environment.

Actions Required During a Version Update

When a version update is introduced, you or your organization's technical contact person should take the following actions into account:

• Compatibility testing – Ensure that your system supports the new MIG version and produces valid data in accordance with the published interface specifications.
• Interface changes – Review the published schemas and any changes to mandatory fields, structures, or validation rules.
• Service interruptions – Take into account any scheduled maintenance windows or production service interruptions related to the version update.
• Version management – Document the version used within your development process and monitor the transition periods announced by Fintraffic.
• Acceptance testing – Test the complete message flow (submission, acknowledgements, and possible error responses) in the staging environment.