Make rail options easier to understand and choose.

A useful example is choosing between two rail connections on one corridor. How do transfers, duration, missing information and model assumptions affect that choice? Farleda can explain available options; a pilot tests whether the presentation is understandable and the underlying data is sufficient.

• One corridor, one audience and a clearly stated decision.
• Record the timetable reference, journey chain and data available at the same query time.
• Evaluate understanding and option quality first; attribute bookings only with an appropriate measurement design.

Before integration, we establish which data the partner may provide and which questions it can answer. A timetable feed does not contain measured vehicle energy. Fare information does not establish bookability.

• Timetable and operating data: coverage, usage rights, refresh rules and a technical contact.
• Operator-specific emissions data: vehicle, occupancy, energy basis, period and accounting boundary.
• User access: permitted recruitment, consent and responsibilities.

We propose a frozen set of test corridors and documented comparison cases. Targets are agreed with the partner. These are suggested evaluation criteria, not results already achieved.

• Coverage: proportion of agreed cases with a usable connection and identified source.
• Comprehension: can test participants explain assumptions, duration and transfers correctly?
• Calculation: do units, traveller count, factors and boundaries match the controlled example?
• Handover: an evaluation report, known gaps and a decision on the next integration step.

The pilot programme provides a bounded period for scoping, implementation and evaluation. Price, start date, data rights, responsibilities and acceptance criteria are agreed individually. Production integration and ongoing service commitments require a separate agreement.