1.1 General Scope of the Standard<\/b><\/p>\n
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:<\/p>\n
the Reference Data Model, EN 12896, known as Transmodel V5.1;<\/p>\n<\/li>\n
EN 28701:2012, Intelligent transport systems \u2013 Public transport \u2013 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;<\/p>\n<\/li>\n<\/ul>\n
incorporating the requirements of:<\/p>\n
EN 15531-1 to -3 and CEN\/TS 15531-4 and -5: Public transport \u2013 Service interface for real-time information relating to public transport operations (SIRI);<\/p>\n<\/li>\n
CEN\/TS 16614-1 and -2: Public transport \u2013 Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.<\/p>\n<\/li>\n<\/ul>\n
Particular attention is drawn to the data model structure and methodology:<\/p>\n
the data model is described in a modular form in order to facilitate the understanding and the use of the model;<\/p>\n<\/li>\n
the data model is entirely described in UML.<\/p>\n<\/li>\n<\/ul>\n
The following functional domains are considered:<\/p>\n
Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;<\/p>\n<\/li>\n
Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);<\/p>\n<\/li>\n
Passenger Information (planned and real-time);<\/p>\n<\/li>\n
Fare Management (fare structure, sales, validation, control);<\/p>\n<\/li>\n
Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;<\/p>\n<\/li>\n
Driver Management:<\/p>\n
Driver Scheduling (day-type related driver schedules),<\/p>\n<\/li>\n
Rostering (ordering of driver duties into sequences according to some chosen methods),<\/p>\n<\/li>\n
Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance);<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
Management Information and Statistics (including data dedicated to service performance indicators).<\/p>\n<\/li>\n<\/ul>\n
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 \u201cCommon Concepts\u201d.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | Annex A (normative)Data Dictionary A.1 Introduction A.2 Data Dictionary \u2014 Operations Monitoring and Control A.2.1 ALARM A.2.2 ARRIVAL <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | A.2.3 CALL A.2.4 CALL FOR MEANS A.2.5 CALL FOR REPAIRS A.2.6 CALL PART <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | A.2.7 CASUALTIES A.2.8 CHANGE OF JOURNEY PATTERN A.2.9 CHANGE OF JOURNEY TIMING <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | A.2.10 CHANGE OF VEHICLE A.2.11 COMPOSITE JOURNEY CONTROL ACTION A.2.12 CONTROL ACTION <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | A.2.13 DATED ARRIVAL A.2.14 DATED CALL A.2.15 DATED CALL PART A.2.16 DATED DEPARTURE <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | A.2.17 DATED JOURNEY PART A.2.18 DATED SPECIAL SERVICE <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | A.2.19 DATED VEHICLE JOURNEY INTERCHANGE A.2.20 DATED VEHICLE SERVICE A.2.21 DATED VEHICLE SERVICE PART <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | A.2.22 DELAY A.2.23 DEPARTURE A.2.24 DEPARTURE EXCHANGE <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | A.2.25 DEPARTURE LAG A.2.26 DETECTED OPERATION A.2.27 DRIVER INCIDENT <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | A.2.28 EASEMENT A.2.29 ELEMENTARY JOURNEY CONTROL ACTION A.2.30 ESTIMATED PASSING TIME <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | A.2.31 EXTRA DATED VEHICLE JOURNEY A.2.32 FACILITY CONDITION <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | A.2.33 FACILITY MONITORING METHOD A.2.34 FACILITY OPERATIONAL EVENT A.2.35 FACILITY STATUS <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | A.2.36 FLEXIBLE JOURNEY ACTIVATION A.2.37 IMPEDED TIME A.2.38 INCIDENT <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | A.2.39 INTERCHANGE CANCELLATION A.2.40 INTERCHANGE CONTROL ACTION <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | A.2.41 INTERCHANGE CREATION A.2.42 INTERCHANGE MODIFICATION <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | A.2.43 JOURNEY CANCELLATION A.2.44 JOURNEY CREATION A.2.45 LOGICAL DRIVER A.2.46 LOGICAL VEHICLE <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | A.2.47 LOGICAL VEHICLE CANCELLATION A.2.48 LOGICAL VEHICLE CREATION A.2.49 METHOD OF CAPTURE A.2.50 MONITORED FACILITY <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | A.2.51 MONITORED JOURNEY PART FACILITY A.2.52 MONITORED LOCAL SERVICE FACILITY A.2.53 MONITORED OPERATION <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | A.2.54 MONITORED PLACE EQUIPMENT FACILITY A.2.55 MONITORED SPECIAL SERVICE A.2.56 MONITORED VEHICLE EQUIPMENT FACILITY <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | A.2.57 MONITORED VEHICLE JOURNEY A.2.58 MONITORED VEHICLE JOURNEY FACILITY A.2.59 OBSERVED PASSING TIME <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | A.2.60 OPERATIONAL EVENT A.2.61 OPERATIONAL MESSAGE A.2.62 PARTIAL JOURNEY CANCELLATION <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | A.2.63 PLANNED REMEDY A.2.64 PRODUCTION PLAN A.2.65 PT SITUATION A.2.66 PT SITUATION AFFECTED SCOPE <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | A.2.67 PT SITUATION CONSEQUENCE A.2.68 PT SITUATION CONSEQUENCE SCOPE <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | A.2.69 PT SITUATION GENERAL CONSEQUENCE A.2.70 PT SITUATION MESSAGE A.2.71 RELATED SITUATION <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | A.2.72 REMEDY A.2.73 RESORPTION A.2.74 RESPACING <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | A.2.75 SITE OPERATIONAL EVENT A.2.76 SITUATION A.2.77 SITUATION CAUSE <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | A.2.78 SITUATION REASON A.2.79 SITUATION SOURCE A.2.80 TYPE OF DELAY <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | A.2.81 TYPE OF SITUATION SOURCE A.2.82 TYPE OF VEHICLE DETECTING A.2.83 TYPE OF VEHICLE MONITORING <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | A.2.84 VEHICLE ASSIGNMENT A.2.85 VEHICLE CONTROL ACTION A.2.86 VEHICLE DETECTING <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | A.2.87 VEHICLE DETECTING LOG ENTRY A.2.88 VEHICLE INCIDENT A.2.89 VEHICLE MONITORING <\/td>\n<\/tr>\n | ||||||
| 87<\/td>\n | A.2.90 VEHICLE MONITORING LOG ENTRY A.2.91 VEHICLE WORK ASSIGNMENT <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | Annex B (normative)Additional Common Concepts \u2014 Extension to EN 12896-1:2016, Public Transport \u2013 Reference Data Model \u2013 Part 1: Common Concepts B.1 Methodology and Conventions B.1.1 Methodology for conceptual modelling B.1.1.1 General B.1.1.2 General B.1.1.3 Packages <\/td>\n<\/tr>\n | ||||||
| 89<\/td>\n | B.1.1.4 Package Prefixes and Package order <\/td>\n<\/tr>\n | ||||||
| 90<\/td>\n | B.1.1.5 Part Prefixes and diagram names B.1.1.6 Class diagrams <\/td>\n<\/tr>\n | ||||||
| 91<\/td>\n | B.1.1.7 Class Diagram Presentations B.1.1.8 Use of Colour <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | B.1.2 MODEL Class Diagrams <\/td>\n<\/tr>\n | ||||||
| 93<\/td>\n | B.1.2.2 Classes and attributes <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | B.1.2.3 Relationships <\/td>\n<\/tr>\n | ||||||
| 102<\/td>\n | B.1.3 Summary of Rules for Transmodel Presentation B.1.3.1 Presentation of Class Structure diagrams <\/td>\n<\/tr>\n | ||||||
| 103<\/td>\n | B.1.3.2 Rules for naming and presenting classes B.1.3.3 Rules for use of role names <\/td>\n<\/tr>\n | ||||||
| 104<\/td>\n | B.1.3.4 Rules for use of multiplicity <\/td>\n<\/tr>\n | ||||||
| 105<\/td>\n | B.1.3.5 Rules for relationship qualifiers <\/td>\n<\/tr>\n | ||||||
| 106<\/td>\n | B.1.3.6 Rules for presenting relationships B.1.3.7 Rules for Placing Role names B.2 Extensions to the Common Concept MODEL B.2.1 General B.2.2 Additional Common Concepts \u2014 Additional Generalizations B.2.2.1 Generic Type of Value \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 108<\/td>\n | B.2.2.2 Generic Assignment \u2013 Conceptual MODEL B.2.2.3 Generic Section \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 109<\/td>\n | B.2.3 Extensions to the Generic Framework B.2.3.1 General B.2.3.2 Alternative Text \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 110<\/td>\n | B.2.3.3 Generic View \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 111<\/td>\n | B.2.3.4 Generic Loggable Object \u2013 Conceptual MODEL B.2.3.5 Event Model \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 112<\/td>\n | B.2.4 Extensions to the Reusable Components B.2.4.1 Employee Model \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 113<\/td>\n | B.2.4.2 Message Model \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 115<\/td>\n | B.2.4.3 Role Model \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 120<\/td>\n | B.2.4.4 Security List \u2013 Conceptual MODEL <\/td>\n<\/tr>\n | ||||||
| 121<\/td>\n | B.2.4.5 Transfer Time \u2013 Conceptual MODEL B.2.5 Data Dictionary B.2.5.1 General <\/td>\n<\/tr>\n | ||||||
| 122<\/td>\n | B.2.5.2 ADMINISTRATIVE ORGANIZATION ROLE B.2.5.3 ALTERNATIVE TEXT B.2.5.4 ASSIGNMENT B.2.5.5 BLACKLIST <\/td>\n<\/tr>\n | ||||||
| 123<\/td>\n | B.2.5.6 CLASS ATTRIBUTE B.2.5.7 CONDUCTOR ROLE B.2.5.8 CUSTOMER SERVICE PROVIDER ROLE B.2.5.9 CUSTOMER SERVICE ROLE <\/td>\n<\/tr>\n | ||||||
| 124<\/td>\n | B.2.5.10 DATA COLLECTOR ROLE B.2.5.11 DRIVER ROLE B.2.5.12 EMPLOYEE B.2.5.13 EMPLOYEE ROLE <\/td>\n<\/tr>\n | ||||||
| 125<\/td>\n | B.2.5.14 EVENT B.2.5.15 GENERAL EVENT B.2.5.16 GENERAL OBSERVER ROLE <\/td>\n<\/tr>\n | ||||||
| 126<\/td>\n | B.2.5.17 GENERAL SECTION B.2.5.18 LOG B.2.5.19 LOG ENTRY B.2.5.20 LOGGABLE OBJECT <\/td>\n<\/tr>\n | ||||||
| 127<\/td>\n | B.2.5.21 MESSAGE B.2.5.22 MESSAGE PART B.2.5.23 MESSAGE PRIORITY B.2.5.24 ORGANIZATION ROLE <\/td>\n<\/tr>\n | ||||||
| 128<\/td>\n | B.2.5.25 PT SCOPE B.2.5.26 PUBLICATION APPROVER ROLE B.2.5.27 PUBLICATION DECISION B.2.5.28 PUBLICATION SCOPE <\/td>\n<\/tr>\n | ||||||
| 129<\/td>\n | B.2.5.29 PUBLICATION WINDOW B.2.5.30 PUBLISHING ACTION B.2.5.31 PUBLISHING CHANNEL B.2.5.32 QUALIFICATION <\/td>\n<\/tr>\n | ||||||
| 130<\/td>\n | B.2.5.33 REGISTRAR ROLE B.2.5.34 SECTION B.2.5.35 SECTION IN LINK SEQUENCE B.2.5.36 SECURITY LIST <\/td>\n<\/tr>\n | ||||||
| 131<\/td>\n | B.2.5.37 SECURITY LISTABLE B.2.5.38 SECURITY LISTING B.2.5.39 SECURITY MANAGER ROLE B.2.5.40 SERVICE OPERATOR ROLE <\/td>\n<\/tr>\n | ||||||
| 132<\/td>\n | B.2.5.41 SITUATION AUTHOR ROLE B.2.5.42 SPECIFIC OBSERVER ROLE B.2.5.43 STATION EMPLOYEE ROLE B.2.5.44 TECHNOLOGY ORGANIZATION ROLE <\/td>\n<\/tr>\n | ||||||
| 133<\/td>\n | B.2.5.45 TRAFFIC INFORMATION OFFICER ROLE B.2.5.46 TRANSFER TIME B.2.5.47 TRANSPORT USER ROLE B.2.5.48 TRAVEL DOCUMENT CONTROLLER ROLE <\/td>\n<\/tr>\n | ||||||
| 134<\/td>\n | B.2.5.49 TRAVEL DOCUMENT CONTROLLING ORGANIZATION ROLE B.2.5.50 TRAVEL ORGANIZATION ROLE B.2.5.51 TYPE OF AUDIENCE B.2.5.52 TYPE OF EVENT <\/td>\n<\/tr>\n | ||||||
| 135<\/td>\n | B.2.5.53 TYPE OF MESSAGE B.2.5.54 TYPE OF MESSAGE PART CONTENT B.2.5.55 TYPE OF QUALIFICATION B.2.5.56 TYPE OF SECURITY LIST <\/td>\n<\/tr>\n | ||||||
| 136<\/td>\n | B.2.5.57 TYPE OF VALUE B.2.5.58 View B.2.5.59 WHITELIST <\/td>\n<\/tr>\n | ||||||
| 137<\/td>\n | Annex C (informative)Data Model Evolution C.1 Change Requests <\/td>\n<\/tr>\n | ||||||
| 165<\/td>\n | C.2 Source of Text C.3 Diagram Status <\/td>\n<\/tr>\n | ||||||
| 167<\/td>\n | Annex D (informative)Mapping to DATEX II and SIRI (SX and FM) D.1 Related standards D.2 Mapping with DATEX II D.2.1 DATEX II <\/td>\n<\/tr>\n | ||||||
| 168<\/td>\n | D.2.2 DATEX II and Transmodel D.2.3 Overview of correspondence of Situation elements <\/td>\n<\/tr>\n | ||||||
| 171<\/td>\n | D.2.4 Outline Mapping between DATEX II and Transmodel <\/td>\n<\/tr>\n | ||||||
| 172<\/td>\n | D.3 Mapping with SIRI SX and SIRI FM D.3.1 SIRI \u2014 Service Interface for Real-time Information <\/td>\n<\/tr>\n | ||||||
| 173<\/td>\n | D.3.2 Outline Mapping between SIRI\u2014 SX \u2014 and Transmodel <\/td>\n<\/tr>\n | ||||||
| 174<\/td>\n | D.3.3 Outline Mapping between SIRI\u2014 FM\u2014 and Transmodel <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Public transport. Reference data model – Operations monitoring and control<\/b><\/p>\n |