An agreed list of day one applications is fundamental to the initial deployment of cooperative ITS. It is understood that Use Cases should cover inter-urban as well as urban environment, probably taking into account different Service Levels
The one derived by the AG on the short list are:
- Simple and non-complex services that provide end user benefit and supported by a solid business model
- A balanced mix of services that support all environments of C-ITS (urban, rural, inter-urban (all V2I2V) and V2V) which can be regarded as minimum set of services for day one
- Services that are feasible with low/minimum risk to avoid a first day bad image hampering further user acceptance
- Services that provide credibility to C-ITS
- Services that support a fast penetration and offer a platform for further deployment of other services
Typical V2V in this respect are
- Hazardous location warning
- Slow vehicle warning
- Traffic Jam ahead warning
- Stationary vehicle warning
- Emergency Brake light
- Emergency vehicle warning
- Motorcycle approaching indication
I2V day one use cases in this respect are
- Road works warning
- In-vehicle signage
- Signal phase and time
- Probe Vehicle Data
Functional specifications and roadmaps towards full deployment for each of the services to be finalized by end 2013 in close cooperation between AG and C2C-CC.
As cooperative systems and services need the collaboration of many stakeholders, it is important to establish an organisational architecture which provides the framework for all activities concerning C-ITS deployment and operation. An organisational architecture forms the basis for agreeing on roles and responsibilities to be performed in the C-ITS context. It allows the mapping of stakeholders who are willing to contribute to C-ITS deployment (actors) with the roles to be performed.
CEN/ISO as one of the standards development organisations has worked on an abstract, technologically agnostic organisational architecture. The related TS 17427 has gone through the national ballot process in June 2013 and is foreseen for publication soon. The roles and responsibilities standard forms also the basis of the “White Papers” developed in close cooperation between the Amsterdam Group and the C2C-CC on the four day one services (see above) with infrastructure involvement.
Figure 4: Top level roles according to organisational architecture (CEN/ISO TS 17427)
The roles and responsibilities standard identifies four top-level roles, namely “Policy Framework”, Service Operation”, “System Management” and “Using the System”. The four top-level roles are detailed by sub-roles. As an example, the policy framework can be subdivided into the role of policy maker and standardization organisation. Obviously, the system management comprises a lot of sub-roles of either strategic or operational nature. Examples include service catalogue manager and compliance manager for the strategic parts as well as security certificate body and service owner for the operational management. The mapping of stakeholders to these uniform roles allows for optimum flexibility against the background of different modes of operation throughout the EU Member States.
Go to Previous Chapter - Go to Next Chapter