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<\/p>\n
multimodal information services;<\/p>\n<\/li>\n
traffic management;<\/p>\n<\/li>\n
urban logistics,<\/p>\n
that are required to support the provision of Urban-ITS.<\/p>\n
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:<\/p>\n
stakeholder engagement;<\/p>\n<\/li>\n
common\/interoperable data;<\/p>\n<\/li>\n
multimodality;<\/p>\n<\/li>\n
creation of (multimodal) transport datasets;<\/p>\n<\/li>\n
multiple means of communication;<\/p>\n<\/li>\n
urban logistics management;<\/p>\n<\/li>\n
creation of urban-interurban interfaces;<\/p>\n<\/li>\n
use of open standards, architectures and specifications;<\/p>\n<\/li>\n
enable rather than prescribe or proscribe.<\/p>\n<\/li>\n<\/ul>\n
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 \u2018New Work Item Proposals\u2019 (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.<\/p>\n
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:<\/p>\n<\/li>\n
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.<\/p>\n<\/li>\n
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.<\/p>\n<\/li>\n
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.<\/p>\n<\/li>\n
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.<\/p>\n
For each of the identified areas, issues to be addressed by the pre-study, as defined by the Terms of Reference, are:<\/p>\n<\/li>\n
Identify key stakeholders;<\/p>\n<\/li>\n
High level mapping for key identified stakeholders for later participation in deliverables specification and development;<\/p>\n<\/li>\n
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);<\/p>\n<\/li>\n
Identifying the systems and devices that could take advantage of common structuring and implementation guidelines;<\/p>\n<\/li>\n
Identifying barriers and constraints to the operation of the open single European market;<\/p>\n<\/li>\n
Identifying transitional and migration issues;<\/p>\n<\/li>\n
Providing a high level generic Concept of Operations for city\/administration support for multimodal travel, traffic management and urban logistic aspects of Urban-ITS;<\/p>\n<\/li>\n
Identifying standards requirements to assist\/guide\/support cities and administrations to provide support for Urban-ITS such as:<\/p>\n
Information level (standards and support measures for defining the meaning of data and messages);<\/p>\n<\/li>\n
Application standards (to define the rules and procedures for exchanging information data);<\/p>\n<\/li>\n
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);<\/p>\n<\/li>\n
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.);<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
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;<\/p>\n<\/li>\n
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.<\/p>\n<\/li>\n<\/ol>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 2 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 3 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 4 Summary of Remit to PT1701 <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 5 Summary of situational factors affecting the study <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 6 Summary of Standards framework <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 7 Summary of Stakeholders and structuring <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 8 Summary of panoptic \u2018across the board\u2019 Requirements <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 9 Summary of communications and security requirements <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 10 Summary of MIS requirements <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 11 Summary of Traffic Management (TM) requirements <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 12 Summary of Urban Logistics (UL) requirements <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 13 Summary of architecture requirements <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | Annex\u00a0A (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 <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | A.1.3 Objectives for Phase 2 outreach <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | A.2 Key issues and summarised recommendations A.2.1 Summarised recommendations <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | A.2.2 Phase 2 outreach <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | A.3 Revised High Level Priority Recommendations for CID Support <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | A.4 Revised Recommendations for other ESOs\/Committees <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | A.5 Revised priority Recommendations for other support measures <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | A.6 Other supported Recommendations for CID support A.7 Other Recommendations for CID support (unsupported by outreach feedback) <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | A.8 Recommendations withdrawn as a result of outreach feedback <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | Annex\u00a0B (informative)Objectives, strategy, philosophy and process of the study B.1 Foreword B.2 Overview B.3 Commission Implementing Decision B.3.1 Overview <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | B.3.2 General requirements for the requested deliverables B.3.3 Requirements to strengthen compatibility and coherence with existing standards and technical specifications <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | B.3.4 Specific requirements for the requested deliverables B.3.5 Multimodal information systems <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | B.3.6 Traffic management, including access regulation B.3.7 Urban logistics, including parking management <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | B.4 Remit to PT1701 <\/td>\n<\/tr>\n | ||||||
| 85<\/td>\n | Annex\u00a0C (informative)Situational Factors affecting the study C.1 Overview <\/td>\n<\/tr>\n | ||||||
| 89<\/td>\n | C.2 Characterising Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | C.3 Stakeholders and actors C.3.1 Stakeholders C.3.1.1 Stakeholders who want Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 98<\/td>\n | C.4 Mixed vendor environment C.4.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | C.4.2 Obligations and expectations of urban public bodies <\/td>\n<\/tr>\n | ||||||
| 103<\/td>\n | C.5 Standards combinations <\/td>\n<\/tr>\n | ||||||
| 105<\/td>\n | C.6 Cooperation C.7 Barriers and constraints to the operation of the open single European market (OSEM) C.7.1 Common issues <\/td>\n<\/tr>\n | ||||||
| 107<\/td>\n | C.7.2 Political obstacles to OSEM C.7.3 Commercial obstacles to OSEM <\/td>\n<\/tr>\n | ||||||
| 108<\/td>\n | C.7.4 Technical obstacles to OSEM <\/td>\n<\/tr>\n | ||||||
| 109<\/td>\n | C.7.5 Contending aspirations of Urban administrations and commercial freight operators C.7.6 Vendor lock-in <\/td>\n<\/tr>\n | ||||||
| 111<\/td>\n | C.8 Autonomous \/automated vehicles C.8.1 Context C.8.2 Autonomous driving and mobility C.8.3 Autonomous driving and connectivity <\/td>\n<\/tr>\n | ||||||
| 112<\/td>\n | C.8.4 Autonomous driving and maps <\/td>\n<\/tr>\n | ||||||
| 114<\/td>\n | C.8.5 Autonomous vehicles and safety issues <\/td>\n<\/tr>\n | ||||||
| 115<\/td>\n | C.8.6 Autonomous vehicles and security C.8.7 Take up of autonomous vehicles <\/td>\n<\/tr>\n | ||||||
| 116<\/td>\n | C.8.8 Autonomous vehicles and associated standardizations <\/td>\n<\/tr>\n | ||||||
| 120<\/td>\n | C.9 Issues associated with the introduction of Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 121<\/td>\n | Annex\u00a0D (informative) Standards Framework D.1 Extant Standards <\/td>\n<\/tr>\n | ||||||
| 122<\/td>\n | D.2 Legacy systems and Standards D.2.1 Context <\/td>\n<\/tr>\n | ||||||
| 123<\/td>\n | D.2.2 Legacy system and standards benefits D.2.3 Legacy Standards for general use <\/td>\n<\/tr>\n | ||||||
| 124<\/td>\n | D.2.3.1 XML <\/td>\n<\/tr>\n | ||||||
| 125<\/td>\n | D.2.3.2 ASN.1 <\/td>\n<\/tr>\n | ||||||
| 126<\/td>\n | D.2.3.3 ISO 14817\u2014 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] <\/td>\n<\/tr>\n | ||||||
| 127<\/td>\n | D.2.3.5 D.2.3.5 ISO 14813-1 ITS services <\/td>\n<\/tr>\n | ||||||
| 128<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 129<\/td>\n | D.2.3.8 ISO 17452 Using UML for ITS interfaces D.2.3.9 ISO 24097 Using Web Services in ITS service provision <\/td>\n<\/tr>\n | ||||||
| 131<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
| 132<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
| 133<\/td>\n | D.2.3.16 ISO TR 26999 Using process oriented methodology in ITS standards [Technical Report] D.2.3.17 ISO TS 17427\u2014 Part 2: Framework overview [Technical Report] D.2.3.18 ISO TS 17427\u2014 Part 3: Concept of operations (ConOps) for \u2018Core\u2019 systems [Technical Report] D.2.3.19 ISO TR 17427\u2014 Part 4: Minimum system requirements and behaviour for core systems [Technical Report] <\/td>\n<\/tr>\n | ||||||
| 134<\/td>\n | D.2.3.20 ISO TR 17427\u2014 Part 6: Core systems risk assessment methodology [Technical Report] D.2.3.21 D.2.3.21 ISO TR 17427\u2014 Part 7: Privacy aspects [Technical Report] D.2.3.22 ISO TR 17427\u2014 Part 8: Liability aspects [Technical Report] D.2.3.23 ISO TR 17427\u2014 Part 9: Compliance and enforcement aspects [Technical Report] <\/td>\n<\/tr>\n | ||||||
| 135<\/td>\n | D.2.3.24 ISO TR 17427\u2014 Part 10: Driver distraction and information display [Technical Report] D.2.3.25 EN 12896 Transmodel <\/td>\n<\/tr>\n | ||||||
| 136<\/td>\n | D.2.3.26 EN 28701 IFOPT <\/td>\n<\/tr>\n | ||||||
| 138<\/td>\n | D.2.3.27 NeTEx (Network and Timetable Exchange) CEN 16614 <\/td>\n<\/tr>\n | ||||||
| 139<\/td>\n | D.2.3.28 SIRI (Service Interface for Real-time Information) EN 15531 <\/td>\n<\/tr>\n | ||||||
| 141<\/td>\n | D.2.3.29 DATEX\/DATEX II <\/td>\n<\/tr>\n | ||||||
| 142<\/td>\n | D.2.3.30 Relevant UIC rail standards <\/td>\n<\/tr>\n | ||||||
| 147<\/td>\n | D.2.3.31 Geo-referencing Standards <\/td>\n<\/tr>\n | ||||||
| 148<\/td>\n | D.2.3.32 Internet Standards <\/td>\n<\/tr>\n | ||||||
| 149<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 153<\/td>\n | D.2.5 Vendor lock-in D.2.6 Transition and migration issues <\/td>\n<\/tr>\n | ||||||
| 155<\/td>\n | D.2.7 Availability of data concepts <\/td>\n<\/tr>\n | ||||||
| 156<\/td>\n | D.3 C-ITS as a tool to overcome silos <\/td>\n<\/tr>\n | ||||||
| 159<\/td>\n | D.4 Organisation and interdependencies <\/td>\n<\/tr>\n | ||||||
| 162<\/td>\n | Annex\u00a0E (informative)Stakeholders and structuring E.1 Key stakeholders E.2 E.2 High level mapping for key identified stakeholders <\/td>\n<\/tr>\n | ||||||
| 163<\/td>\n | E.3 Overall framework required for interoperability and interchangeability E.3.1 Interoperability E.3.2 Interchangeability E.3.3 Intermodality <\/td>\n<\/tr>\n | ||||||
| 164<\/td>\n | E.3.4 Multimodality E.3.5 Sustainability <\/td>\n<\/tr>\n | ||||||
| 170<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 171<\/td>\n | E.4.2 Benefits of data exchange profiles <\/td>\n<\/tr>\n | ||||||
| 172<\/td>\n | E.4.3 Location determination and location referencing E.4.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 174<\/td>\n | E.4.3.2 The layers of a location referencing system <\/td>\n<\/tr>\n | ||||||
| 175<\/td>\n | E.4.3.3 What fits where? E.4.3.4 What exists now? <\/td>\n<\/tr>\n | ||||||
| 178<\/td>\n | E.4.3.5 Where are the gaps in location referencing? <\/td>\n<\/tr>\n | ||||||
| 181<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 182<\/td>\n | E.4.4.2 Accuracy of data available from the urban access data portal <\/td>\n<\/tr>\n | ||||||
| 183<\/td>\n | E.4.5 Structure of Public Transport Service related data E.4.5.1 Data categories <\/td>\n<\/tr>\n | ||||||
| 186<\/td>\n | E.4.5.2 Benefits of a model driven approach <\/td>\n<\/tr>\n | ||||||
| 189<\/td>\n | E.5 High level generic \u2018Concept of Operations\u2019 for city\/administration support for Urban-ITS E.5.1 General E.5.2 Statement of the goals and objectives of the Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 190<\/td>\n | E.5.3 Strategies, tactics, policies, and constraints affecting the Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 193<\/td>\n | E.5.4 Organisations, activities, and interactions among participants and stakeholders for Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 194<\/td>\n | E.5.5 Clear statement of responsibilities and authorities delegated for Urban-ITS E.5.6 Equipment required for Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 195<\/td>\n | E.5.7 Operational processes for the Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 197<\/td>\n | E.5.8 Role of the jurisdiction in Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 198<\/td>\n | E.5.9 Role of the Urban-ITS prime service provider <\/td>\n<\/tr>\n | ||||||
| 199<\/td>\n | E.5.10 Role of the Urban-ITS application service provider E.5.11 Role of the Urban-ITS user <\/td>\n<\/tr>\n | ||||||
| 200<\/td>\n | E.5.12 EGeneric characteristics for all instantiations of the Urban-ITS application service domain E.6 Standards requirements E.7 Identifying standardisation gaps <\/td>\n<\/tr>\n | ||||||
| 201<\/td>\n | E.8 The process of consensus <\/td>\n<\/tr>\n | ||||||
| 203<\/td>\n | Annex\u00a0F (informative)Panoptic (Multi-category) requirements F.1 Panoptic (Multi-category) requirements \u2014 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 <\/td>\n<\/tr>\n | ||||||
| 204<\/td>\n | F.1.6 Multimodality F.1.7 Creation of (multimodal) transport datasets F.1.8 Multiple means of communication <\/td>\n<\/tr>\n | ||||||
| 205<\/td>\n | F.1.9 Creation of urban-interurban interfaces <\/td>\n<\/tr>\n | ||||||
| 206<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 209<\/td>\n | F.1.13 Objectives of EU-ICIP <\/td>\n<\/tr>\n | ||||||
| 211<\/td>\n | F.1.14 Organization of an EU-ICIP Guide <\/td>\n<\/tr>\n | ||||||
| 212<\/td>\n | F.2 Panoptic (Multi-category) requirements \u2014 Relevant business\/service areas and applications identified with key stakeholders F.3 Panoptic (Multi-category) requirements \u2014 Gap and overlap analysis involving European and international SDOs and their relevant deliverables F.3.1 Panoptic (Multi-category) requirements \u2014 Standards to achieve objectives F.3.1.1 Use Case ULG-0001 EU-ICIP Use Case <\/td>\n<\/tr>\n | ||||||
| 214<\/td>\n | F.3.1.2 Use Case ULG-0002 Urban-ITS Interoperable Location Referencing <\/td>\n<\/tr>\n | ||||||
| 215<\/td>\n | F.3.1.3 Use Case ULG-0003 Urban-ITS Location and Time Determination <\/td>\n<\/tr>\n | ||||||
| 216<\/td>\n | F.4 Panoptic (Multi-category) requirements \u2014 Potential revision of existing standards, new standards development and international harmonisation tasks based on gap\/overlap results F.5 Panoptic (Multi-category) requirements \u2014 Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS F.6 Funding issues <\/td>\n<\/tr>\n | ||||||
| 217<\/td>\n | Annex\u00a0G (informative)Multimodal Information Services (MIS) G.1 MIS Objectives, summary and scope addressed G.1.1 General <\/td>\n<\/tr>\n | ||||||
| 219<\/td>\n | G.1.2 Stakeholder engagement G.1.3 Common\/Interoperable data <\/td>\n<\/tr>\n | ||||||
| 220<\/td>\n | G.1.4 Multimodality G.1.4.1 Conventional transport modes G.1.4.2 New alternative transport modes <\/td>\n<\/tr>\n | ||||||
| 222<\/td>\n | G.1.5 Flexible Transport Services G.1.6 Creation of (multimodal) transport datasets <\/td>\n<\/tr>\n | ||||||
| 223<\/td>\n | G.1.7 Multiple means of communication G.1.8 Creation of urban-interurban interfaces <\/td>\n<\/tr>\n | ||||||
| 224<\/td>\n | G.1.9 Use of open standards, architectures and specifications G.1.9.1 Data standards and interoperability <\/td>\n<\/tr>\n | ||||||
| 227<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 228<\/td>\n | G.2.2 MIS Applications (Use Cases) information layers and data types G.2.3 MIS Use Cases context <\/td>\n<\/tr>\n | ||||||
| 230<\/td>\n | G.2.4 MIS Use Cases G.2.4.1 MIS-0001 MIS Planned Data Retrieval <\/td>\n<\/tr>\n | ||||||
| 232<\/td>\n | G.2.4.2 MIS-0002 MIS Real-time Data Capture <\/td>\n<\/tr>\n | ||||||
| 236<\/td>\n | G.2.4.3 MIS-0003 MIS Planned Data Processing <\/td>\n<\/tr>\n | ||||||
| 239<\/td>\n | G.2.4.4 MIS-0004 MIS Real-time Data Processing <\/td>\n<\/tr>\n | ||||||
| 241<\/td>\n | G.2.4.5 MIS-0005 MIS Actual Trip Plan Provision <\/td>\n<\/tr>\n | ||||||
| 251<\/td>\n | G.2.4.6 MIS-0006 MIS Information Structuring <\/td>\n<\/tr>\n | ||||||
| 252<\/td>\n | G.2.4.7 MIS-0007 MIS Information Dissemination <\/td>\n<\/tr>\n | ||||||
| 253<\/td>\n | G.2.4.8 MIS-0008 MIS Query Structuring <\/td>\n<\/tr>\n | ||||||
| 254<\/td>\n | G.2.4.9 MIS-0000 User Support <\/td>\n<\/tr>\n | ||||||
| 256<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 257<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 258<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 259<\/td>\n | G.3.5.1 MIS-0005-1 Gaps – MIS dynamic car-pooling G.3.5.2 MIS-0005-2 Gaps – MIS driver guidance <\/td>\n<\/tr>\n | ||||||
| 260<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 261<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 262<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 263<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 264<\/td>\n | 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. \u2018origin\/destination\u2019, a specific location (e.g. stop point), line, etc.; <\/td>\n<\/tr>\n | ||||||
| 265<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 266<\/td>\n | Annex\u00a0H (informative)Traffic Management (TM) H.1 TM Objectives, summary and scope addressed H.1.1 Traffic management: principles and historical evolvement <\/td>\n<\/tr>\n | ||||||
| 267<\/td>\n | H.1.2 Spheres of activities and problem scenarios <\/td>\n<\/tr>\n | ||||||
| 269<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 270<\/td>\n | H.2.2 TM infrastructure as a toolbox <\/td>\n<\/tr>\n | ||||||
| 273<\/td>\n | H.2.3 Use Cases as a tool to describe the business in the TM-domain <\/td>\n<\/tr>\n | ||||||
| 274<\/td>\n | H.2.4 TM process model as a reference model for TM Use Cases <\/td>\n<\/tr>\n | ||||||
| 276<\/td>\n | H.2.5 TM Use Cases H.2.5.1 TM Planning and system configuration data retrieval <\/td>\n<\/tr>\n | ||||||
| 277<\/td>\n | H.2.5.2 TM Real-time Field Data Capture <\/td>\n<\/tr>\n | ||||||
| 279<\/td>\n | H.2.5.3 TM External System Real Time Data Capture <\/td>\n<\/tr>\n | ||||||
| 280<\/td>\n | H.2.5.4 TM Planned Data Processing & Subsystem Configuration <\/td>\n<\/tr>\n | ||||||
| 281<\/td>\n | H.2.5.5 TM Real-time Data Processing <\/td>\n<\/tr>\n | ||||||
| 283<\/td>\n | H.2.5.6 TM Traffic Condition calculation and Event\/Incident detection <\/td>\n<\/tr>\n | ||||||
| 284<\/td>\n | H.2.5.7 TM Decision and Measure Selection & Structuring <\/td>\n<\/tr>\n | ||||||
| 285<\/td>\n | H.2.5.8 TM Measure realization <\/td>\n<\/tr>\n | ||||||
| 286<\/td>\n | H.2.5.9 TM Information dissemination <\/td>\n<\/tr>\n | ||||||
| 287<\/td>\n | H.2.5.10 TM Procurement and maintenance of Traffic Management infrastructure <\/td>\n<\/tr>\n | ||||||
| 289<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 290<\/td>\n | H.3.2 Interoperability requirements in the TM-domain H.3.2.1 Interface requirements H.3.2.2 Data model requirements <\/td>\n<\/tr>\n | ||||||
| 292<\/td>\n | H.3.3 Use Case based gap and overlap analysis H.3.3.1 TM-0001 Gaps \u2013 TM planning and system configuration data retrieval H.3.3.2 TM-0002a Gaps \u2013 TM real-time field data capture H.3.3.3 TM-0002b Gaps \u2013 TM external system real time data capture H.3.3.4 TM-0003 Gaps \u2013 TM planned data processing & subsystem configuration H.3.3.5 TM-0004 Gaps \u2013 TM Real-time Data Processing <\/td>\n<\/tr>\n | ||||||
| 293<\/td>\n | H.3.3.6 TM-0005 Gaps \u2013 TM Traffic Condition calculation and Event\/Incident detection H.3.3.7 TM-0006 Gaps \u2013 TM decision and measure selection & structuring H.3.3.8 TM-0007 Gaps \u2013 TM measure realization H.3.3.9 TM-0008 Gaps \u2013 TM Information dissemination H.3.3.10 TM-0009 Gaps \u2013 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 <\/td>\n<\/tr>\n | ||||||
| 294<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 295<\/td>\n | H.5 TM Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS H.6 TM Funding issues <\/td>\n<\/tr>\n | ||||||
| 296<\/td>\n | Annex\u00a0I (informative)Urban Logistics (UL) I.1.1 General I.1.2 Stakeholder engagement <\/td>\n<\/tr>\n | ||||||
| 297<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 298<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 299<\/td>\n | I.2.1.2 Bundled consolidation I.2.1.3 Bundled relief I.2.1.4 Advantages and disadvantages of UCC <\/td>\n<\/tr>\n | ||||||
| 300<\/td>\n | I.2.1.5 Examples of urban consolidation centres <\/td>\n<\/tr>\n | ||||||
| 302<\/td>\n | I.2.1.6 Success and failure factors <\/td>\n<\/tr>\n | ||||||
| 304<\/td>\n | I.2.1.7 Urban administration role in UCCs I.2.1.8 ISO Standards for operating UCC systems <\/td>\n<\/tr>\n | ||||||
| 308<\/td>\n | I.2.1.9 International Post Corporation Standards <\/td>\n<\/tr>\n | ||||||
| 311<\/td>\n | I.2.1.10 Conclusions in respect of UCCs <\/td>\n<\/tr>\n | ||||||
| 312<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 313<\/td>\n | I.2.3 UL Applications (Use Cases) I.2.3.1 UL 0100 Freight movement within the urban domain (Source CID) <\/td>\n<\/tr>\n | ||||||
| 330<\/td>\n | I.2.3.2 UL-0200 Management of freight vehicles within the urban zone (Source CID) <\/td>\n<\/tr>\n | ||||||
| 362<\/td>\n | I.2.3.3 UL 0300 Management of vehicle generated pollution within the urban domain (Source CID) <\/td>\n<\/tr>\n | ||||||
| 369<\/td>\n | I.2.3.4 UL 0400 Loading bays information and reservation services for logistical efficiency (Source CID) <\/td>\n<\/tr>\n | ||||||
| 370<\/td>\n | I.2.3.5 UL 0500 Loading bays information and reservation services for specific freight vehicles (Source CID) <\/td>\n<\/tr>\n | ||||||
| 371<\/td>\n | I.2.3.6 UL 0600 Cargo identification (Where relevant to movements inside the urban domain) (Source CID) <\/td>\n<\/tr>\n | ||||||
| 372<\/td>\n | 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) <\/td>\n<\/tr>\n | ||||||
| 373<\/td>\n | I.2.3.9 UL 0900 Charging (e.g. during loading\/unloading at the specific bays) (Source CID) <\/td>\n<\/tr>\n | ||||||
| 374<\/td>\n | I.2.3.10 UL 1000 Intelligent parking for light vehicles (Source CID) <\/td>\n<\/tr>\n | ||||||
| 380<\/td>\n | I.2.3.11 UL 1100 intelligent parking for light commercial vehicles (Source CID)** <\/td>\n<\/tr>\n | ||||||
| 381<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 382<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 383<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 384<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 385<\/td>\n | I.7 UL Roadmap with targeted deliverables and concrete actions to speed up deployment of Urban-ITS <\/td>\n<\/tr>\n | ||||||
| 386<\/td>\n | I.8 UL Funding issues <\/td>\n<\/tr>\n | ||||||
| 387<\/td>\n | Annex\u00a0J (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 <\/td>\n<\/tr>\n | ||||||
| 389<\/td>\n | J.1.3 Common\/Interoperable data <\/td>\n<\/tr>\n | ||||||
| 392<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 393<\/td>\n | J.1.8 Use of open standards, architectures and specifications <\/td>\n<\/tr>\n | ||||||
| 400<\/td>\n | J.2 Hybrid C-ITS communications <\/td>\n<\/tr>\n | ||||||
| 401<\/td>\n | J.2.1 General <\/td>\n<\/tr>\n | ||||||
| 402<\/td>\n | J.2.2 Hybrid communications Types J.2.3 IP for end-to-end communications <\/td>\n<\/tr>\n | ||||||
| 403<\/td>\n | J.2.4 Non-silo approach of hybrid communications <\/td>\n<\/tr>\n | ||||||
| 404<\/td>\n | J.2.5 Hybrid communications : example <\/td>\n<\/tr>\n | ||||||
| 405<\/td>\n | J.2.6 Hybrid Communications \u2013 multiple paths <\/td>\n<\/tr>\n | ||||||
| 406<\/td>\n | J.2.7 Hybrid Communications \u2013 Path selection <\/td>\n<\/tr>\n | ||||||
| 407<\/td>\n | J.2.8 Hybrid Communications \u2013 Collect ITS-station capabilities <\/td>\n<\/tr>\n | ||||||
| 408<\/td>\n | J.2.9 Hybrid Communications \u2013 Collect layer information <\/td>\n<\/tr>\n | ||||||
| 409<\/td>\n | J.2.10 Hybrid Communications \u2013 Communication profile selection <\/td>\n<\/tr>\n | ||||||
| 410<\/td>\n | J.2.11 Hybrid Communications \u2013 Flow Transmission <\/td>\n<\/tr>\n | ||||||
| 411<\/td>\n | J.2.12 Hybrid Communications \u2013 Path and Flow management <\/td>\n<\/tr>\n | ||||||
| 412<\/td>\n | J.2.13 Hybrid Communications \u2013 Application layer J.2.14 Hybrid Communications \u2013 Standards J.3 Security objectives, summary and scope addressed J.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 413<\/td>\n | J.3.2 C-ITS security <\/td>\n<\/tr>\n | ||||||
| 414<\/td>\n | J.3.3 EU-US Task Force HTG6 <\/td>\n<\/tr>\n | ||||||
| 416<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 417<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 418<\/td>\n | J.7.4 Other requirement for new Standard(s) J.8 Funding issues <\/td>\n<\/tr>\n | ||||||
| 419<\/td>\n | Annex\u00a0K (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 <\/td>\n<\/tr>\n | ||||||
| 420<\/td>\n | K.3 UA Standardisation needs and international harmonisation issues K.3.1 UA Background <\/td>\n<\/tr>\n | ||||||
| 421<\/td>\n | K.3.2 UA Standardisation <\/td>\n<\/tr>\n | ||||||
| 422<\/td>\n | K.3.3 UA Harmonisation <\/td>\n<\/tr>\n | ||||||
| 423<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 424<\/td>\n | K.4.1.2 Further architecture related assistance for ITS deployment <\/td>\n<\/tr>\n | ||||||
| 425<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 426<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 427<\/td>\n | Annex\u00a0L (informative)Other identified issues for Urban-ITS (beyond span of CID) L.1 Background L.2 The population is trending to cities <\/td>\n<\/tr>\n | ||||||
| 428<\/td>\n | L.3 Autonomous\/Automated vehicles L.4 Transmodel, DATEX II and associated standards <\/td>\n<\/tr>\n | ||||||
| 430<\/td>\n | Annex\u00a0M (informative)Use Cases Collated <\/td>\n<\/tr>\n | ||||||
| 529<\/td>\n | Annex\u00a0N (informative)References N.1 Standards <\/td>\n<\/tr>\n | ||||||
| 539<\/td>\n | N.2 Legislation and Regulations <\/td>\n<\/tr>\n | ||||||
| 541<\/td>\n | Annex\u00a0O (informative)Principal existing ITS Standards <\/td>\n<\/tr>\n | ||||||
| 571<\/td>\n | Annex\u00a0P (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 <\/td>\n<\/tr>\n | ||||||
| 573<\/td>\n | P.2 Organisations and individuals circulated with the Interim Report for comments and prioritisation <\/td>\n<\/tr>\n | ||||||
| 574<\/td>\n | P.3 Feedback from outreach following circulation of interim report P.3.1 Overview <\/td>\n<\/tr>\n | ||||||
| 577<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 578<\/td>\n | P.3.2.2 HLR2 Location referencing <\/td>\n<\/tr>\n | ||||||
| 580<\/td>\n | P.3.2.3 HLR3 \u2013 Vendor lock-in\/legacy systems and migration paths <\/td>\n<\/tr>\n | ||||||
| 582<\/td>\n | P.3.2.4 HLR4 Emissions management in urban areas <\/td>\n<\/tr>\n | ||||||
| 584<\/td>\n | P.3.2.5 HLR5-Data exchange\/data management <\/td>\n<\/tr>\n | ||||||
| 587<\/td>\n | P.3.2.6 HLR6 Elaborate new urban logistics Use Cases <\/td>\n<\/tr>\n | ||||||
| 589<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 592<\/td>\n | P.3.4.2 CEN PT1701 recommendations that received no support from outreach feedback <\/td>\n<\/tr>\n | ||||||
| 595<\/td>\n | P.3.4.3 CEN PT1701 recommendations that received negative feedback from outreach <\/td>\n<\/tr>\n | ||||||
| 596<\/td>\n | P.4 Collated outreach responses to individual recommendations P.4.1 Standards Policies – Urban-ITS (and general) <\/td>\n<\/tr>\n | ||||||
| 601<\/td>\n | P.4.2 Panoptic-Across the Board <\/td>\n<\/tr>\n | ||||||
| 603<\/td>\n | P.4.3 Multimodal Information <\/td>\n<\/tr>\n | ||||||
| 607<\/td>\n | P.4.4 Traffic Management <\/td>\n<\/tr>\n | ||||||
| 610<\/td>\n | P.4.5 Urban Logistics <\/td>\n<\/tr>\n | ||||||
| 611<\/td>\n | P.4.6 Architecture <\/td>\n<\/tr>\n | ||||||
| 612<\/td>\n | P.4.7 Recommendations for standards deliverables from other CEN Committees\/ other ESO\u2019s \/ recognised standards Issuers <\/td>\n<\/tr>\n | ||||||
| 615<\/td>\n | P.4.8 Recommendations for other associated support measures and policies <\/td>\n<\/tr>\n | ||||||
| 618<\/td>\n | P.5 Other Feedback received <\/td>\n<\/tr>\n | ||||||
| 624<\/td>\n | P.6 Revised High Level Priority Recommendations for CID Support <\/td>\n<\/tr>\n | ||||||
| 628<\/td>\n | P.7 Revised Recommendations for other ESOs\/Committees <\/td>\n<\/tr>\n | ||||||
| 631<\/td>\n | P.8 Revised priority Recommendations for other support measures <\/td>\n<\/tr>\n | ||||||
| 632<\/td>\n | P.9 Other supported Recommendations for CID support P.10 Other Recommendations for CID support (unsupported by outreach feedback) <\/td>\n<\/tr>\n | ||||||
| 633<\/td>\n | P.11 Recommendations withdrawn as a result of outreach feedback <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Standards and actions necessary to enable urban infrastructure coordination to support Urban-ITS<\/b><\/p>\n |