Route Service
Indicator

Overview

A new controller interface to monitor performance

A new controller interface that monitors performance between stations and junctions, as well as through station platforms, alerting controllers to accumulating delays.

This allows a geofenced message to be attached to the infrastructure, automatically alerting staff to the delayed trains whilst also providing a continuous and updated calculation of the average delay expected because of the problem. Registered mobiles and tablets will have a message pushed to them when entering and leaving the affected area.

Features

Based on an abstract map of the TOC broken down into user-definable zones

The system monitors trains between stations and between stations a junction looking for and calculating delays

For each train that passes over a track section, it works out the average delay based on the number of trains that have traversed the section and displays the problem, thereby alerting the controller to delays which are building.

The map is based on TIPLOC locations for stations, sidings and Junctions based on the topology selected

Measures the time it takes for a train to traverse a section of track between TIPLOC’s and comparing this against the train schedule

Intelligent algorithms, machine learning and artificial intelligence, means the solution is continuously learning and updating controllers

Benefits

  • Improved, more accurate information for staff and customers
  • Removes the requirement for manual line of route updates
  • Utilises industry data to help Controllers make better decisions (TD.NET and Darwin)
  • Can calculate delays from multiple operators, when identifying delays
  • A more granular level of data/information down to a TIPLOC and station level
  • Directional delays can be identified
  • Trains can be quickly associated with known delays

Problems we solve

  • Information is often inaccurate, inconsistent, and out of date
  • Line of route delays are often an estimate based on worst case scenario
  • Route delays require manual intervention, regular updates and are often not cleared correctly
  • Legacy systems do not utilise industry data such as TD.NET and Darwin