BSI PD CEN/TR 17401:2020
$198.66
Intelligent transport systems. Urban-ITS. Mixed vendor environment guide
Published By | Publication Date | Number of Pages |
BSI | 2020 | 52 |
This document provides a “Concept of Operations (CONOPS) for the introduction and maintenance of a “Mixed Vendor Environment” (MVE) in the domain of urban-ITS. Structured as:
-
PART I Context and issues to be addressed
-
Describes the context, background, objective of the MVE Guide, and describes the architectural context.
-
-
PART II work concepts
-
Aspects of system design and architecture are examined and the basic knowledge required for the application of Part III are presented.
-
-
PART III Practice
-
Provides system design and procurement on three levels against the background of a procedure model.
-
user level;
-
conceptual explanation;
-
examples.
-
-
-
PART IV Outlook
-
Guidance and requirements for the application of MVE for future business.
-
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
8 | 1 Scope 2 Normative references 3 Terms and definitions |
10 | 4 Symbols and abbreviations |
11 | 5 Part I: Context and issues to be addressed 5.1 Background |
13 | 5.2 Objective of MVE Guide |
14 | 5.3 Approach of the MVE Guide 5.4 Target audience of the MVE Guide |
15 | 5.5 Mixed vendor environments in Urban ITS 5.6 The ‘setting’: MVE challenges and vendor lock-in |
16 | 5.7 History of MVE frameworks 5.8 Principles of co-existence of regional standard solutions for TMS |
18 | 5.9 MVE contexts |
19 | 5.10 MVE challenges: integration and interoperability 5.11 System evolution |
20 | 5.12 MVE requirements: functional integration |
21 | 5.13 MVE requirements: the operator perspective |
22 | 6 MVE architectures 6.1 Architectural overview 6.2 Cooperating traffic management systems |
23 | 6.3 Architecture of roadside systems |
24 | 6.4 Interoperability requirements in the ‘Traffic Management’ domain 7 Existing open specifications 7.1 DATEX II |
25 | 7.2 SNMP |
26 | 7.3 Distributed C-ITS via a secured ITS domain 7.3.1 C-ITS Station |
28 | 7.3.2 ISO/ETSI references for C-ITS |
31 | 8 Part II: Work Concepts 8.1 The application of the MVE Guide 8.1.1 The starter pack of basic knowledge 8.1.2 Subsystem realization and a mixed vendor environment |
32 | 9 Key MVE interfaces for traffic control and management 9.1 Introduction |
33 | 9.2 Principal subsystems for traffic management and their communications requirements 9.2.1 Active Traffic Management (ATM) 9.2.2 Arterial road management 9.2.3 Control zone management/UVAR |
34 | 9.2.4 Dynamic message sign monitoring and control 9.2.5 Incident monitoring 9.2.6 Parking management |
35 | 9.2.7 Ramp meter monitoring and control 9.2.8 Real-time passenger information |
36 | 9.2.9 Real-time traffic monitoring |
37 | 9.2.10 Rising bollards and barrier control 9.2.11 Road Weather Information System monitoring 9.2.12 Speed limit: Variable speed limits 9.2.13 Traffic camera monitoring and control |
38 | 9.2.14 Traffic signal monitoring and control 9.2.15 Traffic optimization 9.2.16 Urban Traffic Management and Control 9.2.17 Variable-message sign |
39 | 10 Key MVE interfaces for public transport 10.1 Introduction 10.2 Existing open specifications 10.2.1 Transmodel (Public Transport) |
40 | 10.2.2 SIRI (Public Transport) |
41 | 10.2.3 NeTEx (Public Transport) |
42 | 11 Mixed vendor environment scenarios 11.1 Introduction 11.2 Scenario 1: Manufacturer mix at field level |
43 | 11.3 Scenario 2: Collation of data from multiple authorities/operators |
44 | 11.4 Scenario 3: Data sharing service |
45 | 12 Part III: Practice (Course of action) 13 PART IV Outlook: Guidance and requirements for the application of MVE for future business 13.1 Trends for urban ITS |
46 | 13.2 Distributed C-ITS via a secured ITS domain |
48 | Annex A (informative)General principles of project planning and management |