Railway Data Interpretation Engine

Identify the train’s route. Qualify its journey.

Using time-stamped GNSS positions, a progression signal—often odometry—and a railway map, MBDD Rail identifies the train’s route and positions the journey by line, track and KP. Supplied events can then be associated with the correct location. The same engine can feed a product with a usable journey or qualify that journey: evidence-backed results, candidates, diagnostics, evidence and sections requiring review remain distinct.

Evaluate a representative journey See how it works

Partner-side baseline A GPS/GNSS trace time-stamped positions, even if incomplete A progression signal often odometry; depending on the use case, speed or a GNSS–inertial chain

Required railway map versioned map of the relevant section, proposed by MBDD-Solutions or provided by the customer.

Enrichments when available supplied source events and rules; operational objects according to map coverage.

Production and qualification Selected route

Produce Selected route · line–track–KP

Qualify Diagnostics · evidence · sections requiring review

Enrich Events associated with the journey

The starting point

Start with the available data.

Events and operational data are often distributed across several departments or systems. Without waiting to assemble everything, MBDD Rail begins qualification from the available baseline; sources opened up later enrich the journey.

Comparison of an RER C journey: on the left, the red raw GPS trace is interrupted in Paris; on the right, the green railway journey is qualified using positions, the progression signal and the topology carried by the railway map. — **RER C example, Île-de-France** The raw GNSS trace loses continuity in Paris. MBDD Rail qualifies the journey using the available positions, progression and railway map; inconclusive sections remain flagged.

The transformation

Position the journey on the railway map.

MBDD Rail workflow Scoped qualification

Partner-side observation baseline

GNSS trace Time-stamped positions Progression Often odometry · depending on the use case, speed or GNSS–inertial data

Required map Reference railway map Track topology · connections · directions · known coverage

Enrichments when available

Supplied source events and rules · operational objects covered by the map

Route identification

Compare · select · support

Route, position and events

1 · According to the evidence level Selected route or candidates 2 · Line · track · KP

3 · Associated source events Diagnostics and sections requiring review Evidence and reservations

Results and decisions

Turn results into decisions.

Use or review the journey

Accept the journey, request a targeted review or reject it.

Target the review

Focus review on candidates, inconclusive sections and recurring patterns.

Use an associated fact

Use its railway position or identify the missing information.

Explore detailed use cases

Events and rules

Associate and qualify events.

MBDD Rail preserves the origin of supplied events, associates them with the qualified journey and distinguishes what it receives from what it issues.

INPUT

Source event

Supplied by onboard equipment, infrastructure or an external system; its origin, timestamp and coverage remain attached to the source.

MBDD OUTPUT

Qualification event

Issued by MBDD to flag an ambiguity, break, limit or section requiring review, together with the corresponding evidence.

PARTNER RULE

Business event

Issued only when a partner-supplied rule applies and is triggered; the rule and the data used remain traceable.

Example of a governed chain

An upstream detection becomes a located railway fact.

Received fact Derived camera detection 10:42:18 · producer and pipeline preserved
MBDD association Line C · Track 2 Increasing direction · available KP 24+738
Partner rule Applicable condition Versioned section, measurement and threshold
Delivery Located business event Evidence, reservations and rule identifier

Explicit boundary

The engine does not process raw images, video or point clouds and does not replace source systems. It qualifies only supplied events covered by the scope; missing data remains non-assessable.

How we work together

From technical qualification to an OEM Production Licence.

MBDD-Solutions supplies and maintains the engine; the partner integrates it into its product and retains the relationship with its users.

Step 1

OEM Technical Qualification

Verify within a bounded scope that the engine fits your product, data flows, infrastructure reference and intended decision.
Evaluate a representative use case
OEM Integration Program

Integrate the selected mode, freeze the contracts and verify conformance, performance and recovery.
Explore the programme
OEM Production License

License the engine for an explicitly named partner product, uses, environments and volumes.

Bounded rights. This model does not automatically include source code, white labelling, a perpetual licence or unrestricted redistribution.
Prepare for production

One engine, two technical modes. Embedded Runtime and Engine API are assessed during qualification; deployment and redistribution rights remain contractual.

OEM Technical Qualification

Qualify MBDD Rail on a representative use case.

Present the need, the data flow to interpret and, where applicable, the target architecture. We frame the scope, results to verify and expected verdict.

Prepare an evaluation