LIVE IN BRUSSELS AND ONLINE 10 & 11 March 2027

ETCS Business Readiness Community
  • Home
  • PURCHASE
    • REPORTS & PASSES
    • CONTACT US
  • WHY ATTEND?
    • Operators
    • Infrastructure Providers
    • Solution Providers
    • Rail Engineer Article
  • PAST EVENTS
    • 2026
    • 2025
    • REPORT SNIPPETS
  • VENUE
    • Radisson Hotel Brussels
  • COMMUNITY
    • Join
  • LIVESTREAM
  • More
    • Home
    • PURCHASE
      • REPORTS & PASSES
      • CONTACT US
    • WHY ATTEND?
      • Operators
      • Infrastructure Providers
      • Solution Providers
      • Rail Engineer Article
    • PAST EVENTS
      • 2026
      • 2025
      • REPORT SNIPPETS
    • VENUE
      • Radisson Hotel Brussels
    • COMMUNITY
      • Join
    • LIVESTREAM
  • Sign In
  • Create Account

  • Orders
  • My Account
  • Signed in as:

  • filler@godaddy.com


  • Orders
  • My Account
  • Sign out

ETCS Business Readiness Community

Signed in as:

filler@godaddy.com

  • Home
  • PURCHASE
    • REPORTS & PASSES
    • CONTACT US
  • WHY ATTEND?
    • Operators
    • Infrastructure Providers
    • Solution Providers
    • Rail Engineer Article
  • PAST EVENTS
    • 2026
    • 2025
    • REPORT SNIPPETS
  • VENUE
    • Radisson Hotel Brussels
  • COMMUNITY
    • Join
  • LIVESTREAM

Account


  • Orders
  • My Account
  • Sign out


  • Sign In
  • Orders
  • My Account

Outputs From The 2026 Conference

The purpose of this conference, which I had the pleasure of chairing, was to understand how ETCS/ERTMS is actually being delivered at scale — and how it can be treated as a transformation without destabilising operations, budgets, authorisation processes, rolling stock economics, or workforce capability.


Most people reading this will already recognise that ETCS and ERTMS implementation is not simply a signalling project. It’s a system-wide change.


And in truth, the technology itself wasn’t really being questioned. 


The case studies demonstrated that it can be made to work operationally.


What the discussion kept coming back to was something more commercial and practical.


Whether it can be delivered consistently, affordably, and repeatedly, across different parts of the railway — particularly for regional and freight operations — without becoming progressively more complex and costly each time.


Across the two days, the presentations covered a wide range — from national programmes through to specific corridor delivery and supplier perspectives.


But once you moved into the Q&A and the conversations around the sessions, the themes became quite consistent.


The point that came up repeatedly was that:


Authorisation, testing and assurance are central to the delivery challenge.


As something that directly affects:


  • cost 
  • timelines 
  • repeatability 


At the same time, no one was suggesting these processes can simply be reduced. Safety remains the overriding requirement.


The difficulty is that the current framework is not easily repeatable at scale, particularly when applied across different fleets, countries and operational contexts.

Bavo Lens, Senior ETCS Engineer, Infrabel

Observation: delivery is shaped more by constraints than by design intent.


Bavo brought a detailed, experience-led perspective, based on over a decade working directly on ETCS programmes.


The Belgian programme was framed clearly as a safety-led transformation, rather than a purely operational upgrade — a point reinforced by reference to various accidents across Europe.


Approach and Trade-offs


What stood out was not just the scale of the programme, but the choices made in how to approach it.


These included:


  • Building internal capability, rather than relying fully on suppliers 
  • Running trackside and onboard migration in parallel 
  • Standardising ways of working early 
  • Progressing toward digital interlockings over time 


None of these are straightforward decisions, and each carries trade-offs. What was useful was understanding the reasoning behind them, rather than just the outcomes.


Working Within Constraints


The reality described was a brownfield environment, with all the associated limitations:


  • Restricted access windows 
  • Legacy infrastructure 
  • Ongoing operational pressures 


Sequencing and Risk


There was also a clear emphasis on sequencing:


  • Aligning ETCS rollout with asset renewal 
  • Using dual signalling during transition 
  • Managing migration in phases 


