Manage – Deliver – Inform
What is Javelin?
Javelin is a web-based back office system that gives operators the ability to manage their passenger information and advertising assets. These and their content are managed through a unified graphical user interface (GUI). The assets can be on-station, on-vehicle or even on-line. Assets can be traditional displays (LED or TFT), audio PA equipment, web feeds or user apps.
Javelin is consists of four primary modules of which the operator can chose to deploy one, some or all depending on the function required. These are:
Function #1 Asset Management - Javelin Maintain
The user friendly Javelin Maintain module provides operators with views of their passenger information estate that shows which assets are working and what they are doing. This module provides operators and maintainers with the tools to diagnose issues quickly and accurately; reducing equipment downtime and allowing more proactive maintenance to be carried out.
As well as maintaining the assets, Javelin gives operators the ability to add to and reconfigure their passenger information assets thereby removing the need for costly system configuration.
Function #2 Manual Content - Javelin Direct
Incorporated within the user GUI, the Javelin Direct module allows operators to manage and create content for deployment to their assets. The system can create, schedule and distribute playlists from a wide variety of sources including textual notices, images, videos, announcements etc. Javelin recognises its connected assets and provides assistance to the operators to ensure content is correctly allocated. The operator GUI allows groups of assets to be created. Commonly within the rail environment, for example, these groups are stations, platforms, concourses, lines of routes, train sets, etc. This capability helps the customer manage even the most complex of estates.
Function #3 Real Time Data Distribution - Javelin RT
The Javelin RT module can take a number of real time data feeds for train, bus, ferry, etc. and filter them for onward distribution to the asset estate. These feeds could be any type of data, in any format, including, for example, Darwin, XML, EDF, TDP & Tiger in the rail market or SIRI & XML in the bus market.
Function #4 Automatic Content Distribution - Javelin Auto
Additional data feeds can be filtered and distributed using the Javelin Auto module; providing the public with a host of informative and interesting secondary content on the displays. For example, Javelin Direct can manage and distribute RSS feeds (for news & weather), Rainbow Board (LUL, SWT, GWR XML) and focused travel disruption information (Tyrell, etc.).
Javelin is designed to provide the operator with a good level of future proofing going forward. This is achieved by maintaining an open approach to its architecture, interface and data handling.
Today, the most appropriate open protocol communication system is IoT, (Internet of Things). Javelin employs the IoT system as its core architecture. Legacy or non-IoT devices are catered for although non IoT devices are catered for with a proxy to convert them to IoT standards. The IoT publish/subscribe approach is ideal for this type of application and enables systems to evolve and grow over time.
In general, Javelin uses low bandwidth 'data only' interfaces in order to avoid the need for expensive. Indeed, almost all functionality is available over legacy RS485 links and/or GSM/4G/3G/GPRS (mobile) connections. Once again, this allows Javelin and the asset estate it manages to evolve over time under the control of the operator rather than the other way round.
Javelin has been built from the ground up with legacy systems in mind so that the majority of existing passenger information assets can be connected directly to Javelin from day one. The functionality available for the legacy equipment will be muted dependent on the type of asset connected, but Javelin will understand its capabilities and will offer what it can.
Javelin provides a system that melds both the ever-changing technologies and passenger needs with the extensive legacy estates already deployed by using a future friendly open approach to its architecture, its interface and its data.