Why now

Four pressures explain the timing of this work, and one persistent gap connects them. Three pressures accumulate as demands on owners of transport networks. The fourth reflects a capability that has finally caught up. The gap describes today's operational reality, which the new demands and the new capability together make addressable.

1. A network under pressure

Much of the European rail network has aged past its design life. SNCF Réseau's audits, Network Rail's control-period condition reports, and ProRail's annual asset-condition publications all surface the same pattern. Renewal trails the work the network needs each year. The backlog accumulates.

Climate stresses the infrastructure. Heatwaves across southern Europe and flood events elsewhere on the network load track, embankments, and drainage in ways the original design did not anticipate.

2. A network asked to do more

Demand on the network climbs. France's SERM programme commits 26 metropolitan areas to regional express service. It puts more trains per hour on networks originally sized for less. The Netherlands runs one of the densest service patterns in Europe on essentially fixed track, and has done so for decades.

The cadence increase has knock-on effects beyond rail. At a busy level crossing, the closure frequency increase implied by SERM raises the average emergency-response delay by around one minute, which carries public-health and societal costs in the hundreds of millions of euros per year on the cardiac-arrest scope alone.

The EU 4th Railway Package opens domestic passenger and freight markets to operators based in other Member States. Networks that historically ran optimised in isolation now have to share a common risk view across borders.

3. A regulatory and budgetary frame

EU Directive 2022/2557 on the resilience of critical entities (CER) entered application in October 2024. It obliges Member States to identify critical operators, including rail. It also obliges those operators to run recurring risk assessment, resilience planning, and incident reporting. The Directive focuses resilience work on the surroundings of each asset, and so complements the expertise owners already hold on the assets themselves.

Public safety budgets do not expand. The work the Directive asks for then needs explicit prioritisation against shared metrics. Renewal on these networks now runs selective.

4. A view that doesn't yet add up across the portfolio

Today, owners read critical points of infrastructure like level crossings one at a time. Studies, reviews, and mandated traffic counts exist. But coverage stays uneven, and the operational view runs as a patchwork.

What's missing is a view across the whole portfolio. One that runs systematic, homogeneous, and easier to maintain. One that adds colour to the picture by surfacing the context around each point. And one that reveals which key flows rely on which points, so the picture clarifies the dependencies.

Turning that context and that dependency view into indicators creates a shared basis. Owners can then compare points across the portfolio. They can prioritise focus areas and investment programmes against the same metrics.

5. A capability that finally fits

The methods to read these networks at scale now sit off-the-shelf. Remote sensing from ESA Copernicus and NASA covers Europe at usable resolution. OpenStreetMap covers European rail and road networks well enough to run routing on. Vector tile rendering and modern routing libraries have matured.

Compute carries the other half. Running the same analytical pipeline against tens of thousands of assets at responsive cadence now sits within reach financially. Work that used to live in local notebooks with locally-defined assumptions can now run across a whole national network against one reference. It can re-run as the data refreshes.

6. Where we fit

SAMRoute targets this work.