This document focuses on the principal aspects of urban ITS where vendor lock-in is recognized as a technical and financial problem: primarily centre-to-field communications and traffic management systems. It will cover the following scope:<\/p>\n
approaches to the management of MVEs by urban authorities, including mitigation and migration options;<\/p>\n<\/li>\n
procedural and operational protocols to achieve interworking, using product\/interface adaptation, translation products, replacement\/reengineering, and other migration strategies;<\/p>\n<\/li>\n
technical options for interworking multiple vendors’ products;<\/p>\n<\/li>\n
mechanisms to enable interoperability through automated translation between specifications, frameworks and product interfaces;<\/p>\n<\/li>\n
review of principal approaches taken to date to implement these options in community frameworks and specifications.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 5.1 General <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 5.2 Interfaces between systems 5.2.1 Introduction 5.2.2 Interfaces with other system owners <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 5.2.3 Interfaces between procurements by a systems owner <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 5.2.4 Interfaces within a single procurement 5.3 Legacy and migration issues 5.3.1 General 5.3.2 Adaptation <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5.3.3 Translation 5.3.4 Migration 6.1 Design methodologies 6.1.1 System design and system architecture <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 6.1.2 Systems, subsystems and interfaces <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 6.2 Public procurement constraints <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.3 Communications 6.3.1 Communications options <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.3.2 Communications approach in an MVE <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 7.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 7.2 Specifications 7.3 Location of functional processing <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 7.4 Data storage and caching <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 7.5 Data models: concepts, definitions and units <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.6 Upper layer protocol adaptors 7.7 Communications network translation <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.8 Information security <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Annex A (informative)Approach of DVM Exchange\/IVERA to interoperability A.1 Introduction A.1.1 DVM-Exchange A.1.2 IVERA A.2 General architectural approach of DVM-Exchange <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | A.3 General architectural approach of IVERA <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | A.4 Procurement issues and impact A.5 Management and governance <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | A.6 Example DVM Exchange\/IVERA implementation: Deventer <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Annex B (informative)Approach of OCIT to interoperability B.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | B.2 General architectural approach B.3 Procurement issues and impact <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | B.4 Management B.5 Example OCIT implementation B.5.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | B.5.2 ITS Example City B.5.3 Advantages and disadvantages B.5.3.1 Advantages <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | B.5.3.2 Disadvantages <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | Annex C (informative)Approach of UTMC to interoperability C.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | C.2 General architectural approach C.2.1 Architectural principles of UTMC C.2.2 The UTMC Level model <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | C.2.3 The UTMC Nodes model <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | C.3 Procurement issues and impact <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | C.4 Management C.5 Example UTMC implementation: Reading C.5.1 Introduction C.5.2 Reading’s ITS <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | C.5.3 Benefits <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | Annex D (informative)Approach of RSMP to interoperability D.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | D.2 General architectural approach of RSMP D.2.1 Object model D.2.2 Sequence diagram and data exchange <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | D.3 Procurement issues and impact <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | D.4 Management and governance <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Urban ITS. Mixed vendor environments, methodologies & translators<\/b><\/p>\n |