Intertraffic Amsterdam 2028: Which Mobility Technologies Deserve a City Pilot?

Reading the 2028 edition correctly

Intertraffic Amsterdam 2028 is scheduled to run from 7 to 10 March 2028 at RAI Amsterdam (Europaplein 24). The biennial flagship of the Intertraffic family, active since 1972, describes itself as the world's leading event for smart, safe and sustainable mobility; recent editions drew close to 30,000 professionals from more than 130 countries with roughly 900 exhibitors and over 300 sessions. Organisers caution that editions, dates and programmes can change, so treat the figures and dates as a starting point and reconfirm them on the official event site before you book travel or open a budget line.

The practical value for a municipal team is segmentation: the show floor and summit are grouped into five families — smart mobility and ITS, road infrastructure, road safety, parking and kerbside, and next mobility (micromobility, EV charging, mobility hubs, last-mile and urban air). A city that arrives with a named problem can work hall by hall instead of wandering between hundreds of stands. The best filter is not booth size but whether a product answers a problem your operator can describe in one or two sentences.

• Smart mobility & ITS: AI/ML, big data, congestion management, C-ITS, traffic monitoring and control, digital infrastructure
• Road infrastructure: asset management, surfaces, lighting, roadside equipment, barriers and marking
• Road safety: detection and enforcement, incident and work-zone management, informing and warning
• Parking: access control, guidance, enforcement, kerb management, payment and charging
• Next mobility: micromobility and LEVs, EV charging, mobility hubs, last-mile delivery and urban air

The realistic shortlist for a city pilot

Technologies that genuinely survive a municipal procurement conversation cluster into a handful of families. First, AI-enabled traffic monitoring and control: camera- and LiDAR-based detection, real-time classification, adaptive signal timing, congestion prediction and digital twins used to retune signal plans. These matter most where you already operate controllers and cameras, because they turn existing sensors into insight rather than demanding new roadside hardware everywhere.

Second, connected and cooperative ITS plus data exchange. C-ITS, low-latency mobility data platforms and cloud interchange engines let authorities exchange real-time data with vehicles and operators. Before adopting any of them, clarify who owns and licenses the data and which open standards (for example C-ITS-style platforms and mobility data hubs) are supported, because interoperability decides whether a pilot can scale beyond one vendor.

Third, safety and enforcement sensing: speed, red-light and work-zone detection, incident detection and analytics for accident hotspots, often paired with warning signs. These pilot cleanly on a single dangerous junction and can be measured almost in real time. Fourth, parking, kerbside and charging — access control, route guidance, enforcement, dynamic kerb management and EV charging integration. Fifth, asset and infrastructure sensing such as distributed fibre-optic monitoring and condition sensing that feed maintenance planning rather than day-to-day traffic control.

What the 2026 winners say about the 2028 curve

The Intertraffic Awards at the 2026 edition are a useful read on product maturity. The Inspiration Award went to a distributed fibre-optic sensing platform able to monitor traffic across long stretches of road in real time by converting vehicle vibrations into traffic data; the Green Globe Award to a CE-certified compressed-air bicycle parking lift; the User Experience Award to a cloud-native engine for low-latency mobility data exchange; the startup award to laser-driven fibre-optic road markings; and a jury mention to temporary tactile guidance films. Two of the four awards leaned on fibre-optic technology, which the jury itself noted could be complementary on future road projects.

Treat these as direction signals rather than a mandatory shopping list: interest is consolidating around data-rich infrastructure sensing, low-tech accessibility and safety aids, and open data exchange. The official wrap-up of the 2026 edition framed the central theme as the transition from vision to implementation — moving beyond pilots toward scalable real-world applications, with public trust and government-industry collaboration treated as preconditions rather than afterthoughts.

Shortlist before you open the budget

Run a single scorecard against every candidate before any budget line is opened. Score each solution from 1 to 5 on problem fit, data access, interoperability, pilot scale, procurement fit, scale economics, operating burden and regional support. A technology with a high wow factor but weak data access or poor integration is usually a showroom demo, not a pilot.

Keep the bar practical. A municipal pilot should be testable at one junction, corridor or zone, measurable against a baseline within roughly twelve months and reversible if the KPI fails. Ask for reference sites, the volume of real deployments and public-sector tender history in comparable cities rather than glossy testimonials.

• Problem fit: does it solve a named local issue — a specific junction, corridor or safety statistic?
• Baseline evidence: is there a measurable current baseline and a realistic target within 12 months?
• Data access: can the city export raw and processed data, and who owns the data after the trial?
• Interoperability: open standards, integration with your controllers, cameras and GIS
• Pilot scale: testable on one object without buying citywide hardware first
• Procurement fit: does it match your tender rules, and does the vendor hold municipal reference contracts?
• Scale economics: full cost per site including maintenance, licensing and upgrades
• Operating burden: does your team have the skills, or does it create new permanent dependencies?
• Regional support: service and support presence in your country or time zone

Trade-offs that kill otherwise good pilots

Most pilot failures sit outside the technology itself. The first is data: who owns the raw and aggregated data after the trial ends, can it be exported in an open format, and what are the rules for handling vehicle and personal data? This is general information; for any specific city the governing law and procurement rules of its jurisdiction must be checked with qualified local advisers.

The second is procurement and vendor lock-in: confirm early that a product fits your tender regulation and that licensing does not bind you to one platform without a migration path. The third is unproven economics — maintenance, upgrades and training often exceed the cost of the first pilot, and the benefit appears only at scale. The fourth is public trust and privacy, especially for cameras and enforcement: a transparent use policy and clearly bounded automation reduce risk. Finally, not every technology needs a pilot — if a mature solution is already standardised, direct procurement against a specification is cheaper and faster than a trial.

Four days at the RAI as a pilot roadmap

Before you travel, assemble a short brief: three named problems, your existing assets (controllers, cameras, GIS) and a fixed set of vendor questions. On the stand, ask to see a real deployment, a live-data demo and an integration diagram against your equipment — not slides. Ask about APIs, uptime, data ownership and warranties, not only price.

After the visit, consolidate results into the scorecard and shortlist no more than two or three technologies for a corridor-level test. Define KPIs, a baseline and an exit criterion in advance — for example, unchanged safety or congestion figures after a year means the pilot closes. Put a contractual obligation on the vendor to hand over data and documentation at the end of the trial, and four days at an exhibition becomes a managed deployment plan.