ERTMS: The European Rail Traffic Management System

ERTMS started as Europe’s answer to fragmented national train protection systems. Today, it should be understood more broadly: as the digital backbone of the Single European Railway Area.

It enables interoperable train control, prepares the migration from GSM-R to FRMCS, supports ERTMS/ATO, and creates the foundation on which future DATO capabilities can be built.

But ERTMS is no longer only a technical standardisation challenge; it is now an industrial, operational and migration challenge. This article explains why the success of ERTMS will depend not only on specifications, but on synchronised deployment, cost control, operational harmonisation, governance and long-term architecture discipline.

Executive Summary

ERTMS, the European Rail Traffic Management System, was created to overcome one of the structural barriers of European railways: the coexistence of many national train protection and signalling systems. This fragmentation created technical, operational and economic barriers to cross-border rail traffic. ERTMS provides a common European framework based on interoperable train control, standardised onboard supervision and harmonised communication between train and trackside.

From an architecture perspective, ERTMS is no longer only a signalling programme. It is the digital backbone of the future European railway system. ETCS provides the train protection and supervision layer. GSM-R, and later FRMCS, provide the railway communication layer. ERTMS/ATO introduces automatic driving inside the ETCS safety envelope. Future capacity concepts, such as Hybrid Train Detection and Moving Block, also depend on the progressive digitalisation of the control-command architecture.

The 2026 ERTMS Work Plan confirms both the importance and the difficulty of this transformation. The debate is no longer about whether ERTMS is needed, but how and when it can be deployed at scale. At the end of 2024, around 12,400 km of the TEN-T network were in operation with ERTMS, including about 10,600 km on the core network. Around 8,730 vehicles were equipped with ETCS, representing about 19% of the estimated existing fleet. These figures show progress, but also a significant gap compared with the 2030 legal requirements and the ambition of a fully interoperable European railway.

The main challenge is no longer only technical feasibility. It is synchronised migration. Trackside deployment and onboard retrofit must progress together. National Class B systems must be phased out in a controlled way. Vehicle owners need investment certainty. Infrastructure managers need stable deployment strategies. Suppliers need industrial capacity and stable specifications. Public authorities need credible funding and governance.

ERTMS also requires harmonisation beyond formal compliance. The ETCS toolbox allows several TSI-compliant implementations, but this can create different driver experiences, different engineering choices and continued market fragmentation. This is why the work on a common operational rulebook and harmonised ETCS Level 2 operation is strategically important. ERTMS must become not only technically interoperable, but operationally coherent.

The next challenge is communication. GSM-R is ageing, while FRMCS is still under specification and migration planning. The transition from GSM-R to FRMCS will be one of the most important railway communication migrations of the coming decade. It must be managed without weakening the continuity of ERTMS operation.

ERTMS is therefore a strategic modernisation programme. It is the foundation for future railway automation, but its success will depend on architecture governance, industrialisation, cost reduction, modularity, operational harmonisation and migration discipline. Without ERTMS, there is no credible DATO trajectory. But without stronger deployment and harmonisation, ERTMS itself risks remaining an overlay rather than becoming the backbone of the Single European Railway Area.

Last modified: 2026-06

Content

1. Why ERTMS still matters
2. From national ATP systems to a European backbone
3. ETCS, GSM-R, FRMCS and ERTMS/ATO
4. ERTMS is not only a technical system
5. Deployment reality in 2026
6. Trackside and onboard migration must be synchronised
7. Harmonisation beyond compliance
8. ERTMS as an industrial programme
9. FRMCS and the communication migration
10. From ERTMS to DATO
11. Architecture perspective
12. Conclusion
13. Documentation and further reading

1. Why ERTMS still matters

ERTMS is sometimes presented as an old topic. It has been discussed for decades. It has appeared in many deployment plans, funding programmes, technical specifications and railway policy documents. For some people, it may even seem like a long and difficult story of delayed deployment.

But this would be the wrong conclusion.

