SIST EN 12896-7:2019

Public transport - Reference data model - Part 7: Driver management

1.1   General Scope of the Standard
The main objective of the present standard 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, Intelligent transport systems - Public transport - 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 European 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: Public transport - Service interface for real-time information relating to public transport operations (SIRI);
-   CEN/TS 16614-1 and -2: Public transport - 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 EN 12896-1, Public transport - Reference data model - Part 1: Common concepts.
1.3   Particular Scope of this Document
The present document entitled Public transport - Reference data model - Part 7: Driver management incorporates the following data packages:
-   Driver Scheduling;
-   Rostering;
-   Personnel Disposition;
-   Driver Control Actions.
This document itself is composed of the following parts:
-   Main document (normative) representing the data model for the concepts shared by the different 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 EN 12896-1:2016, particularly useful for Parts 4 to 8 of the Public Transport Reference Data Model; and
-   Annex C (informative), indicating the data model evolutions.

Öffentlicher Verkehr - Referenzdatenmodell - Teil 7: Fahrermanagement

Transports publics - Modèle de données de référence - Partie 7 : Gestion des conducteurs

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 publics - 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 européenne (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 : Transports publics - Interface de service pour les informations en temps réel relatives à l'exploitation des transports publics (SIRI),
-   CEN/TS 16614-1 et -2 : Transports publics - Échange 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, 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 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é Transports publics - Modèle de données de référence - Partie 7 : gestion des conducteurs intègre les ensembles de données suivants :
-   Horaires des conducteurs,
-   Roulement,
-   Gestion du personnel roulant,
-   Actions de régulation des conducteurs.
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 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 - 7. del: Upravljanje voznega osebja

1.1 Splošno področje uporabe standarda
Glavni cilj trenutnega standarda je predstavitev referenčnega podatkovnega modela za javni prevoz na podlagi:
– referenčnega podatkovnega modela (EN 12896), poznanega kot Transmodel različice 5.1;
– standarda EN 28701:2012, Inteligentni transportni sistemi - Javni prevoz - 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 evropskega 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: Javni prevoz – Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza (SIRI),
– dokumentov CEN/TS 16614-1 in -2: Javni prevoz – Izmenjava omrežnih in voznorednih podatkov (NeTEx), predvsem specifične potrebe za obratovanje vlaka med kraji.
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 standardu EN 12896-1, Javni prevoz – Referenčni podatkovni model javnega prevoza – 1.del: Skupni koncepti.
1.3 Posebno področje uporabe tega dokumenta
Trenutni dokument »Javni prevoz – Referenčni podatkovni model – 7. del«: Upravljanje voznega osebja vključuje naslednje podatkovne pakete:
– razpored voznega osebja;
– urniki;
– razporejanje osebja;
– nadzorni ukrepi voznega osebja.
Ta dokument je sestavljen iz naslednjih delov:
– glavni dokument (normativni), ki predstavlja podatkovni model za pojme, ki si jih delijo različne domene Transmodela;
– dodatek A (normativni), ki vsebuje podatkovni slovar, tj. seznam vseh pojmov in tabel atributov, ki so v glavnem dokumentu, skupaj z definicijami;
– dodatek B (normativni), ki vsebuje dopolnilo k standardu EN 12896-1:2016, še posebej uporaben za dele 4 do 8 referenčnega podatkovnega modela za javni prevoz; in
– dodatek C (informativni) s prikazom razvoja podatkovnega modela.

General Information

• Status: Published
• Public Enquiry End Date: 30-Jan-2019
• Publication Date: 07-Oct-2019
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ITC - Information technology
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 03-Oct-2019
• Due Date: 08-Dec-2019
• Completion Date: 08-Oct-2019
• Directive: 2010/40/EU - Directive 2010/40/EU of the European Parliament and of the Council of 7 July 2010 on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport Text with EEA relevance
• Ref Project: EN 12896-7:2019 - Public transport - Reference data model - Part 7: Driver management

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 12896-7:2019
01-november-2019
Javni prevoz - Referenčni podatkovni model - 7. del: Upravljanje voznega osebja
Public transport - Reference data model - Part 7: Driver management
Transports publics - Modèle de données de référence - Partie 7 : Gestion des
conducteurs
Ta slovenski standard je istoveten z: EN 12896-7:2019
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-7: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-7:2019

---------------------- Page: 2 ----------------------
SIST EN 12896-7:2019


EN 12896-7
EUROPEAN STANDARD

NORME EUROPÉENNE

September 2019
EUROPÄISCHE NORM
ICS 35.240.60
English Version

Public transport - Reference data model - Part 7: Driver
management
Transports publics - Modèle de données de référence -
Partie 7 : Gestion des conducteurs
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-7:2019 E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
Contents Page
European foreword . 5
Introduction . 6
1 Scope . 7
1.1 General Scope of the Standard. 7
1.2 Functional Domain Description . 8
1.3 Particular Scope of this Document . 8
2 Normative references . 8
3 Terms and definitions . 9
4 Symbols and Abbreviations . 11
5 Driver Management. 12
5.1 Introduction . 12
5.2 Driver. 12
5.3 Driver Scheduling. 13
5.3.1 General Remarks . 13
5.3.2 Duties . 13
5.3.3 Driver Trips . 22
5.3.4 Driver Schedule Frame. 24
5.4 Rostering . 24
5.4.1 General Remarks . 24
5.4.2 Roster Matrices . 26
5.4.3 Roster Cycles . 28
5.4.4 Roster Designs . 31
5.4.5 Roster Assignments . 32
5.5 Personnel Disposition (informative) . 33
5.5.1 Introduction . 33
5.5.2 Driver Assignments . 33
5.5.3 Driver Accounting . 36
5.5.4 Accounting the Drivers’ Work . 38
5.6 Driver Control Actions. 39
5.6.1 General . 39
5.6.2 Logical Driver Creation . 40
5.6.3 Logical Driver Cancellation . 40
5.6.4 Change of Driver . 41
(normative) Data Dictionary . 42
A.1 Introduction . 42
A.2 Data Dictionary — Driver Management . 42
A.2.1 ABSENCE . 42
A.2.2 ACCOUNT ENTRY . 42
A.2.3 ACCOUNTING PERIOD . 43
A.2.4 ACTIVITY LOG ENTRY . 43
A.2.5 ASSIGNED DUTY . 44
A.2.6 BREAK. 44
A.2.7 BREAK FACILITY . 45
A.2.8 CHANGE OF DRIVER . 45
2

---------------------- Page: 4 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
A.2.9 COLUMN/DAY . 46
A.2.10 CONTINUOUS DUTY . 46
A.2.11 COST CENTRE . 46
A.2.12 DESIGN WEEK . 46
A.2.13 DESIGN WEEK ELEMENT . 47
A.2.14 DRIVER . 47
A.2.15 DRIVER ASSIGNMENT . 47
A.2.16 DRIVER CONTROL ACTION . 48
A.2.17 DRIVER SCHEDULE FRAME . 48
A.2.18 DRIVER TRIP . 48
A.2.19 DRIVER TRIP TIME . 49
A.2.20 DRIVING SPELL . 49
A.2.21 DUTY . 49
A.2.22 DUTY PART . 50
A.2.23 DUTY TYPE . 51
A.2.24 FILL IN TIME . 51
A.2.25 LOGICAL DRIVER CANCELLATION . 51
A.2.26 LOGICAL DRIVER CREATION . 52
A.2.27 NON-DRIVING SPELL . 52
A.2.28 PAUSE . 52
A.2.29 REST . 53
A.2.30 ROSTER CYCLE . 53
A.2.31 ROSTER CYCLE ELEMENT . 53
A.2.32 ROSTER DESIGN . 54
A.2.33 ROSTER DESIGN IN MATRIX . 54
A.2.34 ROSTER DESIGN TYPE . 54
A.2.35 ROSTER ELEMENT . 55
A.2.36 ROSTER MATRIX . 55
A.2.37 ROW/DRIVER . 55
A.2.38 SPARE DUTY. 56
A.2.39 SPELL . 56
A.2.40 SPLIT DUTY . 57
A.2.41 STAND-BY . 57
A.2.42 STRETCH . 57
A.2.43 TASK . 58
A.2.44 TIME ALLOWANCE . 58
A.2.45 TYPE OF ABSENCE . 59
A.2.46 TYPE OF ALLOWANCE . 59
A.2.47 TYPE OF TASK . 59
A.2.48 TYPE OF WAGE . 60
A.2.49 WAGE INCREASE . 60
A.2.50 WAGE TYPE ASSIGNMENT. 60
A.2.51 WORK . 61
(normative) Additional Common Concepts — Extension to EN 12896-1:2016, Public
transport — Reference data model — Part 1: Common concepts . 62
B.1 Methodology and Conventions . 62
B.1.1 Methodology for conceptual modelling . 62
B.1.2 MODEL Class Diagrams . 66
B.1.3 Summary of Rules for Transmodel Presentation . 78
B.2 Extensions to the Common Concept MODEL . 83
B.2.1 General . 83
B.2.2 Additional Common Concepts . 83
3

---------------------- Page: 5 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
B.2.3 Extensions to the Generic Framework . 86
B.2.4 Extensions to the Reusable Components . 89
B.2.5 Data Dictionary . 98
(informative) Data Model Evolutions. 118
C.1 Change Requests . 118
C.2 Source of Text . 121
C.3 Diagram Status . 121
Bibliography . 123

4

---------------------- Page: 6 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
European foreword
This document (EN 12896-7:2019) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by March 2020, and conflicting national standards shall
be withdrawn at the latest by March 2020.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
The series is composed with the following documents:
 Public transport – Reference data mode – Part 1: Common concepts;
 Public transport – Reference data mode – Part 2: Public transport network;
 Public transport – Reference data mode – Part 3: Timing information and vehicle scheduling;
 Public transport – Reference data mode – Part 4: Operations monitoring and control;
 Public transport – Reference data mode – Part 5: Fare management;
 Public transport – Reference data mode – Part 6: Passenger information;
 Public transport – Reference data mode – Part 7: Driver management;
 Public transport – Reference data mode – Part 8: Management information & statistics; and
 Public transport – Reference data mode – Part 9: Informative documentation [CEN/TR].
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 EN 12896:2006, the technical modifications made are presented in
CEN/TR 12896-9, Public transport – Reference data model – Part 9: Informative documentation.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: 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 the
United Kingdom.
5

---------------------- Page: 7 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
Introduction
Part 1 of this European 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 European 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 presents Passenger Information (planned and real-time).
Part 7 (this part) 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.
6

---------------------- Page: 8 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
1 Scope
1.1 General Scope of the Standard
The main objective of the present standard 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, Intelligent transport systems – Public transport – 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 European 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: Public transport – Service interface for real-time
information relating to public transport operations (SIRI);
 CEN/TS 16614-1 and -2: Public transport – 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);
