Release 2025.2

R2025.1 introduced extensive optimizations with the completely redesigned “Report Duty Changes” feature, especially enhancing collaboration between train drivers and dispatchers. Another highlight was the significant simplification of planning during route interruptions that result in cancellations or rail replacement services (see also: QnamicRelease 2025.1 • QNAMIC ).

Following the comprehensive expansions in the spring, this release focuses on detailed optimization. Numerous UI and performance improvements have been implemented. However, there are also functional advancements: The planning simplifications for route interruptions introduced in the last release have been further refined with the new “Replace Train Section” workflow. Train sections can now be replaced directly from the planning board. All relevant train run data is automatically transferred, and possible alternatives are suggested. Once confirmed by the planner, the new plan is adopted, the old train section is archived, and the process is documented. This step is now significantly faster and, thanks to the automatic transfer of existing data, error-free.

With R2025.2, an ambitious project was also completed, aligning traffic planning more closely with vehicle maintenance planning. Until now, vehicle orders had to be managed via Excel spreadsheets and initiated by email or phone with the transport control center. This mainly affected orders placed by the ECM (Entity in Charge of Maintenance), for example, to schedule vehicles for regular overhauls or wheelset replacements. This ordering process has now been digitized through interfaces: Vehicle orders can now be triggered from a specialized workshop system within the Order Management module. The interfaces were implemented generically using a common language, making it easy to connect systems from different manufacturers (e.g., SAP, IBM, etc.) to RailOpt. Orders are managed within Order Management and treated like regular assignments. This allows maintenance departments, after completing their planning in their maintenance system, to order specific vehicles (by vehicle number) for certain times and schedule them for overhauls. The order is considered in the planning, and the processing status is reported back to the system by the transport control center. Naturally, orders can also be edited or canceled.

We would like to thank our team for their dedicated work and our active user community for their constructive contributions to these developments. As always: After the release is before the release!

We are already looking forward to introducing more innovative features and developments with R2026.1!