Horus module for the recording and preservation of train control and performance data.
Rail event recording is the process of logging specific controls, control performance, and other onboard systems. Train event recorders log data types such as train location, time, speed, direction of travel, brake commands, automatic train control data, and operational commands, among other recorded information.
Event recording is necessary for capturing key data for the investigation of train or operational incidents. Without a dedicated train event recorder, determining the sequence of events leading up to a rail-related incident can be quite difficult. With modern technology available, there are many forms and configurations in which an event recording solution can be built per application. The issue is procuring and maintaining these (usually) independent systems which may require more capital. In this regard, a solution that offers a more integrated approach can provide an always-on device and reduce the need for specialised maintenance.
As Horus captures, processes, records and stores data, the system can be configured to interface with onboard hardware and software to act as an event recorder. This is a powerful add on, software-only application for rail operators looking to complement their existing Horus application. The Horus onboard computer can even be built to crash worthiness standards. Overall, Horus can be configured as a high grade event recording system and becomes an ideal solution for network operators who require a cost-effective event recorder, without the need for another specialised onboard device.
By centralising and logging data from Horus sensors, driver and train performance, as well as onboard controls, operators have greater awareness of events and occurrences onboard their trains. Collected data is configurable to an operator’s business needs and any further Horus applications. All system log files, location and speed data, camera imagery, accelerometer, and navigation sensor data can be structured into an event sequence file that can be replayed for analysis and assessment, or archived as required. This data can also be encrypted for security purposes.
Event replay: Footage from Horus sensors (and other onboard systems as configured) can be played back in real-time to assist in back-end analytical processing.
Crashworthiness: The Horus onboard computer can be built to crash worthiness standards if required.
Built for rail: All system components are rail regulatory, ruggedised standards or as per a Rail Infrastructure Maintainer’s requirements.
One device, many applications: One powerful hardware solution allows many parallel software applications to be operated with no more equipment being necessarily required.
Communicate event information in minutes, not hours: By linking communications functionality to a Horus system, selected information can be communicated to network operations as required. This enables faster response times and the ability to intervene in developing adverse situations.
Configurable: Event recording can continue post the event to capture information surrounding an incident. This can be configured to each applications’ requirements.
Rail vehicle agnostic: Event recording can be used on any rail network, including passenger, freight, and specialty or rail work vehicles.