Skip to main content

Scenarios

Timetable scenarios​

The scenario module allows the creation of new scenarios.

The scenario is a container for a new timetable based on an infrastructure release and a validity period. The validity period of the scenario needs to be within the validity period of the infrastructure release, but can be shorter.

Scenario status​

The scenario can change its state. A newly created scenario is always in the state "Draft". At the moment scenario state changes are not yet available. Three scenario state are available:

  • Sandbox, for creating, drafting, modifying timetables on various time horizons and without editing restrictions.
  • Live, for management of published timetables and synchronisation with TMS and other downstream systems, with editing restrictions (details coming soon)
  • Historic, for import of real data ("Actual trains"), no editing possible

The scenario status is currently under development. More information coming soon; please also check the release notes.

Scenario management​

It is possible to transfer elements from one scenario to another. Some elements will only be transferred under certain conditions. Elements related to OCP or other infrastructure elements not present in the new scenario and elements outside the validity period of the new scenario will not be transferred. Currently it is possible to transfer the following elements:

  • Annotations
  • Train categories
  • Corridors
  • Distributions
  • Holidays
  • Operating Calendars
  • Peak hours
  • Simulation (setups)
  • Station load factors
  • TOCs
  • TCRs
  • Timetable planning rules
  • Train searches
  • Scenario collections
  • User collections
  • Default track assignments
  • Train state

In many cases it is also possible to transfer trains from one scenario to another. Trains with itineraries not corresponding to the infrastructure release or the validity (custom calendar outside the scenario validity period) will not be transferred.

Scenario duplication​

The scenario duplication will duplicate the scenario with a new name and scenario code. Optionally, a change of validity and infrastructure release is possible. If validity period and infrastructure release are not modified, all trains will be duplicated into the new scenario. If validity period or infrastructure release are modified, only trains complying with the modifications will be duplicated. This means trains with a Custom bitmask outside of the new scenario validity will not be duplicated, for example. Trains with a regular Operating Calendar pattern (i.e. every Friday) will be adapted to the new scenario validity period.

Locked scenario​

A scenario is locked if modifications to existing objects in the following characteristics of the Project or Scenario are performed:

  • Travel margins
  • Stop margins
  • Trainset
  • Trainset parts
  • TOC
  • Train categories
  • Holidays
  • Operating Calendars

Additionally, a scenario is locked if new objects in the following characteristics of the Project or Scenario are created:

  • Travel margins
  • Stop margins
  • Trainset
  • Trainset parts

A locked scenario means users will not be able to edit, create or delete trains until the scenario has been unlocked by an admin user.

The lock is necessary to facilitate editing on the abovementioned objects and successively update the timetable without the loss of data. When a scenario is locked it is still possible to edit the Project and Scenario information. We advise to execute the modifications with due care. In case of doubt, please contact TRENOlab before starting the editing of Project and Scenario settings.

As modifications to those objects should be very rare and occur mainly during the testing and setup phase, a locked scenario should be reported to your trenoLive contact person or TRENOlab directly. As an admin you can unlock the scenario by clicking on the "Unlock" button in the table of "Scenarios to unlock".

Please do not click on the "Reproject" without explicit instructions to do so. Reprojection of trains happens automatically during the unlocking process.