This is the text-only-version of www.rmcon.de. Click here for the complete version


CompanyReferencesConsultingRailSysEcoTransITNewsContactHome


About RailSys
Application fields

System components
  • Database
  • Infrastructure Manager
  • Timetable Manager
  • Operational simulation
  • Slot Manager
  • Track blockings
  • Statistical evaluation
  • Interfaces/Requirements
  • Output possibility


  • Users
    Demo download
    Further information
    RailSys/System components/Statistical evaluation

    Finding problems
    During the multiple simulation, all delays of all simulated operating days will be recorded for each train. Certainly you do not have to work with these heaps of data. With help of the "Evaluation Manager" you may assess the extensive results of the simulation in different types of diagrams. The Evaluation Manager shows the critical points of a timetable via diverse modes of display.

    Delay development
    For a multitude of delay data can be used to create sums of train delays at every desired station in the form of bar charts. This enables the investigation of every change in delay along a route.

    Network graphics
    Network graphics show the delays directly along the track network. The development of delays can be easily identified here

    Punctuality or "on time running"
    These distribution graphs are quite suitable if you would like to prove how often scales of delays occur or that you keep a prescribed punctuality, e.g. 95% of all trains should be not delayed more than 5 minutes.

    Vehicle rostering
    The operational simulation helps you to detect early if in reality a vehicle rotation will not work as planned, e.g. because there were not enough reserves planned. This is an important finding, which may be corrected by timetable alterations.

    Reached or missed connections
    Reached or missed connections could be evaluated by detailed protocols for every train. You are able see how high the average percentage of missed connections is and to then act via timetable variation. Your clients will thank you.

    Hindrances
    You can find out which were the most effective hindrances for every train through the use of the protocol files. This enables such questions as "which switch was occupied in the block and hindered the train to go on?" to be answered. This allows you to assign delays directly to infrastructure elements.

    Data to evaluate
    If you want to find the exact results, here is a list of all possible types of evaluation:
    • Average delay per train (at arrival and/or departure)
    • Average delay per delayed train (at arrival and/or departure)
    • Average additional delay per train (at arrival and/or departure)
    • Average additional delay per delayed train (at arrival and/or departure)
    • Delay due to statistical perturbance
    • Number of delayed trains (at arrival and/or departure)
    • Rate of delayed trains (at arrival and/or departure)
    • Distribution of delays (at arrival and/or departure)
    • Number of platform changes due to routing
    • Development of delays between two stations