ERTMS still matters because the problem it was created to solve has not disappeared. European railways remain historically fragmented. National train protection systems, national signalling practices, national operational rules and national engineering choices have shaped the network for more than a century. This fragmentation has consequences. It makes cross-border rail more complex. It increases onboard equipment costs. It complicates authorisation. It reduces economies of scale. It makes it harder for suppliers to industrialise standard products. It slows down the creation of a genuinely interoperable European railway system.

ERTMS is the European answer to this fragmentation.

Its original role was to provide a common train control and communication framework. But its strategic role has grown. ERTMS is now also the platform through which railways can digitalise operations, remove national legacy systems, support future radio communication, enable interoperable Automatic Train Operation, and prepare a more automated railway architecture.

This is why the 2026 ERTMS Work Plan is important. It makes clear that the debate is no longer about whether ERTMS should be deployed. The question is how to accelerate and industrialise its deployment.

This change of question matters.

When a technology moves from “whether” to “how and when”, the challenge changes. It is no longer only about proving that the technology works. It is about governance, cost, migration, funding, standardisation, industrial capacity and operational change.

This is where ERTMS stands today.

It is no longer only a signalling standard waiting to be deployed. It is a strategic modernisation programme that must now be delivered at scale.

2. From national ATP systems to a European backbone

Before ERTMS, European railways developed their own national train protection and signalling systems. Each system reflected national history, technical choices, signalling principles, operational rules and industrial ecosystems.

These systems were often effective within their national context. They protected trains, supported operations and evolved with their infrastructure. But they created a major European problem: trains crossing borders needed to be compatible with several systems.

This led to multi-system locomotives and trainsets. It increased onboard complexity. It increased cost. It created operational constraints. It made cross-border services harder to develop. It also reinforced national markets because signalling and train protection remained deeply linked to domestic technical traditions.

ERTMS was created to break this logic.

The objective was to provide one European train control system that could progressively replace national Class B systems. Instead of each border requiring a change of protection system, the same interoperable framework would be used across Europe.

This was already a major ambition. But over time, ERTMS became more than a replacement of national ATP systems.

It became the backbone of the digital railway.

This is because train protection is one of the most central functions in railway operation. It defines how the train is authorised to move, how speed and distance are supervised, how the driver receives information, and how the train interacts with trackside systems. Once this function becomes standardised and digital, it creates the foundation for other functions.

ERTMS therefore sits at the core of the future railway architecture. It is linked to signalling, onboard equipment, communication, operational rules, traffic management, automatic driving, capacity, migration, authorisation and cybersecurity.

This is why ERTMS should not be understood only as a technical subsystem.

It is the shared European control-command foundation on which future rail automation depends.

3. ETCS, GSM-R, FRMCS and ERTMS/ATO

ERTMS is often associated with ETCS. This is understandable, because ETCS is the most visible and technically central component.

ETCS, the European Train Control System, provides train protection and supervision. It supervises train speed and movement authority. It ensures that the train remains within the authorised safety envelope. It can replace national train protection systems and support cab signalling, especially in ETCS Level 2 operation.

But ERTMS is broader than ETCS.

The railway also needs communication. Today, GSM-R provides the radio communication layer used for railway operational communication and ETCS data transmission in Level 2 contexts. GSM-R has played a crucial role in the deployment of ERTMS. However, it is based on ageing technology and will eventually be replaced by FRMCS, the Future Railway Mobile Communication System.

FRMCS is not only a radio replacement. It is one of the foundations for the future connected railway. It must support the communication needs of ETCS, railway operational voice, future applications, automation and digital services. The transition from GSM-R to FRMCS is therefore not only a telecom migration. It is part of the future ERTMS and DATO architecture.

ERTMS also includes ERTMS/ATO.

ERTMS/ATO introduces interoperable Automatic Train Operation within the ERTMS framework. In GoA2, ATO controls traction and braking while the driver remains in the cab. ETCS continues to supervise the safety envelope. The fundamental principle is clear: ATO drives, ETCS protects.

