SIST EN 12896-8:2019
(Main)Public transport - Reference data model - Part 8 : Management information & statistics
Public transport - Reference data model - Part 8 : Management information & statistics
The data model dedicated to cover a wide range of use cases of the domain Management Information & Statistics (in particuar a subset of use cases described by the project OpRa – Operational Raw Data) will be specified, in particular: data used for statistics and registered data from which service quality indicators may be derived.
The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model.
The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3:
Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains
Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.
Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.
Öffentlicher Verkehr - Referenzdatenmodell - Teil 8: Managementinformationen und Statistiken
Transports publics - Modèle de données de référence - Partie 8 : tableaux de bord et statistiques
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, EN 12896, 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;
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 : Echange de données de 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, contrôle);
- 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 le présent document, et dont les données ont été représentées comme modèle de référence, sont décrits dans l'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 document, intitulée Transports publics – Modèle de données de référence – Partie 8 : tableaux de bord et statistiques, explique comment structurer les données relatives aux étapes de planification (par ex. horaires, temps de trajet, tableaux de roulement des conducteurs, etc.) et/ou à la production réelle quotidienne, et qui sont enregistrées à des fins différentes, notamment pour l'élaboration d'indicateurs de performance de service. Le modèle de données est basé sur un schéma de conception générique, à savoir le modèle Objets enregistrables génériques (fourni dans la partie Concepts communs supplémentaires – Annexe B), et intègre les ensembles de données suivants :
[...]
Javni prevoz - Referenčni podatkovni model - 8. del: Informacije o upravljanju in statistika
Opredeljen bo podatkovni model, ki bo zajemal veliko različnih primerov uporabe informacij o upravljanju in statistike domen (predvsem podskupine primerov uporabe, ki je opisana v projektu OpRa (Operational Raw Data – neobdelani podatki o delovanju)), predvsem: podatki za statistiko in registrirani podatki, iz katerih je mogoče izpeljati kazalnike kakovosti storitev.
Upoštevajo se naslednji načini prevoza: avtobus, podzemna železnica, tramvaj, trolejbus, trajekt, avtobus, medkrajevni železniški prevoz. Posebna pozornost je namenjena strukturi in metodologiji podatkovnega modela: za lažje razumevanje in uporabo modela je podatkovni model opisan v poenotenem jeziku modeliranja UML v modularni obliki.
Model upošteva vrsto zahtev za razširitev, ki so jih formulirali uporabniki, vendar tudi zahtev za zagotovitev skladnosti celotnega modela (1. do 8. del), domen, modeliranih v 1. do 3. delu:
Javni prevoz – Referenčni podatkovni model – 1. del: Splošni pojmi, ki opisuje pojme, skupne različnim funkcionalnim domenam.
Javni prevoz – Referenčni podatkovni model – 2. del: Omrežje javnega prevoza, ki opisuje poti, linije, vzorce potovanj, čas potovanj, storitvene vzorce in načrtovana postajališča.
Javni prevoz – Referenčni podatkovni model – 3. del: Časovne informacije in razporejanje vozil, ki opisuje vozne čase, poti vozil, dnevne razporede različnih vrst vozil.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 12896-8:2019
01-november-2019
Javni prevoz - Referenčni podatkovni model - 8. del: Informacije o upravljanju in
statistika
Public transport - Reference data model - Part 8 : Management information & statistics
Öffentlicher Verkehr - Referenzdatenmodell - Teil 8: Managementinformationen und
Statistiken
Transports publics - Modèle de données de référence - Partie 8 : tableaux de bord et
statistiques
Ta slovenski standard je istoveten z: EN 12896-8:2019
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-8: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-8:2019
---------------------- Page: 2 ----------------------
SIST EN 12896-8:2019
EN 12896-8
EUROPEAN STANDARD
NORME EUROPÉENNE
September 2019
EUROPÄISCHE NORM
ICS 35.240.60
English Version
Public transport - Reference data model - Part 8 :
Management information & statistics
Transports publics - Modèle de données de référence - Öffentlicher Verkehr - Referenzdatenmodell - Teil 8:
Partie 8 : tableaux de bord et statistiques Managementinformationen und Statistiken
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-8:2019 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
Contents Page
European foreword . 7
Introduction . 8
1 Scope . 9
1.1 General Scope of the Standard. 9
1.2 Functional Domain Description . 10
1.3 Particular Scope of this Document . 10
2 Normative references . 10
3 Terms and definitions . 11
3.1 General Terms and Definitions: . 11
3.2 Domain Specific Terms and Definitions: . 13
4 Symbols and Abbreviations . 14
5 Management Information and Statistics Domain . 14
5.1 Introduction . 14
5.1.1 Information Needs . 14
5.1.2 Calculation of indicators . 15
5.1.3 Functions Covered . 17
5.1.4 Limitations of the Model . 18
5.2 Management Information and Statistics Data Model . 19
5.2.1 Loggable Objects Model . 19
5.2.2 Logging Time and Place . 19
5.2.3 Recorded Objects . 20
5.2.4 Recorded Use of Services . 24
5.2.5 Examples of use of the LOGGABLE OBJECT pattern . 25
Annex A (normative) Data Dictionary . 31
A.1 Introduction . 31
A.2 Data Dictionary — Management Information and Statistics . 31
A.2.1 BOARDING AND ALIGHTING . 31
A.2.2 BOARDING BASED PASSENGER COUNT . 31
A.2.3 DATED JOURNEY INFORMATION RECORDING . 31
A.2.4 INTERCHANGE STATUS . 32
A.2.5 LOCATED EVENT . 32
A.2.6 ONBOARD DEVICE BASED PASSENGER COUNT . 32
A.2.7 RECORDED LEG . 33
A.2.8 RECORDED STOP . 33
A.2.9 RECORDED TRIP . 33
A.2.10 TICKETING BASED PASSENGER COUNT . 33
Annex B (normative) Additional Common Concepts — Extension to EN 12896-1:2016, Public
transport – Reference data model – Part 1: Common Concepts . 34
2
---------------------- Page: 4 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
B.1 Methodology and Conventions . 34
B.1.1 Methodology for conceptual modelling . 34
B.1.1.1 General . 34
B.1.1.2 Packages . 34
B.1.1.3 Package Prefixes and Package order . 35
B.1.1.4 Part Prefixes and diagram names . 36
B.1.1.5 Class diagrams . 36
B.1.1.6 Class Diagram Presentations . 37
B.1.1.7 Use of Colour . 37
B.1.2 MODEL Class Diagrams . 38
B.1.2.1 General . 38
B.1.2.2 Classes and attributes . 39
B.1.2.2.1 General . 39
B.1.2.2.2 Attribute visibility . 39
B.1.2.2.3 Attribute names . 40
B.1.2.2.4 Attribute types . 40
B.1.2.2.5 Multiplicity of Attributes . 40
B.1.2.2.6 Common attributes . 40
B.1.2.2.7 Simple Diagram Example . 40
B.1.2.3 Relationships . 42
B.1.2.3.1 General . 42
B.1.2.3.2 Association relationships . 42
B.1.2.3.3 Reflexive associations . 42
B.1.2.3.4 Aggregation relationship . 43
B.1.2.3.5 Generalization relationship . 44
B.1.2.3.6 Multiplicity (Cardinality) of Relationships . 45
B.1.2.3.7 Presence of Relationships on a given diagram . 45
B.1.2.3.8 Relationships and navigability . 46
B.1.2.3.9 Positional semantics for laying out classes and relationships . 47
B.1.2.3.10 Explicit Frames . 47
B.1.3 Summary of Rules for Transmodel Presentation . 48
B.1.3.1 Presentation of Class Structure diagrams . 48
B.1.3.2 Rules for naming and presenting classes . 48
B.1.3.3 Rules for use of role names . 49
B.1.3.4 Rules for use of multiplicity . 50
B.1.3.5 Rules for relationship qualifiers . 50
3
---------------------- Page: 5 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
B.1.3.6 Rules for presenting relationships . 51
B.1.3.7 Rules for Placing Role names . 51
B.2 Extensions to the Common Concept MODEL . 52
B.2.1 General . 52
B.2.2 Additional Common Concepts . 52
B.2.2.1 Additional Generalizations . 52
B.2.2.1.1 Generic Type of Value – Conceptual MODEL . 52
B.2.2.1.2 Generic Assignment – Conceptual MODEL . 53
B.2.2.1.3 Generic Section – Conceptual MODEL . 54
B.2.3 Extensions to the Generic Framework . 55
B.2.3.1 General . 55
B.2.3.2 Alternative Text – Conceptual MODEL . 55
B.2.3.3 Generic View – Conceptual MODEL . 56
B.2.3.4 Generic Loggable Object – Conceptual MODEL . 57
B.2.3.5 Event Model – Conceptual MODEL. 57
B.2.4 Extensions to the Reusable Components . 58
B.2.4.1 Employee Model – Conceptual MODEL . 58
B.2.4.2 Message Model – Conceptual MODEL . 59
B.2.4.2.1 Messages . 59
B.2.4.2.2 Publication Scope . 60
B.2.4.3 Role Model – Conceptual MODEL . 61
B.2.4.3.1 Generic Roles . 61
B.2.4.3.2 Service Organization Roles . 62
B.2.4.3.3 Employee Roles . 62
B.2.4.3.4 Administrative Organization Roles . 63
B.2.4.3.5 Technology Organization Roles . 64
B.2.4.3.6 Messaging Roles . 65
B.2.4.3.7 Transport Customer Roles . 66
B.2.4.4 Security List – Conceptual MODEL . 66
B.2.4.5 Transfer Time – Conceptual MODEL . 67
B.2.5 Data Dictionary . 67
B.2.5.1 General . 67
B.2.5.2 ADMINISTRATIVE ORGANIZATION ROLE . 68
B.2.5.3 ALTERNATIVE TEXT . 68
B.2.5.4 ASSIGNMENT . 68
B.2.5.5 BLACKLIST . 68
4
---------------------- Page: 6 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
B.2.5.6 CLASS ATTRIBUTE . 69
B.2.5.7 CONDUCTOR ROLE . 69
B.2.5.8 CUSTOMER SERVICE PROVIDER ROLE . 69
B.2.5.9 CUSTOMER SERVICE ROLE . 69
B.2.5.10 DATA COLLECTOR ROLE . 70
B.2.5.11 DRIVER ROLE . 70
B.2.5.12 EMPLOYEE. 70
B.2.5.13 EMPLOYEE ROLE . 70
B.2.5.14 EVENT . 71
B.2.5.15 GENERAL EVENT . 71
B.2.5.16 GENERAL OBSERVER ROLE . 71
B.2.5.17 GENERAL SECTION . 71
B.2.5.18 LOG . 72
B.2.5.19 LOG ENTRY . 72
B.2.5.20 LOGGABLE OBJECT . 72
B.2.5.21 MESSAGE . 72
B.2.5.22 MESSAGE PART . 73
B.2.5.23 MESSAGE PRIORITY . 73
B.2.5.24 ORGANIZATION ROLE . 73
B.2.5.25 PT SCOPE . 73
B.2.5.26 PUBLICATION APPROVER ROLE . 73
B.2.5.27 PUBLICATION DECISION . 74
B.2.5.28 PUBLICATION SCOPE. 74
B.2.5.29 PUBLICATION WINDOW . 74
B.2.5.30 PUBLISHING ACTION . 74
B.2.5.31 PUBLISHING CHANNEL . 75
B.2.5.32 QUALIFICATION . 75
B.2.5.33 REGISTRAR ROLE . 75
B.2.5.34 SECTION . 75
B.2.5.35 SECTION IN LINK SEQUENCE . 76
B.2.5.36 SECURITY LIST. 76
B.2.5.37 SECURITY LISTABLE . 76
B.2.5.38 SECURITY LISTING . 76
B.2.5.39 SECURITY MANAGER ROLE . 76
B.2.5.40 SERVICE OPERATOR ROLE . 77
B.2.5.41 SITUATION AUTHOR ROLE . 77
5
---------------------- Page: 7 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
B.2.5.42 SPECIFIC OBSERVER ROLE . 77
B.2.5.43 STATION EMPLOYEE ROLE . 77
B.2.5.44 TECHNOLOGY ORGANIZATION ROLE . 78
B.2.5.45 TRAFFIC INFORMATION OFFICER ROLE . 78
B.2.5.46 TRANSFER TIME . 78
B.2.5.47 TRANSPORT USER ROLE. 78
B.2.5.48 TRAVEL DOCUMENT CONTROLLER ROLE . 79
B.2.5.49 TRAVEL DOCUMENT CONTROLLING ORGANIZATION ROLE . 79
B.2.5.50 TRAVEL ORGANIZATION ROLE . 79
B.2.5.51 TYPE OF AUDIENCE . 79
B.2.5.52 TYPE OF EVENT . 80
B.2.5.53 TYPE OF MESSAGE . 80
B.2.5.54 TYPE OF MESSAGE PART CONTENT . 80
B.2.5.55 TYPE OF QUALIFICATION . 80
B.2.5.56 TYPE OF SECURITY LIST . 81
B.2.5.57 TYPE OF VALUE. 81
B.2.5.58 View . 81
B.2.5.59 WHITELIST . 81
Annex C (informative) Data Model Evolutions. 83
C.1 Change Requests . 83
C.2 Source of Text . 83
C.3 Diagram Status . 83
Bibliography . 85
6
---------------------- Page: 8 ----------------------
SIST EN 12896-8:2019
EN 12896-8:2019 (E)
European foreword
This document (EN 12896-8:2019) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
...
SLOVENSKI STANDARD
oSIST prEN 12896-8:2019
01-januar-2019
-DYQLSUHYR]5HIHUHQþQLSRGDWNRYQLPRGHOGHO ,QIRUPDFLMHRXSUDYOMDQMXLQ
VWDWLVWLND
Public transport - Reference data model - Part 8 : Management information & statistics
Ta slovenski standard je istoveten z: prEN 12896-8
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 12896-8: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-8:2019
---------------------- Page: 2 ----------------------
oSIST prEN 12896-8:2019
DRAFT
EUROPEAN STANDARD
prEN 12896-8
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2018
ICS 35.240.60
English Version
Public transport - Reference data model - Part 8 :
Management information & satistics
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-8:2018 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
1.1 General Scope of the document . 5
1.2 Functional Domain Description . 6
1.3 Particular Scope of this Document . 6
2 Normative references . 6
3 Terms and definitions . 7
3.1 General Terms and Definitions . 7
3.2 Domain Specific Terms and Definitions . 9
4 Symbols and Abbreviations . 10
5 Management Information and Statistics Domain . 10
5.1 Introduction . 10
5.1.1 Information Needs . 10
5.1.2 Calculation of indicators . 11
5.1.3 Functions Covered . 13
5.1.4 Limitations of the Model . 14
5.2 Management Information and Statistics Data Model . 15
5.2.1 Loggable Objects Model . 15
5.2.2 Logging Time and Place . 15
5.2.3 Recorded Objects . 16
5.2.4 Recorded Use of Services . 20
5.2.5 Examples of use of the LOGGABLE OBJECT pattern . 21
Annex A (normative) Data Dictionary . 27
A.1 Introduction . 27
A.2 Data Dictionary . 27
Annex B (normative) Additional Common Concepts — Extension to EN 12896-1:2016
“Public Transport Reference Data Model — Part 1: Common Concepts” . 31
B.1 Methodology and Conventions . 31
B.2 Extensions to the Common Concept MODEL . 49
Annex C (informative) Data Model Evolutions. 80
C.1 Change Requests . 80
C.2 Source of Text . 80
C.3 Diagram Status . 80
Bibliography . 82
2
---------------------- Page: 4 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
European foreword
This document (prEN 12896-8: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 CEN/TR 12896-9 “Public transport - reference data model - Part 9: Informative Documentation”.
3
---------------------- Page: 5 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8: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 document 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 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 (this part) presents Management Information and Statistics.
4
---------------------- Page: 6 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
1 Scope
1.1 General Scope of the document
The main objective of the present document 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: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.
5
---------------------- Page: 7 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8: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 document, 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 8:
Management Information and Statistics” describes how to structure data which refers to the planning
stages (e.g. timetables, run times, driver rosters etc.) and/or to the daily actual production, and which is
registered for different purposes, in particular to build service performance indicators. The data model
is based on a generic design pattern, Generic Loggable Objects Model (provided in the Additional
Common Concepts part – Annex B), and incorporates the following data packages:
— Logging Time and Place, providing additions to the Generic Loggable Objects Model,
— Recorded Objects
— Recorded Use of Services
— Service Journey Performance.
The last three packages show how the recorded data contributes to the implementation of indicators.
This document itself is composed of the following parts:
— Main document (normative),
— 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 EN 12896-1:2016, particularly useful for parts 4 to
8 of the Public Transport Reference Data Model;
— Annex C (informative), indicating the data model evolution from the previous version.
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-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
ISO 4217:2015, Codes for the representation of currencies
ISO 80000-1:2009, Quantities and units — Part 1: General
6
---------------------- Page: 8 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
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
3.1.1
attribute
property of an entity.
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
conceptual data model in the context of data modelling,
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 which, in this European Standard, is a sub-activity of a functional area.
7
---------------------- Page: 9 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
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.
3.1.14
logical level
logical data model in the context of data modelling
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.
8
---------------------- Page: 10 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
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 Management Information and Statistics domain are used. Terms which
are also data entity names are defined in the data dictionary in Annex A and are mostly not repeated here.
3.2.1
aggregation frame
data structure within which the data values are grouped and used for a formula to provide an indicator
3.2.2
indicator
set of data (calculated or measured) which may be either qualitative or quantitative that is used to
provide information on the status (may be a measure, a functional state, etc.) or the quality of a service
or a function.
3.2.3
indicator type
category of a given indicator, e.g. time, length, passenger count, price, vehicle, etc.
3.2.4
indicator unit
measurement unit (e.g. metres, seconds, passengers, etc.) in which a specific indicator is measured.
3.2.5
formula
method to calculate indicators that are based on other indicators or on a set of raw data.
3.2.6
granularity
input for calculation processes representing the smallest unit(s) to generate output indicator(s).
9
---------------------- Page: 11 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
3.2.7
O/D matrix
tabular structure describing data by origin/destination parameters (e.g. daily traffic volume between
zones)
3.2.8
indicator parameter type
category of a given indicator parameter, e.g. time, length, passenger count, price, vehicle, etc.
3.2.9
indicator parameter unit
measurement unit (e.g. meters, seconds, passengers, etc.) in which a specific indicator parameter is
measured.
4 Symbols and Abbreviations
IFOPT Identification of Fixed Objects in Public Transport.
ISO International Standards Organization.
IT Information Technology.
O/D Origin / Destination
PT Public Transport.
PTO Public Transport Operator.
SI International System of Units (abbreviated from the French Système international)
SIRI Service Interface for Real-time Information.
TM Transmodel
UML Unified Modelling Language.
5 Management Information and Statistics Domain
5.1 Introduction
5.1.1 Information Needs
Management information deals with functions analysing production data in order to evaluate the service
quality or to take corrective measures in planning and managing operations. In public transport, for
instance, the study of operational data (e.g. observed run times, passenger load) collected during service
operations is an input for strategic planning (e.g. how and when to amend the schedules), tactical
planning (e.g. when to undertake a certain control action), quality follow-up, etc.
Management information uses therefore two main types of data:
— data resulting from the planning stages, i.e. theoretical data on the production orders (e.g. timetables,
run times, driver rosters etc.);
— data describing the daily actual production (e.g. observed passing times, actual number of
passengers, missed interchanges, modifications operated to the plan etc.).
Advances in technology, in particular as regards to data storage, allow the provision of the necessary data
in production databases, against which the desired requests can be made by public transport managers.
10
---------------------- Page: 12 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
Consistent data structures make the design of such requests easier, and offer the flexibility required to
meet a large variety of needs.
5.1.2 Calculation of indicators
The number of different ways of processing PT data in order to issue relevant and synthetic information
reports for managers is almost infinite. The criteria for doing so will depend on local conditions, on the
level of management, on the time scale of the analysis, etc. The objective of the reference model is not to
describe the processing methods, but to offer data structures able to fulfil their manifold requirements.
The result of raw data processing provides different types of indicators, each specialized for reporting
information on a specific aspect of public transport. (Service Demand, Commercial Speed, etc.).
An indicator relates to a set of data (planned, measured, or a combination of both) and may be either
qualitative or quantitative. Indicators of lower level objects may be overridden by higher level objects
(e.g. an indicator related to the ROUTE can override the aggregation - summary, average, etc. - of
indicators related to ROUTE LINK).
Indicators may be of several indicator types, for example, they may describe the time, length, passenger
count, price, vehicle, etc.
An indicator unit is used to describe the measurement unit of quantitative indicators. Unit names shall
follow standards ISO 4217:2015 for currency codes, and ISO 80000:2009 for SI units.
A set of parameters may be associated with any indicator to represent the scope of that particular
indicator (for example, a TIME BAND and a DAY TYPE for a passenger count indicator).
Indicator parameter type describes categories of the indicator parameter: time, length, passenger count,
price, vehicle, etc.
Indicator parameter unit describes the measurement unit of quantitative indicator parameters. Unit
names shall follow standards ISO 4217:2015 for currency codes, and ISO 80000:2009 for SI units.
A formula describes the method to calculate indicators that are based on other indicators and/or on a set
of raw data.
An aggregation frame describes a data structure within which the data values are grouped and used for
a formula to provide an indicator.
A granularity entity determines the smallest unit(s) in a calculation process which generates indicator(s).
A calculation process that generates the indicators is characterized by indicator parameters, formula,
aggregation frame and granularity unit.
The main elements used to calculate indicators are presented in the figure below.
11
---------------------- Page: 13 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
Aggregation frame
a set of data that is the basis for the calculation
Granularity
of an indicator by a formula
defines the smallest unit(s) the indicators
Indicator (input)
need to be generated for
Indicator type Indicator unit
Indicator parameter
Formula Calculator
Indicator parameter Indicator parameter
type unit defines a repeatable way to execute executes formulae and generates result
calculations indicators and indicator parameters
Indicator (input)
Indicator type Indicator unit
Indicator (output)
Indicator type Indicator unit
Indicator parameter
Indicator parameter Indicator parameter
type unit
Indicator parameter
Indicator parameter Indicator parameter
type unit
Figure 1 — Calculation of indicators
This figure also indicates that indicators might be generated by a previous (nested) calculation, and might
be used in another calculation process.
For example, the calculation of the length of a tram network for each infrastructure operator (assuming
there are more than one) may be modelled as follows:
— indicator (input): length of the projection of ROUTE LINKs on the infrastructure, parameterized by
infrastructure operator;
— aggregation frame: defines a set of ROUTE LINKs that make up the network;
— granularity: defines that the indicators shall be grouped by infrastructure operator;
— formula: calculates the sums of the length of each item in the aggregation frame;
— calculator: executes the formula for each infrastructure operator;
— indicator (output): total length of the network, parameterized by infrastructure operator.
A typical use of indicators is when the actual service has to be compared to the planned service. To ensure
the same indicator parameters are used in the comparison, a common granularity definition might be
needed to govern the calculation processes and provide the same level of detail for both actual
(measured) and planned service indicators. This is illustrated by the figure below.
12
---------------------- Page: 14 ----------------------
oSIST prEN 12896-8:2019
prEN 12896-8:2018 (E)
Aggregation frame (for planned service)
a set of data of the planned service that is the basis for the calculation
of an indicator by a formula
Formula
Indicator of planned service (input)
defines a repeatable way to execute
calculations
Calculator (for planned service)
Comparable indicator(s) for planned service
executes formula and generates result
indicators for planned service
Granularity (common)
Comparison
(scalar,
defines the common smallest unit(s)
spatial,
the indicators need to be generated for temporal,
in both planned and actual domains
etc.)
Calculator (for actual service)
Comparable indicator(s) for actual service
executes formula and generates result
Aggregation frame (for actual service)
indicators for actual service
a set of data of the actual service that is the basis for the calculation
of an indicator by a formula
Formula
Indicator of actual service (input)
defines a repeatable way to execute
calculations
Figure 2 — Comparison of planned and actual service indicators
5.1.3 Functions Covered
The following functions as defined in Operating Raw data and statistics exchange are covered by
Transmodel v6:
a) Service dimensions: this function considers all the information to evaluate the dimension of the
service in terms of number of lines, journeys, available seats, etc.
b) Commercial speed: this function considers all the information needed to evaluate the commercial
speed of the fleet
c) Service spatial coverage: this function considers all the information relevant t
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.