MBDD-Solutions MBDD Rail
FR EN
Evaluate your data

Railway journey qualification

From GPS to the kilometre point. The journey becomes usable.

GPS positions do not always show which track a train is using. MBDD Rail places them on the railway network to qualify the journey, locate each measurement by line, track and kilometre point (KP), and associate the assets encountered. Uncertain sections remain clearly flagged.

Evaluate a journey See how it works
Your data A GPS/GNSS trace time-stamped positions, even if incomplete A progression signal speed, odometry or a usable GNSS–inertial chain

A challenge specific to rail

When GPS is no longer enough.

In a yard, at a junction or in a tunnel, the nearest track is not always the track travelled. MBDD Rail qualifies the journey against the railway topology and delivers the selected route when supported by evidence, together with its evidence, reservations and sections requiring review.

RER C journey comparison: on the left, the raw red GPS trace is interrupted in Paris; on the right, the green qualified railway journey remains continuous. Raw GPS trace Qualified railway journey
RER C example, Île-de-France The red trace loses continuity in Paris. The green journey is produced from the available signals and network topology. Inconclusive sections remain flagged in the deliverable.

Paris and tunnels

Continuity can be supported despite degraded GNSS when the other signals and network topology provide sufficient evidence.

Without relying on a train speed sensor

A time-stamped GNSS–inertial chain can be qualified without odometry when it provides usable progression.

High-frequency data

Useful frequency and precision are qualified against the available measurements, metadata and reference.

The transformation

Turn GPS coordinates into railway information.

Latitude and longitude locate a point on a map. MBDD Rail places that point on the railway network and identifies the surrounding railway context.

  1. Locate every measurement on the network

    The trace becomes a sequence of positions associated with a line, track, direction of travel and kilometre point when available.

  2. Project operational assets onto the journey

    Equipment, stations, beacons, structures, sections and other objects are placed along the progression when covered by the reference.

  3. Share a common railway reference

    Measurements, alerts and successive runs use the same reference. Teams know where to look and what remains to be confirmed.

The result

A useful view from the first screen.

The selected journey, sections requiring review and associated facts are shown before the calculation details.

Qualified railway journey

The selected route, without hiding inconclusive sections.

Targeted diagnostic

Only the sections that require team review.

Operational context

Measurements, alerts and assets associated with the relevant passage.

Use cases

Practical questions for your teams.

Which route did the train take? Where should teams look? Where did an alert occur?

Identify the tracks supported by the evidence

Decide whether to use, review or reject the result.

Target changing sections

Focus monitoring where it is useful.

Locate a railway alert

Use the location or report what is missing.

Explore use cases

A progressive offering

From the first journey to operation within your information system.

Start by verifying the value of MBDD Rail on your own data. Whether you choose the File Runtime or the Pilot Journey API, MBDD Rail integrates with your information system to suit your data flows, volumes and operating constraints.

  1. Recommended starting point

    Scoped evaluation

    Measure the value of MBDD Rail on a small number of journeys and your own files.

    • Qualified journeys and available positions
    • Sections requiring review, evidence and limits
    • A clear recommendation for the next step
    Evaluate a journey

  2. File Runtime

    Process file-based batches regularly within your information system, without requiring prior API integration.

    • Structured file-based inputs and outputs
    • Diagnostics and evidence package
    • Results that teams or information systems can use
    Explore the File Runtime

  3. Pilot Journey API

    Build a qualified journey history, compare journeys and integrate their results into your tools.

    • Searchable history of journeys and their evidence
    • Comparison over shared topological sections
    • Collective variation campaigns across comparable cohorts
    • Progressive connection to the information system

    Evolving value. Collective campaigns currently qualify variations in speed or longitudinal acceleration. Zone-based comparison of train attitude, when supplied by a documented GNSS/INS chain, is an extension that still requires qualification.

    Explore an integration

You do not have to choose immediately. The scoped evaluation first verifies value on your data. The File Runtime or Pilot Journey API are proposed when the scope and results justify them.

Scoped evaluation

Evaluate a first journey.

Send us one journey, the question to answer and the list of available files. In 30 minutes, we define what an initial evaluation can genuinely demonstrate.

Prepare the evaluation