This makes ERTMS/ATO a natural extension of ERTMS. It does not replace ETCS. It adds an operational automation layer inside the ETCS safety envelope.

These three elements — ETCS, railway radio communication and ERTMS/ATO — show why ERTMS is no longer only a signalling programme.

ETCS protects.
GSM-R and FRMCS connect.
ERTMS/ATO automates driving.

Together, they form the digital foundation on which future European railway automation will be built.

4. ERTMS is not only a technical system

ERTMS can be described technically. It has onboard equipment, trackside equipment, radio communication, balises, Radio Block Centres, movement authorities, braking curves, driver-machine interfaces, specifications, baselines and compatibility requirements.

All of this matters.

But the difficulty of ERTMS deployment cannot be understood only from the technical description. The hardest part is not only to install equipment. The hardest part is to transform an existing railway system while it continues to operate.

ERTMS is deployed in brownfield environments. Existing national signalling systems remain in service. Trains must continue to run. Rolling stock fleets are heterogeneous. Infrastructure renewal cycles are long. Operators have different business cases. Infrastructure managers have different deployment strategies. National operational rules remain in place. Authorisation processes must be managed. Costs must be controlled.

This makes ERTMS a migration system.

It is not deployed once. It is infused into an existing railway, line by line, vehicle by vehicle, corridor by corridor and rule by rule.

This is why ERTMS must be understood as a strategic modernisation project. It is technical, but not only technical. It is industrial, because suppliers must deliver equipment at scale. It is operational, because rules and driver experience must be harmonised. It is economic, because costs and benefits are distributed between infrastructure managers, railway undertakings, rolling stock owners and public authorities. It is political, because national systems must be replaced by a European common system.

This is also why ERTMS deployment can be slow.

The technology may be mature, but the system into which it is deployed is complex. ERTMS does not only replace equipment. It challenges national habits, existing architectures, procurement models, authorisation practices and investment logic.

The future success of ERTMS depends on recognising this complexity and managing it deliberately.

5. Deployment reality in 2026

The 2026 ERTMS Work Plan gives a useful picture of the current situation.

There is political support for ERTMS. The European regulatory framework has been reinforced. The revised TEN-T Regulation and the 2023 CCS TSI have strengthened the deployment and technical framework. ERA’s role as system authority has been confirmed. The governance around Europe’s Rail, including the System Pillar, Innovation Pillar and Deployment Group, gives the sector a stronger framework for technical evolution, innovation and deployment.

But the deployment reality remains challenging.

At the end of 2024, around 12,400 km of the TEN-T network were in operation with ERTMS in the EU-27. Around 10,600 km were on the core network. Additional deployment is planned before 2030, but current planning remains significantly below the legal requirement for the 2030 core network target. The Work Plan indicates that, based on current planning, only about half of the core network target would be achieved by 2030.

The onboard situation is also incomplete. Around 8,730 vehicles were equipped with ETCS by the end of 2024, corresponding to roughly 19% of the estimated total fleet. More vehicles are contracted or planned, but the scale of retrofit remains large.

These figures are important because ERTMS only delivers its full value when infrastructure and trains are equipped together.

A line equipped with ERTMS does not deliver full interoperability if too few trains can use it. A train equipped with ETCS does not gain much value if the routes it operates are not equipped. A network cannot phase out national Class B systems unless both trackside and onboard migration are sufficiently advanced.

This is why ERTMS deployment cannot be assessed only in kilometres of track or numbers of equipped vehicles.

The real question is synchronisation.

Are the lines equipped where the vehicles operate?
Are the vehicles equipped where the lines are ready?
Can national systems be removed?
Can operators simplify onboard equipment?
Can infrastructure managers simplify trackside architecture?
Can the system move from overlay to replacement?

If the answer is no, ERTMS remains an additional layer. If the answer is yes, ERTMS becomes the backbone.

6. Trackside and onboard migration must be synchronised

One of the main lessons of ERTMS deployment is that trackside and onboard migration must be synchronised.