7

---------------------- Page: 9 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
 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 document, and
of which the data have been represented as the reference model, are described in EN 12896-1, Public
transport – Reference data model – Part 1: Common concepts.
1.3 Particular Scope of this Document
The present document entitled Public transport – Reference data model – Part 7: Driver management
incorporates the following data packages:
 Driver Scheduling;
 Rostering;
 Personnel Disposition;
 Driver Control Actions.
This document itself is composed of the following parts:
 Main document (normative) presenting the data model for the concepts shared by the different
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 EN 12896-1:2016, particularly useful for Parts 4
to 8 of the Public Transport Reference Data Model; and
 Annex C (informative), indicating the data model evolutions.
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
EN 12896-4:2019, Public transport — Reference data model — Part 4: Operations monitoring and control
8

---------------------- Page: 10 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (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:
NOTE The following generic terms are used.
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
3.1.4
database
collection of data
Note 1 to entry: Often used in the sense of the physical implementation of a data model.
3.1.5
data domain
data structure (which is, 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
9

---------------------- Page: 11 ----------------------
SIST EN 12896-7:2019
EN 12896-7:2019 (E)
3.1.9
function
activity
Note 1 to entry: In this European Standard, 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 da
...

SLOVENSKI STANDARD
oSIST prEN 12896-7:2019
01-januar-2019
-DYQLSUHYR]5HIHUHQþQLSRGDWNRYQLPRGHOGHO8SUDYOMDQMHYR]QHJDRVHEMD
Public transport - Reference data model - Part 7: Driver management
Ta slovenski standard je istoveten z: prEN 12896-7
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 12896-7: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-7:2019

