iRFP English

Here you will soon find the new features of the December 2025 annual update.

 

 

New FBS-Features And Current Developements

FBS Yearly Update December 2025

Below you will find new features that we partly presented at the FBS user conference in May 2025 in Dresden and September 2025 in Koblenz.

Overview:

iPLAN, General

Introduction of Tabs

The main window can now display a tab bar. It shows all opened windows and allows to quickly change between them. The order can also be changed via Drag&Drop. Right clicking the bar next to the last tab also allows to customise it and its appearance.

Rework of the Train Summary window

Numerous adjustments to the window make it easier to work with and find trains. The total number of train is no displayed at the bottom right. Pressing CTRL+A selects all trains. In addition, finding trains based on their operation days was simplified. The cog button can be used to adjust how sets of days (SD) are displayed. In addition the "..." button in the operation days filter opens menu similar to the moon button and the operation days filter now works semantically. Searching for e.g. "1.5." shows every train that runs on the first of May.

Rework of the Window Change train numbers for several trains

Layer and grouping are now adopted from the train summary window and displayed., The train number range is now created automatically based on the selected trains, but can also be set manually.

The new function renumber consecutively renumbers the list to the right, starting from the top, without any gaps. Even and uneven numbers are incremented independently. If the new train numbers to be assigned are already in use, this is shown in red (however, this can also occur if the train number 'frees up' due to being reassigned, so the warning should be treated with caution).

It is also possible to assign a new train number index.

Small adjustments

  • The FBS start window and updates now use the https-protocol (instead of http) which conforms to modern safety standards.
  • Zooming in the network map has been changed from Num +/- to CTRL+Num +/-.

iPLAN, Graphic Timetable

Function Call up train (Alt+Z) improved

The function Call up train now preferably finds visible trains. If there are no visible trains in the graphic time table, an invisible train will be opened instead. Starting from the selected train the next visible instance of the train number is opened (ignoring the primary path).

Die Funktion Zug aufrufen findet jetzt bevorzugt sichtbare Züge. Sollten keine passenden sichtbaren Züge im Bildfahrplan vorhanden sein, wird stattdessen ein unsichtbarer Zug geöffnet. Es wird vom markierten Zug aus die nächste sichtbare Instanz der Zugnummer geöffnet (ungeachtet der Hauptlaufs). Soll nach einem bestimmten Hauptlauf gesucht werden muss explizit "-Hx" hinter der Zugnummer eingegeben werden (z.B. "80513-H1"). Wird keine sichtbare Instanz gefunden, wird stattdessen die nächste nicht sichtbare Instanz gefunden.

iPLAN, Customer's Timetable

Numerous minor adjustments to the timetable

  • The spacing between column separators and letters in 'From/To' rows has been increased.
  • The window Synchronise customer's timetable now has filters below the change list.
  • Connections are also synchronised with Synchronise customer's timetable.
  • New function when creating new customer's timetables to hide external arrival/departure times:
    • The first arrival time is deleted if the train in the table starts with an arrival at a from/to station.
    • The last arrival time is deleted if the train in the table ends with a departure from a from/to station.
  • The 'ar' for arrival times in departure rows is now below the time instead of to the left of it (as long as there is enough space).
  • Under Global Programme Configuration --> Timetable, Light Set A now has its own column.
  • Inserting a travel connection also fills in previous stops. This may result in better connections being overlooked. (Example: Train travels from Amstetten to Vienna. Arrival in St. Pölten is also filled in, even if there may be a better connection from Amstetten).
  • Adding a train within the (previous) operating day limit causes this to be recalculated - if none can be determined, the train is placed at the end.
  • If connection chains have different operating days, these are combined. If the times differ, the shortest transfer time is ‘rounded up’.



iPLAN, Station Timetable

Multiselect implemented in the track occupancy scheme

The following actions are supported:

    • Assign track
    • Label settings of trains
    • Delete trains
  • Deleting trains doesn't automatically delete their dependent switchovers (anymore)
  • Vehicle switchovers can be deleted via Drag&Drop in the track occupancy scheme ("Drop" on the base train). If there is more than one switchover from the base train, a list with all switchovers is shown
  • Platform position (left/right to the track) is adopted from the infrastructure data of the graphic timetable when creating a station timetable
  • Filter for days of operation added to the headerlists for trains and vehicle switchovers, including semantic analysis of operational days
  • When the station timetable is closed, the current view (train summary in table form/vehicle swithcovers/track occupancy scheme) is safed in the registry and automatically applied when the station timetable is opened again
  • New function "Transfer track allocations to the trains in the graphic timetable": A list shows differences of the track allocations in the station timetable and graphic timetables, allowing the user to select individual entries for synchronisation. An attempt is being made to keep the "primary" track of a train in the graphic timetable. If the "primary" track is changed, there is an implicit recalculation of the train run times.
  • Function "Open graphic timetable of train" has been added.

railML-Export

  • railML-export now suppoerts railML 2.5.
  • If there is no train product, the train category is used instead
  • Closed carriages are no longer included for amount of seats
  • A unique railML formation is created for every train composition with/without closed carriages
  • Internal short terms and names of vehicles are also put out for carriages

Return to the top