This project concerns different aspects of supporting mixed vendor environments in urban-ITS. The work is very intertwined, and although work is quite advanced (approaching 200 pages of specifications), it is still under development. It is expected to circulate working drafts during January 2019. It will provide a suite of standards deliverables designed to achieve successful implementation of urban-ITS systems in a mixed vendor environment.
This suite of standards deliverables will support the family of existent standards, and those under development, referencing both common communications protocols and data definitions, that, in combinations, enable Urban-ITS (and ITS in general) to function and be managed, and will reference application standards, and their interdependencies and relationships.
Urban authorities use an increasing array of intelligent transport systems (ITS) to deliver their services. Historically, urban ITS have tended to be single solutions provided to a clear requirements specification by a single supplier. Increasingly, as ITS opportunities become more complex and varied. They involve the integration of multiple products from different vendors, procured at different times and integrated by the urban authority.
The need for a mixture of systems provided by different manufacturers to so-called Mixed Vendor Environments (MVEs) is a growing paradigm, which results primarily from the demand for the introduction of competition in the context of public tenders, and the increasing networking of existing stand-alone solutions to address complex traffic management systems.
The mix of systems of different manufacturers is also, in part, a result from technological change. Established companies are suddenly in competition with new companies that exploit technological changes and offer exclusively, or at a reasonable price, new or improved functionality for sub systems.
However, ITS design is often proprietary and, as a consequence, integration and interoperability can be difficult, time-consuming, and expensive, limiting the ability of urban authorities to deploy innovative solutions to transport problems. In some Member States, national/regional solutions to this problem have been created, and there are also some solutions in specific domains, which have been very beneficial. However, these are not uniform across Europe, compromising the efficiency of the single market.
The project has three objectives:
This project will result in three deliverables.The following scopes remain indicative and not final, and there may be some variation in the final versions of these scopes:
This standard 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.
PART IV Outlook
Guidance and requirements for the application of MVE for future business.
I have moved this whole text to the start of what is now titled “Context and issues to be addressed”. The reason for this is that in CEN documents the Scope contains only a summary list of what is addressed in the document, and possibly state its limitations.
This standard provides a background to the relevance of standards concerning mixed vendor environments in the context of urban-ITS. It describes key mixed vendor environments interfaces.
It describes openly plied proprietary standards and extant communications protocols that can be used in mixed vendor environments in the context of urban-ITS.
This standard focuses on the principal aspects of urban ITS where vendor lock-in is recognised as a technical and financial problem: primarily centre-to-field communications and traffic management systems. It will cover the following scope: