Process of defining the organizational viewpoint

The general description of the organizational viewpoint in section 3.3.2.1.3 does not pro-vide any blueprint description that only needs to be customized for the Reference Archi-tecture. Therefore, the Top Down Approach and Bottom Up Approach are used again to develop a detailed description of the Reference Architecture organizational viewpoint. As-pects, methods and useful approaches mentioned in section 3.3.2.1 are taken up again and

will be applied in detail in the following paragraphs.

Chapter 6 already concluded that the approaches for deriving an actual Reference Ar-chitecture has almost no implications on the description of the organizational viewpoint.

The resulting roles and responsibilities both in the process oriented and the state transition based approach are almost identical, usually only the scope of the viewpoint description gets broader in the latter case.

Basis for the description of the organizational viewpoint are the functional work flows of services addressed in the respective architecture, hence, the same processes and state machine like in section 7.2 are applied.

7.1.2.1. Top Down Approach

The Top Down Approach identifies suitable high level descriptions of organizational ar-chitectures, selects an appropriate one and customizes this according to the needs and requirements of C-ITS.

The evaluation in section 3.3.2.1 showed that only few organizational architecture models are available that might be consulted as high level blueprint for the C-ITS organizational architecture. The only one that in fact practically supports the high-level description of roles and responsibilities was ITIL v3 developed by the Open Group [ITIL, n.d.]. ITIL v3 provides a large number of roles that cover all phases of software and product develop-ment starting from strategic and design decision to impledevelop-mentation, operation and main-tenance. Its scope thereby is already much broader than a pure service process focused approach. Therefore, the consideration of ITIL resembles the state transition approach (6.1.2).

A first pre-selection and structuring of the ITIL v3 roles was done within the development of the CEN / ISO 17427 standard [ISO 17427, 2013]. The details on the selection and mani-pulation process can be found in Appendix C.

Result of the pre-selection and structuring activity are the following remaining (modified) ITIL roles: Financial Manager, Service Catalogue Manager, Service Level Manager, Ser-vice Owner, Technical Analyst, Risk Manager, Capacity Manager, Availability Manager, IT Operations Manager, Information Security Manager, Compliance Manager, C-ITS Ar-chitect, Change Manager, Project Manager, Configuration Manager, Test Manager, Access Manager and (modified) the Service Recipient.

For the C-ITS characteristics the role of the Communication Manager was added in the description in section 7.1.3. Together with the results of the Bottom Up Approach (section 7.1.2.2) they will form the basis for the organizational viewpoint of the Reference Architec-ture (7.1.3).

7.1.2.2. Bottom Up Approach

The Bottom Up Approach starts from practical examples and implementations describing a system in detail and develops based on that a more abstract and general description. The existing descriptions are mainly based on process oriented procedures.

Main focus of the Bottom Up Approach in this thesis is the operational process of the

se-lected service, therefore, the identified roles are from the field of Functional Operation. A similar analysis is of course possible for other aspects of a system but is not in the scope of this thesis. Details on these facets, which are required for the complete description of the organizational viewpoint, are derived from the Top Down Approach.

The steps of the Bottom Up Approach are accomplished on a set of services which first needs to be identified. Currently, there is no real-world implementation of C-ITS services available. Several research projects developed and implemented different C-ITS services, various initiatives defined lists with so called ’Day 1 services’ which probably will be im-plemented first when deployment of C-ITS starts. Examples are the Day 1 services listed by the Amsterdam Group, by the Car2Car Communication Consortium or European projects like Easyway (details in section 7.2.2). For the development of the organizational view-point with the Bottom Up Approach, services shall be selected in a way that the results are comparable with already finished evaluation activities on ITS architecture structures.

Therefore, the example service selected for the Matrix report [Lotz et al., 2012] is chosen here again: Traffic Information on Hazardous Location.

For the selected service the corresponding actors responsible for certain activities within the service’s workflows are identified and help to develop general roles and responsibili-ties that finally are documented in the C-ITS organizational architecture. A detailed de-scription of the approach can be found in Appendix D. The C-ITS specific functional roles identified through the Bottom Up Approach are Content Provider, Service Provider and Service Recipient.

Besides the analysis of services, the results of three projects are taken into consideration.

The C-ITS project SafeSpot executed a similar approach like the analysis in the Bottom Up Approach, a summary of the results was already presented in section 3.3.2.1.2. The system operation related roles described in SafeSport and those identified through the Bottom Up process cover the same responsibilities and mainly differ in their names.

A detailed stakeholder analysis was carried out by the European Easyway project [Schind-helm et al., 2012]. Therefore, the top-priority services selected within the project were mapped to a general process description like in the Bottom Up Approach described in Ap-pendix D, additionally a set of stakeholder interviews were conducted. Based on those interviews a Strengths Weaknesses Opportunities Threats (SWOT) analysis of potential organizational structures for the individual services were undertaken. The stakeholder analysis did not yet draw any conclusions on preferred scenarios but paved the way for activities on the organizational viewpoint like the standardization in ISO 17427 [2013].

Different aspects addressed in the EASYWAY stakeholder analysis were picked up again for the description of roles and responsibilities in ISO 17427 e.g. the TISA value chain as basis for the analysis of the operational process. The results from the stakeholder analysis gave first ideas on the stakeholders perspective on possible roles – and thereby introduced and reflected the true reality in the discussion about the organizational viewpoint.

And last but not least, the FRAME project developed an extensive list of actors which is published in D15 part 6 [Bossom et al., 2011]. Like suggested in section 3.3.2.1.2 the list of actors was matched against the roles identified by the previously discussed input

sources of the Bottom Up Approach: The FRAME actors mentioned in D15 cover many different aspects of ITS and span a large number of different domains. Most of them can be matched to roles, especially from functional operation, and confirm the results from the other approaches described in this section. Unfortunately, there are as well actors men-tioned which are actually elements of the technical viewpoint, a clear separation did not take place.