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

Overview

The Austrian programme has two halves that meet in the middle. On the enforcement side, two pilots work on what an inspector actually sees at the roadside. The first adds cabotage data to the existing enforcement IT system and then tries to automate the cabotage check that officers currently perform by hand. The second goes further and converges eFTI data with other sources — smart tachograph routes, and potentially toll and camera data — so an inspection draws on several systems at once rather than on transport documents alone.

On the platform side, three pilots take an eFTI platform through its lifecycle. Data ingestion comes first: onboarding an economic operator and integrating its transport management or ERP system so that source data is transformed into an eFTI-compliant dataset according to the Common Data Set and Annex I. Certification comes next, interpreting the Delegated Act criteria and taking the platform through a mock or example certification exercise. Gate integration comes last, covering secure certificate exchange, platform onboarding to the gate, the first AS4 message, and delivery of a compliant dataset filtered by the authority’s access rights.

Together the five make a complete national picture: an authority that can read the data, a platform that can produce it, and a gate-connected path between them tested against the certification criteria. Several steps are explicitly conditional — the ingestion and platform work depends on the official XSD and Schematron release, and the certification exercise depends on a conformity assessment body being available.

Lead beneficiary

ASFINAG and Schieneninfrastruktur-Dienstleistungsgesellschaft mbH (SCHIG), Austria

Countries involved

Austria. Cross-border participation is optional for the two enforcement pilots, not included for the ingestion and certification pilots, and potentially included for gate integration depending on scope; a test platform, preferably in an EU partner country, supplies cabotage test data

Transport modes

Road for the enforcement pilots; road with extension to combined transport for the ingestion pilot; road and combined transport for the certification and gate integration pilots

Main stakeholders

Austrian police · the ministry responsible for inspections (BMIMI, BMI) · the company providing the existing enforcement application · a test platform, preferably in an EU partner country, for cabotage test data · participating economic operators providing TMS/ERP access · platform and gate operators · a conformity assessment body or external evaluators.

eFTI components

Across the five pilots: eFTI Gate · eFTI Platform · AAP · Registry of identifiers · CA application. The data ingestion pilot uses the platform alone; the certification pilot does not include the CA application

Timeline

Q1 2026 – Q4 2029 across the five pilots: cabotage piloting Q1–Q2 2027, smart enforcement piloting Q4 2028, platform pilots dependent on the official XSD and Schematron release and on the availability of a conformity assessment body

Pilot type

Two competent authority pilots run with the supplier of the enforcement system; three platform pilots covering ingestion, certification and gate integration
Integrate cabotage data into the enforcement system and, optionally, perform an automatic cabotage calculation based on eFTI data.
Combine eFTI data with additional sources. Optionally, compare eFTI cabotage data with smart tachograph routes and check the feasibility of using additional data such as toll and camera data.
Onboard at least one economic operator to the platform, integrate its TMS or ERP system, transform source data into an eFTI-compliant dataset, and validate data quality, completeness and semantic correctness.
Interpret and operationalise the Delegated Act certification criteria, prepare platform evidence and documentation, validate compliance for road and combined transport, and identify and address compliance gaps.
Define a secure channel for certificate exchange, onboard the platform to the gate, validate access-right-based data retrieval, and simulate production-like operational conditions.
Automatic Cabotage Check

a competent authority carries out heavy vehicle inspections supported by an application that performs cabotage checks automatically. Piloting Q1–Q2 2027, as part of the test run of the production system.

Smart Enforcement

inspections supported by an application that converges data from different sources, such as eFTI and the digital tachograph. Piloting Q4 2028.

Platform Data Ingestion Pilot (PDIP)

mapping logistics data from economic operator systems to the common eFTI data model, validating compliance and ensuring scalability for future onboarding.

Platform Certification Pilot (PCP)

the platform undergoes a mock or example certification process to demonstrate compliance with the Delegated Act requirements for eFTI platforms.

Platform Gate Integration Pilot (PGIP)

secure exchange of certificates, onboarding of the platform to the gate, first AS4 message, push of identifiers activating a draft dataset, and delivery of a compliant dataset based on access-rights filtering upon authority request.

On the enforcement side the programme expects a first demonstration of real-life business value for cabotage, usability feedback that feeds back into the inspector’s application, and a working cabotage check on the main authority’s final hardware and software — followed, in the second pilot, by enhanced inspections through the integration of eFTI with additional data.

On the platform side it expects a demonstrated ability to onboard economic operators and reliably generate compliant eFTI datasets from existing operational systems; validated certification readiness with a clear compliance roadmap for formal certification; and demonstrated end-to-end compliant data exchange between platform and gate under authority request scenarios.