Again, not as abstract strategy, but as a way of managing operational risk.


Human Factors


As in earlier discussions (including London 2025), human factors were brought in early:


  • Interface design 
  • Driver interaction 
  • Operational usability 


What was helpful here was the explanation of why these decisions were taken when they were, and how that thinking developed over time.

Dr. Florian Kappler, Head of ERTMS, BLS AG, Switzerland

Observation: planning discipline becomes more important as uncertainty increases.


Dr Florian Kappler (BLS AG) described the challenge of migrating a live, mixed-use network.


To put that in context:


  • 71.5 million passengers annually 
  • ~20,000 freight movements 
  • A fully operational system, not a clean deployment 


ETCS was presented not in isolation, but as part of a wider system including:


  • FRMCS 
  • ATO 
  • Digital operational processes 


Some of these elements are still evolving, which introduces uncertainty into planning.


Rather than fixing a single path early, different scenarios were tested:


  • Rollout speed 
  • Corridor strategies 
  • Lifecycle considerations 
  • Integration with future systems 


These were then narrowed into a preferred approach, balancing cost, risk and impact.


A point that came through clearly — both in the presentation and discussion — was the need to align:


  • Rolling stock 
  • Infrastructure 
  • Communications 


Early in the process.


This is straightforward in principle, but more difficult in practice when not all end states are defined.


There was also a more reflective point around cost.


Short- to medium-term optimisation is relatively manageable.


The more difficult challenge is ensuring that decisions taken now do not lead to repeated upgrades or rework later.


Where that longer-term view is not built in, cost tends to reappear over time.

Etienne Kuntzel, Project Manager OCORA, SNCF

Observation: cost is driven more by lifecycle behaviour than initial installation.


Etienne Kuntzel outlined the scale of rollout required across Europe — tens of thousands of vehicles over the coming years.


At current delivery rates and cost structures, there is a clear gap between ambition and execution.


Where Cost Accumulates


A key point made here, and reinforced elsewhere, is that cost is not concentrated in installation.

It accumulates over time through:


  • Maintenance 
  • Upgrades 
  • Obsolescence 
  • Integration of additional functions 


Role of Architecture


Part of this comes back to how systems are designed.


Where architectures are tightly coupled or bespoke:


  • Changes require rework 
  • Upgrades trigger revalidation 
  • Integration becomes more complex 


Modularity as an Ongoing Direction


The move toward more modular architectures is therefore seen less as optimisation, and more as a way of managing future complexity.


In practice, that means:


  • Greater separation of components 
  • Standardised interfaces 
  • Systems that can be adapted through configuration      


The discussion acknowledged that this is not simple to implement, particularly given existing systems, but the direction of travel was clear.

Kjell Holter Head of Technical Management – ERTMS Pgm. BANE Norway

Kjell Holter of Bane NOR presentation related to a living example of the digital railway in operation. 

The approach integrates ETCS within a broader digital architecture, combining signalling, traffic management, and communications systems. Strong emphasis is placed on system and operational standardisation, replacing fragmented legacy systems with unified functionality.


Pilot and early deployment lines demonstrate high safety, availability, and low maintenance, supporting the case for ETCS Level 2 without signals. However, technical challenges remain, particularly in odometry, where GNSS and radar solutions each have limitations.


The programme also looks ahead to future capabilities, including ATO, FRMCS, and train integrity.

Overall, Norway’s experience shows that ETCS can be successfully deployed at scale, but requires strong integration, standardisation, and ongoing technical adaptation.

Thomas Joindot, Technical Director at SNCF Réseau

Thomas walked through the ETCS migration on the Nice–Ventimiglia corridor — a relatively short but complex coastal line in the south of France — which has been used as a pilot for a number of reasons.


It’s geographically constrained, has a relatively contained fleet, and the signalling assets were reaching end of life, dating back to electrification in the late 1960s. So it presented a combination of pressure points that made  a viable test case.


What was particularly valuable about this session is that it didn’t spend much time on the standard ETCS talking points.


Issues like:


  • requirements definition 
  • system design 
  • rolling stock fitment 


were acknowledged, but not treated as the main story.


