TYRELL IO
Twelve Years On. Still the Gold Standard.
A Class Leading Messaging System
Tyrell IO is the UK’s leading rail disruption messaging system, used right across the industry. Hundreds of millions of disruption messages have been delivered over the years, ensuring that staff and customers - via a series of delivery channels - receive complete, consistent real-time updates about rail disruption. Better quality information leads to an enhanced customer experience, and ensures that staff are fully aware of all relevant issues at all times.
Powerful & Flexible
Optimised for rapid data capture and messaging, Tyrell IO can distribute information nationwide in seconds. Messaging includes free format and structured options whilst giving complete flexibility. Event and situation data can be rapidly entered with templates consisting of compulsory and optional fields, with sentences being built automatically out of the content. Tyrell IO feeds a large number of downstream systems.
Real-Time Information
The core function of Tyrell IO is to keep staff and customers (via a series of different delivery channels) informed about unplanned disruption.
That might be issues at stations (e.g. no step-free access, as the lifts are out of order), problems with specific trains (cancellations, alterations, or changes to on-board facilities), or more general problems associated with a route (e.g. a line-side fire, an issue at a level crossing, or weather-related incidents or issues). Tyrell IO provides a two-way flow of information between train operators, Network Rail and other public transport operators.
Intelligent
With access to real-time and historical data, railway timetables, and train movement data, Tyrell IO shares a rail topological rail database with other Nexus Alpha systems including ARRAKIS, giving complete route awareness when it comes to the impact of service disruption.
TYRELL IO NEAT Forms
At the heart of Tyrell IO are advanced function interactive templates - or NEAT Forms (NEAT standing for “Nexus Alpha Extended Attribute Templates”). These allow messages to be constructed quickly and efficiently, with a traffic light system of RED (compulsory field), GREEN (complete field), and AMBER (content may be added to the field), ensuring that messages are always sent with the minimum required content, but content can then be added easily on updates, and the disruption evolves.
TYRELL IO Service Data
Tyrell IO holds the National Rail timetables, and had access to movement data in order to alert user in Operational Controls about service disruption.
TYRELL IO Timetables
Train services can easily be manipulated, either individually, or in groups. The latter might be used if there were diversions, say, where helper trains can be used to quickly splice in a diversionary route. As Tyrell IO is underpinned by the Geographical Database that Nexus Alpha has developed, it is not possible to amend trains to contain calling points that are not geographically connected, eliminating potential errors.
TYRELL IO Alert Book (Himalia)
As well as operators being able to enter information quickly and efficiently, Tyrell IO also automatically monitors train service performance. So when trains don’t leave stations when they are supposed to (based on the timetable), users are alerted, so that they can investigate, and ensure that staff and customers have the most up-to-date accurate picture of any likely disruption.
All data sent via Tyrell IO is tracked and logged, allowing performance figures and KPIs to be obtained using the PIDD Real Time Reporting Suite. The Suite, together with Tyrell IO, the ARRAKIS App and Portal, CX Notifications, JourneyCheck, and other bespoke data services ensure that everybody is connected and everybody has access to the best possible information available.