Trinet’s seven pilots answer one question from seven directions: where does a compliant eFTI dataset come from? Rather than assuming operators will create eFTI data as a new activity, most of the pilots take an existing structured document that somebody is already legally obliged to produce, and test whether it can serve as the source.
Three pilots supply platforms. A standalone SaaS platform serves operators that, for reasons such as size or cost, do not require their own internal certified systems. An existing eCMR product, Transbook Docs, is extended to meet the full eFTI platform requirements. And a modular add-on upgrades a third-party transport management system into a compliant platform without replacing it, supporting rapid EU-wide adoption by letting legacy systems become compliant without full system replacement.
Four pilots test document sources. Customs declarations — import, export and transit — are examined for whether they hold enough of the eFTI dataset to avoid re-entry. ICS2 entry summary declarations, filed before goods arrive, are tested as a pre-arrival source. Excise movement documents under EMCS are tested for alcohol, tobacco and energy products, with the administrative reference code assessed as a linkage to the eFTI identifier. And an electronic air waybill brings aviation into the picture.
GEFEG, the metadata-structure consultant to DG MOVE for the eFTI common data set, does the modelling and schema production behind the model these pilots must conform to. Its contribution is track by track: schema support and conformance validation for the eCMR pilot, subset definitions for customs, and a joint mapping of eFTI onto the ICS2 and EU customs data models.