---------------------- Page: 2 ----------------------
oSIST prEN 12896-7:2019


DRAFT
EUROPEAN STANDARD
prEN 12896-7
NORME EUROPÉENNE

EUROPÄISCHE NORM

November 2018
ICS 35.240.60
English Version

Public transport - Reference data model - Part 7: Driver
management

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-7:2018 E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7: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 . 11
4 Symbols and Abbreviations . 11
5 Driver Management. 12
5.1 Introduction . 12
5.2 Driver. 12
5.3 Driver Scheduling. 12
5.3.1 General Remarks . 12
5.3.2 Duties . 13
5.3.3 Driver Trips . 21
5.3.4 Driver Schedule Frame. 23
5.4 Rostering . 24
5.4.1 General Remarks . 24
5.4.2 Roster Matrices . 25
5.4.3 Roster Cycles . 27
5.4.4 Roster Designs . 30
5.4.5 Roster Assignments . 31
5.5 Personnel Disposition (informative) . 32
5.5.1 Introduction . 32
5.5.2 Driver Assignments . 32
5.5.3 Driver Accounting . 35
5.5.4 Accounting the Drivers’ Work . 37
5.6 Driver Control Actions. 38
(normative) Data Dictionary . 41
A.1 Introduction . 41
A.2 Data Dictionary . 41
A.2.1 Driver Management. 41
(normative) Additional Common Concepts — Extension to EN 12896-1:2016, Public
transport — Reference data model — Part 1: Common concepts . 61
B.1 Methodology and Conventions . 61
B.1.1 Methodology for conceptual modelling . 61
B.1.2 MODEL Class Diagrams . 65
B.1.3 Summary of Rules for Transmodel Presentation . 77
B.2 Extensions to the Common Concept MODEL . 82
B.2.1 Additional Common Concepts . 82
B.2.2 Extensions to the Generic Framework . 85
2

