Shopping Cart

No products in the cart.

BSI PD CEN/TR 17143:2017

$215.11

Intelligent transport systems. Standards and actions necessary to enable urban infrastructure coordination to support Urban-ITS

Published By Publication Date Number of Pages
BSI 2017 642
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]

The scope of this project is to undertake a pre-study providing stakeholder mapping, framework identification, gap analysis and identification of standards and related actions required to address the urban infrastructure aspects: the provision of

  1. multimodal information services;

  2. traffic management;

  3. urban logistics,

    that are required to support the provision of Urban-ITS.

    Specifically, the scope of this pre-study is to produce a technical report that will (by December 2015), for each area, specifically address the standardisation requirements to meet the following technical challenges:

    • stakeholder engagement;

    • common/interoperable data;

    • multimodality;

    • creation of (multimodal) transport datasets;

    • multiple means of communication;

    • urban logistics management;

    • creation of urban-interurban interfaces;

    • use of open standards, architectures and specifications;

    • enable rather than prescribe or proscribe.

    It is the intention that, while the formal deliverable of this pre-study will be a technical report, that the project team will also identify areas for draft ‘New Work Item Proposals’ (and justifications) for work items to fill the identified gaps, where those gaps can be filled by Standards deliverables, and that the pre-study will also consider and make recommendations for any other support measures that are considered important or essential in order for the successful implementation, management and support of Urban-ITS in an environment where this is an administration controlled and led activity and not a community-wide managed or controlled activity.

    The pre-study report, in addition to its submission to the European Commission, shall be in a format suitable for adaptation to a European standardisation deliverable on Use Cases addressing the three areas of this request and highlighting their possible interdependencies. Specifically, a gap analysis identifying additional requirements and priorities for:

  4. Architecture: high level proposals outlining the parameters for a European standardisation deliverable for Urban-ITS architecture integrating the three areas of this request and highlighting connexions or interfaces with surrounding ITS applications as well as compatibility or coherence with existing standards, technical specifications, data models.

  5. Multimodal Information Services: Standardisation deliverables in support of new mobility services, such as car sharing, car-pooling, public bike sharing services, park & ride, bike & ride, etc. Alternative fuel infrastructure, including information on location and availability of stations, charging models and capacity at stations, (integrated) payment schemes, etc. A European standardisation deliverable on reference data model, common data dictionary and metadata structure for multimodal information services.

  6. Traffic Management: Standardisation deliverables in support of European standards for: a set of traffic management measures (encompassing the necessary infrastructure / static road data, dynamic road status data, traffic data or traffic control data, weather data), a set of traffic re-routing, traffic prioritisation and access regulation measures including intersections management (supplemented by vehicle identification data). In particular, the different types of road user charging models set up in various cities as well as the modalities of shared use of dedicated lanes by different types of vehicles (e.g. freight, public transport, emergency vehicles) should be considered. European standards or European Standardisation deliverables on reference data model, common data dictionary and metadata structure for traffic management including access regulation.

  7. Urban Logistics (Including parking management): Standardisation deliverables in support of European standards for: Intelligent parking for light vehicles, commercial vehicles and trucks. The option of extending existing technical specifications or profiles regarding parking or adapting them to the needs of the urban areas should be considered; loading bays information and reservation services for specific freight vehicles and logistic sectors. Standards and specifications proposed will need to address both infrastructure and vehicles (including vehicle and/or load identification where relevant). Moreover, the use of alternatively fuelled vehicles for urban logistics, and the options of their charging (e.g. during loading/unloading at the specific bays) should also be looked into. A European standardisation deliverable on reference data model, common data dictionary and metadata structure for urban logistics including parking management.

    For each of the identified areas, issues to be addressed by the pre-study, as defined by the Terms of Reference, are:

  8. Identify key stakeholders;

  9. High level mapping for key identified stakeholders for later participation in deliverables specification and development;

  10. Identifying the overall framework required for interoperability and interchangeability, particularly in respect of central communications architectures and centre-to-field communications (and providing use-case examples);

  11. Identifying the systems and devices that could take advantage of common structuring and implementation guidelines;

  12. Identifying barriers and constraints to the operation of the open single European market;

  13. Identifying transitional and migration issues;

  14. Providing a high level generic Concept of Operations for city/administration support for multimodal travel, traffic management and urban logistic aspects of Urban-ITS;

  15. Identifying standards requirements to assist/guide/support cities and administrations to provide support for Urban-ITS such as:

    • Information level (standards and support measures for defining the meaning of data and messages);

    • Application standards (to define the rules and procedures for exchanging information data);

    • Communications transport standards (to provide specifications for common rules and procedures guidelines that cities and administrations may wish to consider adopting to exchange application data between point ‘A’ and point ‘X’ on a network);

    • Subnetwork standards (to define the rules and procedures guidelines that cities and administrations may wish to consider adopting for exchanging data between two ‘adjacent’ devices over some communications media) Identifying existing standards and widely used technical means (such as DATEX II, XML, FTP, SNMP, SMTP, TCP, UDP, PPP, Ethernet, ASN.1, UTMC, OCA etc.);

  16. Identifying standardisation gaps and providing a list of potential work items to be developed during the early tenure of the Standardization Request (CID) to support and enable cities and administrations to effectively implement Urban-ITS and to enable the functioning of the Single European open market in the Urban-ITS sector;

  17. Identifying any other measures that would be a prerequisite to/or priority for the implementation of Urban-ITS to enable multimodal travel, traffic management and urban logistic aspects.