If the infrastructure is equipped first, operators may not immediately benefit unless their trains are fitted. If trains are equipped first, operators may carry the cost without enough usable routes. If national systems remain alongside ERTMS for too long, infrastructure managers must maintain several systems. If vehicles must carry both national systems and ETCS, onboard complexity remains high.

This creates a difficult investment problem.

Infrastructure managers may see ERTMS as a way to renew signalling, remove lineside signals, reduce national legacy systems and prepare digital operation. Railway undertakings and rolling stock owners may see the onboard retrofit as expensive, disruptive and difficult to justify unless enough infrastructure is equipped.

Both views are rational.

This is why public funding, long-term planning and coordinated deployment strategies are essential. ERTMS is a network transformation. Its benefits are systemic, but its costs are distributed. A railway undertaking may pay for onboard equipment, while part of the benefit appears in infrastructure simplification or network interoperability. An infrastructure manager may equip a corridor, but the benefit depends on the rolling stock that operates there.

This is also why the phase-out of Class B systems matters.

As long as national systems remain, the railway does not fully simplify. ERTMS may then become an overlay rather than a replacement. The infrastructure remains complex. The onboard equipment remains complex. Costs remain high.

Phasing out Class B systems is therefore not only a symbolic step. It is the moment when ERTMS starts to deliver simplification rather than additional complexity.

But this phase-out can only happen when migration is synchronised and operationally credible.

This is one of the deepest challenges of ERTMS: the system must be deployed not only technically, but coherently.

7. Harmonisation beyond compliance

A line can be TSI-compliant and still not contribute fully to harmonisation.

This is one of the most important architecture lessons of ERTMS.

The ETCS specification provides a toolbox. It allows many implementation choices. This flexibility can be useful. It allows systems to be adapted to national contexts, existing infrastructure and operational needs. But it can also create variation.

Different trackside engineering choices, different operational rules, different driver experiences, different national procedures and different interpretations can all remain within a formally compliant framework.

The result is a paradox. The system is interoperable in principle, but fragmented in practice.

This is why harmonisation must go beyond compliance.

The 2026 Work Plan gives particular importance to the development of a common operational rulebook for ETCS Level 2, especially for radio-based ETCS operation without lineside signals. This work aims to define not only technical functions, but also harmonised operational processes, signalling principles, engineering rules and driver interaction.

This is strategically important.

ERTMS cannot become a real European backbone if every country implements it in a way that creates a different user experience, different operating logic and different engineering assumptions. The railway needs more than a shared specification. It needs a shared operational concept.

This does not mean that all networks become identical. But it does mean that variation must be controlled.

The objective is not only to certify ERTMS installations. The objective is to make them behave as part of a coherent European railway system.

This is where the System Pillar becomes important. Its role is to support a common operational vision, a functional system architecture and more harmonised specifications for the future railway.

ERTMS deployment without operational harmonisation risks reproducing fragmentation inside the European standard.

ERTMS deployment with operational harmonisation can create a real backbone.

8. ERTMS as an industrial programme

ERTMS is also an industrial programme.

This point is sometimes underestimated. The railway sector often speaks about specifications, authorisations and deployment plans. But if Europe wants ERTMS to be deployed at scale, suppliers must be able to produce, integrate, test, maintain and upgrade ERTMS solutions with sufficient capacity and stability.

ERTMS deployment requires onboard equipment, trackside equipment, engineering, testing, authorisation, software updates, configuration management, installation capacity, maintenance capability and cybersecurity management. It also requires trained people: engineers, installers, assessors, project managers, operators, drivers, maintainers and safety experts.

A sharp increase in deployment will therefore create pressure on industrial capacity.

This is why long-term planning is essential. Suppliers cannot scale capacity if demand remains fragmented, uncertain or unstable. Infrastructure managers cannot plan efficiently if specifications, funding and deployment priorities are uncertain. Railway undertakings cannot invest confidently if they do not know when and where ERTMS will be usable.

Industrialisation also requires cost control.

