Compare train runs
Align comparable passages on the same reference to reveal differences and recurring sections, without inferring their cause.
Use cases
Start with the question to answer.
Which route did the train take? Where did an alert occur? Which sections recur across several runs? MBDD Rail turns these questions into located, verifiable results.
Once the railway journey is qualified
One reference for train and network data.
Each run becomes comparable and can be enriched with the available measurements and operational objects.
Associate trainborne measurements
Place each trainborne measurement, alert or finding at the right time, on the right track and at the right kilometre point when available.
Use high-frequency data
Preserve useful temporal detail when the signals, their metadata and the reference support its qualification.
Connect operational assets
Project equipment, stations, beacons, structures, sections and other objects covered by the versioned reference along the journey.
Determine which tracks are supported by the journey evidence.
For measurement, inspection or operational trains, particularly in yards, at junctions, in tunnels or in areas with degraded GPS.
- Situation
- The GPS trace passes near several tracks and does not provide enough evidence to select a route with certainty.
- Result
- The most coherent tracks, available kilometre positions and passages that still require review.
- Decision
- Use the journey, review selected passages or reject it.
- Measure
- Time saved on manual review and the number of journeys that can be used without rework.
Identify sections where train runs change.
Compare similar passages and highlight places where a change recurs.
- Situation
- Teams have to review long journeys even though only a few sections may warrant investigation.
- Result
- A short list of sections recurring across several runs, with observed measurements and analysis limits.
- Decision
- Focus monitoring on these sections, adjust it or stop it.
- Measure
- Track length and number of sections requiring review before and after the MBDD analysis.
Place an alert at the right journey location.
Associate a time-stamped alert produced by the train, infrastructure or another system with the relevant passage.
- Situation
- The alert exists but is not yet associated with the track, kilometre point or exact time of passage.
- Result
- The alert is placed on the journey using the available information, or clearly reported as impossible to locate.
- Decision
- Use the location, request an additional file or set the case aside.
- Measure
- Association time and number of incomplete cases.
Locate an inspection finding.
Place a human finding, camera detection or LiDAR measurement already produced by another tool on the journey.
- Situation
- The finding exists, but identifying the track and exact location still requires manual research.
- Result
- The finding is associated with the corresponding passage, together with its source and any location uncertainty.
- Decision
- Forward the located finding or request targeted rework.
- Limit
- MBDD Rail does not read images, video or point clouds and does not diagnose the physical condition of infrastructure.
A different need?
Three questions are enough to begin.
An initial discussion establishes whether MBDD Rail can provide a useful answer with the available data.
What do you want to locate?
A train, measurement, alert or finding produced by another system.
Where should it appear?
On a line, track, kilometre point or section, or near a railway asset.
How will you use the result?
Review a journey, monitor a section, prepare an intervention or forward a located finding.
Scoping
Send us one journey and the question to answer.
We will explain what your files already support, what is missing and how to assess the value of the result.