---------------------- Page: 4 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
B.2.3 Extensions to the Reusable Components . 88
B.2.4 Data Dictionary . 97
(informative) Data Model Evolutions . 117
C.1 Change Requests . 117
C.2 Source of Text . 120
C.3 Diagram Status. 120
Bibliography . 122

3

---------------------- Page: 5 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7: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 EN 12896 series, Public transport — Reference data model, is composed with the following
documents:
 Part 1: Common concepts;
 Part 2: Public transport network;
 Part 3: Timing information and vehicle scheduling;
 Part 4: Operations monitoring and control [currently at Enquiry stage];
 Part 5: Fare management [currently at Enquiry stage];
 Part 6: Passenger information [currently at Enquiry stage];
 Part 7: Driver management [currently at Enquiry stage];
 Part 8 : Management information & statistics [currently at Enquiry stage]; and
 Part 9: Informative documentation [CEN/TR].
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.
4

---------------------- Page: 6 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7: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 presents Passenger Information (planned and real-time).
Part 7 (this part) 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-7:2019
prEN 12896-7:2018 (E)
1 Scope
1.1 General Scope of the Standard
The main objective of the present standard 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, Intelligent transport systems — Public transport — 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 European 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: Public transport — Service interface for real-time
information relating to public transport operations (SIRI);
 CEN/TS 16614-1 and -2: Public transport — 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);
