1.1 General scope of the Standard
The main objective of this European Standard is to present the Public Transport Reference Data Model based on:
- the Public Transport Reference Data Model published 2006 as EN12896 and known as Transmodel V5.1,
- the model for the Identification of Fixed Objects for Public transport, published 2009 as EN 28701and known as IFOPT,
incorporating the requirements of
- EN15531-1 to 3 and TS15531-4 and 5: Service interface for real-time information relating to public transport operations (SIRI),
- TS16614-1 and 2: Network and Timetable Exchange (NeTEx),
in particular the specific needs for long distance train operation.
Particular attention is drawn to the data model structure and methodology:
- the data model is described in a modular form in order to facilitate understanding and 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 network description as in Transmodel V5.1 extended by the relevant parts of IFOPT.
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)
- Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions
- Fare Management (fare structure and access rights definition, sales, validation, control)
- 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”.
1.2 Functional domain description
1.2.1 Public transport network and stop description
The reference data model includes entity definitions for different types of points and links as the building elements of the topological network. Stop points, timing points and route points, for instance, reflect the different roles one point may have in the network definition: whether it is used for the definition of (topological or geographical) routes, as a point served by vehicles when operating on a line, or as a location against which timing information like departure, passing, or wait times are stored in order to construct the timetables.
The line network is the fundamental infrastructure for the service offer, to be provided in the form of vehicle journeys which passengers may use for their trips. The main entities describing the line network in the reference data model are the line, the route and the journey pattern, which refer to the concepts of an identified service offer to the public, the possible variants of itineraries vehicles would follow when serving the line, and the (possibly different) successions of stop points served by the vehicles when operating on the route.
The functional views of the network are described as layers. A projection is a mechanism enabling the description of the correspondence between the different layers. This mapping between the layers is particularly useful when spatial data from different environments (sources, functional domains) have to be combined. An example of such a situation is the mapping of the public transport network on the road network. (...)
Required fields are indicated with *