Instead, the focus shifted to the areas that tend to have a more direct impact on delivery — and, importantly, on cost.


In particular:


  • maintenance complexity, especially where legacy systems are still in place alongside new ones 
  • supply chain capability, both in terms of capacity and coordination 
  • financing constraints, which affect how quickly programmes can move 
  • programme timing, particularly when multiple dependencies sit on the same corridor 


Brownfield Reality, Properly Understood


There was also a more implicit point running through the presentation.

This is not a greenfield deployment where you can optimise the system from the outset.


It is a live, ageing railway, where:


  • assets need to be renewed while operations continue 
  • safety has to be maintained throughout 
  • and multiple projects are often happening at the same time 


A few of the more practical aspects were worth noting.


One was the impact on station design and operational precision, particularly where capacity gains are expected. These are not marginal adjustments — they require a level of alignment between infrastructure and operations that is quite demanding.


Another was the continuous renewal requirement. On a line of this age, ETCS is not being introduced in isolation — it sits alongside ongoing work just to maintain the baseline level of safety and performance.


And then there is the issue of overlapping projects. Managing ETCS alongside other major works on the same corridor creates sequencing challenges that are not easy to resolve.

Thijs Van Steen, Programme Manager, ERTMS Programme Directorate, Netherlands

Thijs van Steen, Programme Director for ERTMS in the Netherlands, emphasised that:

ERTMS is not just an infrastructure programme.


It is the coordination of an entire ecosystem:


  • Passenger rail 
  • Freight 
  • High-speed services 
  • Infrastructure managers 
  • Government stakeholders 


— all under conditions of uncertainty.


Governance Model


What stood out was the governance approach:


Not:


  • A single centralised authority 

And not:


  • A fully decentralised system 


But a structured, multi-layer model, involving:


  • Ministry level 
  • Executive board 
  • Programme directorate 
  • Infrastructure manager 
  • Operators (NS, freight, regional) 


How Decisions Are Made


Decision-making is:


  • Layered 
  • Structured 
  • Adaptive 


With clear principles for:


  • Intervention 
  • Escalation 
  • Progress tracking 


One of the most striking insights:


“Culture eats strategy for breakfast.”


The implication being:


Success depends less on technical execution, and more on:


  • How effectively organisations collaborate 
  • How decisions are made across boundaries 
  • How uncertainty is managed collectively 

Alex Bétis, CEO, The Signalling Company

This session moved away from general discussion and into a very specific operational case — retrofitting a freight fleet under current regulatory and technical conditions.


The Linéas example provided that anchor (Linéas co-authored the presentation but were unable to make the event in person)


A fleet of just over 100 locomotives, operating across multiple countries, with a long maintenance horizon and no real option to step out of service for extended periods. In that sense, it reflects the reality many freight operators are dealing with.


One point that came through clearly is that, taken step by step, the retrofit process itself is not especially complicated.


It follows a familiar structure:


  • selecting and modifying a prototype vehicle 
  • integrating ETCS onboard 
  • carrying out testing 
  • going through authorisation 
  • then rolling out across the fleet 


In isolation, none of these stages are new.


Where it becomes difficult is how that process behaves at scale and over time.


What was especially interesting — and where this session added something different — was in how the signalling company framed a way forward.


The core idea was a shift away from a hardware-led, reauthorisation-heavy model, toward something more software-driven and upgradeable.


In practical terms, that means:


  • designing onboard systems that can be updated without full re-certification each time 
  • separating software changes from hardware interventions where possible 
  • reducing the need for repeated physical modification of the locomotive 


The argument wasn’t that authorisation disappears — clearly it doesn’t — but that the frequency and scale of intervention can be reduced if the system is designed differently from the outset.


For freight operators, the current model tends to treat each upgrade or change as a significant event:


  • new baseline 
  • new hardware 
  • new approval cycle 


Which leads to repeated cost and downtime.


The alternative being suggested is a model where:


  • changes are more incremental 
  • upgrades are managed more like software releases 
  • and the impact on operations is reduced 


That doesn’t remove the underlying complexity, but it does change how often it has to be dealt with in a disruptive way.


