IoT and big data in rail are transforming how infrastructure managers understand their assets, but understanding and deciding are still two different things writes Adam Medley, Head of Operations at Rail BI.
The rail industry is in the midst of a data revolution. Sensors are being embedded across infrastructure at scale, IoT connectivity is expanding rapidly and the amount of asset condition information available to infrastructure managers has never been greater.
But volume isn’t the same as value, and for all the investment in data capture, planning processes are not always keeping pace. In a lot of cases, we see the volume of condition data growing faster than an organisation’s ability to absorb and use it in live planning.
Simply put, the industry is only beginning to seriously grapple with what happens to that information once it exists, and while the majority of condition data is currently making its way into the planning process, it’s not always doing so directly or systematically.
In too many organisations, the teams managing asset condition data and planning and investment decisions work in separate systems with no automatic connection between them. Inspections are completed, condition records updated and assessments filed, but that information then has to be manually extracted, translated and passed between organisational siloes before it can influence a workbank priority or inform a business case.
At each of those handoffs, there’s latency, interpretation and the risk of inconsistency. By the time asset condition data reaches the people making investment decisions, it may already be out of date, partially understood or simply not visible in the planning environment at all.
The result is a gap between what the data shows and what actually gets decided, and in an industry where investment decisions shape infrastructure for decades, that gap has real consequences.
When Small Gaps Become Big Problems
At programme scale, small disconnects rarely stay small. A renewal date that hasn’t been updated, a cost assumption that no longer reflects current conditions, a package built on stale data… any of these can skew prioritisation decisions, compromise reporting accuracy and weaken confidence in the plan as a whole.
This, in turn, means that planning becomes slower and less reliable. Operators spend more time checking assumptions, programmes become harder to prioritise clearly and the network is exposed to more poorly timed or weakly justified interventions.
Closing the Loop
The answer to this problem is better connection between the data and the planning processes that should be shaped by it. What the industry needs, and what Rail BI was built to deliver, is a closed loop: an environment where asset condition information and infrastructure planning live together, and where a change in one automatically informs the other.
In practice, this means that when a field assessment is completed, it doesn’t disappear into a separate system awaiting manual review. It’s structured, approved and used to update the underlying asset and renewal data directly. That updated information then flows into the planning environment, where teams can adjust interventions, re-sequence packages, revise cost profiles and update business cases without having to rebuild everything from scratch or reconcile across multiple disconnected tools.
The difference this makes is most visible at the point where asset condition changes unexpectedly. Take a location where new assessment results show that some assets require earlier intervention than planned, while others can safely be deferred. In a disconnected environment, acting on that information means a manual process of extraction, recalculation and re-submission that can take weeks. In a connected one, the planning environment updates to reflect the new picture almost immediately, allowing teams to re-sequence the package, revise the cost model and strengthen the business case while the decision still matters.
This is what closing the loop looks like in practice: not a single technology, but a single environment in which asset evidence and planning action stay connected from field assessment through to investment decision.
What Good Looks Like
Closing the loop isn’t a single implementation project with a defined end point. It’s a shift in how an organisation thinks about the relationship between asset data and planning, and the characteristics of organisations that have made that shift are recognisable.
The first is a single, governed asset picture. Rather than condition data spread across inspection systems, spreadsheets and local records, there’s one authoritative source that feeds everything downstream. Teams aren’t reconciling competing versions of the truth before they can make a decision, they’re working from the same evidence base, with the same assumptions, in real time.
The second is structured assessment workflows. Field data doesn’t arrive in the planning environment informally or inconsistently. There’s a defined process for how assessments are completed, approved and translated into updates to the asset and renewal picture. That structure is what makes automation possible and manual reconciliation unnecessary.
The third is a planning process that isn’t dependent on repeated spreadsheet reconciliation. Changes in asset condition are reflected in workbank priorities quickly enough to support live decision-making. Scenarios can be compared, costs modelled and business cases updated without starting from scratch each time. The planning environment moves at the speed of the evidence, rather than the speed of the next manual review cycle.
Together, these characteristics define an organisation that’s genuinely connected IoT and big data in rail to the decisions that matter. Not one that is simply collecting more information, but one that’s consistently acting on it.
From Collection to Connection
The conversation around IoT and big data in rail has never been more active, as the use cases are multiplying, and the potential to run a safer, more efficient and better-planned railway is real. But the industry’s attention has been disproportionately focused on the collection end of the data pipeline.
The organisations that will see the greatest return on their investment in IoT and big data in rail are not necessarily those with the most sophisticated data capture. They will be those that have done the harder, less visible work of connecting that data to planning: building the governance, workflows and integrated environment that allows asset evidence to drive investment decisions in something close to real time.
For infrastructure managers who want to explore what closing the loop could look like for their organisation, why not come speak to us at The Rise of IoT, AI & Data in Rail 2026 conference this month in Cologne? We’ll be there on 20-21 May and welcome your questions. For those unable to attend, reach out to us via railbi.com or [email protected].