Get Ready for eFTI!  9 July 2027 – countdown to compliance starts now!✦

Overview

This pilot has no truck in it. It addresses a problem every other pilot will run into: the eFTI data model has a published Version 1.0 and a next version coming, and for a period implementers will have to support both at once.

The work is analytical and sequenced. It starts with a structured comparison between Version 1.0 and the upcoming version, with particular attention to combined transport elements and dangerous goods, and produces a documented element-level difference matrix. It then analyses what happens when an implementer — an eFTI gate, a national subset owner, an economic operator — has to support both versions simultaneously, quantifying the differences in scope, complexity and effort and mapping them to concrete integration scenarios. Finally it identifies and tests practical steps that could make migration and coexistence smoother, and turns them into guidance.

The scenarios it works through are the ones that break in practice: dual-version support by a platform, gate routing and validation across multiple data model versions, exchange of regulatory data including combined transport elements, mapping between the two datasets, and the effect on economic operator workflows and onboarding. The scale of the change is not trivial — the impact assessment covers 30 to 50 new elements in combined transport alone. For a framework whose adoption depends on implementers not being deterred, reducing that friction is the pilot’s stated purpose.

Lead beneficiary

Pionira and GEFEG

Countries involved

EU-wide — the pilot is relevant to all EU data exchanges rather than to a specific corridor

Transport modes

Focus on combined transport

Main stakeholders

Gate operators · eFTI platform providers · competent authority application developers.

eFTI components

eFTI Platform. eFTI Gate, AAP and CA application simulated. Registry of identifiers not included

Timeline

The work is sequenced in five steps: structural analysis, generation of a differential matrix, analysis of implementation scenarios, proposed implementation methods and solutions, and concluding analysis and recommendations

Pilot type

Ecosystem pilot
  • Produce a structured comparison between the published Version 1.0 of the eFTI data model and the upcoming next version, with particular focus on combined transport elements and dangerous goods.
  • Analyse the implementation impact when an implementer needs to support both versions at the same time.
  • Quantify the differences in scope, complexity and effort introduced by the new elements and map them to concrete integration scenarios.
  • Identify and test practical steps that may make the migration and the coexistence of two versions smoother.
  • Derive practical recommendations and migration guidance for implementers and policy stakeholders.
UC1

Dual-version support by an eFTI platform.

UC2

eFTI Gate routing and validation with multiple data model versions.

UC3

Exchange of regulatory data including combined transport elements.

UC4

Mapping between Version 1.0 and next-version datasets.

UC5

Impact on economic operator workflows and onboarding.

The pilot expects to deliver a comparative analysis of Version 1.0 and the new working version, including a documented element-level difference; an impact assessment focused on combined transport, covering the 30 to 50 new elements; and a scenario-based assessment of dual-version implementation at gate and operator level.

It also expects technical tools and solutions where these prove feasible, and a final report with recommendations for implementers, national authorities and the wider eFTI community.