The main objective of the present standard is to present the reference data model for public transport, based on:<\/p>\n
the reference data model, EN 12896, known as Transmodel V5.1;<\/p>\n<\/li>\n
EN 28701, known as IFOPT;<\/p>\n<\/li>\n<\/ul>\n
incorporating the requirements of:<\/p>\n
EN 15531-1 to \u22123 and CEN\/TS 15531-4 and CEN\/TS 15531-5, Service interface for real-time information relating to public transport operations (SIRI);<\/p>\n<\/li>\n
CEN\/TS 16614-1 and CEN\/TS 16614-2, Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation.<\/p>\n<\/li>\n<\/ul>\n
A particular attention is drawn to the data model structure and methodology:<\/p>\n
the data model is described in a modular form in order to facilitate the understanding and the use of the model;<\/p>\n<\/li>\n
the data model is entirely described in UML.<\/p>\n<\/li>\n<\/ul>\n
In particular, a Reference Data Model kernel is described, referring to the data domain:<\/p>\n
network description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.<\/p>\n<\/li>\n<\/ul>\n
This part corresponds to the Transmodel V5.1 network description extended by the IFOPT relevant parts.<\/p>\n
Furthermore, the following functional domains are considered:<\/p>\n
timing information and vehicle scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);<\/p>\n<\/li>\n
passenger information (planned and real-time);<\/p>\n<\/li>\n
fare management (fare structure, sales, validation, control);<\/p>\n<\/li>\n
operations monitoring and control: operating day-related data, vehicle follow-up, control actions;<\/p>\n<\/li>\n
management information and statistics (including data dedicated to service performance indicators);<\/p>\n<\/li>\n
driver management:<\/p>\n
driver scheduling (day-type related driver schedules);<\/p>\n<\/li>\n
rostering (ordering of driver duties into sequences according to some chosen methods);<\/p>\n<\/li>\n
driving personnel disposition (assignment of logical drivers to physical drivers and recording of driver performance).<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
The data modules dedicated to cover most functions of the above domains will be specified.<\/p>\n
Several concepts are shared by the different functional domains. This data domain is called \u201ccommon concepts\u201d.<\/p>\n
They are:<\/p>\n
public transport network and stop description;<\/p>\n<\/li>\n
timing information and vehicle scheduling;<\/p>\n<\/li>\n
passenger information;<\/p>\n<\/li>\n
fare management;<\/p>\n<\/li>\n
operations monitoring and control;<\/p>\n<\/li>\n
management information;<\/p>\n<\/li>\n
personnel management: driver scheduling, rostering, personnel disposition.<\/p>\n<\/li>\n<\/ul>\n
The aspects of multi-modal operation and multiple operators\u2019 environment are also taken into account.<\/p>\n
1.3 Particular scope of this document<\/b><\/p>\n
The present European Standard entitled \u201cReference data model for public transport \u2013 Part 3: Timing information and vehicle scheduling\u201d incorporates:<\/p>\n
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;<\/p>\n<\/li>\n
dated journey model: describes the link of the timing information for a single operating day and the day type related timing;<\/p>\n<\/li>\n
passing times model: describes all the different types of passing times for the day type related information;<\/p>\n<\/li>\n
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;<\/p>\n<\/li>\n
vehicle journey assignment model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys.<\/p>\n<\/li>\n<\/ul>\n
This document itself is composed of the following parts:<\/p>\n
main document (normative) representing the data model;<\/p>\n<\/li>\n
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;<\/p>\n<\/li>\n
Annex B (informative), indicating the data model evolutions.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | Contents Page <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 2 Normative references 3 Terms and definitions 4 Symbols and abbreviations 5 Timing information and vehicle scheduling data domain <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | Annex\u00a0A (normative) Data Dictionary <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | Annex\u00a0B (informative)Status of the Textual Descriptions and Model Evolution <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Public transport. Reference data model – Timing information and vehicle scheduling<\/b><\/p>\n |