SIST EN 12896-4:2019
(Main)Public transport - Reference data model - Part 4: Operations monitoring and control
Public transport - Reference data model - Part 4: Operations monitoring and control
The data modules dedicated to cover most functions of the domain Operations Monitoring and Control will be specified, in particular: vehicle detecting and monitoring, events & control actions, messaging. This part will take into account SIRI and align with SIRI as far as possible.
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 4: Betriebsüberwachung und Steuerung
Transports publics - Modèle de données de référence - Partie 4 : suivi et contrôle de l'exploitation
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) à la suite de leur publication,
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 : transport public-é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, 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 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ée « Transports publics – Modèle de données de référence – Partie 4 : suivi et contrôle de l’exploitation » intègre les ensembles de données suivants :
- le MODÈLE de composants de production datés,
- le MODÈLE d’APPEL,
- le MODÈLE de plan de production,
- le MODÈLE de détection et de suivi,
- le MODÈLE d’action de régulation,
- le MODÈLE d’événement et d’incident,
- le MODÈLE de messagerie,
- le MODÈLE de situation et
- le MODÈLE de surveillance et de disponibilité des installations.
[...]
Javni prevoz - Referenčni podatkovni model - 4. del: Spremljanje delovanja in nadzor
Določeni so podatkovni moduli, ki zajemajo večino funkcij domene spremljanja delovanja in nadzora, zlasti zaznavanje in spremljanje vozil, dogodke in nadzorne ukrepe, sporočila. Ta del upošteva funkcijo SIRI in je z njo usklajen v največji možni meri.
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-4:2019
01-november-2019
Javni prevoz - Referenčni podatkovni model - 4. del: Spremljanje delovanja in
nadzor
Public transport - Reference data model - Part 4: Operations monitoring and control
Öffentlicher Verkehr - Referenzdatenmodell Teil 4: Betriebsüberwachung und Steuerung
Transports publics - Modèle de données de référence - Partie 4 : suivi et contrôle de
l'exploitation
Ta slovenski standard je istoveten z: EN 12896-4:2019
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 12896-4: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-4:2019
---------------------- Page: 2 ----------------------
SIST EN 12896-4:2019
EN 12896-4
EUROPEAN STANDARD
NORME EUROPÉENNE
September 2019
EUROPÄISCHE NORM
ICS 35.240.60
English Version
Public transport - Reference data model - Part 4:
Operations monitoring and control
Transports publics - Modèle de données de référence - Öffentlicher Verkehr - Referenzdatenmodell Teil 4:
Partie 4 : suivi et contrôle de l'exploitation Betriebsüberwachung und Steuerung
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-4:2019 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 12896-4:2019
EN 12896-4:2019 (E)
Contents Page
European foreword . 10
Introduction . 11
1 Scope . 12
1.1 General Scope of the Standard. 12
1.2 Functional Domain Description . 13
1.3 Particular Scope of this Document . 13
2 Normative references . 14
3 Terms and definitions . 14
4 Symbols and Abbreviations . 16
5 Operations monitoring and control . 17
5.1 Introduction . 17
5.2 Dated Operational Plans . 18
5.2.1 Principles . 18
5.2.2 Vehicle Work Production Components . 19
5.2.3 Dated Vehicle Service . 23
5.2.4 Dated Call . 24
5.2.5 Implementation of Dated Plans . 25
5.2.6 Production Plan . 25
5.3 Resource Detection and Monitoring . 27
5.3.1 Limits . 27
5.3.2 Functions Related to the Monitoring Process . 27
5.3.3 Resources to be monitored . 28
5.3.4 Vehicle Detecting . 29
5.3.5 Vehicle Monitoring . 30
5.4 Vehicle Assignments . 31
5.4.1 General . 31
5.4.2 Assignments . 32
5.4.3 Work Plan Assignment . 32
5.4.4 Vehicle Assignment . 33
5.5 Monitored Operations . 33
5.5.1 Monitored Services . 33
5.5.2 Monitored Passing Times . 35
5.5.3 Other Monitored Situations . 36
5.5.4 Expected and Registered Situation . 37
5.6 Control Actions . 37
5.6.1 General . 37
5.6.2 Vehicle Control Actions . 39
5.6.3 Elementary Journey Control Actions. 40
5.6.4 Composite Journey Control Actions . 43
5.6.5 Interchange Control Actions . 44
5.7 Operational Events . 46
5.8 Operational Messages . 48
5.9 Situation Description . 49
5.10 Monitored Facilities . 52
2
---------------------- Page: 4 ----------------------
SIST EN 12896-4:2019
EN 12896-4:2019 (E)
Annex A (normative) Data Dictionary . 55
A.1 Introduction. 55
A.2 Data Dictionary — Operations Monitoring and Control . 55
A.2.1 ALARM . 55
A.2.2 ARRIVAL . 55
A.2.3 CALL . 56
A.2.4 CALL FOR MEANS . 56
A.2.5 CALL FOR REPAIRS . 56
A.2.6 CALL PART . 56
A.2.7 CASUALTIES . 57
A.2.8 CHANGE OF JOURNEY PATTERN . 57
A.2.9 CHANGE OF JOURNEY TIMING . 57
A.2.10 CHANGE OF VEHICLE . 58
A.2.11 COMPOSITE JOURNEY CONTROL ACTION . 58
A.2.12 CONTROL ACTION . 58
A.2.13 DATED ARRIVAL . 59
A.2.14 DATED CALL . 59
A.2.15 DATED CALL PART . 59
A.2.16 DATED DEPARTURE . 59
A.2.17 DATED JOURNEY PART . 60
A.2.18 DATED SPECIAL SERVICE . 60
A.2.19 DATED VEHICLE JOURNEY INTERCHANGE . 61
A.2.20 DATED VEHICLE SERVICE. 61
A.2.21 DATED VEHICLE SERVICE PART . 61
A.2.22 DELAY . 62
A.2.23 DEPARTURE . 62
A.2.24 DEPARTURE EXCHANGE . 62
A.2.25 DEPARTURE LAG . 63
A.2.26 DETECTED OPERATION . 63
A.2.27 DRIVER INCIDENT . 63
A.2.28 EASEMENT . 64
A.2.29 ELEMENTARY JOURNEY CONTROL ACTION . 64
A.2.30 ESTIMATED PASSING TIME . 64
A.2.31 EXTRA DATED VEHICLE JOURNEY . 65
A.2.32 FACILITY CONDITION . 65
A.2.33 FACILITY MONITORING METHOD . 66
3
---------------------- Page: 5 ----------------------
SIST EN 12896-4:2019
EN 12896-4:2019 (E)
A.2.34 FACILITY OPERATIONAL EVENT . 66
A.2.35 FACILITY STATUS . 66
A.2.36 FLEXIBLE JOURNEY ACTIVATION . 67
A.2.37 IMPEDED TIME . 67
A.2.38 INCIDENT . 67
A.2.39 INTERCHANGE CANCELLATION . 68
A.2.40 INTERCHANGE CONTROL ACTION . 68
A.2.41 INTERCHANGE CREATION . 69
A.2.42 INTERCHANGE MODIFICATION . 69
A.2.43 JOURNEY CANCELLATION . 70
A.2.44 JOURNEY CREATION . 70
A.2.45 LOGICAL DRIVER . 70
A.2.46 LOGICAL VEHICLE . 70
A.2.47 LOGICAL VEHICLE CANCELLATION . 71
A.2.48 LOGICAL VEHICLE CREATION . 71
A.2.49 METHOD OF CAPTURE . 71
A.2.50 MONITORED FACILITY . 71
A.2.51 MONITORED JOURNEY PART FACILITY . 72
A.2.52 MONITORED LOCAL SERVICE FACILITY . 72
A.2.53 MONITORED OPERATION . 72
A.2.54 MONITORED PLACE EQUIPMENT FACILITY . 73
A.2.55 MONITORED SPECIAL SERVICE . 73
A.2.56 MONITORED VEHICLE EQUIPMENT FACILITY . 73
A.2.57 MONITORED VEHICLE JOURNEY . 74
A.2.58 MONITORED VEHICLE JOURNEY FACILITY . 74
A.2.59 OBSERVED PASSING TIME . 74
A.2.60 OPERATIONAL EVENT . 75
A.2.61 OPERATIONAL MESSAGE . 75
A.2.62 PARTIAL JOURNEY CANCELLATION . 75
A.2.63 PLANNED REMEDY . 76
A.2.64 PRODUCTION PLAN . 76
A.2.65 PT SITUATION. 76
A.2.66 PT SITUATION AFFECTED SCOPE . 76
A.2.67 PT SITUATION CONSEQUENCE . 77
A.2.68 PT SITUATION CONSEQUENCE SCOPE . 77
A.2.69 PT SITUATION GENERAL CONSEQUENCE . 78
4
---------------------- Page: 6 ----------------------
SIST EN 12896-4:2019
EN 12896-4:2019 (E)
A.2.70 PT SITUATION MESSAGE . 78
A.2.71 RELATED SITUATION . 78
A.2.72 REMEDY . 79
A.2.73 RESORPTION . 79
A.2.74 RESPACING . 79
A.2.75 SITE OPERATIONAL EVENT . 80
A.2.76 SITUATION . 80
A.2.77 SITUATION CAUSE . 80
A.2.78 SITUATION REASON . 81
A.2.79 SITUATION SOURCE . 81
A.2.80 TYPE OF DELAY . 81
A.2.81 TYPE OF SITUATION SOURCE . 82
A.2.82 TYPE OF VEHICLE DETECTING . 82
A.2.83 TYPE OF VEHICLE MONITORING. 82
A.2.84 VEHICLE ASSIGNMENT . 83
A.2.85 VEHICLE CONTROL ACTION. 83
A.2.86 VEHICLE DETECTING . 83
A.2.87 VEHICLE DETECTING LOG ENTRY . 84
A.2.88 VEHICLE INCIDENT . 84
A.2.89 VEHICLE MONITORING. 84
A.2.90 VEHICLE MONITORING LOG ENTRY. 85
A.2.91 VEHICLE WORK ASSIGNMENT . 85
Annex B (normative) Additional Common Concepts — Extension to EN 12896-1:2016, Public
Transport – Reference Data Model – Part 1: Common Concepts . 86
B.1 Methodology and Conventions . 86
B.1.1 Methodology for conceptual modelling . 86
B.1.1.1 General . 86
B.1.1.2 General . 86
B.1.1.3 Packages . 86
B.1.1.4 Package Prefixes and Package order . 87
B.1.1.5 Part Prefixes and diagram names . 88
B.1.1.6 Class diagrams . 88
B.1.1.7 Class Diagram Presentations . 89
B.1.1.8 Use of Colour . 89
B.1.2 MODEL Class Diagrams . 90
B.1.2.1 General . 90
B.1.2.2 Classes and attributes . 91
5
---------------------- Page: 7 ----------------------
SIST EN 12896-4:2019
EN 12896-4:2019 (E)
B.1.2.2.1 General . 91
B.1.2.2.2 Attribute visibility . 91
B.1.2.2.3 Attribute names . 92
B.1.2.2.4 Attribute types . 92
B.1.2.2.5 Multiplicity of Attributes . 92
B.1.2.2.6 Common attributes . 92
B.1.2.2.7 Simple Diagram Example . 92
B.1.2.3 Relationships . 94
B.1.2.3.1 General . 94
B.1.2.3.2 Association relationships . 94
B.1.2.3.3 Reflexive associations . 94
B.1.2.3.4 Aggregation relationship . 95
B.1.2.3.5 Generalization relationship . 96
B.1.2.3.6 Multiplicity (Cardinality) of Relationships . 97
B.1.2.3.7 Presence of Relationships on a given diagram. 97
B.1.2.3.8 Relationships and navigability . 98
B.1.2.3.9 Positional semantics for laying out classes and relationships . 100
B.1.2.3.10 Explicit Frames .
...
SLOVENSKI STANDARD
oSIST prEN 12896-4:2019
01-januar-2019
-DYQLSUHYR]5HIHUHQþQLSRGDWNRYQLPRGHOGHO6SUHPOMDQMHGHORYDQMDLQ
QDG]RU
Public transport - Reference data model - Part 4: Operations monitoring and control
Öffentlicher Verkehr - Referenzdatenmodell Teil 4 - 8
Ta slovenski standard je istoveten z: prEN 12896-4
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 12896-4: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-4:2019
---------------------- Page: 2 ----------------------
oSIST prEN 12896-4:2019
DRAFT
EUROPEAN STANDARD
prEN 12896-4
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2018
ICS 35.240.60
English Version
Public transport - Reference data model - Part 4:
Operations monitoring and control
Öffentlicher Verkehr - Referenzdatenmodell Teil 4 - 8
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-4:2018 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 12896-4:2019
prEN 12896-4:2018 (E)
Contents Page
European foreword . 13
Introduction . 14
1 Scope . 15
1.1 General Scope of the Standard. 15
1.2 Functional Domain Description . 16
1.3 Particular Scope of this Document . 16
2 Normative references . 17
3 Terms and definitions . 17
3.1 General Terms and Definitions . 17
3.2 Domain Specific Terms and Definitions . 19
4 Symbols and Abbreviations . 19
5 Operations monitoring and control . 20
5.1 Introduction . 20
5.2 Dated Operational Plans . 21
5.2.1 Principles . 21
5.2.2 Vehicle Work Production Components . 22
5.2.3 Dated Vehicle Service . 26
5.2.4 Dated Call . 27
5.2.5 Implementation of Dated Plans . 28
5.2.6 Production Plan . 29
5.3 Resource Detection and Monitoring . 30
5.3.1 Limits . 30
5.3.2 Functions Related to the Monitoring Process . 30
5.3.3 Resources to be monitored . 31
5.3.4 Vehicle Detecting . 32
5.3.5 Vehicle Monitoring . 33
5.4 Vehicle Assignments . 34
5.4.1 General . 34
5.4.2 Assignments . 35
5.4.3 Work Plan Assignment . 35
5.4.4 Vehicle Assignment . 36
5.5 Monitored Operations . 36
5.5.1 Monitored Services . 36
5.5.2 Monitored Passing Times . 38
5.5.3 Other Monitored Situations . 39
5.5.4 Expected and Registered Situation . 40
5.6 Control Actions . 40
5.6.1 General . 40
5.6.2 Vehicle Control Actions . 41
5.6.3 Elementary Journey Control Actions. 43
5.6.4 Composite Journey Control Actions . 46
5.6.5 Interchange Control Actions . 47
5.7 Operational Events . 49
5.8 Operational Messages . 51
5.9 Situation Description . 52
5.10 Monitored Facilities . 55
Annex A (normative) Data Dictionary . 57
2
---------------------- Page: 4 ----------------------
oSIST prEN 12896-4:2019
prEN 12896-4:2018 (E)
A.1 Introduction. 57
A.2 Data Dictionary . 57
A.2.1 Operations Monitoring and Control . 57
A.2.1.1 ALARM . 57
A.2.1.2 ARRIVAL . 57
A.2.1.3 CALL . 58
A.2.1.4 CALL FOR MEANS . 58
A.2.1.5 CALL FOR REPAIRS . 58
A.2.1.6 CALL PART . 58
A.2.1.7 CASUALTIES . 59
A.2.1.8 CHANGE OF JOURNEY PATTERN . 59
A.2.1.9 CHANGE OF JOURNEY TIMING . 59
A.2.1.10 . CHANGE OF
VEHICLE . 60
A.2.1.11 . COMPOSITE JOURNEY CONTROL
ACTION . 60
A.2.1.12 . CONTROL
ACTION . 60
A.2.1.13 . DATED
ARRIVAL . 61
A.2.1.14 . DATED
CALL . 61
A.2.1.15 . DATED CALL
PART . 61
A.2.1.16 . DATED
DEPARTURE . 61
A.2.1.17 . DATED JOURNEY
PART . 62
A.2.1.18 . DATED SPECIAL
SERVICE . 62
A.2.1.19 . DATED VEHICLE JOURNEY
INTERCHANGE . 62
A.2.1.20 . DATED VEHICLE
SERVICE . 63
A.2.1.21 . DATED VEHICLE SERVICE
PART . 63
A.2.1.22 . DELAY
. 63
A.2.1.23 . DEPARTURE
. 63
3
---------------------- Page: 5 ----------------------
oSIST prEN 12896-4:2019
prEN 12896-4:2018 (E)
A.2.1.24 . DEPARTURE
EXCHANGE . 64
A.2.1.25 . DEPARTURE
LAG. 64
A.2.1.26 . DETECTED
OPERATION . 64
A.2.1.27 . DRIVER
INCIDENT . 65
A.2.1.28 .EASEMENT
. 65
A.2.1.29 . ELEMENTARY JOURNEY CONTROL
ACTION . 65
A.2.1.30 . ESTIMATED PASSING
TIME . 65
A.2.1.31 . EXTRA DATED VEHICLE
JOURNEY . 66
A.2.1.32 . FACILITY
CONDITION . 66
A.2.1.33 . FACILITY MONITORING
METHOD . 67
A.2.1.34 . FACILITY OPERATIONAL
EVENT . 67
A.2.1.35 . FACILITY
STATUS . 67
A.2.1.36 . FLEXIBLE JOURNEY
ACTIVATION . 68
A.2.1.37 . IMPEDED
TIME . 68
A.2.1.38 . INCIDENT
. 68
A.2.1.39 . INTERCHANGE
CANCELLATION . 69
A.2.1.40 .INTERCHANGE CONTROL
ACTION . 69
A.2.1.41 . INTERCHANGE
CREATION. 69
A.2.1.42 . INTERCHANGE
MODIFICATION . 70
A.2.1.43 . JOURNEY
CANCELLATION . 70
A.2.1.44 . JOURNEY
CREATION. 70
4
---------------------- Page: 6 ----------------------
oSIST prEN 12896-4:2019
prEN 12896-4:2018 (E)
A.2.1.45 .LOGICAL
DRIVER . 71
A.2.1.46 .LOGICAL
VEHICLE . 71
A.2.1.47 . LOGICAL VEHICLE
CANCELLATION . 71
A.2.1.48 . LOGICAL VEHICLE
CREATION . 71
A.2.1.49 . METHOD OF
CAPTURE . 72
A.2.1.50 .MONITORED
FACILITY. 72
A.2.1.51 . MONITORED JOURNEY PART
FACILITY. 72
A.2.1.52 . MONITORED LOCAL SERVICE
FACILITY. 72
A.2.1.53 .MONITORED
OPERATION . 73
A.2.1.54 . MONITORED PLACE EQUIPMENT
FACILITY. 73
A.2.1.55 . MONITORED SPECIAL
SERVICE . 73
A.2.1.56 .MONITORED VEHICLE EQUIPMENT
FACILITY. 74
A.2.1.57 . MONITORED VEHICLE
JOURNEY . 74
A.2.1.58 . MONITORED VEHICLE JOURNEY
FACILITY. 74
A.2.1.59 . OBSERVED PASSING
TIME . 74
A.2.1.60 .OPERATIONAL
EVENT . 75
A.2.1.61 .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.