6

---------------------- Page: 8 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
 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 EN 12896-1, Public
transport — Reference data model — Part 1: Common concepts.
1.3 Particular Scope of this Document
The present document entitled Public transport — Reference data model — Part 7: Driver management
incorporates the following data packages:
 Driver Scheduling;
 Rostering;
 Personnel Disposition;
 Driver Control Actions.
This document itself is composed of the following parts:
 Main document (normative) representing the data model for the concepts shared by the different
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 EN 12896-1:2016, particularly useful for Parts 4
to 8 of the Public Transport Reference Data Model; and
 Annex C (informative), indicating the data model evolutions.
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
7

---------------------- Page: 9 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
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
2
EN 12896-5:– , Public transport — Reference data model — Part 5: Fare management
EN 15531-1, Public transport — Service interface for real-time information relating to public transport
operations — Part 1: Context and framework
EN 15531-2, Public transport — Service interface for real-time information relating to public transport
operations — Part 2: Communications
EN 15531-3, Public transport — Service interface for real-time information relating to public transport
operations — Part 3: Functional service interfaces
CEN/TS 15531-4, Public transport — Service interface for real-time information relating to public
transport operations — Part 4: Functional service interfaces: Facility Monitoring
CEN/TS 15531-5, Public transport — Service interface for real-time information relating to public
transport operations — Part 5: Functional service interfaces - 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
EN 28701:2012, Intelligent transport systems — Public transport — Identification of Fixed Objects in
Public Transport (IFOPT)
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 are used.

1
 Under preparation.
2
 Under preparation.
8

---------------------- Page: 10 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
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
3.1.4
database
collection of data
Note 1 to entry: Often used in the sense of the physical implementation of a data model.
3.1.5
data domain
data structure (which is, 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; in this European Standard, 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)
9

---------------------- Page: 11 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
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 denormalized 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
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 is 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
10

---------------------- Page: 12 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
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 driver management domain are used. Terms which are also data
entity names are defined in the data dictionary in Annex A and are not repeated here.
3.2.1
relief
person taking the place of another person as responsible for a certain task (such as driving a bus)
3.2.2
roster
plan showing turns of duty or leave for individuals in an organization
4 Symbols and Abbreviations
IFOPT Identification of Fixed Objects in Public Transport (EN 28701:2012)
ISO  International Organization for Standardization
IT  Information Technology
NeTEx Network and Timetable Exchange (CEN/TS 16614 series)
PT  Public Transport
PTO  Public Transport Operator
SIRI  Service Interface for Real-time Information (EN 15531 (all parts) and CEN/TS 15531
(all parts))
SIRI-FM Service Interface for Real-time Information Facility Monitoring (CEN/TS 15531-4)
SIRI-SX Service Interface for Real-time Information Situation Exchange (CEN/TS 15531-5)
UML Unified Modelling Language
URI  Uniform Resource Identifier
URL  Universal Resource Locator
11

---------------------- Page: 13 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
5 Driver Management
5.1 Introduction
The description of driver management is divided into three main parts. The first major part concerns
driver scheduling, in essence creating the day-type related driver schedules where the required work is
divided into duties that represents a set of work to be performed by one driver on one day.
The next major part concerns rostering, describing how the driver duties are ordered into sequences,
according to some chosen method, to obtain a starting point for a balanced work share among the
personnel over the planning period.
The final major part is the personnel disposition, describing how physical drivers are assigned to do the
work of a logical driver. This part also covers the recording of driver performance.
Additionally, there are clauses concerning driver, driver trip and driver control actions.
5.2 Driver
class DM DR Driver MODEL
Name: DM DR Driver MODEL
AC Employee MODEL::EMPLOYEE
Author: Transmodel
Version: 6.0-1.0
Created: 2014-12-01 00:00:00
Updated: 2017-06-09 14:56:36
DRIVER
«UID»
Id

