At the end of last month’s article, I planted a seed. I wrote about Digital Automatic Coupling (DAC) and its significance for ETCS deployment on freight corridors. The argument was straightforward. DAC enables continuous monitoring of train integrity across a freight consist, which in turn makes Hybrid Train Detection (HTD) viable for freight. And HTD, as I explained, is arguably the greatest practical step forward for ETCS capacity since the technology was invented. A genuine unlock.

The final paragraph of that article contained a sentence I want to pick up today. I wrote that the interface between DAC-enabled train integrity reporting and ETCS onboard and trackside systems is “precisely the kind of thing that needs rigorous, independent validation before it goes near a live railway.”

I meant every word of it. And today I want to explain why.

The Testing Problem Nobody Talks About

Railway signalling has always had a testing problem. Not a shortage of testing, quite the opposite. Every project tests extensively. The problem is where and how that testing happens.

For most of the history of ETCS deployment, serious integration testing has been done in one of three ways. First, on the live railway, in possessions, at great inconvenience and cost. Second, on dedicated test tracks, where they exist, in countries that had the foresight and funding to build them. Third, at supplier test facilities, where the environment is controlled but, critically, the equipment under test is always that supplier’s own.

To read more about this article and to have full access to premium content SUBSCRIBE to Basic Subscription Plan or Premium Subscription Plan.