ERTMS must be high-performing, but it must also be affordable to deploy, maintain and upgrade. Cost drivers such as repeated tests, national variations, complex authorisation, low modularity, supplier-specific integration and insufficient harmonisation must be addressed.

This is a key lesson for future DATO as well.

A railway technology can be technically successful and still fail to scale if it is too expensive, too variable, too difficult to authorise, too hard to maintain or too uncertain for investors.

ERTMS is therefore not only a deployment programme. It is a test of Europe’s ability to industrialise a common railway architecture.

If ERTMS can become more modular, more harmonised and easier to upgrade, it will also prepare the industrial conditions for DATO.

9. FRMCS and the communication migration

ERTMS also depends on railway communication.

Today, GSM-R provides the dedicated railway radio communication layer used for operational voice and ETCS data communication. It has been a central enabler of ETCS Level 2. But GSM-R is based on 2G technology, and the railway sector must prepare its migration towards FRMCS.

FRMCS, the Future Railway Mobile Communication System, is one of the major transformations ahead. It is expected to support future railway communication needs, including ETCS, operational voice, data applications and future digital services. It is also part of the broader move towards a more connected and automated railway system.

But the migration is difficult.

The specifications must be completed. The migration path must be defined. Infrastructure managers and railway undertakings need to know when to invest. Suppliers need clarity. GSM-R continuity must be secured until FRMCS is ready. Dual operation or transitional scenarios may be required. Cross-border operation must remain reliable.

This creates another system migration problem.

The railway cannot simply switch off GSM-R and switch on FRMCS overnight. Trains and infrastructure will migrate progressively. Some areas may operate GSM-R. Some may operate FRMCS. Some may need dual capability. Operators may need to equip vehicles before the infrastructure is ready, or the other way around.

This is similar to the broader ERTMS migration challenge.

The technology migration is not only technical. It is operational and economic.

FRMCS also matters because DATO will need more communication capability than today’s railway. More automation, more remote supervision, more data exchange, more dynamic traffic management and more cybersecurity all increase the importance of reliable communication.

This is why FRMCS should not be treated as a telecom side project.

It is part of the ERTMS backbone evolution.

10. From ERTMS to DATO

ERTMS is not DATO. But DATO cannot be built without ERTMS.

This distinction is important.

ERTMS provides the European control-command foundation. ETCS supervises train movement. ERTMS/ATO automates driving within the ETCS safety envelope. FRMCS will provide the future communication layer. Future capacity concepts such as Hybrid Train Detection and Moving Block build on digital train control, train positioning, train integrity, infrastructure data and operational coordination.

DATO goes further.

Digital and Automatic Train Operation requires the railway system to coordinate ATO, ETCS, TMS, FRMCS, rolling stock, train health, mission fitness, Remote Driving, perception, cybersecurity, operational rules and data architecture as a system-of-systems.

ERTMS is therefore the backbone, not the complete body.

Its success determines whether future automation can be interoperable or fragmented.

If ERTMS is deployed as a patchwork, with persistent national variations, weak operational harmonisation and long coexistence with Class B systems, then DATO will inherit that complexity.

If ERTMS becomes a harmonised, affordable, modular and widely deployed backbone, then DATO can build on it.

This is why ERTMS deployment matters for the future of automation. It is not a separate topic. It is the foundation of the European automation trajectory.

The path from ERTMS to DATO can be seen as a sequence.

First, harmonise train protection through ETCS.
Then, secure and modernise railway communication through FRMCS.
Then, add interoperable automatic driving through ERTMS/ATO.
Then, improve capacity through Hybrid Train Detection, Moving Block and more dynamic traffic management.
Then, progressively introduce higher automation capabilities through DATO.

This sequence is not purely linear, and several steps will overlap. But the architectural logic remains: DATO needs a backbone.

ERTMS is that backbone.

11. Architecture perspective

From an architecture perspective, ERTMS can be understood through four roles.

The first role is interoperability. ERTMS replaces the logic of national train protection systems with a common European framework. This is the original purpose, and it remains essential.

