Time-stamped GPS/GNSS positions
A time-stamped trace, even if some points are missing or precision falls in places.
Evaluation using your data
Verify MBDD Rail using your data before integrating it.
Using a representative journey, MBDD-Solutions runs the engine, measures the results and documents the limitations. You can then decide to integrate, complete the data or exclude the assessed scope.
This scoped evaluation constitutes the OEM Technical Qualification. It specifies the metrics, produced journeys, sections requiring review and recommended integration conditions.
To get started
The useful minimum is often simpler than expected.
For the qualification, we verify whether your positions and a usable progression signal can be compared with an infrastructure reference for the relevant section. This signal may come from speed, odometry or a time-stamped GNSS–inertial chain. The infrastructure reference may be provided by MBDD-Solutions or by your teams.
Time-stamped progression signal
Speed, odometry or a GNSS–inertial chain that tracks the train’s progression.
The sector’s railway infrastructure reference
Infrastructure reference availability is verified for each section. The qualification specifies the source, version, topological coverage, available KPs and objects, and applicable rights. Your own infrastructure reference can be used when it must be authoritative.
Depending on the representative use case
Also qualify event association and monitoring rules.
When your product already receives alerts, camera or LiDAR facts, derived measurements or infrastructure events, the qualification can verify their admission, railway association and expected delivery.
Describe what is already produced
Producer, type, timestamp, unit, upstream pipeline, coverage, declared quality and available event dictionary.
Define the expected decision
Observed quantity, section or asset, window, threshold or condition, recipient and expected behaviour when the data is not assessable.
Verify the end-to-end result
Available journey, line, track, direction and KP, produced event, rule identifier, evidence, reservations and integration format.
Raw camera media, video and point clouds are not analysed by the engine. The qualification uses the finding, detection or measurement already produced by the source chain.
Association of previously produced camera or LiDAR facts can currently be evaluated through the Embedded Runtime; the corresponding Engine API extension is not active. Infrastructure events remain limited to the profiles, types and coverage governed for the scope.
The principle
The qualification identifies precisely which data must be completed.
You know which file to add, which section to revisit and which result can be measured after completing the data.
-
Define the decision
What you want to verify and how to recognise a useful result.
-
Review the files
GPS/GNSS, progression, infrastructure reference and, depending on the case, supplied events, coverage and rules.
-
Qualify the journey
Select tracks supported by the evidence and flag uncertain passages.
-
Compare
Measure review time and the quality of the results obtained.
-
Choose the next step
Proceed with integration, complete the data or exclude the assessed scope.
Deliverables
The result, its limits and the files needed to review it.
The output begins with a concise summary. Technical details remain available for those who need to review or reproduce the calculation.
What the qualification must verify
The initial question, selected journeys and the criteria used to assess the result.
Condition of your files
Covered periods, interruptions, time offsets and missing data.
Journeys and sections requiring review
Selected tracks, associated facts, produced events, uncertain sections and the reasons explaining each limitation.
Results and next step
Measured results and a clear recommendation: integrate, complete the data or exclude the assessed scope.
At the end
An integration decision based on measured results.
At the end of the qualification, the partner has the information needed to proceed with integration, complete the data or exclude the assessed scope. The decision is based on criteria defined before execution and on reproducible results.
- Integration recommended: the results meet the agreed criteria.
- Data to complete: an identified gap still prevents the criteria from being met.
- Scope not suitable: the engine does not sufficiently meet the assessed need.
Take action
Present a representative use case.
Once the need, available data streams and expected decision have been clarified, submit these elements to scope the OEM technical qualification.