Data Communication on Vehicles

Standardization of the application rules concerning the WORLDFIP or CAN data bus transmission. Environmental and electrical conditions and limits inside the vehicle.

OJP standard

Open API for distributed journey planning

OJP initiative was born to answer the esigence to exchange accurate and timely information about public transport (PT) servicesand  to implement systems able to provide Multi-modal information for longer-distance journeys.

Several systems have been developed to answer to this requirement, based on different architecture, but he nature of the enquiries sent between the systems, and the content of the responses sent in return, were essentially the same. This suggested that it would be possible to define a single Open Journey Planning API to support all distributed journey planning systems.

OJP allows a system to engineer just one interface that it can make available rather than having to engineer separate APIs for each bipartite exchange arrangement that may be required with other systems.

The establishment of Open APIs has been enabled by increasingly standardised in Public Transport by following the principles set out in the “Public Transport Reference Data Model” (Transmodel) EN standard, and its related implementation Standards and specifications.

The ITS Directive Delegated Regulation for provision of EU-wide multimodal travel information services is the legal framework for travel data access and distributed journey planning in Europe. This initiative will provide the necessary requirements to make EU-wide multimodal travel information services accurate and available across borders. One of the key requirements concerns linking travel information services for distributed journey planning. Upon request, travel information service providers shall provide to another information service provider ‘routing results’ based on static, and where possible, dynamic information. The ‘routing results’ shall be based on:

  1. the enquirers start and end points of a journey along with the specific time and date of departure or arrival, or both;
  2. possible travel options along with the specific time and date of departure or arrival, or both, including any possible connections;
  3. the handover point between travel information services;
  4. in case of disturbances, alternative possible travel options along with the specific time and date of departure or arrival, or both, and any connections, where available.

The Delegated Regulation recommends that the CEN OPEN API standard for distributed journey planning is used by local, regional and national travel information service providers.

OpRa standard

Operating Raw Data and statistics exchange

OpRa is an CEN initiative with main focus on the identification of Public Transport raw data to be exchanged, gathered and stored in order to support Study and Control of Pubic Transpoprt Service.

The work consists in the production of a CEN Technical Report, to document the results of the performed analysis, in order to precisely define the scope of the following Technical Specification (TS) or European Norm (EN) definition work.

Particular attention on raw data identification is focused on actual and measured information, i.e. information which cannot be changed anymore in the future.

This information is mainly an output of the Transmodel (TRM) domains

  • Part4: “Operations monitoring  & control”;
  • Part 8: “Management Information and statistics“ focused on raw data for indicators calculation.

It will describes the recorded reality of operation, like  delays and cancelled vehicle journeys, etc. either through individual measurements at a given sampling interval or in an aggregate ways (statistics).

OpRa work scope is coherent with those covered by NeTEx, SIRI and Trasnmodel as depicted in the following picture:

In this perspective, a deep study of Public Transport Service is performed with Information exchanges with stakeholders (mainly authorities, operators and system providers) to clearly identify the needs and define Use Cases.

NeTEx standard

Network Timetable Exchange

NeTEx is a CEN Technical Standard for exchanging Public Transport Network, schedules and related data. It is divided into three parts, each covering a functional subset of the CEN Transmodel:

  • Part 1 describes the Public Transport Network topology (CEN/TS 16614-1:2014);
  • Part 2 describes Scheduled Timetables (CEN/TS 16614-2:2014);
  • Part 3 covers Fare information (CEN/TS 16614-3:2015).

NeTEx provides a means to exchange data for passenger information such as stops, routes timetables and fares, among different computer systems, together with related operational data. It can be used to collect and integrate date from many different stakeholders, and to reintegrate it as  it evolves through succesive versions.

All three parts covered by NeTEx use the same framework of reusable components, versioning mechanisms, validity conditions, global identification mechanisms, etc., defined in a NeTEx framework in Part1.  NeTEx also includes, container elements called “version frames” to group data into coherent sets for efficient exchange.

NeTEx schema can thus be used to exchange:

  • Public Transport schedules including stops, routes, departures times / frequencies, operational notes, and map coordinates.
  • Routes with complex topologies such as circular routes, cloverleaf and lollipops, and complex workings such as short working and express patterns. Connections with other services can also be described
  • The days on which the services run, including availability on public holidays and other exceptions.
  • Composite journeys such as train journeys that merge or split trains
  • Information about the Operators providing the service.
  • Additional operational information, including, positioning runs, garages, layovers, duty crews, useful for AVL and on-board ticketing systems.
  • Data about the Accessibility of services to passengers with restricted mobility.
  • Data is versioned with management metadata allowing updates across distributed systems
  • Fare structures, (flat fares, point to point fares, zonal fares)
  • Fare products (Single tickets, return tickets, day, and season passses etc)
  • Fare prices that apply at specific dates

Transmodel has been a fundamental input, more information can be found at www.netex-cen.eu.


Identification of Fixed Objects in Public Transport

The project developed a logical data model for the fixed objects relevant for public transport, in particular for stops and points of interest. Transmodel v5.1 has been a fundamental input. IFOPT has been revised and incorporated into Transmodel v6 – Part 2.

SIRI standard

Standard Interface for Real-time Information

SIRI is a CEN Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.

SIRI It is divided into five parts, each compliant with CEN Transmodel:

  • Part 1: Context and framework (CEN/TS 15531-1:2015);
  • Part 2: Communications infrastructure (CEN/TS 15531-2:2015);
  • Part 3: Functional service interfaces (CEN TS/15531-3:2015);
  • Part 4: Functional service interfaces: Facility Monitoring (CEN/TS 15531-4:2011);
  • Part 5: Functional service interfaces – Situation Exchange (CEN/TS 15531-05:2016)-

As regards the SIRI-SX and SIRI-FM,  these parts are of specific relevance for Transmodel (Part 4: Operations Monitoring and Control).

  • The SIRI Situation Exchange service (EN 15531-5) covers the exchange of information describing an incident, typically an unplanned event such as a disruption, but also planned events that affect public transport or its use, such as engineering works, or major public events that will affect the use or availability of transport. The SIRI-SX service was originally designed to be, as far as possible, consistent with the DATEX II and TPEG standards, which also include situation and public event representations.
  • The SIRI Facility Monitoring service (EN 15531-4) covers the exchange of information concerning the current status of facilities (corresponding to kind of Transmodel EQUIPMENT). It provides a short description of the facility itself, the availability status and specifically the impact of the availability status for various categories of disabled or incapacitated people.

Both Situation Exchange and Facility Monitoring services encompassed extensions to the Transmodel 5.0 conceptual model on which they are based. Transmodel 6.0 has taken these extensions as input change requests, and the reference model has been updated accordingly to support them.

SIRI allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with general informational messages related to the operation of the services. The information can be used for many different purposes, for example:

  • To provide real time-departure from stop information for display on stops, internet and mobile delivery systems;
  • To provide real-time progress information about individual vehicles;
  • To manage the movement of buses roaming between areas covered by different servers;
  • To manage the synchronisation of guaranteed connections between fetcher and feeder services;
  • To exchange planned and real-time timetable updates;
  • To distribute status messages about the operation of the services;
  • To provide performance information to operational history and other management systems.

Transmodel has been a fundamental input; more information can be found at  https://www.siri-cen.eu