R2026.1
The highlight of the Fall 2025.2 release was the closer integration of highly specialized surrounding systems with RailOpt, our highly specialized railway resource management system. Using a generic interface implemented via a common language, maintenance systems from various providers, such as SAP, IBM, and others, can now be easily connected to RailOpt. The resulting vehicle orders allow ECMs, Entities in Charge of Maintenance, to request individual vehicles directly and by exact vehicle number, for example to send them for inspections or wheelset maintenance.
With the Spring 2026.1 release, we would first like to greet our French-speaking users, and those who may become French-speaking users in the future. RailOpt and RailOpt WEB are now fully available in French! This is especially good news for our users at multilingual CFL. Nous vous saluons chaleureusement!
From a functional perspective, the most important enhancements in this release are the further refinements to the “Report Duty Changes” feature. With this update, four additional variants of travel times and services within and outside working time are now available. This allows actual duty and travel times relevant to billing and working-time regulations to be recorded, documented, and processed for planning purposes with even greater precision. Once confirmed in the system, the effects on break times and payroll are automatically taken into account.
To improve transparency, dedicated rows have been added to the planning board, where changes and resulting conflicts are clearly displayed. Train drivers also receive conflict notifications if entries violate working-time regulations or trigger other planning conflicts.
With the upcoming release, dispatchers will be able to accept or reject changes directly in these rows. In addition, the feature will be expanded to include further activities between duties.
The implemented and upcoming enhancements to the “Report Duty Changes” feature were developed in close collaboration with several of our long-standing users. They reflect concrete experience from day-to-day operations and show how strongly the ongoing development of our solutions is shaped by the practical requirements of railway undertakings.
With the transition to TAF/TAP TSI, the way planners and dispatchers work is changing dramatically. As a result, the requirements for RailOpt are changing as well. After intensive development work, RailOpt now supports the business processes involved in train path ordering. The new way of working introduces new, dynamic information that is relevant for planners and dispatchers. This information must be easy to access at the right time, without visually overloading the user interface. For this reason, the status information for train paths ordered via Telematics TSI is now displayed clearly using color codes in a separate area above the services. Additional actions related to train path ordering can also be triggered from this area. In a future release, train inconsistencies will also be displayed in this dedicated area.
A heartfelt thank-you to our team for their tremendous efforts over the past few weeks, and to our user community for the many suggestions, ideas, and continuous feedback. This is exactly what drives the improvements that define this release.
And as always: after the release is before the release. We look forward to everything we will tackle together next with R2026.2.