BS EN 12896-3:2016

Pertains to the reference data model for public transport, based on: - the reference data model, EN 12896, known as Transmodel V5.1; - EN 28701, known as IFOPT; incorporating the requirements of: - EN 15531-1 to 3 and CEN/TS 15531-4 and CEN/TS 15531-5, Service interface for real-time information relating to public transport operations (SIRI); - CEN/TS 16614-1 and CEN/TS 16614-2, Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation.

The main objective of the present standard is to present the reference data model for public transport, based on:

• the reference data model, EN 12896, known as Transmodel V5.1;

• EN 28701, known as IFOPT;

incorporating the requirements of:

• EN 15531-1 to −3 and CEN/TS 15531-4 and CEN/TS 15531-5, Service interface for real-time information relating to public transport operations (SIRI);

• CEN/TS 16614-1 and CEN/TS 16614-2, Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation.

A particular attention is drawn to the data model structure and methodology:

• the data model is described in a modular form in order to facilitate the understanding and the use of the model;

• the data model is entirely described in UML.

In particular, a Reference Data Model kernel is described, referring to the data domain:

• network description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.

This part corresponds to the Transmodel V5.1 network description extended by the IFOPT relevant parts.

Furthermore, the following functional domains are considered:

• timing information and vehicle scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);

• passenger information (planned and real-time);

• fare management (fare structure, sales, validation, control);

• operations monitoring and control: operating day-related data, vehicle follow-up, control actions;

• management information and statistics (including data dedicated to service performance indicators);

• driver management:

  • driver scheduling (day-type related driver schedules);

  • rostering (ordering of driver duties into sequences according to some chosen methods);

  • driving personnel disposition (assignment of logical drivers to physical drivers and recording of driver performance).

The data modules dedicated to cover most functions of the above domains will be specified.

Several concepts are shared by the different functional domains. This data domain is called “common concepts??.

They are:

• public transport network and stop description;

• timing information and vehicle scheduling;

• passenger information;

• fare management;

• operations monitoring and control;

• management information;

• personnel management: driver scheduling, rostering, personnel disposition.

The aspects of multi-modal operation and multiple operators’ environment are also taken into account.

1.3 Particular scope of this document

The present European Standard entitled “Reference data model for public transport – Part 3: Timing information and vehicle scheduling?? incorporates:

• journey and journey times model: describes the time-related information at the level of vehicle journeys, i.e. planned timing for the vehicles at day-type level;

• dated journey model: describes the link of the timing information for a single operating day and the day type related timing;

• passing times model: describes all the different types of passing times for the day type related information;

• vehicle service model: describes the information related the work of vehicles as planned for days types. it constitutes the main part of the vehicle scheduling data domain;

• vehicle journey assignment model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys.

This document itself is composed of the following parts:

• main document (normative) representing the data model;

• Annex A (normative), containing the data dictionary and attributes tables, i.e. the list of all the concepts present in the main document together with the definitions;

• Annex B (informative), indicating the data model evolutions.