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.