PDF Catalog

PDF Pages PDF Title
2 undefined
13 Introduction
15 1 Scope
17 2 Terms and definitions
30 3 Symbols and abbreviations
35 4 Summary of Remit to PT1701
36 5 Summary of situational factors affecting the study
38 6 Summary of Standards framework
39 7 Summary of Stakeholders and structuring
40 8 Summary of panoptic ‘across the board’ Requirements
45 9 Summary of communications and security requirements
47 10 Summary of MIS requirements
50 11 Summary of Traffic Management (TM) requirements
53 12 Summary of Urban Logistics (UL) requirements
55 13 Summary of architecture requirements
57 Annex A (informative)Detailed Recommendations of CEN/TC 278/PT 1701
A.1 Background and Structure of this Annex
A.1.1 Background
A.1.2 Use Cases
59 A.1.3 Objectives for Phase 2 outreach
61 A.2 Key issues and summarised recommendations
A.2.1 Summarised recommendations
62 A.2.2 Phase 2 outreach
66 A.3 Revised High Level Priority Recommendations for CID Support
70 A.4 Revised Recommendations for other ESOs/Committees
72 A.5 Revised priority Recommendations for other support measures
74 A.6 Other supported Recommendations for CID support
A.7 Other Recommendations for CID support (unsupported by outreach feedback)
75 A.8 Recommendations withdrawn as a result of outreach feedback
78 Annex B (informative)Objectives, strategy, philosophy and process of the study
B.1 Foreword
B.2 Overview
B.3 Commission Implementing Decision
B.3.1 Overview
80 B.3.2 General requirements for the requested deliverables
B.3.3 Requirements to strengthen compatibility and coherence with existing standards and technical specifications
81 B.3.4 Specific requirements for the requested deliverables
B.3.5 Multimodal information systems
82 B.3.6 Traffic management, including access regulation
B.3.7 Urban logistics, including parking management
83 B.4 Remit to PT1701
85 Annex C (informative)Situational Factors affecting the study
C.1 Overview
89 C.2 Characterising Urban-ITS
94 C.3 Stakeholders and actors
C.3.1 Stakeholders
C.3.1.1 Stakeholders who want Urban-ITS
96 C.3.1.2 Stakeholders who use Urban-ITS
C.3.1.3 Stakeholders who govern Urban-ITS
C.3.1.4 Stakeholders who Make ITS
C.3.2 Actors
98 C.4 Mixed vendor environment
C.4.1 Introduction
100 C.4.2 Obligations and expectations of urban public bodies
103 C.5 Standards combinations
105 C.6 Cooperation
C.7 Barriers and constraints to the operation of the open single European market (OSEM)
C.7.1 Common issues
107 C.7.2 Political obstacles to OSEM
C.7.3 Commercial obstacles to OSEM
108 C.7.4 Technical obstacles to OSEM
109 C.7.5 Contending aspirations of Urban administrations and commercial freight operators
C.7.6 Vendor lock-in
111 C.8 Autonomous /automated vehicles
C.8.1 Context
C.8.2 Autonomous driving and mobility
C.8.3 Autonomous driving and connectivity
112 C.8.4 Autonomous driving and maps
114 C.8.5 Autonomous vehicles and safety issues
115 C.8.6 Autonomous vehicles and security
C.8.7 Take up of autonomous vehicles
116 C.8.8 Autonomous vehicles and associated standardizations
120 C.9 Issues associated with the introduction of Urban-ITS
121 Annex D (informative) Standards Framework
D.1 Extant Standards
122 D.2 Legacy systems and Standards
D.2.1 Context
123 D.2.2 Legacy system and standards benefits
D.2.3 Legacy Standards for general use
124 D.2.3.1 XML
125 D.2.3.2 ASN.1
126 D.2.3.3 ISO 14817— Requirements for TICS central data registry and TICS data dictionaries; parts 1,2 & 3
D.2.3.4 ISO TR 12859 Data privacy in ITS Service provision [Technical Report]
127 D.2.3.5 D.2.3.5 ISO 14813-1 ITS services
128 D.2.3.6 ISO 14813-5 Describing Architecture in ITS Standards
D.2.3.7 ISO 14813-6 Use of ASN.1 in ITS Standards
129 D.2.3.8 ISO 17452 Using UML for ITS interfaces
D.2.3.9 ISO 24097 Using Web Services in ITS service provision
131 D.2.3.10 ISO TR 24098 Procedures for developing ITS deployment plans [Technical Report]
D.2.3.11 DISO TR 24529 / ISO 19501 Using UML in ITS Standards [Technical Report]
132 D.2.3.12 D.2.3.12 ISO 24531 Using XML in ITS Standards, Data Registries, and Data Dictionaries
D.2.3.13 ISO TR 24532 Using CORBA in ITS Standards, Data Registries, and Data Dictionaries [Technical Report]
D.2.3.14 ISO TR 25100 User guide for harmonisation of data concepts [Technical Report]
D.2.3.15 ISO TR 25102 ITS Use Case pro-forma Template [Technical Report]
133 D.2.3.16 ISO TR 26999 Using process oriented methodology in ITS standards [Technical Report]
D.2.3.17 ISO TS 17427— Part 2: Framework overview [Technical Report]
D.2.3.18 ISO TS 17427— Part 3: Concept of operations (ConOps) for ‘Core’ systems [Technical Report]
D.2.3.19 ISO TR 17427— Part 4: Minimum system requirements and behaviour for core systems [Technical Report]
134 D.2.3.20 ISO TR 17427— Part 6: Core systems risk assessment methodology [Technical Report]
D.2.3.21 D.2.3.21 ISO TR 17427— Part 7: Privacy aspects [Technical Report]
D.2.3.22 ISO TR 17427— Part 8: Liability aspects [Technical Report]
D.2.3.23 ISO TR 17427— Part 9: Compliance and enforcement aspects [Technical Report]
135 D.2.3.24 ISO TR 17427— Part 10: Driver distraction and information display [Technical Report]
D.2.3.25 EN 12896 Transmodel
136 D.2.3.26 EN 28701 IFOPT
138 D.2.3.27 NeTEx (Network and Timetable Exchange) CEN 16614
139 D.2.3.28 SIRI (Service Interface for Real-time Information) EN 15531
141 D.2.3.29 DATEX/DATEX II
142 D.2.3.30 Relevant UIC rail standards
147 D.2.3.31 Geo-referencing Standards
148 D.2.3.32 Internet Standards
149 D.2.3.33 Organisation based standards and practices
D.2.3.34 Openly plied proprietary standards
D.2.4 Legacy system and standards issues
153 D.2.5 Vendor lock-in
D.2.6 Transition and migration issues
155 D.2.7 Availability of data concepts
156 D.3 C-ITS as a tool to overcome silos
159 D.4 Organisation and interdependencies
162 Annex E (informative)Stakeholders and structuring
E.1 Key stakeholders
E.2 E.2 High level mapping for key identified stakeholders
163 E.3 Overall framework required for interoperability and interchangeability
E.3.1 Interoperability
E.3.2 Interchangeability
E.3.3 Intermodality
164 E.3.4 Multimodality
E.3.5 Sustainability
170 E.4 Systems and devices that could take advantage of common structuring and implementation guidelines
E.4.1 Benefits of a common reference data model/ Meta-data registry
171 E.4.2 Benefits of data exchange profiles
172 E.4.3 Location determination and location referencing
E.4.3.1 Introduction
174 E.4.3.2 The layers of a location referencing system
175 E.4.3.3 What fits where?
E.4.3.4 What exists now?
178 E.4.3.5 Where are the gaps in location referencing?
181 E.4.3.6 Future requirements
E.4.3.7 Location referencing recommendations
E.4.4 Open urban data access portal
E.4.4.1 Availability of the portal
182 E.4.4.2 Accuracy of data available from the urban access data portal
183 E.4.5 Structure of Public Transport Service related data
E.4.5.1 Data categories
186 E.4.5.2 Benefits of a model driven approach
189 E.5 High level generic ‘Concept of Operations’ for city/administration support for Urban-ITS
E.5.1 General
E.5.2 Statement of the goals and objectives of the Urban-ITS
190 E.5.3 Strategies, tactics, policies, and constraints affecting the Urban-ITS
193 E.5.4 Organisations, activities, and interactions among participants and stakeholders for Urban-ITS
194 E.5.5 Clear statement of responsibilities and authorities delegated for Urban-ITS
E.5.6 Equipment required for Urban-ITS
195 E.5.7 Operational processes for the Urban-ITS
197 E.5.8 Role of the jurisdiction in Urban-ITS
198 E.5.9 Role of the Urban-ITS prime service provider
199 E.5.10 Role of the Urban-ITS application service provider
E.5.11 Role of the Urban-ITS user
200 E.5.12 EGeneric characteristics for all instantiations of the Urban-ITS application service domain
E.6 Standards requirements
E.7 Identifying standardisation gaps
201 E.8 The process of consensus
203 Annex F (informative)Panoptic (Multi-category) requirements
F.1 Panoptic (Multi-category) requirements — Objectives, summary and scope addressed
F.1.1 Objectives
F.1.2 Summary
F.1.3 Scope
F.1.4 Stakeholder engagement
F.1.5 Common/Interoperable data
204 F.1.6 Multimodality
F.1.7 Creation of (multimodal) transport datasets
F.1.8 Multiple means of communication
205 F.1.9 Creation of urban-interurban interfaces
206 F.1.10 Use of open standards, architectures and specifications
F.1.11 Enable rather than prescribe or proscribe
F.1.12 Obtaining consistency across the European Community, and across wider domains
209 F.1.13 Objectives of EU-ICIP
211 F.1.14 Organization of an EU-ICIP Guide
212 F.2 Panoptic (Multi-category) requirements — Relevant business/service areas and applications identified with key stakeholders
F.3 Panoptic (Multi-category) requirements — Gap and overlap analysis involving European and international SDOs and their relevant deliverables
F.3.1 Panoptic (Multi-category) requirements — Standards to achieve objectives
F.3.1.1 Use Case ULG-0001 EU-ICIP Use Case
214 F.3.1.2 Use Case ULG-0002 Urban-ITS Interoperable Location Referencing
215 F.3.1.3 Use Case ULG-0003 Urban-ITS Location and Time Determination
216 F.4 Panoptic (Multi-category) requirements — Potential revision of existing standards, new standards development and international harmonisation tasks based on gap/overlap results
F.5 Panoptic (Multi-category) requirements — Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS
F.6 Funding issues
217 Annex G (informative)Multimodal Information Services (MIS)
G.1 MIS Objectives, summary and scope addressed
G.1.1 General
219 G.1.2 Stakeholder engagement
G.1.3 Common/Interoperable data
220 G.1.4 Multimodality
G.1.4.1 Conventional transport modes
G.1.4.2 New alternative transport modes
222 G.1.5 Flexible Transport Services
G.1.6 Creation of (multimodal) transport datasets
223 G.1.7 Multiple means of communication
G.1.8 Creation of urban-interurban interfaces
224 G.1.9 Use of open standards, architectures and specifications
G.1.9.1 Data standards and interoperability
227 G.1.10 Enable rather than prescribe or proscribe
G.2 MIS Relevant business/service areas and applications identified with key stakeholders
G.2.1 MIS Business service area
228 G.2.2 MIS Applications (Use Cases) information layers and data types
G.2.3 MIS Use Cases context
230 G.2.4 MIS Use Cases
G.2.4.1 MIS-0001 MIS Planned Data Retrieval
232 G.2.4.2 MIS-0002 MIS Real-time Data Capture
236 G.2.4.3 MIS-0003 MIS Planned Data Processing
239 G.2.4.4 MIS-0004 MIS Real-time Data Processing
241 G.2.4.5 MIS-0005 MIS Actual Trip Plan Provision
251 G.2.4.6 MIS-0006 MIS Information Structuring
252 G.2.4.7 MIS-0007 MIS Information Dissemination
253 G.2.4.8 MIS-0008 MIS Query Structuring
254 G.2.4.9 MIS-0000 User Support
256 G.3 MIS Gap and overlap analysis involving European and international SDOs and their relevant deliverables
G.3.1 MIS-0001 Gaps- MIS planned data retrieval
257 G.3.2 MIS-0002 Gaps – MIS real-time data capture
G.3.2.1 MIS-0002-1 Gaps – MIS operational raw data provision
G.3.3 MIS-0003 Gaps – MIS planned data processing
258 G.3.3.1 MIS-0003-1 Gaps – MIS scheduled trip plan provision
G.3.3.2 MIS-0003-2 Gaps – MIS planned data updating
G.3.4 MIS-0004 – Gaps – MIS real-time data processing
G.3.4.1 MIS-0004-1 GAPS – MIS real-time data updating
G.3.5 MIS-0005 Gaps – MIS actual trip plan provision
259 G.3.5.1 MIS-0005-1 Gaps – MIS dynamic car-pooling
G.3.5.2 MIS-0005-2 Gaps – MIS driver guidance
260 G.3.6 MIS-0006 Gaps – MIS information structuring
G.3.7 MIS-0007 Gaps – MIS information dissemination
G.3.8 MIS-0008 Gaps – MIS query structuring
G.3.9 MIS-0000 Gaps – user support
G.4 MIS Potential revision of existing standards, new standards development and international harmonisation tasks based on gap/overlap results
G.4.1 MIS planned data retrieval UC-MIS- 0001
261 G.4.2 MIS real-time data capture UC-MIS- 0002
G.4.3 MIS operational raw data provision UC- MIS-0002-1
G.4.4 MIS planned data processing UC-MIS-0003
262 G.4.5 MIS scheduled trip plan provision UC-MIS-0003-1
G.4.6 MIS planned data updating UC-MIS-0003-2
G.4.7 MIS real-time data processing UC-MIS-0004
263 G.4.8 MIS real-time data updating UC-MIS-0004-1
G.4.9 MIS Actual Trip Plan Provision UC-MIS-0005
G.4.10 MIS Dynamic Car-pooling UC- MIS-0005-1
G.4.11 MIS Driver Guidance UC-MIS-0005-2
264 G.4.12 MIS Information Structuring UC-MIS-0006
G.4.13 MIS Information Dissemination UC-MIS-0007
G.4.14 MIS Query Structuring UC-MIS-0008
G.4.15 to topology-related concepts i.e. ‘origin/destination’, a specific location (e.g. stop point), line, etc.;
265 G.4.16 User Support
G.5 MIS Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS
G.6 Funding issues
266 Annex H (informative)Traffic Management (TM)
H.1 TM Objectives, summary and scope addressed
H.1.1 Traffic management: principles and historical evolvement
267 H.1.2 Spheres of activities and problem scenarios
269 H.1.3 Solution strategies and processes
H.2 TM Relevant business/service areas and applications identified with key stakeholders
H.2.1 Impact facilities of Traffic Management
270 H.2.2 TM infrastructure as a toolbox
273 H.2.3 Use Cases as a tool to describe the business in the TM-domain
274 H.2.4 TM process model as a reference model for TM Use Cases
276 H.2.5 TM Use Cases
H.2.5.1 TM Planning and system configuration data retrieval
277 H.2.5.2 TM Real-time Field Data Capture
279 H.2.5.3 TM External System Real Time Data Capture
280 H.2.5.4 TM Planned Data Processing & Subsystem Configuration
281 H.2.5.5 TM Real-time Data Processing
283 H.2.5.6 TM Traffic Condition calculation and Event/Incident detection
284 H.2.5.7 TM Decision and Measure Selection & Structuring
285 H.2.5.8 TM Measure realization
286 H.2.5.9 TM Information dissemination
287 H.2.5.10 TM Procurement and maintenance of Traffic Management infrastructure
289 H.3 TM Gap and overlap analysis involving European and international SDOs and their relevant deliverables
H.3.1 Problems in the TM domain related to the lack of standards
290 H.3.2 Interoperability requirements in the TM-domain
H.3.2.1 Interface requirements
H.3.2.2 Data model requirements
292 H.3.3 Use Case based gap and overlap analysis
H.3.3.1 TM-0001 Gaps – TM planning and system configuration data retrieval
H.3.3.2 TM-0002a Gaps – TM real-time field data capture
H.3.3.3 TM-0002b Gaps – TM external system real time data capture
H.3.3.4 TM-0003 Gaps – TM planned data processing & subsystem configuration
H.3.3.5 TM-0004 Gaps – TM Real-time Data Processing
293 H.3.3.6 TM-0005 Gaps – TM Traffic Condition calculation and Event/Incident detection
H.3.3.7 TM-0006 Gaps – TM decision and measure selection & structuring
H.3.3.8 TM-0007 Gaps – TM measure realization
H.3.3.9 TM-0008 Gaps – TM Information dissemination
H.3.3.10 TM-0009 Gaps – TM procurement and maintenance of traffic management infrastructure
H.4 TM Potential revision of existing standards, new standards development and international harmonisation tasks based on gap/overlap results
H.4.1 Preliminary observation
294 H.4.2 TM Architecture recommendations
H.4.2.1 Background
H.4.3 H.4.3 Traffic management domain specific recommendations
H.4.3.1 Background
H.4.3.2 Recommendations
295 H.5 TM Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS
H.6 TM Funding issues
296 Annex I (informative)Urban Logistics (UL)
I.1.1 General
I.1.2 Stakeholder engagement
297 I.1.3 Common/Interoperable data
I.1.4 Multimodality
I.1.5 Creation of (multimodal) transport datasets
I.1.6 Multiple means of communication
I.1.7 Creation of urban-interurban interfaces
298 I.1.8 Use of open standards, architectures and specifications
I.1.9 Enable rather than prescribe or proscribe
I.2 UL Relevant business/service areas and applications identified with key stakeholders
I.2.1 Urban freight consolidation centres
I.2.1.1 UCC Concept
299 I.2.1.2 Bundled consolidation
I.2.1.3 Bundled relief
I.2.1.4 Advantages and disadvantages of UCC
300 I.2.1.5 Examples of urban consolidation centres
302 I.2.1.6 Success and failure factors
304 I.2.1.7 Urban administration role in UCCs
I.2.1.8 ISO Standards for operating UCC systems
308 I.2.1.9 International Post Corporation Standards
311 I.2.1.10 Conclusions in respect of UCCs
312 I.2.1.11 Full and partially laden trucks
I.2.1.12 Pick-up points and storage facilities
I.2.1.13 Pollution control
I.2.2 UL Business service area
313 I.2.3 UL Applications (Use Cases)
I.2.3.1 UL 0100 Freight movement within the urban domain (Source CID)
330 I.2.3.2 UL-0200 Management of freight vehicles within the urban zone (Source CID)
362 I.2.3.3 UL 0300 Management of vehicle generated pollution within the urban domain (Source CID)
369 I.2.3.4 UL 0400 Loading bays information and reservation services for logistical efficiency (Source CID)
370 I.2.3.5 UL 0500 Loading bays information and reservation services for specific freight vehicles (Source CID)
371 I.2.3.6 UL 0600 Cargo identification (Where relevant to movements inside the urban domain) (Source CID)
372 I.2.3.7 UL 0700 Use of alternatively fuelled vehicles for urban logistics (Source CID) *
I.2.3.8 UL 0800 Charging alternatively fuelled vehicles (Source CID)
373 I.2.3.9 UL 0900 Charging (e.g. during loading/unloading at the specific bays) (Source CID)
374 I.2.3.10 UL 1000 Intelligent parking for light vehicles (Source CID)
380 I.2.3.11 UL 1100 intelligent parking for light commercial vehicles (Source CID)**
381 I.2.3.12 UL 1200 Intelligent parking for heavy goods vehicles (Source CID)**
I.3 UL Existing CEN/TC 278 working groups involved and co/cross working arrangements
382 I.4 UL International/European harmonisation requirements
I.5 UL Gap and overlap analysis involving European and international SDOs and their relevant deliverables
I.5.1 UL–0110v1 Provision of relevant traffic information- congestion; green wave; etc. data
I.5.2 Delivery vehicle realtime mapping/route optimisation
383 I.5.3 Vehicle access management and monitoring
I.5.4 Vehicle Speed Monitoring
I.5.5 Urban Consolidation Centres (UCC)
I.5.6 Oversize Management
384 I.5.7 Emissions monitoring
I.5.8 Low Emission Zones- Data Formats
I.5.9 Cross Border Enforcement
I.5.10 Charging alternatively fuelled vehicles on streets
I.6 UL Potential revision of existing standards,
I.6.1 Weigh in motion
I.6.2 Vehicle parking facilities
385 I.7 UL Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS
386 I.8 UL Funding issues
387 Annex J (informative)Communications and Security (CS) issues for Urban-ITS
J.1 Communications objectives, summary and scope addressed
J.1.1 Stakeholder engagement
J.1.2 Cooperative-ITS and Urban-ITS
389 J.1.3 Common/Interoperable data
392 J.1.4 Multimodality
J.1.5 Creation of (multimodal) transport datasets
J.1.6 Multiple means of communication
J.1.7 Creation of urban-interurban interfaces
393 J.1.8 Use of open standards, architectures and specifications
400 J.2 Hybrid C-ITS communications
401 J.2.1 General
402 J.2.2 Hybrid communications Types
J.2.3 IP for end-to-end communications
403 J.2.4 Non-silo approach of hybrid communications
404 J.2.5 Hybrid communications : example
405 J.2.6 Hybrid Communications – multiple paths
406 J.2.7 Hybrid Communications – Path selection
407 J.2.8 Hybrid Communications – Collect ITS-station capabilities
408 J.2.9 Hybrid Communications – Collect layer information
409 J.2.10 Hybrid Communications – Communication profile selection
410 J.2.11 Hybrid Communications – Flow Transmission
411 J.2.12 Hybrid Communications – Path and Flow management
412 J.2.13 Hybrid Communications – Application layer
J.2.14 Hybrid Communications – Standards
J.3 Security objectives, summary and scope addressed
J.3.1 Introduction
413 J.3.2 C-ITS security
414 J.3.3 EU-US Task Force HTG6
416 J.4 Enable rather than prescribe or proscribe
J.5 Relevant business/service areas and applications identified with key stakeholders
J.6 Other gap and overlap analysis involving European and international SDOs and their relevant deliverables
J.6.1 Business service area(s) (Use Cases)
J.6.2 Other applications
J.6.3 Working groups involved and co/cross working arrangements
417 J.6.4 International/European harmonisation requirements
J.7 Other gap and overlap analysis involving European and international SDOs and their relevant deliverables
J.7.1 Other standards requirements to achieve objectives
J.7.2 Other existing Standards
J.7.3 Other Gap Analysis
418 J.7.4 Other requirement for new Standard(s)
J.8 Funding issues
419 Annex K (informative)Urban-ITS Architecture aspects (UA)
K.1 UA Coherence of Use Cases with FRAME Architecture
K.2 UA Gap analysis between Use Cases and FRAME Architecture
420 K.3 UA Standardisation needs and international harmonisation issues
K.3.1 UA Background
421 K.3.2 UA Standardisation
422 K.3.3 UA Harmonisation
423 K.4 UA Actions required to speed up deployment of Urban-ITS
K.4.1 Enhancing tools to assist ITS deployments
K.4.1.1 Extending FRAME
424 K.4.1.2 Further architecture related assistance for ITS deployment
425 K.4.2 Stakeholder engagement
K.4.3 Common/Interoperable data
K.4.4 Multimodality
K.4.5 Creation of (multimodal) transport datasets
K.4.6 Multiple means of communication
K.4.7 Creation of urban-interurban interfaces
K.4.8 Use of open standards, architectures and specifications
K.4.9 Enable rather than prescribe or proscribe
K.5 UA Identified resources of expertise (individuals, organisations) to participate in this work
426 K.6 UA Consideration of optimum internal organisation to most effectively address these issues
K.7 UA Funding issues
K.8 Requests for support actions
427 Annex L (informative)Other identified issues for Urban-ITS (beyond span of CID)
L.1 Background
L.2 The population is trending to cities
428 L.3 Autonomous/Automated vehicles
L.4 Transmodel, DATEX II and associated standards
430 Annex M (informative)Use Cases Collated
529 Annex N (informative)References
N.1 Standards
539 N.2 Legislation and Regulations
541 Annex O (informative)Principal existing ITS Standards
571 Annex P (informative)Outreach Responses; Outreach contacts, contributors, and effects on Recommendations
P.1 Organisations and individuals consulted during the preparation of the interim and final reports
573 P.2 Organisations and individuals circulated with the Interim Report for comments and prioritisation
574 P.3 Feedback from outreach following circulation of interim report
P.3.1 Overview
577 P.3.2 Outreach feedback in relation to the priority areas identified at the Outreach meeting
P.3.2.1 HLR1- High level recommendation 1: Guide EU-ICIP
578 P.3.2.2 HLR2 Location referencing
580 P.3.2.3 HLR3 – Vendor lock-in/legacy systems and migration paths
582 P.3.2.4 HLR4 Emissions management in urban areas
584 P.3.2.5 HLR5-Data exchange/data management
587 P.3.2.6 HLR6 Elaborate new urban logistics Use Cases
589 P.3.3 Projects recommended, but under the lead of existing initiatives of CEN/TC 278 or other ESOCs.
P.3.4 Outreach feedback to PT1701 recommendations
P.3.4.1 CEN PT1701 recommendations supported by outreach feedback
592 P.3.4.2 CEN PT1701 recommendations that received no support from outreach feedback
595 P.3.4.3 CEN PT1701 recommendations that received negative feedback from outreach
596 P.4 Collated outreach responses to individual recommendations
P.4.1 Standards Policies – Urban-ITS (and general)
601 P.4.2 Panoptic-Across the Board
603 P.4.3 Multimodal Information
607 P.4.4 Traffic Management
610 P.4.5 Urban Logistics
611 P.4.6 Architecture
612 P.4.7 Recommendations for standards deliverables from other CEN Committees/ other ESO’s / recognised standards Issuers
615 P.4.8 Recommendations for other associated support measures and policies
618 P.5 Other Feedback received
624 P.6 Revised High Level Priority Recommendations for CID Support
628 P.7 Revised Recommendations for other ESOs/Committees
631 P.8 Revised priority Recommendations for other support measures
632 P.9 Other supported Recommendations for CID support
P.10 Other Recommendations for CID support (unsupported by outreach feedback)
633 P.11 Recommendations withdrawn as a result of outreach feedback
BSI PD CEN/TR 17143:2017
$215.11