🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN 12896-4:2019:2020 Edition

BS EN 12896-4:2019:2020 Edition

$215.11

Public transport. Reference data model – Operations monitoring and control

Published By Publication Date Number of Pages
BSI 2020 178
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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 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
57 Annex A (normative)Data Dictionary
A.1 Introduction
A.2 Data Dictionary — Operations Monitoring and Control
A.2.1 ALARM
A.2.2 ARRIVAL
58 A.2.3 CALL
A.2.4 CALL FOR MEANS
A.2.5 CALL FOR REPAIRS
A.2.6 CALL PART
59 A.2.7 CASUALTIES
A.2.8 CHANGE OF JOURNEY PATTERN
A.2.9 CHANGE OF JOURNEY TIMING
60 A.2.10 CHANGE OF VEHICLE
A.2.11 COMPOSITE JOURNEY CONTROL ACTION
A.2.12 CONTROL ACTION
61 A.2.13 DATED ARRIVAL
A.2.14 DATED CALL
A.2.15 DATED CALL PART
A.2.16 DATED DEPARTURE
62 A.2.17 DATED JOURNEY PART
A.2.18 DATED SPECIAL SERVICE
63 A.2.19 DATED VEHICLE JOURNEY INTERCHANGE
A.2.20 DATED VEHICLE SERVICE
A.2.21 DATED VEHICLE SERVICE PART
64 A.2.22 DELAY
A.2.23 DEPARTURE
A.2.24 DEPARTURE EXCHANGE
65 A.2.25 DEPARTURE LAG
A.2.26 DETECTED OPERATION
A.2.27 DRIVER INCIDENT
66 A.2.28 EASEMENT
A.2.29 ELEMENTARY JOURNEY CONTROL ACTION
A.2.30 ESTIMATED PASSING TIME
67 A.2.31 EXTRA DATED VEHICLE JOURNEY
A.2.32 FACILITY CONDITION
68 A.2.33 FACILITY MONITORING METHOD
A.2.34 FACILITY OPERATIONAL EVENT
A.2.35 FACILITY STATUS
69 A.2.36 FLEXIBLE JOURNEY ACTIVATION
A.2.37 IMPEDED TIME
A.2.38 INCIDENT
70 A.2.39 INTERCHANGE CANCELLATION
A.2.40 INTERCHANGE CONTROL ACTION
71 A.2.41 INTERCHANGE CREATION
A.2.42 INTERCHANGE MODIFICATION
72 A.2.43 JOURNEY CANCELLATION
A.2.44 JOURNEY CREATION
A.2.45 LOGICAL DRIVER
A.2.46 LOGICAL VEHICLE
73 A.2.47 LOGICAL VEHICLE CANCELLATION
A.2.48 LOGICAL VEHICLE CREATION
A.2.49 METHOD OF CAPTURE
A.2.50 MONITORED FACILITY
74 A.2.51 MONITORED JOURNEY PART FACILITY
A.2.52 MONITORED LOCAL SERVICE FACILITY
A.2.53 MONITORED OPERATION
75 A.2.54 MONITORED PLACE EQUIPMENT FACILITY
A.2.55 MONITORED SPECIAL SERVICE
A.2.56 MONITORED VEHICLE EQUIPMENT FACILITY
76 A.2.57 MONITORED VEHICLE JOURNEY
A.2.58 MONITORED VEHICLE JOURNEY FACILITY
A.2.59 OBSERVED PASSING TIME
77 A.2.60 OPERATIONAL EVENT
A.2.61 OPERATIONAL MESSAGE
A.2.62 PARTIAL JOURNEY CANCELLATION
78 A.2.63 PLANNED REMEDY
A.2.64 PRODUCTION PLAN
A.2.65 PT SITUATION
A.2.66 PT SITUATION AFFECTED SCOPE
79 A.2.67 PT SITUATION CONSEQUENCE
A.2.68 PT SITUATION CONSEQUENCE SCOPE
80 A.2.69 PT SITUATION GENERAL CONSEQUENCE
A.2.70 PT SITUATION MESSAGE
A.2.71 RELATED SITUATION
81 A.2.72 REMEDY
A.2.73 RESORPTION
A.2.74 RESPACING
82 A.2.75 SITE OPERATIONAL EVENT
A.2.76 SITUATION
A.2.77 SITUATION CAUSE
83 A.2.78 SITUATION REASON
A.2.79 SITUATION SOURCE
A.2.80 TYPE OF DELAY
84 A.2.81 TYPE OF SITUATION SOURCE
A.2.82 TYPE OF VEHICLE DETECTING
A.2.83 TYPE OF VEHICLE MONITORING
85 A.2.84 VEHICLE ASSIGNMENT
A.2.85 VEHICLE CONTROL ACTION
A.2.86 VEHICLE DETECTING
86 A.2.87 VEHICLE DETECTING LOG ENTRY
A.2.88 VEHICLE INCIDENT
A.2.89 VEHICLE MONITORING
87 A.2.90 VEHICLE MONITORING LOG ENTRY
A.2.91 VEHICLE WORK ASSIGNMENT
88 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 General
B.1.1.2 General
B.1.1.3 Packages
89 B.1.1.4 Package Prefixes and Package order
90 B.1.1.5 Part Prefixes and diagram names
B.1.1.6 Class diagrams
91 B.1.1.7 Class Diagram Presentations
B.1.1.8 Use of Colour
92 B.1.2 MODEL Class Diagrams
93 B.1.2.2 Classes and attributes
96 B.1.2.3 Relationships
102 B.1.3 Summary of Rules for Transmodel Presentation
B.1.3.1 Presentation of Class Structure diagrams
103 B.1.3.2 Rules for naming and presenting classes
B.1.3.3 Rules for use of role names
104 B.1.3.4 Rules for use of multiplicity
105 B.1.3.5 Rules for relationship qualifiers
106 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 — Additional Generalizations
B.2.2.1 Generic Type of Value – Conceptual MODEL
108 B.2.2.2 Generic Assignment – Conceptual MODEL
B.2.2.3 Generic Section – Conceptual MODEL
109 B.2.3 Extensions to the Generic Framework
B.2.3.1 General
B.2.3.2 Alternative Text – Conceptual MODEL
110 B.2.3.3 Generic View – Conceptual MODEL
111 B.2.3.4 Generic Loggable Object – Conceptual MODEL
B.2.3.5 Event Model – Conceptual MODEL
112 B.2.4 Extensions to the Reusable Components
B.2.4.1 Employee Model – Conceptual MODEL
113 B.2.4.2 Message Model – Conceptual MODEL
115 B.2.4.3 Role Model – Conceptual MODEL
120 B.2.4.4 Security List – Conceptual MODEL
121 B.2.4.5 Transfer Time – Conceptual MODEL
B.2.5 Data Dictionary
B.2.5.1 General
122 B.2.5.2 ADMINISTRATIVE ORGANIZATION ROLE
B.2.5.3 ALTERNATIVE TEXT
B.2.5.4 ASSIGNMENT
B.2.5.5 BLACKLIST
123 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
124 B.2.5.10 DATA COLLECTOR ROLE
B.2.5.11 DRIVER ROLE
B.2.5.12 EMPLOYEE
B.2.5.13 EMPLOYEE ROLE
125 B.2.5.14 EVENT
B.2.5.15 GENERAL EVENT
B.2.5.16 GENERAL OBSERVER ROLE
126 B.2.5.17 GENERAL SECTION
B.2.5.18 LOG
B.2.5.19 LOG ENTRY
B.2.5.20 LOGGABLE OBJECT
127 B.2.5.21 MESSAGE
B.2.5.22 MESSAGE PART
B.2.5.23 MESSAGE PRIORITY
B.2.5.24 ORGANIZATION ROLE
128 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
129 B.2.5.29 PUBLICATION WINDOW
B.2.5.30 PUBLISHING ACTION
B.2.5.31 PUBLISHING CHANNEL
B.2.5.32 QUALIFICATION
130 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
131 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
132 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
133 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
134 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
135 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
136 B.2.5.57 TYPE OF VALUE
B.2.5.58 View
B.2.5.59 WHITELIST
137 Annex C (informative)Data Model Evolution
C.1 Change Requests
165 C.2 Source of Text
C.3 Diagram Status
167 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
168 D.2.2 DATEX II and Transmodel
D.2.3 Overview of correspondence of Situation elements
171 D.2.4 Outline Mapping between DATEX II and Transmodel
172 D.3 Mapping with SIRI SX and SIRI FM
D.3.1 SIRI — Service Interface for Real-time Information
173 D.3.2 Outline Mapping between SIRI— SX — and Transmodel
174 D.3.3 Outline Mapping between SIRI— FM— and Transmodel

Related products

BS EN 12896-4:2019
$215.11