Annual report 2025  Software: Overview  Product Management

Product Management Review 2025

Viriato Highlights From 2025

As part of the ongoing development that we undertake to improve Viriato for our users, amongst many tactical improvements in 2025 this are some of the features we have implemented within the software.

Program framework:

  • The Viriato Enterprise train window has been replaced by a new implementation which integrates the train and train family windows into a single view like that of Viriato Standard, making working with train and train families easier.
  • The Rolling Stock management view was rewritten and now has the same look and feel as Viriato and offers new data exchange functionality between different Viriato Versions (e.g. Viriato Standard and Enterprise)

Path search and algorithms:

  • The path search module now includes additional settings allowing finer control over how the conflict free paths are found. These include settings which control how much additional time can be added to a train run, whether reserves should be kept for performance purposes, the ability to ignore capacity restrictions in nodes where the user believes sufficient capacity will be available regardless of the analysis, a problem analysis mode which identifies the nodes with insufficient capacity when conflict free paths cannot be found and the improved selection of multiple trains for the case where the user is inserting different trains sequentially into the timetable.
  • A new platform assignment finder module has been added which can search for conflict free platform assignments in stations for existing timetables using the Gurobi solver.

Prototyping and new algorithms:

  • A new algorithm “BzValidator” (from Bauzuschlag, the German term for the engineering works allowance) has been developed for verifying that trains contain sufficient time reserves for engineering works in their planned times. In many countries there are rules that trains must contain a specified amount of reserve time per 100km, or between key nodes there must be a specific amount of reserve time to be allocated for the purpose of good timekeeping despite the train encountering any engineering works.
  • The Conflict Resolver prototype described in last year’s annual report, which uses a mathematical solver to eliminate (or reduce) train conflicts in a timetable using the microscopic model accessed through MoD is being reimplemented in the Viriato program itself in order to enable this feature to be used productively. This development will continue in 2026.

Train planning:

  • A new “passing” stop type has been introduced to model trains which don’t start or end with a stop (for example, when entering the network at a country border), and these are displayed in the graphic views.
  • For each train family, a direction (e.g. up/down) can be defined allowing a standardised view of a train’s travel direction when making planning decisions.
  • There are additional train filters available for node track used, timetable period and model week.
  • For section tracks which are bidirectional, the primary direction can now be defined, and this is then used when routing trains enabling more accurate routing decisions by default.
  • The selection of trains in the graphic timetable has been improved by allowing the selection of multiple trains directly from region drawn with the mouse.
  • In the netgraph, transfer times at stations can be loaded and displayed from the trip time analysis module allowing a clearer view of interchange possibilities within stations.
  • The empty runs templates in the rostering module can now be extended by defining a list of nodes it travels through to create more realistic trains.
  • The workflow in Viriato Enterprise has been improved with several functions now working as they do in Viriato Standard, such as splitting families into single trains, bulk running time calculation and automatically deriving trains which are identical to the template train.
  • In Viriato Enterprise there is a batch function to combining trains which meet at a location into a single train, the Robustness and Path Search modules now work for infrastructures with phases, and the management of train numbers from defined ranges of numbers to be used within a timetable.
  • The Netgraph has had the selection of lines for editing and layouting made easier, and the grouping of trains workflow improved to allow better representation of the desired service pattern.

Data exchange:

  • railML 2.5 timetable import and export has been added to Viriato (in addition to existing railML formats) and certified by railML.org as being compliant with the standard. This ensures that Viriato is aligned with railML versions that are currently maintained by the railML community.
  • Viriato infrastructure (nodes in Viriato Standard and nodes and sections in Viriato Enterprise) can now be imported from Excel spreadsheets, improving the speed of model creation and maintenance.
  • A new optional add-on module is available to export a timetable in the NeTEx (Network Timetable Exchange) format. This format is a CEN Technical Standard for exchanging Public Transport schedules and related data. Currently, only the export of the CH profile is available based on the definition of specific attributes relating to the infrastructure or train runs defined within the Viriato database.

MoD (Microscopy-on-Demand):

  • The Microscopy on Demand (MoD) module has been extended to allow the planning of additional incoming or outgoing routes and the use of additional stops, which are graphically represented in the MoD-Topoviewer and are included in the railML export.