So the signalling company’s approach is essentially trying to flatten that curve — not just by simplifying the initial retrofit, but by reducing what happens afterwards.


Rafał Trznadel, Sales Director and Co-Founder, SIM Factor

This session provided a useful shift in perspective, moving away from infrastructure and system design, and focusing on what is often treated as a secondary consideration — how drivers and the supporting operational workforce  actually adapt to ETCS in practice.


Rafal approached this less as a training topic and more as a transition in how the railway is operated at a human level.


The central point he made — and it’s one that is easy to underestimate — is that ETCS does not just introduce a new interface.


It changes the role of the driver.


Moving from:


  • interpreting trackside signals and physical cues 

to:

  • operating through a digital in-cab system, where information is mediated differently 


It is a shift in how decisions are made, how attention is managed, and how confidence in the system is built.


The cost of training came through quite clearly.


Training a single driver can exceed £100,000, depending on the approach taken and the level of simulation involved.


But the more important point was not the headline figure — it was what drives that cost.

In particular:


  • time to competency 
  • dropout or retraining 
  • inefficient sequencing of training stages 


If those are not managed well, the cost increases quickly, and the impact is not just financial — it affects operational readiness.


Simulation as Part of the Programme, Not an Add-On


What SimFactor is proposing is to treat simulation differently.


Not just as a training tool, but as something that supports the wider programme.

In practice, that means using simulation earlier and more continuously:


  • at the selection stage, to assess aptitude 
  • during initial familiarisation, before formal training begins 
  • throughout training, to build confidence progressively 
  • and even into operations, as a way of maintaining competence 


There was also a useful distinction made between different types of simulation.


Not everything needs to be a full cab environment.


Depending on the stage, different tools can be used:


  • lighter digital environments for early familiarisation 
  • more structured simulation for training 
  • full cab replication where required 


This is partly a cost consideration, but also about using the right level of fidelity at the right time.

Mirko Blazic, Technical Lead, EULYNX

Stephen Lemon Executive Director, Rail Systems & Operations Reform National Transport Commission

Daim Willemse, Senior Advisor Strategy and Culture, ProRail, Netherlands

  • Interface standardisation is not a technical detail — it is a strategic control mechanism.
  • EULYNX is positioned not just as a technical initiative, but as a system-level solution space, focused on:

  1. Modular signalling architectures 
  2. Open, standardised interfaces 
  3. A continuously evolving framework led by infrastructure manager

It is how Europe can:

  • Regain control of system costs 
  • Enable scalability 
  • Reduce dependency on fragmented, bespoke solutions 

Daim Willemse, Senior Advisor Strategy and Culture, ProRail, Netherlands

Stephen Lemon Executive Director, Rail Systems & Operations Reform National Transport Commission

Daim Willemse, Senior Advisor Strategy and Culture, ProRail, Netherlands

  Treat ETCS rollout as a learning system, 

not just a delivery programme 

  • Prioritise real-world operational testing over reliance on lab environments 
  • Use live issues (e.g., connection loss) as structured learning inputs 
  • Align teams across organisations with a clear shared purpose (“why”) 
  • Measure learning maturity and capability, not just deployment milestones 

Stephen Lemon Executive Director, Rail Systems & Operations Reform National Transport Commission

Stephen Lemon Executive Director, Rail Systems & Operations Reform National Transport Commission

  • In fragmented rail systems, organisations may wish to prioritise      interoperability frameworks before large-scale deployment 
  • Where multiple operators exist, it may be worth developing national funding mechanisms for onboard fitment 
  • In mixed traffic environments, stakeholders could consider phased      deployment strategies aligned to operational priorities 
  • Where standards are imported (e.g. TSIs), organisations might need to adapt them carefully to local operating conditions 
  • In long-term programmes, governance bodies may need to actively prevent divergence rather than simply coordinate it 

Peteveikko Lyly, Mobile Networks Expert, Finnish Transport Infrastructure Agency

  • Consider commercial telecom networks as viable alternatives to dedicated rail networks 
  • Use multi-operator redundancy (multi-path) to achieve resilience 
  • Leverage standard 4G/5G technologies to accelerate deployment 
  • Plan for parallel operation (pre-FRMCS + FRMCS) rather than full      replacement 
  • Treat communications as a service layer, not owned infrastructure 

