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 and announcements. 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. Within the rail environment for example, these groups include stations, platforms, concourses, lines of routes, and trains. Buses can combine groups based on line of route.This capability helps the customer manage even the most complex of estates.
Real time data distribution: Javelin RT (On station only)
The Javelin RT module can take a number of different real-time data feeds for trains, buses and ferries and filter them for onward distribution to the on station asset estate. These feeds could be any type of data, in any format, including, for example, Darwin, XML, Worldline EDF, TDP and Worldline Tiger in the rail market or SIRI and XML in the bus market.
On a priority CIS display the service running feed could come directly to the asset or from a third-party system.
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 and weather), Rainbow Board (LUL, SWT, GWR XML) and focused travel disruption information.
Javelin is designed to provide the operator with a great level of future proofing going forward. This is achieved by maintaining an open approach to its architecture, open interfaces and data handling.
There is no reason why third party systems could and should integrate into Javelin and vice versa. The data structures used within Javelin can all be made available.
Scalability and security
Javelin has been designed with scalability and security included from day one. Javelin is built on Amazon AWS services and runs on a server-less cloud platform, allowing the system to expanded seamless as and when more processing or CPU bandwidth is required. It uses the latest firewall technologies and security built into IoT as its model.
Today, the most appropriate open protocol communication system is the Internet of Things (IoT). 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 minimise data transmission costs. 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. The majority of the existing passenger information can be connected directly to Javelin. 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.