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.