David Choda, Principal Engineer - Telecoms, Network Rail

  • Treat communications as critical infrastructure, not a supporting system 
  • Plan for dual-running (GSM-R + FRMCS) over extended periods 
  • Address coverage gaps (“not-spots”) early, as they directly impact ETCS reliability 
  • Align ETCS rollout with communications readiness to avoid performance issues 
  • Prepare for significant infrastructure expansion (e.g., more radio masts) 

Carole Coune, Secretary General, Association of European Rail Rolling Stock Lessors (AERRL)

  • Treat testing and authorisation as primary cost drivers, not secondary processes 
  • Prioritise reuse of test data and documentation across borders 
  • Challenge national-specific requirements that undermine interoperability 
  • Invest in centralised testing infrastructure and lab capabilities 
  • Push for simplified, standardised EU-wide authorisation pathways 

This provides a snapshot of the themes and pressures that shaped the two days—but it only begins to reflect the depth of insight shared across both the formal sessions and the more candid discussions around them.


What emerged is a picture of a European landscape that remains, by global standards, highly advanced in European Rail Traffic Management System deployment. At the same time, there is a growing recognition across different parts of the ecosystem that delivering the next phase at scale will require further alignment—particularly as programmes move from early implementation into repeatable, system-wide rollout.


Rather than being a question of capability or intent, the discussion is increasingly centred on how existing processes, frameworks and commercial models can continue to adapt in line with the realities of large-scale deployment—across both passenger and freight environments, and across networks with very different starting points.


One area that was consistently referenced—albeit from different perspectives—was authorisation.


There was a shared sense among many contributors that, while the current frameworks are grounded in important safety and interoperability principles, there may be opportunities over time to explore how they can operate more efficiently in certain contexts. This is particularly relevant for iterative onboard changes, where some participants noted the cumulative impact of repeated reauthorisation cycles on cost, timelines and programme confidence.


In that light, several constructive lines of thought emerged, including:


  • The potential to increase reuse of testing evidence and documentation where appropriate 
  • Continued exploration of more proportionate, risk-based approaches in specific scenarios 
  • Greater clarity and consistency around how different types of changes are categorised and assessed 
  • Ongoing dialogue around how recognition between national authorities could evolve over time 


These are not simple questions, nor are they new—but they appear to be gaining renewed focus as programmes scale.


Alongside this, there was also interest in how assurance models themselves may develop. For example, some contributors pointed to the role that more modular system architectures could play in supporting more flexible and reusable assurance approaches. Others highlighted the possible value of expanding laboratory-based testing capacity as a complement to existing field-based processes—particularly where it can improve efficiency without compromising robustness.


The freight discussion brought a slightly different set of considerations.


Participants highlighted that, in some cases, the commercial drivers for onboard investment can look different from those in passenger programmes. As a result, there may be value in continued exploration of how funding approaches, incentives, or cost-sharing models could evolve—particularly in freight-heavy environments where the wider system benefits are clear, but the individual business case can be more complex.


Finally, there was a noticeable shift in how future upgrades are being thought about.


Several contributors reflected on the potential for more software-led upgrade pathways over time, which could help reduce operational disruption and create more flexible long-term upgrade cycles—although, as always, this brings its own technical and assurance considerations.


What the event ultimately highlighted is not a single conclusion, but a shared direction of travel.

ERTMS and ETCS are progressing—and will continue to do so. The focus now appears to be on how delivery models, processes and collaboration frameworks can continue to evolve alongside that progress, in a way that supports scale, maintains confidence, and reflects the diversity of operational realities across Europe.


But even at a high level, the tone of the conversation was clear:


There is strong momentum—combined with a growing openness to refine how that momentum is delivered in practice.


The full conference output—covering detailed case studies, extended Q&A discussions, and a broad set of recommendations—explores these themes in greater depth and are available to download on this website.


Steve D Thomas 1 April 2026 

Copyright © 2025 ETCS Business Readiness Community Strategy Engineering Research Group 2025 - All Rights Reserved.

www.ETCS-business-readiness.com

  • Terms and Conditions

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

DeclineAccept