Presenting a technical paper - Why presenting this research matters more than publishing it

One of the opportunities I look out for as a young engineer is the chance to present a technical paper and gather learnings from it. In December 2025, I had the opportunity to present my technical paper at the IRSE ASPECT 2025 conference in Yokohama, Japan. As well as the chance to visit a new city, I was excited to present my paper and see what panel discussions would follow.

As most of you in the rail industry (and passengers) know, we are currently facing a paradox: we are being asked to run more trains on the same infrastructure while using significantly less energy. With traction accounting for roughly 86% of total rail energy use, this presents a fundamental operational challenge. The intersection of engineering and modelling – the area I work in – is often looked at to address this.

My recent paper, Leveraging Operational Modelling to Drive Efficiency and Sustainability in Rail Systems, argues that modelling must move from a specialist academic tool used only for megaprojects to an everyday driver of decision-making. Whether evaluating ETCS/ATO rollouts or quantifying Time Signal at Red (TSAR) inefficiencies, modelling allows us to find the operational frontier of existing networks before committing to major capital spend.

Presenting this research at the ASPECT conference highlighted a crucial reality: publishing is passive, but presenting is transformative. While my case studies showed we can detect instability and energy-performance trade-offs (like Energy × Average Minutes Late) before they happen, the real value lay in the dialogue that followed the presentation. I learned that infrastructure engineers, asset managers, and energy specialists all see modelling through different lenses: capacity, cost, or carbon.

The panel discussion that followed my presentation reinforced a sobering gap: modelling is still too often used reactively rather than proactively. To bridge this, we must move beyond the technical "how" and focus on the strategic "why." If we want to move from "interesting technical tool" to "strategic operational necessity," we must translate our simulations into the language of business and operations. Modelling shouldn't sit in isolation; it should be the heartbeat of our energy and asset strategies.

Written by Kuldeep Dungarwal