The second role is safety supervision. ETCS defines the supervised movement envelope. It ensures that trains respect movement authorities and speed-distance constraints. This makes ETCS the protection foundation for future automated driving.

The third role is digital connectivity. GSM-R and FRMCS provide the communication layer needed for ETCS Level 2, operational communication and future digital railway functions. Without communication, the digital railway cannot operate as a connected system.

The fourth role is migration architecture. ERTMS is the system through which Europe moves from national signalling diversity towards a more harmonised railway architecture. This migration includes trackside deployment, onboard retrofit, Class B phase-out, authorisation, cost reduction, operational harmonisation and industrial capacity.

These four roles explain why ERTMS is difficult.

It is not only a product. It is not only an onboard unit. It is not only a trackside installation. It is not only a regulatory requirement.

It is a European railway architecture programme.

This also explains why ERTMS success cannot be measured only by installed kilometres or equipped vehicles. Those indicators are necessary, but incomplete. A more architectural assessment would ask:

Is deployment synchronised between trains and infrastructure?
Are Class B systems being phased out?
Are operational rules converging?
Are costs decreasing through harmonisation and modularity?
Is the driver experience becoming more consistent?
Is the industrial base able to deliver at scale?
Is FRMCS migration prepared?
Is ERTMS/ATO supported?
Does the deployment prepare DATO rather than adding another layer?

These are architecture questions.

They are also the questions that determine whether ERTMS becomes the backbone of the Single European Railway Area or remains a difficult overlay on top of national systems.

The future of ERTMS depends on making the first option real.

12. Conclusion

ERTMS began as Europe’s response to fragmented national signalling and train protection systems.

It remains that response. But it has become more.

ERTMS is now the digital backbone of the European railway system. It provides the protection layer through ETCS. It relies on railway radio communication through GSM-R and, in the future, FRMCS. It supports interoperable automatic driving through ERTMS/ATO. It prepares the foundation for future capacity concepts, automation and DATO.

The 2026 deployment reality shows both progress and urgency. ERTMS is politically supported, legally reinforced and technically mature enough to be deployed at scale. But deployment remains slower than needed. Trackside and onboard migration are not yet sufficiently synchronised. National systems remain. Costs remain high. Operational harmonisation is still incomplete. FRMCS migration brings new uncertainty.

This does not weaken the case for ERTMS. It makes it stronger.

Because the alternative is continued fragmentation.

A European railway system that wants more cross-border traffic, more rail freight, more high-speed services, more capacity, more automation and more resilience cannot remain dependent on national signalling islands.

ERTMS is the common foundation. But it must now be treated as a strategic modernisation programme: industrial, operational, digital and architectural.

The next phase is therefore not only to deploy ERTMS. It is to make ERTMS deployable, affordable, maintainable, harmonised and evolvable.

This is the condition for the next step.

Without ERTMS, DATO has no stable European backbone.
Without harmonisation, ERTMS risks reproducing fragmentation inside the common standard.
Without industrialisation, deployment will remain too slow.
Without migration discipline, ERTMS will remain an overlay rather than a simplification.

ERTMS is not the end of railway digitalisation.

It is where the European digital railway begins.

Documentation and further reading

Voie Libre articles

• Automatic Train Protection
• ERTMS/ETCS: The European Train Control System
• Automatic Train Operation
• ERTMS/ATO: Europe’s Interoperable Train Autopilot
• From Fixed Blocks to Moving Block: Unlocking Capacity on Existing Railway Infrastructure
• Migration to ERTMS/ATO
• Traffic Management System
• Railway Automation: From GoA2 to GoA4
• Remote Driving
• DATO as a System-of-Systems
• Railway Automation, ERTMS and DATO Glossary

European framework and deployment

• European Commission — ERTMS Third Work Plan of the European Coordinator, 2026

Europe’s Rail and future architecture

• Europe’s Rail Joint Undertaking — Work Programme 2026
• Standardisation and TSI Input Plan