Skip to content
Independent reference on the Future Railway Mobile Communication System

Design · 3.11

Assessing test tracks and pilot projects

Time: about 10–13 minutes including the task; estimate

Guiding question: Which pilot finding can be transferred to your project?

Learning objective: You assess pilot reports by findings, limitations and transferability.

Prerequisites: Previous lessons through 3.10, particularly the case file developed there.

What a pilot says about your project

Talbahn reads a report of successful FRMCS trials. This does not mean its own train, service and network configuration has been accepted. A pilot investigates a defined scope. Its findings are valuable when objectives, configuration, versions and results are described clearly.

The following assessment uses public primary sources checked against 11 October 2026. Project objectives remain objectives; reported results apply to the described trial. Current planning information is also provided on the dated page Status and timeline.

Three evidenced perspectives

5GRAIL D5.3 documents a final demonstration on 20 September 2023 in the German testbed. It reports MCPTT group communication and GSM-R interworking, among other activities, and describes limits of the investigations. Talbahn uses it as a source of specific test cases, not as evidence of a later complete V3 implementation. [S46, clause 4]

DB describes 5G-RACOM trials combining railway and public mobile networks with multipath methods in the Digital Rail Testbed in the Ore Mountains. This suggests a useful Talbahn test: deliberately degrade a transport path and measure the application effect. Talbahn's own configuration must still pass that test. [S47]

CORDIS describes FP2-MORANE-2 as a validation project. Its plan identifies three laboratories and five field trials: two at ADIF and one each at DB, Trafikverket and ProRail. These are statements about the planned programme. They do not establish that all trials are complete or every result is public. [S48]

Read a report technically

Report element Talbahn's question
Objective Which function or performance question was investigated?
Configuration Which components, networks, applications and versions participated?
Method Which starting states, loads, movements and faults were introduced?
Result What was measured, within which boundaries and limitations?
Transferability What matches our project, and what needs retesting?

A demonstration can show real progress without testing every combination. A mixed group call under low load, for example, does not establish priority handling under resource scarcity. A report without raw data is not worthless, but its value for particular procurement requirements is limited.

Check your understanding

Talbahn copies “interworking successful” from a pilot announcement into its acceptance matrix. What is missing before marking the entry green?

Model answer

Identify the tested functions, combinations, versions and conditions and their match to Talbahn's requirements. An announcement can justify an investigation direction. Acceptance requires assigned evidence or additional tests of our own.

What to remember

Pilots provide knowledge and test ideas. Results transfer through stated applicability limits, not a generic success label.

Your Talbahn case file

Choose one of the three references and record a usable finding, a limitation and a resulting test of your own. Record source date and retrieval date.

Sources

  • S46 · 5GRAIL D5.3: Conclusion Report on Field Trials

    5GRAIL D5.3: Conclusion Report on Field Trials

    Version: D5.3 · Checked: 2026-10-11

    Scope: Clause 4: demonstration on 20 September 2023 and limitations.

    Limitations: Named teaching edition; no blanket product or project approval.

    Used in: 3.11

  • S47 · DB: 5G-RACOM

    DB: 5G-RACOM

    Version: 2026 · Checked: 2026-10-11

    Scope: Report on hybrid networks and multipath trials.

    Limitations: Named teaching edition; no blanket product or project approval.

    Used in: 2.18, 3.11

  • S48 · CORDIS: FP2-MORANE-2

    CORDIS: FP2-MORANE-2

    Version: 101196125 · Checked: 2026-10-11

    Scope: Project plan: laboratories and five field trials.

    Limitations: Planning statements do not establish completed trials; use the central timeline for schedule information.

    Used in: 3.11

Shared source register

Your progress is stored in this browser on this device.