BS EN 12896-7:2019:2020 Edition
$215.11
Public transport. Reference data model – Driver management
Published By | Publication Date | Number of Pages |
BSI | 2020 | 126 |
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”.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
44 | Annex A (normative)Data Dictionary A.1 Introduction A.2 Data Dictionary — Driver Management A.2.1 ABSENCE A.2.2 ACCOUNT ENTRY |
45 | A.2.3 ACCOUNTING PERIOD A.2.4 ACTIVITY LOG ENTRY |
46 | A.2.5 ASSIGNED DUTY A.2.6 BREAK |
47 | A.2.7 BREAK FACILITY A.2.8 CHANGE OF DRIVER |
48 | A.2.9 COLUMN/DAY A.2.10 CONTINUOUS DUTY A.2.11 COST CENTRE A.2.12 DESIGN WEEK |
49 | A.2.13 DESIGN WEEK ELEMENT A.2.14 DRIVER A.2.15 DRIVER ASSIGNMENT |
50 | A.2.16 DRIVER CONTROL ACTION A.2.17 DRIVER SCHEDULE FRAME A.2.18 DRIVER TRIP |
51 | A.2.19 DRIVER TRIP TIME A.2.20 DRIVING SPELL A.2.21 DUTY |
52 | A.2.22 DUTY PART |
53 | A.2.23 DUTY TYPE A.2.24 FILL IN TIME A.2.25 LOGICAL DRIVER CANCELLATION |
54 | A.2.26 LOGICAL DRIVER CREATION A.2.27 NON-DRIVING SPELL A.2.28 PAUSE |
55 | A.2.29 REST A.2.30 ROSTER CYCLE A.2.31 ROSTER CYCLE ELEMENT |
56 | A.2.32 ROSTER DESIGN A.2.33 ROSTER DESIGN IN MATRIX A.2.34 ROSTER DESIGN TYPE |
57 | A.2.35 ROSTER ELEMENT A.2.36 ROSTER MATRIX A.2.37 ROW/DRIVER |
58 | A.2.38 SPARE DUTY A.2.39 SPELL |
59 | A.2.40 SPLIT DUTY A.2.41 STAND-BY A.2.42 STRETCH |
60 | A.2.43 TASK A.2.44 TIME ALLOWANCE |
61 | A.2.45 TYPE OF ABSENCE A.2.46 TYPE OF ALLOWANCE A.2.47 TYPE OF TASK |
62 | A.2.48 TYPE OF WAGE A.2.49 WAGE INCREASE A.2.50 WAGE TYPE ASSIGNMENT |
63 | A.2.51 WORK |
64 | Annex B (normative)Additional Common Concepts — Extension to EN 12896-1:2016, Public transport — Reference data model — Part 1: Common concepts B.1 Methodology and Conventions B.1.1 Methodology for conceptual modelling B.1.1.1 Introduction B.1.1.2 General B.1.1.3 Packages |
65 | B.1.1.4 Package Prefixes and Package order |
66 | B.1.1.5 Part Prefixes and diagram names B.1.1.6 Class diagrams |
67 | B.1.1.7 Class Diagram Presentations |
68 | B.1.1.8 Use of Colour B.1.2 MODEL Class Diagrams B.1.2.1 General |
69 | B.1.2.2 Classes and attributes |
73 | B.1.2.3 Relationships |
80 | B.1.3 Summary of Rules for Transmodel Presentation B.1.3.1 Presentation of Class Structure diagrams B.1.3.2 Rules for naming and presenting classes |
81 | B.1.3.3 Rules for use of role names |
82 | B.1.3.4 Rules for use of multiplicity |
83 | B.1.3.5 Rules for relationship qualifiers |
84 | B.1.3.6 Rules for presenting relationships B.1.3.7 Rules for Placing Role names |
85 | B.2 Extensions to the Common Concept MODEL B.2.1 General B.2.2 Additional Common Concepts B.2.2.1 Additional Generalizations |
88 | B.2.3 Extensions to the Generic Framework B.2.3.1 Alternative Text – Conceptual MODEL |
89 | B.2.3.2 Generic View – Conceptual MODEL B.2.3.3 Generic Loggable Object – Conceptual MODEL |
90 | B.2.3.4 Event Model – Conceptual MODEL |
91 | B.2.4 Extensions to the Reusable Components B.2.4.1 Employee Model – Conceptual MODEL |
92 | B.2.4.2 Message Model – Conceptual MODEL |
94 | B.2.4.3 Role Model – Conceptual MODEL |
99 | B.2.4.4 Security List – Conceptual MODEL |
100 | B.2.4.5 Transfer Time – Conceptual MODEL B.2.5 Data Dictionary B.2.5.1 ADMINISTRATIVE ORGANIZATION ROLE |
101 | B.2.5.2 ALTERNATIVE TEXT B.2.5.3 ASSIGNMENT |
102 | B.2.5.4 BLACKLIST B.2.5.5 CLASS ATTRIBUTE B.2.5.6 CONDUCTOR ROLE |
103 | B.2.5.7 CUSTOMER SERVICE PROVIDER ROLE B.2.5.8 CUSTOMER SERVICE ROLE B.2.5.9 DATA COLLECTOR ROLE |
104 | B.2.5.10 DRIVER ROLE B.2.5.11 EMPLOYEE B.2.5.12 EMPLOYEE ROLE B.2.5.13 EVENT |
105 | B.2.5.14 GENERAL EVENT B.2.5.15 GENERAL OBSERVER ROLE B.2.5.16 GENERAL SECTION |
106 | B.2.5.17 LOG B.2.5.18 LOG ENTRY B.2.5.19 LOGGABLE OBJECT |
107 | B.2.5.20 MESSAGE B.2.5.21 MESSAGE PART B.2.5.22 MESSAGE PRIORITY |
108 | B.2.5.23 ORGANIZATION ROLE B.2.5.24 PT SCOPE B.2.5.25 PUBLICATION APPROVER ROLE |
109 | B.2.5.26 PUBLICATION DECISION B.2.5.27 PUBLICATION SCOPE B.2.5.28 PUBLICATION WINDOW B.2.5.29 PUBLISHING ACTION |
110 | B.2.5.30 PUBLISHING CHANNEL B.2.5.31 QUALIFICATION B.2.5.32 REGISTRAR ROLE |
111 | B.2.5.33 SECTION B.2.5.34 SECTION IN LINK SEQUENCE B.2.5.35 SECURITY LIST |
112 | B.2.5.36 SECURITY LISTABLE B.2.5.37 SECURITY LISTING B.2.5.38 SECURITY MANAGER ROLE |
113 | B.2.5.39 SERVICE OPERATOR ROLE B.2.5.40 SITUATION AUTHOR ROLE B.2.5.41 SPECIFIC OBSERVER ROLE |
114 | B.2.5.42 STATION EMPLOYEE ROLE B.2.5.43 TECHNOLOGY ORGANIZATION ROLE B.2.5.44 TRAFFIC INFORMATION OFFICER ROLE |
115 | B.2.5.45 TRANSFER TIME B.2.5.46 TRANSPORT USER ROLE B.2.5.47 TRAVEL DOCUMENT CONTROLLER ROLE |
116 | B.2.5.48 TRAVEL DOCUMENT CONTROLLING ORGANIZATION ROLE B.2.5.49 TRAVEL ORGANIZATION ROLE B.2.5.50 TYPE OF AUDIENCE |
117 | B.2.5.51 TYPE OF EVENT B.2.5.52 TYPE OF MESSAGE B.2.5.53 TYPE OF MESSAGE PART CONTENT |
118 | B.2.5.54 TYPE OF QUALIFICATION B.2.5.55 TYPE OF SECURITY LIST B.2.5.56 TYPE OF VALUE |
119 | B.2.5.57 View B.2.5.58 WHITELIST |
120 | Annex C (informative)Data Model Evolutions C.1 Change Requests |
123 | C.2 Source of Text C.3 Diagram Status |