Connecting Platforms — dangerous goods in intermodal transportFENIX2.0

Overview

Dangerous goods documentation in intermodal transport is still largely paper, handed physically from shipper to carrier to terminal along the chain. This pilot digitalises that handover and makes it eFTI-compliant, using FENIX connectors for decentralised data exchange rather than routing everything through a single central platform.

Three use cases build on each other. The first digitalises the IMO dangerous goods declaration inside the transport management process of combined transport operators, aligned with the EDIGES standard for intermodal transport and involving logistics service providers, intermodal terminals, rail operators and intermodal operators. The second covers the hinterland leg of a maritime door-to-door dangerous goods shipment, generating an eFTI Common Dataset from intermodal hinterland transport documents, road consignment notes and manifests, and drawing on maritime data standards. The third connects eFTI platforms — starting with the German national gateway operated by Toll Collect and later other Member States — through the FENIX connector, including secure exchange with non-eFTI platforms and applications.

Lead beneficiary

FENIX2.0, Germany, with TRICON Nürnberg and Studiengesellschaft Kombinierter Verkehr (SGKV)

Countries involved

Germany, extending to other Member States

Transport modes

Road and rail (intermodal and maritime hinterland)

Main stakeholders

FENIX2.0 · TRICON Nürnberg · Studiengesellschaft Kombinierter Verkehr (SGKV) · Toll Collect

eFTI components

eFTI Gate · eFTI Platform · AAP · Registry of identifiers · CA application

Timeline

Planning first half of 2025 (to M16)
Development second half of 2025 (to M28)
Piloting M22–M47
Results 02.2028–03.2028

Status
(summer 2026)

Development — process analysis complete, first simulation test run
  • Enable integration of eFTI platforms across Member States and economic operators to create a unified eFTI Common Dataset for digital freight documentation.
  • Demonstrate the practical application of eFTI standards in intermodal logistics, in combination with other transport modes.
  • Develop and validate mechanisms for authorities to access economic operators’ data securely and efficiently.
  • Provide a practical proof of concept for platform interoperability and interface standardisation.
  • Streamline data exchange for economic operators, reducing administrative burden and improving data accuracy.

UC1

Integration of the dangerous goods declaration (IMO) in intermodal continental transport: digitalisation of the dangerous goods document inside the digital transport management process of combined transport operators, aligned with the EDIGES standard and involving logistics service providers, intermodal terminals, rail operators and intermodal operators, with exchange enabled by FENIX connectors.

UC2

Integration of the dangerous goods declaration (IMO) in intermodal maritime hinterland transport: the hinterland leg of a maritime door-to-door dangerous goods shipment, generating an eFTI Common Dataset from hinterland transport documents, road consignment notes and manifests, using maritime data standards.

UC3

eFTI platform and FENIX connector interaction: integration of eFTI platforms, first with the German national gateway and later across Member States, to build an eFTI dataset from FENIX connector exchange, including secure and reliable exchange with non-eFTI platforms and applications.

The pilot has completed its kick-off and stakeholder interviews, a detailed process analysis, the definition and development of the data exchange scheme, a first test realisation for simulation, and the connector concept. It confirmed that dangerous goods transport documents are still paper-based, not integrated with digital standards such as EDIGES, and handed over manually along the transport chain — and that the FENIX connector appears very well suited to decentralised exchange of the IMO document.

Next come an eFTI-conformant data exchange proposal to be discussed with the German national gateway, integration into the Nürnberg terminal operating system, and testing with local logistics service providers and shippers.