scope:

The main objective of the present Standard is to present thepublic transport reference data model based on: ? the publictransport reference data model published 2006 as EN 12896 and knownas Transmodel V5.1; ? the model for the Identification of FixedObjects for Public transport, published 2009 as EN 28701and knownas IFOPT; incorporating the requirements of ? EN 15531-1 to 3 andCEN/TS 15531-4 and CEN/TS 15531-5, Service interface for real-timeinformation 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 trainoperation. Particular attention is drawn to the data modelstructure and methodology: ? the data model is described in amodular form in order to facilitate understanding and use of themodel; ? the data model is entirely described in UML. Inparticular, a reference data model kernel is described, referringto the data domain: ? network description: routes, lines, journeypatterns, timing patterns, service patterns, scheduled stop pointsand stop places. ? This part corresponds to the network descriptionas in Transmodel V5.1 extended by the relevant parts of IFOPT. ?Furthermore, the following functional domains are considered: ?timing information and vehicle scheduling (runtimes, vehiclejourneys, day type-related vehicle schedules); ? passengerinformation (planned and real-time); ? operations monitoring andcontrol: operating day-related data, vehicle follow-up, controlactions; ? fare management (fare structure and access rightsdefinition, sales, validation, control); ? management informationand statistics (including data dedicated to service performanceindicators); ? driver management: ? driver scheduling (day-typerelated driver schedules) ? rostering (ordering of driver dutiesinto sequences according to some chosen methods); ? drivingpersonnel disposition (assignment of logical drivers to physicaldrivers and recording of driver performance). The data modulesdedicated to cover most functions of the above domains will bespecified. Several concepts are shared by the different functionaldomains. This data domain is called ?common concepts?.