Use cases

Start with the question to answer.

Which journey do the data support selecting? Where did an alert occur? Which sections recur across several runs? Which rule should monitor a measurement or enriched data? MBDD Rail turns these questions into located, verifiable results.

A practical question Real journeys A useful result

Once the railway journey is qualified

One reference for train and network data.

Each train run becomes comparable and can be enriched with available measurements and operational objects. These uses can be evaluated on a bounded dataset or integrated into existing tools and processing workflows.

Compare train runs

Align comparable passages on the same reference to reveal differences and recurring sections, without inferring their cause.

Associate trainborne measurements

Associate each onboard measurement, alert or finding with the qualified journey, including the line, track and kilometre points covered by the infrastructure reference.

Apply a governed rule

Monitor a measurement, enriched data, a section or a qualified indicator using a partner-provided rule.

Connect operational assets

Project equipment, stations, beacons, structures, sections and other objects covered by the versioned reference along the journey.

Qualify the journey in the partner’s reference.

Using data from an instrumented rail vehicle or onboard equipment, particularly in yards, at junctions, in tunnels or in GNSS-degraded areas.

Situation
In a yard, at a junction, in a tunnel or in a GNSS-degraded area, multiple routes may remain compatible with the available observations.
Result
A qualified journey in the partner’s infrastructure reference, including line, track, covered kilometre positions and sections requiring 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.

Monitor a measurement or enriched data.

Apply a partner rule to a time-stamped quantity, technical indicator or external context once the journey has been qualified.

Situation
A team wants to track a percentile change, attitude change, derived measurement or weather context over an identified section, track or asset.
Result
The measurement and applied rule are delivered with the journey, available railway position, coverage and reservations.
Decision
Send a business event to the information system, target a review or declare the case not assessable when the data is insufficient.
Limit
The rule must be supplied and versioned. A threshold or correlation demonstrates neither a physical defect nor its cause.

Associate an alert with the qualified journey.

Associate a time-stamped alert produced by the train, infrastructure or another system with the relevant passage.

Situation
The alert is time-stamped and may already have a source reference without being directly associated with the qualified journey or the reference expected by the application.
Result
The alert is associated with the passage and target reference using the available information, or clearly reported as impossible to associate.
Decision
Use the association, request an additional file or set the case aside.
Measure
Association time and number of incomplete cases.

Associate an inspection finding with the qualified journey.

Associate a human finding, camera detection or LiDAR measurement already produced by another tool with the partner’s reference.

Situation
The finding may have a source reference without being directly associated with the passage, track or reference expected by the application.
Result
The finding is associated with the passage and target reference, together with its provenance and any location uncertainty.
Decision
Forward the associated 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.

Prepare an evaluation