SIST EN 12896-6:2019
(Main)Public transport - Reference data model - Part 6: Passenger information
Public transport - Reference data model - Part 6: Passenger information
1.1 General scope of the standard
The main objective of the present document is to present the Reference Data Model for Public Transport, based on:
- the Reference Data Model, EN12896, known as Transmodel V5.1;
- EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication,
incorporating the requirements of:
- EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Service interface for real-time information relating to public transport operations (SIRI);
- CEN/TS 16614-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 the understanding and the use of the model;
- the data model is entirely described in UML.
The following functional domains are considered:
- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;
- 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;
- 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);
- Management Information and Statistics (including data dedicated to service performance indicators).
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
The different functional domains (enumerated above) taken into account in the present standard, and of which the data have been represented as the reference model, are described in "Public Transport Reference Data Model - Part 1: Common Concepts".
1.3 Particular Scope of this document
The present European Standard entitled "Reference Data Model for Public Transport - Part 6: Passenger Information" incorporates the following main data packages:
- Trip Description;
- Passenger Queries.
This document itself is composed of the following parts:
- Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel;
- Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions;
- Annex B (normative), providing a complement to EN12896-1:2016, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model;
- Annex C (informative), indicating the data model evolutions;
- Annex D (informative), indicating the high-level equivalences of the example passenger information functional requests to the capabilities of other standards;
- Annex E (informative), providing an example set of commonly found passenger information functional requests and data dictionary for the elements used in the examples.
Öffentlicher Verkehr - Referenzdatenmodell - Teil 6: Information an Reisende
Transports publics - Modèle de données de référence - Partie 6 : Information des usagers
1.1 Domaine d'application général de la norme
La présente norme a pour principal objectif de présenter le modèle de données de référence pour les transports publics, en se basant sur :
- le modèle de données de référence, EN12896, intitulé Transmodel V5.1;
- la norme EN 28701:2012, Systèmes de transport intelligents - Transports en commun - Identification des objets fixes dans les transports publics (IFOPT), bien qu'il convienne de noter que cette norme particulière a été retirée car elle est désormais incluse dans les Parties 1 et 2 de la présente norme (EN 12896 1:2016 et EN 12896 2:2016) suite à leur publication réussie,
et en intégrant les exigences des normes suivantes :
- EN 15531 1 à -3 et CEN/TS 15531 4 et −5 : Transport public - interface de service pour les informations en temps réel relatives à l'exploitation des transports publics (SIRI);
- CEN/TS 16614 1 et -2 : Transport public -échange de données réseau et d'horaires (NeTEx), et plus particulièrement les besoins spécifiques liés à l'exploitation de trains longue distance.
La structure et la méthodologie du modèle de données font l'objet d'une attention particulière :
- le modèle de données est décrit sous une forme modulaire afin de faciliter sa compréhension et son utilisation;
- le modèle de données est entièrement décrit en langage UML.
Les domaines fonctionnels suivants sont pris en considération :
- Description du réseau : itinéraires, trajets, parcours, missions horaires, missions commerciales, points d'arrêt planifiés et lieux d'arrêt;
- Informations horaires et horaires des véhicules (temps de trajet, courses de véhicules, horaires des véhicules en fonction de jours types);
- Information des usagers (temps planifié et temps réel);
- Gestion tarifaire (structure tarifaire, ventes, validation, régulation);
- Suivi et contrôle de l'exploitation (données relatives au jour d'exploitation, suivi de véhicules, actions de régulation);
- Gestion des conducteurs :
- Horaires des conducteurs (horaires des conducteurs en fonction de jours types);
- Roulement (organisation des services agent en séquences en appliquant les méthodes sélectionnées);
- Gestion du personnel roulant (affectation de conducteurs logiques aux conducteurs physiques et enregistrement des tâches exécutées par les conducteurs);
- Tableaux de bord et statistiques (notamment les données consacrées aux indicateurs de performance de service).
Les modules de données dont l'objet sera de couvrir la plupart des fonctions des domaines susmentionnés seront spécifiés.
Plusieurs concepts sont partagés par ces différents domaines fonctionnels. Le présent domaine de données est intitulé « Concepts communs ».
1.2 Description d'un domaine fonctionnel
Les différents domaines fonctionnels (répertoriés ci-dessus) pris en compte dans la présente norme, et dont les données ont été représentées comme modèle de référence, sont décrits dans EN 12896-1:2016, « Transports publics – Modèle de données de référence – Partie 1 : concepts communs ».
1.3 Domaine d'application particulier du présent document
Le présent présent, intitulé Transports publics – Modèle de données de référence – Partie 6 : information des usagers intègre les principaux ensembles de données suivants :
- Description des déplacements,
- Requêtes des usagers.
Le présent document est lui-même constitué des parties suivantes :
- le corps du document (normatif), représentant le modèle de données pour les concepts communs aux différents domaines tarifaires couverts par Transmodel,
- l'Annexe A (normative), qui contient le dictionnaire des données, c.-à-d. la liste de tous les concepts et les tableaux des attributs présents dans le document principal, ainsi que les définitions,
[...]
Javni prevoz - Referenčni podatkovni model - 6. del: Informiranje potnikov
1.1 Splošno področje uporabe standarda
Glavni cilj trenutnega dokumenta je predstavitev referenčnega podatkovnega modela za javni prevoz na podlagi:
– referenčnega podatkovnega modela (EN12896), poznanega kot Transmodel različice 5.1;
– standarda EN 28701:2012, Identifikacija stalnih objektov v javnem transportu (IFOPT), čeprav je treba upoštevati, da je bil ta standard umaknjen in je po uspešni objavi 1. in 2. dela tega standarda (EN 12896-1:2016 in EN 12896-2:2016) vključen v ta dva dela;
vsebuje zahteve:
– standardov od EN 15531-1 do -3 ter CEN/TS 15531-4 in -5: Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza (SIRI);
– dokumentov CEN/TS 16614-1 in -2: Izmenjava omrežnih in voznorednih podatkov (NeTEx), predvsem specifične potrebe za medkrajevni železniški prevoz.
Posebna pozornost je namenjena strukturi podatkovnega modela in metodologiji:
– podatkovni model je opisan v modularni obliki za lažje razumevanje in uporabo modela;
– podatkovni model je v celoti opisan v poenotenem jeziku modeliranja UML.
Obravnavane so naslednje funkcionalne domene:
– opis omrežja: poti, linije, vzorci potovanj, čas potovanj, storitveni vzorci in načrtovana postajališča;
– časovne informacije in razporejanje vozil (vozni čas, poti vozil, dnevni razporedi različnih vrst vozil);
– informiranje potnikov (načrtovano in v realnem času);
– upravljanje voznin (struktura voznin, prodaja, preverjanje, nadzor);
– spremljanje delovanja in nadzor: dnevni podatki o delovanju, spremljanje vozil, nadzorni ukrepi;
– upravljanje voznega osebja:
– razpored voznikov (dnevni razporedi voznikov),
– urniki (razporejanje dolžnosti voznikov v zaporedje glede na nekatere izbrane metode),
– razporejanje voznega osebja (dodelitev logičnih voznikov fizičnim voznikom in beleženje storilnosti voznika);
– informacije o upravljanju in statistika (vključno s podatki, namenjenimi kazalcem uspešnosti storitev).
Določeni bodo podatkovni modeli, ki bodo zajemali večino funkcij iz zgornjih domen.
Različne funkcionalne domene imajo skupnih več pojmov. Ta podatkovna domena se imenuje »Skupni pojmi«.
1.2 Opis funkcionalne domene
Različne funkcionalne domene (naštete zgoraj), ki so upoštevane v trenutnem standardu in katerih podatki so predstavljeni kot referenčni model, so opisane v »Referenčnem podatkovnem modelu javnega prevoza – 1.del: Skupni pojmi«.
1.3 Posebno področje uporabe tega dokumenta
Trenutni evropski standard »Referenčni podatkovni model za javni prevoz – 6. del: Informiranje potnikov« vključuje naslednje glavne podatkovne pakete:
– opis poti;
– poizvedbe potnikov.
Ta dokument je sestavljen iz naslednjih delov:
– glavni dokument (normativni), ki predstavlja podatkovni model za pojme, ki si jih delijo različne tarifne domene v Transmodelu;
– dodatek A (normativni), ki vsebuje podatkovni slovar, tj. seznam vseh pojmov in preglednic atributov, ki so v glavnem dokumentu, skupaj z definicijami;
– dodatek B (normativni), ki vsebuje dopolnilo k standardu EN12896-1:2016, še posebej uporaben za dele od 4 do 8 referenčnega podatkovnega modela za javni prevoz;
– dodatek C (informativni) s prikazom razvoja podatkovnega modela;
– dodatek D (informativni), ki glede na zahteve drugih standardov prikazuje visoko ustreznost primerov funkcionalnih zahtev informacij za potnike;
– dodatek E (informativni), ki podaja primer nabora najpogosteje najdenih funkcionalnih zahtev informacij za potnike in podatkovni slovar za elemente, uporabljene v primerih.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 12896-6:2019
01-november-2019
Javni prevoz - Referenčni podatkovni model - 6. del: Informiranje potnikov
Public transport - Reference data model - Part 6: Passenger information
Öffentlicher Verkehr - Referenzdatenmodell - Teil 6: Information an Reisende
Transports publics - Modèle de données de référence - Partie 6 : Information des
usagers
Ta slovenski standard je istoveten z: EN 12896-6:2019
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-6:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 12896-6:2019
---------------------- Page: 2 ----------------------
SIST EN 12896-6:2019
EN 12896-6
EUROPEAN STANDARD
NORME EUROPÉENNE
September 2019
EUROPÄISCHE NORM
ICS 35.240.60
English Version
Public transport - Reference data model - Part 6:
Passenger information
Transports publics - Modèle de données de référence - Öffentlicher Verkehr - Referenzdatenmodell - Teil 6:
Partie 6 : Information des usagers Information an Reisende
This European Standard was approved by CEN on 19 April 2019.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 12896-6:2019 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 12896-6:2019
EN 12896-6:2019 (E)
Contents Page
European foreword . 11
Introduction . 12
1 Scope . 13
1.1 General Scope of the Standard. 13
1.2 Functional Domain Description . 14
1.3 Particular Scope of this document . 14
2 Normative references . 14
3 Terms and definitions . 15
4 Symbols and abbreviations . 18
5 Passenger Information Domain . 19
5.1 Scope and overview . 19
5.2 Passenger Information . 20
5.2.1 Provision of Information . 20
5.2.2 Types of Passenger Information . 23
5.2.3 Timetable Information . 25
5.2.4 Passenger Trip Planning . 29
5.2.5 Estimation of Trip Duration . 33
5.2.6 Information on Fares . 35
5.2.7 Other Information . 36
5.3 Use Cases for the Passenger Information Model. 37
5.3.1 Purpose . 37
5.3.2 Business context . 37
5.3.3 Actors and use case types . 38
5.3.4 Use cases . 39
5.4 Public Transport Passenger Information – Conceptual MODEL . 41
5.4.1 General . 41
5.4.2 Trip Description . 41
5.4.3 Passenger Information Queries . 53
Annex A (normative) Data Dictionary . 55
A.1 Introduction . 55
A.2 Data Dictionary — Passenger Information . 55
A.2.1 ACCESS LEG . 55
A.2.2 LEG . 55
A.2.3 LEG TRACK . 55
A.2.4 MEAN INTERCHANGE TIME . 56
A.2.5 MEAN PASSENGER WAIT TIME . 56
A.2.6 MEAN RUN TIME . 56
A.2.7 MIXED TRIP . 57
A.2.8 MONITORED LEG . 57
2
---------------------- Page: 4 ----------------------
SIST EN 12896-6:2019
EN 12896-6:2019 (E)
A.2.9 MONITORED LEG ARRIVAL . 57
A.2.10 MONITORED LEG CALL . 58
A.2.11 MONITORED LEG CALL PART . 58
A.2.12 MONITORED LEG DEPARTURE . 58
A.2.13 MONITORED LEG PROGRESS . 59
A.2.14 MONITORED TRIP . 59
A.2.15 MONITORED TRIP PATTERN . 59
A.2.16 NON-PT TRIP . 60
A.2.17 OTHER LEG . 60
A.2.18 PARTICIPANT SYSTEM . 60
A.2.19 PATH GUIDANCE. 61
A.2.20 PI DELIVERY . 61
A.2.21 PI REQUEST . 61
A.2.22 PI REQUEST FILTER. 62
A.2.23 PI REQUEST POLICY . 62
A.2.24 PT CONNECTION LEG . 62
A.2.25 PT FARE OFFER . 63
A.2.26 PT RIDE LEG . 63
A.2.27 PT TRIP . 63
A.2.28 TRAVEL . 64
A.2.29 TRAVEL FLOW . 64
A.2.30 TRAVELLING ENTITY . 64
A.2.31 TRIP . 64
A.2.32 TRIP PATTERN . 65
A.2.33 TRIP PATTERN MONITORING . 65
A.2.34 TRIP REASON . 65
A.2.35 TYPE OF GUARANTEE . 66
A.2.36 TYPE OF PASSENGER . 66
A.2.37 TYPE OF TRAVELLING ENTITY . 66
A.2.38 TYPE OF REQUEST . 67
Annex B (normative) Additional Common Concepts — Extension to EN 12896-1:2016, Public
transport – Reference data model – Part 1: Common concepts . 68
B.1 Methodology and Conventions . 68
B.1.1 Methodology for conceptual modelling . 68
B.1.1.1 General . 68
B.1.1.2 Packages . 68
B.1.1.3 Package Prefixes and Package order . 69
3
---------------------- Page: 5 ----------------------
SIST EN 12896-6:2019
EN 12896-6:2019 (E)
B.1.1.4 Part Prefixes and diagram names . 70
B.1.1.5 Class diagrams . 70
B.1.1.6 Class Diagram Presentations . 71
B.1.1.7 Use of Colour . 71
B.1.2 MODEL Class Diagrams . 72
B.1.2.1 General . 72
B.1.2.2 Classes and attributes . 73
B.1.2.2.1 General . 73
B.1.2.2.2 Attribute visibility . 74
B.1.2.2.3 Attribute names . 74
B.1.2.2.4 Attribute types . 74
B.1.2.2.5 Multiplicity of Attributes . 74
B.1.2.2.6 Common attributes . 74
B.1.2.2.7 Simple Diagram Example . 74
B.1.2.3 Relationships . 76
B.1.2.3.1 General . 76
B.1.2.3.2 Association relationships . 76
B.1.2.3.3 Reflexive associations . 76
B.1.2.3.4 Aggregation relationship . 77
B.1.2.3.5 Generalization relationship . 78
B.1.2.3.6 Multiplicity (Cardinality) of Relationships . 79
B.1.2.3.7 Presence of Relationships on a given diagram. 79
B.1.2.3.8 Relationships and navigability . 80
B.1.2.3.9 Positional semantics for laying out classes and relationships . 81
B.1.2.3.10 Explicit Frames . 81
B.1.3 Summary of Rules for Transmodel Presentation . 82
B.1.3.1 Presentation of Class Structure diagrams . 82
B.1.3.2 Rules for naming and presenting classes . 82
B.1.3.3 Rules for use of role names . 83
B.1.3.4 Rules for use of multiplicity . 84
B.1.3.5 Rules for relationship qualifiers . 84
B.1.3.6 Rules for presenting relationships . 85
B.1.3.7 Rules for Placing Role names . 86
B.2 Extensions to the Common Concept MODEL . 86
B.2.1 General . 86
B.2.2 Additional Common Concepts — Additional Generalizations . 86
4
---------------------- Page: 6 ----------------------
SIST EN 12896-6:2019
EN 12896-6:2019 (E)
B.2.2.1 Generic Type of Value – Conceptual MODEL . 86
B.2.2.2 Generic Assignment – Conceptual MODEL . 88
B.2.2.3 Generic Section – Conceptual MODEL . 88
B.2.3 Extensions to the Generic Framework . 89
B.2.3.1 General . 89
B.2.3.2 Alternative Text – Conceptual MODEL . 89
B.2.3.3 Generic View – Conceptual MODEL . 90
B.2.3.4 Generic Loggable Object – Conceptual MODEL. 91
B.2.3.5 Event Model – Conceptual MODEL . 91
B.2.4 Extensions to the Reusable Components . 92
B.2.4.1 Employee Model – Conceptual MODEL . 92
B.2.4.2 Message Model – Conceptual MODEL. 93
B.2.4.2.1 Messages . 93
B.2.4.2.2 Publication Scope . 94
B.2.4.3 Role Model – Conceptual MODEL . 95
B.2.4.3.1 Generic Roles . 95
B.2.4.3.2 Service Organization Roles . 96
B.2.4.3.3 Employee Roles . 97
B.2.4.3.4 Administrative Organization Roles . 97
B.2.4.3.5 Technology Organization Roles . 98
B.2.4.3.6 Messaging Roles . 99
B.2.4.3.7 Transport Customer Roles . 100
B.2.4.4 Security List – Conceptual MODEL . 100
B.2.4.5 Transfer Time – Conceptual MODEL . 101
B.2.5 Data Dictionary . 101
B.2.5.1 General . 101
B.2.5.2 ADMINISTRATIVE ORGANIZATION ROLE . 102
B.2.5.3 ALTERNATIVE TEXT. 102
B.2.5.4 ASSIGNMENT. 102
B.2.5.5 BLACKLIST . 102
B.2.5.6 CLASS ATTRIBUTE . 103
B.2.5.7 CONDUCTOR ROLE . 103
B.2.5.8 CUSTOMER SERVICE PROVIDER ROLE . 103
B.2.5.9 CUSTOMER SERVICE ROLE . 104
B.2.5.10 DATA COLLECTOR ROLE . 104
B.2.5.11 DRIVER ROLE . 104
5
---------------------- Page: 7 ----------------------
SIST EN 12896-6:2019
EN 12896-6:2019 (E)
B.2.5.12 EMPLOYEE . 104
B.2.5.13 EMPLOYEE ROLE . 105
B.2.5.14 EVENT . 105
B.2.5.15 GENERAL EVENT . 105
B.2.5.16 GENERAL OBSERVER ROLE . 106
B.2.5.17 GENERAL SECTION . 106
B.2.5.18 LOG . 106
B.2.5.19 LOG ENTRY . 106
B.2.5.20 LOGGABLE OBJECT . 107
B.2.5.21 MESSAGE . 107
B.2.5.22 MESSAGE PART . 107
B.2.5.23 MESSAGE PRIORITY . 107
B.2.5.24 ORGANIZATION ROLE . 108
B.2.5.25 PT SCOPE . 108
B.2.5.26 PUBLICATION APPROVER ROLE . 108
B.2.5.27 PUBLICATION DECISION . 109
B.2.5.28 PUBLICATION SCOPE . 109
B.2.5.29 PUBLICATION WINDOW . 109
B.2.5.30 PUBLISHING ACTION . 109
B.2.5.31 PUBLISHING CHANNEL . 110
B.2.5.32 QUALIFICATION . 110
B.2.5.33 REGISTRAR ROLE . 110
B.2.5.34 SECTION .
...
SLOVENSKI STANDARD
oSIST prEN 12896-6:2019
01-januar-2019
-DYQLSUHYR]5HIHUHQþQLSRGDWNRYQLPRGHOGHO ,QIRUPLUDQMHSRWQLNRY
Public transport - Reference data model - Part 6: Passenger information
Ta slovenski standard je istoveten z: prEN 12896-6
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 12896-6:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 12896-6:2019
---------------------- Page: 2 ----------------------
oSIST prEN 12896-6:2019
DRAFT
EUROPEAN STANDARD
prEN 12896-6
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2018
ICS 35.240.60
English Version
Public transport - Reference data model - Part 6:
Passenger information
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 278.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 12896-6:2018 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
1.1 General scope of the standard . 6
1.2 Functional Domain Description . 7
1.3 Particular Scope of this document . 7
2 Normative references . 7
3 Terms and definitions . 8
3.1 General terms and definitions . 8
3.2 Domain specific terms and definitions . 10
4 Symbols and abbreviations . 11
5 Passenger Information Domain . 12
5.1 Scope and overview . 12
5.2 Passenger Information . 13
5.2.1 Provision of Information . 13
5.2.2 Types of Passenger Information . 16
5.2.3 Timetable Information . 18
5.2.4 Passenger Trip Planning . 22
5.2.5 Estimation of Trip Duration . 26
5.2.6 Information on Fares . 28
5.2.7 Other Information . 29
5.3 Use Cases for the Passenger Information Model. 30
5.3.1 Purpose . 30
5.3.2 Business context . 30
5.3.3 Actors and use case types . 31
5.3.4 Use cases . 32
5.4 Public Transport Passenger Information – Conceptual MODEL . 34
5.4.1 General . 34
5.4.2 Trip Description . 34
5.4.3 Passenger Information Queries . 46
A.1 Introduction . 48
A.2 Data Dictionary . 48
B.1 Methodology and Conventions . 61
B.2 Extensions to the Common Concept MODEL . 79
C.1 Change Requests . 111
C.2 Source of Text . 121
C.3 Diagram Status . 122
D.1 Table of equivalent SIRI Services . 123
D.2 Table of equivalent OADJP Services . 123
2
---------------------- Page: 4 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
E.1 Introduction. 125
E.2 Overview of Passenger Information Functional Requests. 125
E.3 System Provisioning Queries. 127
E.4 Travel Related Queries . 129
E.5 Fare Related Queries . 141
E.6 Data Dictionary . 150
Bibliography . 167
3
---------------------- Page: 5 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
European foreword
This document (prEN 12896-7:2018) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
The series composed of the following documents:
— Public transport - reference data model - Part 1: Common Concepts;
— Public transport - reference data model - Part 2: Public Transport Network;
— Public transport - reference data model - Part 3: Timing Information and Vehicle Scheduling;
— Public transport - reference data model - Part 4: Operations Monitoring and Control;
— Public transport - reference data model - Part 5: Fare Management;
— Public transport - reference data model - Part 6: Passenger Information;
— Public transport - reference data model - Part 7: Driver Management; and
— Public transport - reference data model - Part 8: Management Information and Statistics.
Together these create version 6 of the European Standard EN 12896, known as “Transmodel”, and thus
replace EN 12896:2006, known as “Transmodel v5.1”.
In comparison with the previous edition, the technical modifications made are presented in the Technical
Report TR 12896-9 “Public transport - reference data model - Part 9: Informative Documentation”.
4
---------------------- Page: 6 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
Introduction
Part 1 of this standard presents the following items:
— Rationale for the Transmodel Standard;
— Use of the Transmodel Standard;
— Applicability of the Transmodel Standard;
— Conformance Statement;
— Transmodel Origins;
— Reference to the Previous Version and Other Documents.
The data structures represented in Part 1 are generic patterns that are referenced by different other
parts.
Part 2 of this standard presents space-related data structures.
Part 3 presents time-related data structures and replaces the sections of EN 12896:2006 referring to the
time-related Tactical Planning Components and to Vehicle Scheduling.
Part 4 presents data referring to daily operations (i.e. to operational days), different from those planned
for day types (space-related data structures and tactical planning components) and including operational
raw data referring to operations follow-up.
Part 5 presents fares structures including sales, validation and control.
Part 6 (this part) presents Passenger Information (planned and real-time).
Part 7 presents Driver Management including Driver Scheduling (day-type related driver schedules),
Rostering (ordering of driver duties into sequences according to some chosen methods) and Driving
Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver
performance).
Part 8 presents Management Information and Statistics.
5
---------------------- Page: 7 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
1 Scope
1.1 General scope of the standard
The main objective of the present document is to present the Reference Data Model for Public Transport,
based on:
— the Reference Data Model, EN12896, known as Transmodel V5.1;
— EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this
particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard
(EN 12896-1:2016 and EN 12896-2:2016) following their successful publication,
incorporating the requirements of:
— EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Service interface for real-time information relating
to public transport operations (SIRI);
— CEN/TS 16614-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 the understanding and the use of
the model;
— the data model is entirely described in UML.
The following functional domains are considered:
— Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled
stop points and stop places;
— 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;
— 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);
— Management Information and Statistics (including data dedicated to service performance
indicators).
The data modules dedicated to cover most functions of the above domains will be specified.
6
---------------------- Page: 8 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
Several concepts are shared by the different functional domains. This data domain is called “Common
Concepts”.
1.2 Functional Domain Description
The different functional domains (enumerated above) taken into account in the present standard, and of
which the data have been represented as the reference model, are described in “Public Transport
Reference Data Model – Part 1: Common Concepts”.
1.3 Particular Scope of this document
The present European Standard entitled “Reference Data Model for Public Transport – Part 6: Passenger
Information” incorporates the following main data packages:
— Trip Description;
— Passenger Queries.
This document itself is composed of the following parts:
— Main document (normative) representing the data model for the concepts shared by the different
fare domains covered by Transmodel;
— Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute
tables present in the main document together with the definitions;
— Annex B (normative), providing a complement to EN12896-1:2016, particularly useful for parts 4 to
8 of the Public Transport Reference Data Model;
— Annex C (informative), indicating the data model evolutions;
— Annex D (informative), indicating the high-level equivalences of the example passenger information
functional requests to the capabilities of other standards;
— Annex E (informative), providing an example set of commonly found passenger information
functional requests and data dictionary for the elements used in the examples.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 12896:2006, Public Transport Reference Data Model (“Transmodel v5.1”)
EN 12896-1:2016, Public transport — Reference data model — Part 1: Common concepts
EN 12896-2:2016, Public transport — Reference data model — Part 2: Public transport network
EN 12896-3:2016, Public transport — Reference data model — Part 3: Timing information and vehicle
scheduling
1
EN 12896-4, Public Transport Reference Data Model — Part 4: Operations Monitoring and Control
(“Transmodel v6”)
1
Under preparation
7
---------------------- Page: 9 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
2
Public Transport Reference Data Model — Part 5: Fare Management (“Transmodel v6”)
EN 12896-5,
3
EN 12896-7, Public Transport Reference Data Model — Part 7: Driver Management (“Transmodel v6”)
4
EN 12896-8, Public Transport Reference Data Model — Part 8: Management Information and Statistics
(“Transmodel v6”)
EN 15531-1:2015, Public transport — Service interface for real-time information relating to public
transport operations — Part 1: Context and framework
EN 15531-2:2015, Public transport — Service interface for real-time information relating to public
transport operations — Part 2: Communications
EN 15531-3:2015, Public transport — Service interface for real-time information relating to public
transport operations — Part 3: Functional service interfaces
CEN/TS 15531-4:2011, Public transport — Service interface for real-time information relating to public
transport operations — Part 4: Functional service interfaces: Facility Monitoring
CEN/TS 15531-5:2016, Public transport - Service interface for real-time information relating to public
transport operations — Part 5: Functional service interfaces situation exchange: Situation Exchange
CEN/TS 16614-1, Public transport — Network and Timetable Exchange (NeTEx) — Part 1: Public transport
network topology exchange format
CEN/TS 16614-2, Public transport — Network and Timetable Exchange (NeTEx) — Part 2: Public transport
scheduled timetables exchange format
CEN/TS 16614-3, Public transport — Network and Timetable Exchange (NeTEx) — Part 3: Public transport
fares exchange format
CEN/TS 17118:2017, Intelligent transport systems — Public transport — Open API for distributed journey
planning
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
3.1 General terms and definitions
The following generic terms and definitions are used.
3.1.1
attribute
property of an entity
2
Under preparation
3
Under preparation
4
Under preparation
8
---------------------- Page: 10 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
3.1.2
conceptual data model
description of a real-world domain in terms of entities, relationships and attributes in an implementation
independent manner in order to provide a structure on which the rest of the development of an
application system can be based
3.1.3
conceptual level
in the context of data modelling, the conceptual data model
3.1.4
database
collection of data; often used in the sense of the physical implementation of a data model
3.1.5
data domain
data structure (in this European Standard, a part of the Reference Data Model for Public Transport) made
up of data related to each other, through the fact that there is a functional area or group of functions using
this data set as a whole.
3.1.6
data model
description of a real-world domain in terms of data and relationships
3.1.7
entity
object (data) that has its own existence (as opposed to an attribute)
3.1.8
fare management
all activities related to the collection of money from passengers
3.1.9
function
activity
Note 1 to entry: In this European Standard, a sub-activity of a functional area.
3.1.10
functional area
arbitrarily defined set of activities, used, in this European Standard, to define the objectives and limits of
the data model
3.1.11
interoperability
ability of (sub)systems to interact with other (sub)systems according to a set of predefined rules
(interface)
3.1.12
logical data model
data design that takes into account the type of database to be used but which does not consider means of
utilization of space or access.
3.1.13
logical denormalised model
relational data model that is not fully normalized, i.e. does not completely follow the normalization rules
and thus may be redundant
9
---------------------- Page: 11 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
3.1.14
logical level
in the context of data modelling, the logical data model
3.1.15
management information
all activities allowing the company management to collect the information necessary to meet problem-
solving needs
3.1.16
object-oriented data model
data structure expressed according to principles that allow for a direct implementation as an object-
oriented database, where information is represented in form of objects, i.e. respecting the principle of
encapsulation meaning in particular that each data are accessed or modified through operations
(methods) belonging to it
3.1.17
operations monitoring and control
all activities related to the transportation process, i.e. real-time functions related to the driving and
transportation of passengers according to given instructions, including the monitoring of the driving
process and its control in case of deviations, as well as all activities that support the driving process such
as traffic light priority, track switching, bay selection, advance/delay advice, etc.
3.1.18
passenger information
all activities related to informing the users either on the planned or on the actual transportation services
3.1.19
personnel disposition
all activities related to the mid-term and short-term management of drivers
3.1.20
real-time control
see operations monitoring and control
3.1.21
relational data model
type of logical data model giving the information as series of tables (relations) and attributes, and
possessing the following characteristics: a) all attribute values are atomic; b) all “tuples”
(rows/occurrences) are distinct; c) no part of the primary key may be null; and d) foreign key values must
correspond to an existing primary key in another relation or be null
3.1.22
scheduling
see tactical planning.
3.1.23
tactical planning
all activities related to the tactical planning of transportation, splitting into vehicle scheduling, driver
scheduling, rostering.
3.2 Domain specific terms and definitions
The following terms specific to the passenger information domain are used. Terms which are also data
entity names are defined in the data dictionary in Annex A and are not repeated here.
10
---------------------- Page: 12 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
3.2.1
distributed journey planner
trip planner that computes its results by delegating planning to other systems for those parts of the trip
covering specific areas or modes
3.2.2
exchange point
agreed handover point for linking distributed journey planning systems
3.2.3
observer
someone who looks at Passenger Information
3.2.4
repeated trip
same trip made over the same route multiple times, for example to commute to work or school
3.2.5
single trip
trip that goes direct from an origin to a destination without breaks in the journey
3.2.6
text to speech
automatic generation of speech from a textual representation
3.2.7
trip repair
activity of looking for travel advice regarding a specific trip in order to recover a from a disruption to
services
4 Symbols and abbreviations
For the purposes of this document, the following symbols and abbreviations apply.
ABT Account Based Ticketing
API Application Program Interface
DJP Distributed Journey Planner
FQ Fare Query
GIS Geographic Information System
GTFS General (sometimes “Google”) Transit Feed Specification
IFM Interoperable Fare Management
FM Fare Management
IFOPT Identification of Fixed Objects in Public Transport
ISO International Standards Organization
IT Information Technology
NeTEx Network and Timetable Exchange
NFC Near Field Communication
OADJP Open API for Distributed Journey Planner
PI Passenger Information
PT Public Transport
11
---------------------- Page: 13 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
QR Query Request
TD Trip Description
TTS Text to Speech
SIRI Service Interface for Real-time Information
UML Unified Modelling Language
URL Universal Resource Locator
VDV Verband Deutscher Verkehrsunternehmen (D)
WGS World Geodetic Standard
5 Passenger Information Domain
5.1 Scope and overview
The passenger information part of Transmodel describes the data which are presented to passengers by
applications that can interact directly with passengers. This covers both data on the planned and actual
services, but also data resulting from the planning and control processes which may result in service
modifications.
Classically, passenger information was published as printed timetables or shown on electro mechanical
boards in stations. Earlier generations of electronic display were typically available only in stations using
localized systems.
Modern passenger information systems are generally provided through service interfaces that access
online data and may be used from web and mobile internet devices anywhere.
Applications providing data to customers typically use an optimized API to fetch the data from a back-
end system. The standard does not aim to define an actual API for such services, but rather to provide a
mapping that shows how the data elements of the reference model relate to the different possible types
of passenger Information service.
Two other CEN standards provide concrete API’s;
— SIRI (Server Interface for Real Time Information - EN 15531-1:2015, EN 15531-2:2015,
EN 15531-3:2015, CEN/TS 15531-4:2011 and CEN/TS 15531-5:2016), which provides real-time
status information; and
— OADJP (Open API for Distributed Journey Planning - CEN/TS 17118:2017) describes stop finding, trip
planning, schedule, and related APIs.
All of the following are relevant for delivering passenger information;
— Passenger information facilities and their utilization for passenger queries;
— Detailed descriptions of all the conceptual components of a passenger trip, as possibly needed by an
interactive passenger information system when answering a PI REQUEST;
— Basic definitions of run times and wait times needed to calculate trip duration;
— Planned, predicted, and actual passing times of journeys at individual stops;
— Service modifications decided by the schedulers or the control staff, resulting in changes of the
vehicle journeys and blocks, compared to the original plan;
12
---------------------- Page: 14 ----------------------
oSIST prEN 12896-6:2019
prEN 12896-6:2018 (E)
— Fare structures, fareProducts and prices along with distribution and fulfilment options.
Most types of passenger information make use of many underlying elements from the topological
network definition, such as the lines and journeys which form the service offer, the definition of run and
wait times, and other fundamental definitions. Geographical information may possibly be provided in
some cases if corresponding application systems are available, for example to show the route of a bus.
Specific types of passenger queries may be related to fares, where the relevant information elements are
included in the fare collection sub-model of the reference data model.
Thus, the information basis for passenger information systems is widely spread over the whole reference
data model, and the genuine passenger information data model covers only those elements which cannot
be derived from, and are not explicitly included in, other parts of the model. It is also useful to indicate
how such data may be assembled into specific services corresponding to commonly-made passenger
queries.
5.2 Passenger Information
5.2.1 Provision of Information
5.2.1.1 General
In early generations of information systems used for public transport, the passenger information
functions were often designed as sub-functions of other systems. For instance, printed timetables were
simply an end product of th
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.