Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 8: Traffic management publications and extensions dedicated to the urban environment

Part 8 specifies additional data model structures that are applicable for traffic management applications in general and the urban environment in particular. It addresses data concepts to support the exchange of traffic management plans, rerouting, extensions of the existing DATEX II core model for this purpose in combination with additions to better support application into the urban environment.
It establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Control Centres (TCCs),
-   Traffic Information Centres (TICs),
-   Service Providers (SPs).

Intelligente Verkehrssysteme - DATEX-II-Datenaustauschspezifikationen für Verkehrsmanagement und Verkehrsinformationen - Teil 8: Publikationen von Verkehrsmanagementmaßnahmen und kommunale Ergänzungen

Systèmes de transport intelligents - DATEX II Spécification des échanges de données pour la gestion du trafic et l'information routières - Partie 8: Publications et extensions pour la gestion du trafic dédiées à l'environnement urbain

Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri upravljanju prometa in informiranju - 8. del: Publikacije in razširitve za upravljanje prometa, namenjene mestnemu okolju

General Information

Status
Not Published
Public Enquiry End Date
03-Dec-2024
Technical Committee
Current Stage
5520 - Unique Acceptance Procedure (UAP) (Adopted Project)
Start Date
03-Oct-2024
Due Date
20-Feb-2025

Relations

Buy Standard

Draft
kTS FprCEN/TS 16157-8:2024 - BARVE
English language
114 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-november-2024
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri
upravljanju prometa in informiranju - 8. del: Publikacije in razširitve za upravljanje
prometa, namenjene mestnemu okolju
Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 8: Traffic management publications and extensions
dedicated to the urban environment
Intelligente Verkehrssysteme - DATEX-II-Datenaustauschspezifikationen für
Verkehrsmanagement und Verkehrsinformationen - Teil 8: Publikationen von
Verkehrsmanagementmaßnahmen und kommunale Ergänzungen
Systèmes de transport intelligents - DATEX II Spécification des échanges de données
pour la gestion du trafic et l'information routières - Partie 8: Publications et extensions
pour la gestion du trafic dédiées à l'environnement urbain
Ta slovenski standard je istoveten z: FprCEN/TS 16157-8
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

FINAL DRAFT
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
September 2024
ICS Will supersede CEN/TS 16157-8:2020
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information -
Part 8: Traffic management publications and extensions
dedicated to the urban environment
Systèmes de transport intelligents - DATEX II Intelligente Verkehrssysteme - DATEX-II-
Spécification des échanges de données pour la gestion Datenaustauschspezifikationen für
du trafic et l'information routières - Partie 8: Verkehrsmanagement und Verkehrsinformationen -
Publications et extensions pour la gestion du trafic Teil 8: Publikationen von
dédiées à l'environnement urbain Verkehrsmanagementmaßnahmen und kommunale
Ergänzungen
This draft Technical Specification is submitted to CEN members for Vote. It has been drawn up by the Technical Committee
CEN/TC 278.
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, Türkiye 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 Technical Specification. It is distributed for review and comments. It is subject to change
without notice and shall not be referred to as a Technical Specification.

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
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. FprCEN/TS 16157-8:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Symbols and abbreviations . 7
5 UML notation . 8
6 «D2Namespace» UrbanExtensions . 8
6.1 Overview . 8
6.2 ClassifiedDelay Class. 9
6.3 EquipmentOrSystemType Class . 11
6.4 GeneralInstructionsToRoadUsers Class . 11
6.5 GeneralNetworkManagementType Class . 12
6.6 InfrastructureDamageType Class . 13
6.7 InfrastructureDescriptor Class . 13
6.8 LaneEnum Class . 14
6.9 NonVehicularRoadUsers Classes . 15
6.10 ObstructionType Class . 16
6.11 RoadOrCarriagewayOrLaneManagement Class . 17
6.12 StreetWorks Class . 18
6.13 VehicleType Class . 18
7 «D2Namespace» ReroutingManagementEnhanced . 19
7.1 Overview . 19
7.2 Semantics – Rerouting management and route description . 22
7.3 Semantics - RouteAllocation . 23
7.4 Semantics – Capacity Management . 24
8 «D2Namespace» TrafficManagementPlan . 25
8.1 Scope and Purpose of TrafficManagementPlan . 25
8.2 Key Concepts . 26
8.3 TmplanTablePublication . 27
8.4 TmplanTable . 27
8.4.1 Overview . 27
8.4.2 Scenario . 28
8.4.3 Strategy . 29
8.4.4 Measure . 29
8.4.5 Action . 30
8.4.6 OperatorActionDefinition . 31
8.4.7 TmplanOperationPublication . 33
8.5 TmplanImplementingAction . 34
Annex A (normative) Data Dictionary . 36
A.4.2 The <> "EquipmentOrSystemTypeEnumExtendedUrban" . 38
A.4.3 The <>
"GeneralInstructionToRoadUsersTypeEnumExtendedUrban" . 39
A.4.4 The <> "GeneralNetworkManagementTypeEnumExtendedUrban" . 39
A.4.5 The <> "InfrastructureDamageTypeEnumExtendedUrban" . 39
A.4.6 The <> "InfrastructureDescriptorEnumExtendedUrban" . 40
A.4.7 The <> "LaneEnumExtendedUrban" . 41
A.4.8 The <> "NonVehicularRoadUserTypeEnum" . 41
A.4.9 The <> "ObstructionTypeEnumExtendedUrban" . 41
A.4.10 The <>
"RoadOrCarriageWayOrLaneManagementTypeEnumExtendedUrban" . 42
A.4.11 The <> "StreetWorksTypeEnum" . 43
A.4.12 The <> "VehicleTypeExtendedUrban" . 43
A.5 Data Dictionary for "ReroutingManagementEnhanced" . 44
A.5.1 "Allocation" package . 44
A.5.2 "Classes" package . 47
A.6 Data Dictionary of <> for "ReroutingManagementEnhanced" . 55
A.6.1 The <> "PriorityIndex" . 55
A.7 Data Dictionary of <> for "ReroutingManagementEnhanced" . 55
A.7.2 The <> "CommentTypeEnumExtended". 55
A.7.3 The <> "CapacityManagementActionEnum" . 56
A.7.4 The <> "CapacityManagementMeasureEnum" . 56
A.7.5 on>> "ComplianceOptionEnumExtended" . 57
A.7.6 The <> "ConditionOperator" . 57
A.7.7 The <> "FacilityTypeEnum" . 58
A.7.8 The <> "PublicTransportTypeEnum" . 59
A.7.9 The <> "PublicTransportVehicleType" . 59
A.7.10 The <> "ReroutingAdviceTypeEnum" . 60
A.7.11 The <> "ReroutingTypeEnum". 60
A.7.12 The <> "TrafficTypeEnumExtended" . 61
A.8 Data Dictionary for "TrafficManagementPlan" . 61
A.8.1 "Action" package . 61
A.8.2 "Measure" package . 63
A.8.3 "OperatorActionDefinition" package . 65
A.8.4 "Scenario" package. 68
A.8.5 "TmplanOperation" package . 73
A.8.6 "TmplanOperationPublication" package . 80
A.8.7 "TmplanTable" package . 81
A.8.8 "TmplanTablePublication" package . 84
A.9 Data Dictionary of <> for "TrafficManagementPlan" . 85
A.10 Data Dictionary of <> for "TrafficManagementPlan" . 85
A.1
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.