generic overall architecture for C-ITS
6.1. Guidance for the description of an architecture for a system and its services
7.1.3. Resulting organizational viewpoint – Roles in C-ITS
For the description of the organizational viewpoint finally the results of the Top Down and Bottom Up Approach are merged. Both approaches contribute with valuable aspects and shall be included in the final description of the organizational viewpoint of the Reference Architecture.
Originally, the method described in sections 7.1.2.1 and 7.1.2.2 was developed and first time applied for the standardization of the C-ITS organizational architecture in CEN TC 278 WG 16 DT4 (lead: Teresina Herb). Results (as of July 2013) are documented in ISO 17427 [2013]. A short summary in German on ISO 17427 can be found in Straßenverkehrs-technik [Herb, 2013].
Since the publication of both ISO 17427 and the article in Straßenverkehrstechnik the dis-cussion on ISO 17427 continued and first attempts were undertaken to practically apply the structures described in the standard. Those first experiences resulted in a need for some changes of names, descriptions and structures of roles. Due to the characteristics of the standardization processes, they are not yet published as an update but are already included in the following description of the organizational viewpoint. An update of the ISO 17427 standard is ongoing.
Apart from the roles and responsibilities the organizational viewpoint is supposed to de-scribe strategic goals, objectives as well as the rules and policies applicable in the system (see definition in section 3.3.2.1.3). Those aspects cannot be described abstractly as they are system and implementation dependent. Therefore, they are not covered in this generic Reference Architecture viewpoint description.
7.1.3.1. High level roles in C-ITS
Before focusing on the resulting organizational viewpoint there are some general findings on organizational architectures that can be derived from combining the results of applying the Top Down and Bottom Up Approach (sections 7.1.2.1 and 7.1.2.2):
• roles and responsibilities can be identified and described on different levels of detail
• an implemented system does require different levels of detail for the organizational architecture of different parts of the system – the level of detail is not homogenous across all parts of the system
Referring to those general results the identified roles and responsibilities are structured accordingly. Different levels of abstraction and detail are reflected in the organizational
architecture and a set of high-level roles and corresponding sub-roles are identified and described. On the top level the following roles were determined (see as well Figure 7.1):
• System Operation (from Bottom Up Approach)
• System Management (from Top Down Approach)
• Functional Operation (from Bottom Up Approach)
• Policy Framework (from Top Down Approach)
The four high level roles are in line with the ones described in ISO 17427 and are defined as follows [ISO 17427, 2013]:
Figure 7.1.: High-level roles and their relationships
The role ’System Operation’ is responsible for the proper execution of the applications that provide an end-to-end ITS service. This includes reliability for the coordination, orga-nization and execution of the whole process from initial data collection to the presentation of the final service result. One of the major interfaces of this role is with the actor(s) of the role ’Functional Operation’ who use(s) the system.
The role ’Functional Operation’ is responsible for the proper functional operation of its particular sub-role. To perform an appropriate operation an actor of the role ’Functional Operation’ uses the system provided by actors of the role ’System Operation’.
The role ’System Management’ is responsible to fulfill all required management activities within the system, this especially includes activities supporting ’System Operation’. Ad-ditional actions are the management of the ’Policy Framework’ activities.
The role ’Policy Framework’ is responsible for all governing and institutional activities required in the system.
Usually those four high level roles will not be the roles that will be assigned to real ac-tors in a system, the roles System Operation, Functional Operation, System Management
and Policy Framework require more detailed sub-roles which share the tasks and respon-sibilities originally assigned to the high-level role. The process described in the Top Down and Bottom Up Approach produced the following roles with sub roles:
7.1.3.2. Role: Functional Operation
The role ’Functional operation’ has two different aspects modelled as sub-roles ’Generic functional operation’ and ’Specific functional operation’. Each actor with a role ’Func-tional operation’ has at least one sub-role in ’Generic func’Func-tional operation’ and at least one sub-role in ’Specific functional operation’. The ’Generic functional operation’ reflects the process chain of the corresponding services and the ’Specific functional operation’ reflects the functional sub-role within a specific C-ITS scenario.
Figure 7.2 shows the relation between the sub-roles of the role ’Functional operation’. The core roles of ’Functional Operation’ are the ’Generic functional operation’ sub-roles. The corresponding responsibilities are closely linked to a C-ITS services and were initially derived from the service process. Actors assigned to one of the ’Generic functional op-eration’ sub-roles not solely cover these responsibility, they additionally have a ’Specific functional operation’ sub-role. The dotted white oval in Figure 7.2 shows an example where an actor has the generic sub-role ’Service provider’ and the specific sub-role ’Road-works operator’. Depending on the C-ITS scenario different combinations of the generic and specific functional operation sub-roles exist.
Figure 7.2.: Role ’Functional operation’, its subroles and examples for their relation
The sub-role ’Generic functional operation’ reflects the process chain of the corresponding service. It is composed of the sub-roles ’Content provider’, ’Service provider’ and ’Service recipient’.
• Content Provider
provides various types of content
• Service Provider
identifies which algorithm is suitable to fulfill the end-to-end ITS service, it deter-mines the content that is required to run the ITS service, afterwards runs the ITS service and provides the service result
• Service Recipient
incorporates the triggering of ITS services available within the system. The sub-role Service Recipient has a tight relation to the role System Operation
The sub-role ’Specific functional operation’ reflects the functional sub-role within a spe-cific C-ITS scenario. It is composed of the sub-roles ’Traffic participant’, ’Infrastructure Operator’ and ’Manufacturer’.
• Traffic participant
summarizes traffic participants in a specific C-ITS scenario. (Sub-roles: Driver, Spe-cial vehicle driver)
• Infrastructure Operator
summarizes any infrastructure operator involved in a specific C-ITS scenario. (Sub-roles: Road Operator, Road Works Operator)
• Manufacturer
is responsible for the manufacturing of any products used in a specific C-ITS scena-rio. (Sub-roles: C2X equipment manufacturer, vehicle manufacturer, infrastructure manufacturer)
Details on the mentioned sub-roles are available in the updated but not yet published version of ISO 17427.
7.1.3.3. Role: System Management
System Management is responsible for all management activities in the system. It supports both ’System operation’ and ’Policy framework’. It is a distributed role with multiple entities:
• Service Catalogue Manager
responsible for up-to-date maintaining of the service catalogue that lists all registered ITS services
• C-ITS Architect
maintains the implemented ITS architecture with its architecture viewpoints
• Change Manager
responsible for all change activities including the collection of change requests, han-dling of change requests and application of changes
• Test Manager
ensures that the deployed C-ITS services fulfill their specification
• Service Level Manager
responsible for negotiating the C-ITS service level agreements and ensures that these are met
• Compliance Manager
ensures that standards, guidelines, laws and regulations for C-ITS are followed and applied
• Financial Manager
is optional, depending on the type of ITS service. Responsible for managing budge-ting, accounting and charging in the context of the ITS service.
• Service Owner
responsible for designing and delivering particular C-ITS services within the agreed service levels
• Project Manager
responsible for planning and coordinating the resources to deploy, operate and main-tain C-ITS
• Information Security Manager
ensures the confidentiality, integrity and availability of the system, data, information services and users
7.1.3.4. Role: System Operation
The role ’System operation’ shall be responsible for all activities related to the operation of the system.
• Communication Manager
enables the communication between ITS Stations
• Risk Manager
identifies, assess and controls risks
• Capacity Manager
ensures that C-ITS services and infrastructure are able to deliver the agreed capacity and performance targets
• Availability Manager
defines, analyzes, plans, measures and improves all aspects of availability
• Technical Analyst
provides technical expertise and support for the management of the C-ITS infrastruc-ture
• Configuration Manager
maintains information about infrastructure equipment and hardware required to de-liver C-ITS services
• IT-operations Manager
responsible for the proper operation of the IT-system
• Access Manager
responsible for granting the right to access a C-ITS service to authorized service reci-pients and preventing access of non-authorized service recireci-pients
7.1.3.5. Role: Policy Framework
The role Policy Framework provides the governing and institutional activities in the sys-tem, including necessary policies, regulations, laws and agreements.
• Non-regulatory Policy Institution
definition of non-regulatory policies (e.g. agreements between stakeholders, regula-tions)
• Authority
definition of regulatory policies. (Sub-roles: Legislative, Jurisdiction, Executive)
• Standardization
develops, maintains and provides standards
• Security Certificate Body
issues certificates, keys, pseudonyms to secure C-ITS communication etc.