Figure 1 — Driver MODEL
The DRIVER entity describes a physical driver, who is an EMPLOYEE (see EN 12896-1) of the public
transport company.
Note that in the first stages of the planning process there are no direct references to the DRIVER (i.e. the
physical driver). Instead a theoretical LOGICAL DRIVER is used during planning, and later on there will
be a separate assignment of which DRIVER (physical driver) that shall perform the duties specified for a
certain LOGICAL DRIVER.
5.3 Driver Scheduling
5.3.1 General Remarks
Driver scheduling involves the construction of driver DUTies to cover the scheduled SERVICE
JOURNEYs (see EN 12896-3) at minimum cost. This process shall also give DRIVERs fair workloads,
which comply with the law and with the agreements made between the company and, for example,
driver unions. There are numerous parameters, such as maximum length of driving time allowed
without a break, which will be essential input for the driver scheduling algorithm. These are not
12

---------------------- Page: 14 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
included in the reference model, because they do not have a complex structure or relationships to the
data model entities but are simple values.
In many cases, BLOCKs (see EN 12896-3) will have already been compiled before the start of the driver
scheduling process and will be used as input. However, schedulers do not always want to work in that
order; the model allows DUTies to be entered into the system before pieces of vehicle work have been
assigned to them.
5.3.2 Duties
5.3.2.1 Duty Components

Figure 2 — Simplified overview of the main concepts in a duty in relation to a driver
A DUTY describes a day’s work for a LOGICAL DRIVER on one DAY TYPE. A DUTY may be a SPARE
DUTY, in which case no specific work has yet been assigned to it, or an ASSIGNED DUTY, which is
composed of a hierarchy of components.
Operators and applications use various DUTY component levels. The reference model includes more
levels than any one company is likely to want, in order to support these existing ways of structuring the
data. Some of these levels may only be used within the driver scheduling package and will not be
needed in a company database. They are included in the model because they explain the relationships
between entities that will be in such a company database.
13

---------------------- Page: 15 ----------------------
oSIST prEN 12896-7:2019
prEN 12896-7:2018 (E)
class DM DS Duty MODEL
ORGANISATION PART
AC Employee MODEL::
CC Service Calendar
CC Generic Organisation
TYPE OF QUALIFICATION
MODEL::DAY TYPE
MODEL::
for
ORGANISATIONAL UNIT
1
required
0.* in charge of 0.1
for
0.*
requiring under charge of
0.*
0.*
DUTY DM Duty Type MODEL::
worked on
DUTY TYPE
PreparationDuration [0.1]
FinishingDuration [0.1]
classified as
1
«UID»
Id
0.* classifying
Name: DM DS Duty MODEL
ASSIGNED DUTY SPARE DUTY
Author: Transmodel
Version: 6.0-1.0
«UID» «UID»
Created: 2014-12-01 00:00:00
Id Id
Updated: 2018-04-20 08:15:30
made up of 0.1
0.*
part of
ended at
end of POINT
DUTY PART
NT Timing Pattern
1
0.*
AccountingFactor [0.1] MODEL::TIMING POINT
AccountingTime [0.1]
started at start of
DriverAccessDuration [0.1]
1
DriverReturnDuration [0.1] 0.*
StartTime [0.1]
EndTime [0.1]
PreparationDuration [0.1]
DM Duty Stretch MODEL::
part of
FinishingDuration [0.1] including
STRETCH
«UID»
0.*
0.1
Id

Figure 3 — Duty MODEL
An ASSI
...