Enterprise Architecture - SESAR WP B

A study has been undertaken in three phases within SESAR Work Package B to examine the use of Enterprise Architecture techniques within the SESAR programme:

  • The first phase, concluded in May 2011, captured and documented the SESAR stakeholder’s and external stakeholder’s requirements for the enterprise architecture.
  • The second phase concluded in August 2011 examines the design of the enterprise architecture framework and the methods needed to develop the enterprise architecture during the Programme.
  • The third phase concluded in December 2011 and as a result, validated the architecture framework and method by applying them to the programme. The findings of the study are used to create a set of communication materials.


Purpose of Enterprise Architecture in SESAR

The study has defined the following needs for the Enterprise Architecture in SESAR:

  • Ensuring consistency within the more than 200 projects of the SESAR Programme by providing a coherent framework to support the development of consistent and interoperable solutions,
  • Providing a framework for the description of the changes in concept and stakeholder capability between steps in the SESAR Concept Story Board,
  • Focussing research on performance.
  • Identifying dependencies and information exchanges between stakeholders with neighbouring capabilities, thus
  • support decision making to optimise investment in research and development during the SESAR development phase to ensure work is focused on the right developments, also supporting identification of duplication and missing work;
  • Supporting communication within the SESAR Programme and with external stakeholders,
  • Supporting the development of business cases for investments described in the ATM Master Plan, and
  • After SESAR Development Phase, the European stakeholder can reuse the EAEA and adapt it to the reality of their local needs and environment in order to optimise the deployment of these concepts and tools to ensure that they improve in a timely manner ATM performance against the targets set by the European Commission.
  • Supporting the development of assurance arguments for presentation to regulators.


The design of the European ATM Enterprise Architecture (EAEA)

The study confirmed the choice of the NATO Architecture Framework (NAF v 3.0) as a suitable enterprise architecture framework for the development of the EAEA. The study also decided to integrate in the EAEA on the SESAR Programme’s existing entities that describe the changes in concept (Operational Focus Areas, Operational Packages and Sub-Packages) and the steps that stakeholders need to take to implement them (Operational Improvement steps (OIs) and Enablers).

Each progressive step represents an increasing level of ability in those responsible for delivering an improvement in performance in air traffic management over the previous step.

Each step in the SESAR Concept Storyboard will have a separate Enterprise Architecture. The changes between the Enterprise Architecture for one step to another being defined by the Operational Focus Areas (OFA) that describe the beneficial changes in the concept. The OFAs group the Operational Improvement steps (OIs) that define the changes in operational concept and the Enablers that define the changes in a stakeholder’s capability configurations or the institutional arrangements necessary to support the architecture.

Through a set of selected NAF sub-views, EAEA will describe the business (performance, goals and capability), operational, technical and technological aspects of the European ATM for each step and their relationships. These sub-views will be populated to drive the work and/or capture the results of the coordination with all the SESAR projects.

The study defined also the relationships of the EAEA and the rest of the SESAR Programme deliverables (documents, requirements, data and service models and ATM Master Plan). This is presented inan explanatory figure and more details can be found here.

The breadth and depth of detail contained within the EAEA is sufficient to satisfy the purpose defined above. The description of the information to be exchanged between stakeholders is used to identify the services exchanged over SWIM.

The EAEA development will follow an iterative approach that is tailored for purpose of each iteration.

In the first deployment phase, work will be concentrated on populating the views that describe and structure the results of the early concept development for each of the SESAR Concept Story Board steps and the planning work that determines the changes.

In the following phase, the remaining detail of the enterprise architecture will be populated as the development phase unfolds. Leading to an Enterprise Architecture developed to E-OVCM Maturity Level 3 for each step in the SESAR Concept Story Board.

Further information

These links provide further information related to WPB: