Knowing what TSI CCS 2023 requires is one thing. Applying it to an existing fleet is another. Retrofit projects are where the new regulation creates the most complexity — and where teams with incomplete preparation consistently run into serious difficulty.

Why Retrofit Is Harder Than Greenfield

New infrastructure projects start with a clean slate. Retrofit projects do not. Older rolling stock was designed without ETCS in mind — limited physical space, non-standardised interfaces, legacy communication buses, and ageing brake systems all create constraints that simply do not exist in greenfield deployments.

TSI CCS 2023 introduces five new mandatory provisions — CMD, TIM, ETH-CN, cybersecurity, and FRMCS readiness — on top of the Baseline 4 requirement. Each one is manageable in isolation. The challenge is integrating all of them into a vehicle that was not designed to accommodate any of them.

---

The Four Most Common Sources of Project Difficulty

1. Skipping the Architecture Assessment

The single most common cause of scope creep and schedule overrun in retrofit projects is proceeding to procurement without a thorough system architecture assessment.

Older vehicles frequently lack standardised interfaces for new ETCS hardware. Physical space constraints affect where OBUs, antennas, and ETH-CN switches can be installed. Brake and traction signal interfaces vary between fleet types and manufacturers.

A comprehensive architecture assessment before any procurement decision is not optional — it is the difference between a project that delivers on time and one that does not. This assessment should cover:

• Available space for new hardware
• Existing interface standards and gaps
• Compatibility with CMD and TIM requirements
• ETH-CN cabling feasibility
• Antenna placement for FRMCS readiness

2. Late Interface Definition for TIM and Brake/Traction Signals

TIM integrates with odometry, brake systems, the DMI, and the RBC. The boundary between ETCS and TCMS needs to be defined precisely — and it needs to be defined early.

Teams that delay this decision consistently encounter integration problems in the final stages of a project, when options are limited and costs are high. Define TIM interface boundaries as part of the architecture assessment, not as a detail to resolve during system integration testing.

The same applies to brake and traction signal interfaces. These are the points where ETCS interacts most directly with the vehicle’s existing systems, and ambiguity here creates problems that are expensive to resolve late in the project.

3. Managing Safety and Cybersecurity in Silos

Under TSI CCS 2023, safety and cybersecurity are joint lifecycle activities. EN 50701 mandates a cybersecurity lifecycle that runs in parallel with — and is integrated into — the safety lifecycle.

In practice, many organisations still treat these as separate workstreams managed by different teams with limited coordination. The result is authorisation delays that are extremely difficult to recover from. Safety cases that do not address cybersecurity risks are increasingly rejected by notified bodies.

The fix is straightforward in principle but requires deliberate organisational change: safety and cybersecurity teams must collaborate from project initiation. Joint management plans and integrated validation reports should be the standard deliverable, not an afterthought.

4. Underusing Simulation Environments

On-track validation time is expensive, constrained, and difficult to reschedule. Issues discovered during on-track testing have a disproportionate impact on project timelines because the options for resolving them quickly are limited.

Simulation environments allow teams to identify and resolve integration problems before they become field problems. The investment in simulation infrastructure consistently pays back — not just in cost terms but in the quality of the on-track validation process itself, which becomes a confirmation exercise rather than a discovery exercise.

---

Incorporating CMD, TIM, and ETH-CN Into Retrofit Scope

Each of the three new mandatory interface provisions creates specific retrofit challenges worth understanding in detail.

CMD requires continuous monitoring of motion data during standstill. For fleets without redundant tachometers or digital brake sensors, additional hardware is needed. This hardware needs to be integrated, validated, and included in the safety case. Budget and schedule allowances for this are frequently underestimated in early project planning.

TIM adds complexity to the brake system interface. The choice of implementation method — physical sensors, pneumatic checks, on-board algorithms, or driver declarations — has significant implications for validation scope and ongoing operational procedures. This choice should be made during the architecture assessment, not during detailed design.

ETH-CN introduces significant cabling work on older vehicles. Cable routing through existing vehicle structures, switch installation, and EMC compliance testing all need to be scoped carefully. Hybrid architectures — ETH-CN alongside retained legacy buses — are permitted during the transition period and can significantly reduce the cabling scope for initial retrofit phases.

---

Strategic Recommendations

Based on the patterns visible across recent ETCS retrofit projects, five things consistently differentiate successful projects from difficult ones:

1. Commission a thorough architecture assessment before procurement. Understand your legacy constraints before committing to a technical solution.
2. Define TIM and brake/traction interface boundaries early. Make this a deliverable of the architecture phase, not something resolved during integration.
3. Integrate safety and cybersecurity management from day one. Joint management plans, shared risk registers, and integrated validation reports are the standard you should be working to.
4. Invest in simulation infrastructure. The return on investment is consistently positive when measured against the cost of on-track validation delays.
5. Plan for FRMCS readiness now. Even if your project sits within the dual-bearer phase, antenna placement and router integration are significantly easier to accommodate during a retrofit than to add retrospectively.

---