Dynamic timetable information system

 

The transport company in the German state of Thüringen provided inadequate timetable information that was still based entirely on the distribution of classic timetable boards. Proper information on connections was unavailable and updating the data was extremely complicated due to the manual interaction with the various planning systems.

Using the Batix application platform, an information system that fully meets all the requirements for a modern system was implemented on the basis of OpenTripPlaner and OpenStreetMap.
In addition, the mesh-up and optimisation of these available, licence-free information logics and map-based materials were used to create financial leeway for the customer-friendly design of the dialogue systems in apps and on websites.

The Batix platform also enables a high-performance frontend engine, which asynchronously performs all user functionalities. The result is that calculation-heavy information logics are carried out by high-performance web servers and supplied to the corresponding frontend systems for presentation.

External partners are supplied with tangible added value. Administrations, cultural institutions and other public and private institutions can receive and depict filtered timetable information including the latest changes. The content of the output can be configured, as can the design, within certain limits. The data can be transmitted in the form of a standard interface (XML, CSV, ...), configurable widgets or HTML pages, or as a customised interface.

Functionality

  • Merger of data from transport planning (Hastus), workshop management, personnel planning (IVU), real-time data / RBL (IVU)
  • Use and further development of information logics (OpenTripPlaner)
  • Linking of timetable information data with everyday situations (appointments with the authorities, shopping, hiking, commuting, etc. and combinations with alternative forms of transport (rail, car, bicycle, walking)
  • Integration of information systems for distances within certain time windows (extremely relevant for e.g. property selection and job search)
  • Supply of data and operation of the information system via a web frontend or separate apps (iOS, Android, Web App)
  • Merger of data from different providers possible
  • Integration of price information and ticketing solution
  • External interfaces for information systems

FACTS & FIGURES

  • 8.5 million passengers
  • 62 lines
  • 250 vehicles

TECHNICAL BASIS

  • Batix framework
  • Java
  • Apache
  • TomCat
  • Debian Linux
  • API connection to various back office solutions

Images