ENAV EUROCONTROL FREQUENTIS INDRA

Transcription

1 Final Project Report Document information Project Title Options on High Level Architecture Project Number B Project Manager NATS Deliverable Name Final Project Report Deliverable ID D01 Edition Template Version Task contributors. NATS- Leader ENAIRE DFS DSNA ENAV EUROCONTROL FREQUENTIS INDRA NORACON LEONARDO THALES Abstract The project developed the Foundation Method for the identification, design and validation of Common Services for SESAR and validated the method by designing the Remote Tower and Extended AMAN (E-AMAN) Common services.

2 Authoring & Approval Prepared By - Authors of the document. Name & Company Position & Title Date Tony Vaudrey NATS Project Leader 08/09/2016 Sujan Perera NATS Contributor 08/09/2016 Reviewed By - Reviewers internal to the project. Name & Company Position & Title Date Tony Vaudrey NATS Project Leader 09/09/2016 Fausto Bruni Leonardo Contributor 09/09/2016 Claus Scheuren DFS Contributor 09/09/2016 Siggi Schaefer DFS Contributor 09/09/2016 Fredy Pietrus DSNA Contributor 09/09/2016 Christine Salles DSNA Contributor 09/09/2016 Markus Klopf Frequentis Contributor 09/09/2016 Marc Brochard Eurocontrol Contributor 09/09/2016 Philippe Naves Eurocontrol Contributor 09/09/2016 Alberto Anguita Indra Contributor 09/09/2016 Jun Chen Xu Indra Contributor 09/09/2016 Roman Nossal Noracon Contributor 09/09/2016 Lars Helleblad Noracon Contributor 09/09/2016 Andres Grijalba ENAIRE Contributor 09/09/2016 Generoso Paolillo Leonardo Contributor 09/09/2016 Richard Beaulieu Thales Contributor 09/09/2016 Hugh Rodrick Thales Contributor 09/09/2016 Vincenzo Zampognaro ENAV Contributor 09/09/2016 Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations. Name & Company Position & Title Date Morten Grandt DFS WP B Manager 09/09/2016 Approved for submission to the SJU By - Representatives of the company involved in the project. Name & Company Position & Title Date Fausto Bruni Leonardo Contributor 09/09/2016 Claus Scheuren DFS Contributor 09/09/2016 Siggi Schaefer DFS Contributor 09/09/2016 Fredy Pietrus DSNA Contributor 09/09/2016 Christine Salles DSNA Contributor 09/09/2016 Markus Klopf Frequentis Contributor 09/09/2016 Marc Brochard Eurocontrol Contributor 09/09/2016 Philippe Naves Eurocontrol Contributor 09/09/2016 Alberto Anguita Indra Contributor 09/09/2016 Jun Chen Xu Indra Contributor 09/09/ of 10

3 Roman Nossal Noracon Contributor 09/09/2016 Lars Helleblad Noracon Contributor 09/09/2016 Andres Grijalba ENAIRE Contributor 09/09/2016 Generoso Paolillo Leonardo Contributor 09/09/2016 Richard Beaulieu Thales Contributor 09/09/2016 Hugh Rodrick Thales Contributor 09/09/2016 Vincenzo Zampognaro ENAV Contributor 09/09/2016 Rejected By - Representatives of the company involved in the project. Name & Company Position & Title Date <Name / Company> <Position / Title> <DD/MM/YYYY> Rational for rejection None. Document History Edition Date Status Author Justification /04/2016 Draft Tony Vaudrey Revised Template /05/16 Draft Sujan Perera /05/2016 Draft Sujan Perera /05/2016 Draft Sujan Perera /05/2016 Issue Sujan Perera /07/2016 Draft Sujan Perera /07/2016 Issue Sujan Perera /09/2016 Issue Sujan Perera Intellectual Property Rights (foreground) This deliverable consists of SJU foreground. Update following B4.5 member comment. Update to deliverables list to include Remote Tower documentation. Update following additional comments. Issue (note final delivery to SJU due July 2016) Update following comment and inclusion of final deliverables. Update to new template, addition of references, list of services not progressed to completion and minor comment update. Update following SJU comment and minor typo errors. 3 of 10

4 Acronyms Acronym AMAN ANSP ATM BI EATMA FAB HLA SESAR SDM SJU SWIM WP Definition Arrival Manager Air Navigation Service Provider Air Traffic Management Business Improvement European Air Traffic Management Architecture Functional Airspace Block High Level Architecture Single European Sky ATM Research Programme Service Delivery Management SESAR Joint Undertaking System-Wide Information Management Work Package 4 of 10

5 1 Project Overview The purpose of WP B was to develop and validate a foundation method to identify opportunities for the provision of common air navigation services or their related functions in the context of SESAR, and subsequently to examine the strategies for delivery, high level business and technical architecture options for deployment 1.1 Project progress and contribution to the Master Plan The provision of Air Traffic Management in Europe is highly fragmented with many different organisations operating in the region. It is thus a general principle within the Single European Sky and the SESAR programme that where possible, services should be provided in a harmonized way to enable a simpler and more efficient supply. Therefore, in the context of the European ATM Master Plan and the SESAR programme R&D activities, the high level definition of the future ATM system architecture needs to address the different options of local, non-local, regional/fab or centralised implementation of services and operations. In this context the term common services describes those services that are used by several stakeholders and provided on their behalf by one organisation or several in a similar manner. The provision of common services will therefore be examined in the context of local, non-local, regional, FAB and centralised models. Benefit will only be derived if the design of the new services significantly improves the overall performance of ATM or reduces the cost of its provision, driven by scale and competition. These services are not necessarily provided and consumed locally, nor needed at a pan- European level and may only be applicable to a specific region. It is therefore important when identifying candidate services to understand the best context for their delivery and to design a business operations model that is proportionate to scale of the need. The project performed a proof of concept study and developed a foundation method for identifying, assessing and designing common services. The method considers the architectural, business and regulatory perspectives, stakeholder priorities, focussing on the objectives and benefits of improved efficiencies in European ATM. The project intended to validate the method by applying it to six prioritised candidate services [5]: - Remote Towers - Extended AMAN (originally Delay Sharing) - SWIM Common Components - Global Surveillance - Sub-regional DCB - Data Centre (originally Virtual Centre) The first exercise, developing the Remote Towers service, resulted in a number of improvements to the method. A further three services were then considered, before selecting Extended AMAN - in preference to SWIM Common Components and Data Centre for Virtual Centres - to be examined in more detail to provide final improvements within B4.5. The Common Service for the provision of Extended AMAN is now described in EATMA [16]. The foundation method thus provides a robust process for the handling of Common Services in SESAR Project achievements The project established a foundation method for the discovery, identification and design of Common Services. The method provides a means for describing the business model for a common service using the Business Model Canvas and a high level architecture within the European ATM Architecture (EATMA) as an alternative option to the existing architecture. This later work required close co- 5 of 10

6 operation with B04.01 (European ATM Enterprise Architecture: Performance and Business) and B04.03 (Technical System Architecture) as introducing the concept of a common services extended the use of services in SESAR. To that point, services were only considered in the context of SWIM, hence necessitating an enhancement of the architecture framework. The work resulted in a more comprehensive description of services in the EATMA, taking into account the business and operational dimensions. This work will provide a basis for future work in SESAR 2020, in particular the operation of Project PJ.19- Content Integration and PJ.15- Common Services. A significant number of candidate common services were identified within the Candidate Services document [5]. These represent a good starting point for further SESAR activity. Of the high priority candidates (see section 1.1), the Remote Towers and Extended AMAN services were developed to validate the Common Services Foundation. The resulting products, though not intended to be SESAR solutions, provide the ground work for later work to provide a more robust design and implementation of each of them. Of the high priority services, which were not developed further in B4.5: - Sub-Regional Demand Capacity Balancing and Data Centres are due to be developed further in SESAR 2020 (PJ.15 - Common Services) - SWIM Common Components and Global Surveillance remain candidates for future SESAR activity. 1.3 Project Deliverables The following table presents the relevant deliverables that have been produced by the project. Reference Title Description D03 Service Candidates Document This document captures the identification of candidate Common Services, the service description, the subsequent assessment and scoring and the final selection of six short-listed services for further processing. Service identification was performed by expert brainstorming, while the description and assessment of services was based on the Service description and attribute template created by Task 002 of B The ranking and selection of services applied the portfolio analysis technique combined with expert judgement. D05 Business Model Services Part B - Extended AMAN This document describes the Business Model Extended AMAN Common service. D06 High Level Technical Architecture Service Part B - Extended AMAN This document describes the High Level Architectures and changes to the content of EATMA for the Extended AMAN Common service. D07 Action Plan Service Part B- Extended AMAN This document describes the Action Plan for the Extended AMAN Common service so providing guidance to the SJU and Stakeholders on the steps necessary to implement it D14 Service Candidates Report Project B04.05 developed a method for identify such opportunities in SESAR and tested it by designing a common service for the provision of ATS to an aerodrome from a Remote Tower. This paper describes the conclusions of the exercise and makes recommendations to improve the method. 6 of 10

7 D15 Common Services Foundation Method Update This document provides an updated method for designing Common Services business models and for modelling Common Services in the European Air Traffic Management Architecture (EATMA) based in the lessons learned from B activities. D16 D17 D18 Business Model for the Remote Tower Common Service High Level Technical Architecture Service Action Plan for the Remote Tower Common Service This document considers one of the operational concepts in SESAR, the Remote Provision of ATS for an Aerodrome and proposes through the description of a business model how the adoption of a common service in this instance could benefit Aerodromes and the wider community. This document provides a partial high level architecture of the Remote Tower Common Service. The objective is to illustrate the process to be applied in defining the HLA of a common service by using a concrete example. This document describes the Action Plan for the Remote Tower Common Service so providing guidance to the SJU and Stakeholders on the steps necessary for implementation D19 Report on the Preparation for transition and hand-over 2020 This document identifies the issues recommended for consideration in SESAR 2020 as a result of B4.5 Common Services activities Common Services considered by B4.5 but which were not developed to formal deliverables were: - Global Surveillance - Sub-Regional Demand Capacity Balancing - SWIM Common Components - Data Centre. 1.4 Contribution to Standardisation The project identified possible services that could be subject to standardisation once the business benefits for the ATM community have been successfully validated. For example the use of a standardised service for the interface between a Remote Tower Facility and a remote Tower Centre opens up the possibility for the competitive selection of the ANSP- thus driving down the cost of provision. The lack of a standard would encourage supplier lock-in and thus reduce the benefit. 1.5 Project Conclusion and Recommendations The Common Services Foundation Method [5] - which is to be the basis of SESAR 2020 PJ15 (Common Services) activity - provides a robust process for the discovery, identification and design of a Common Service, including the development of business model and high level architecture. The project also provides the business models and high level architectural descriptions for two Common Services that will be further developed during SESAR The project has developed the process of expressing Business Improvement (BI) as a Service Delivery Management (SDM) Operational Improvements step. 7 of 10

8 The project's development of the Common Services for Remote Towers and EAMAN provided architecture descriptions for these two areas that identified and captured issues in associated process documents or action plans. Worthy of note however is that while both concepts were mature (validated at EOVCM level V3) in the programme, it was a change to the current operational roles and responsibilities which drove the Common Services direction. For EAMAN in particular - it was considered that operational accountability precluded operational outsourcing - resulting in a potentially significant costing saving being excluded from consideration. Further operational development would therefore be necessary to validate the separation of the roles involved to realise the benefits. For the Remote Tower, the benefits were focussed on the airport as the consumer of the service, rather than the provider, the ANSP, in the original project. This change impacted on the design of the remote tower, particularly the need for an open, standard service for the interface between the remote tower facility and the remote tower centre. The main benefit resulting from the Remote Tower Common Service is the availability of affordable ATS at an aerodrome, leading to market changes and the potential expansion of the network. The Common Services approach is an important contribution to the reduction in cost of European ATM. Currently, they are only considered as an alternative rather than the primary deployment architecture. While this may change with the cost benefit analyses produced by SESAR 2020 PJ15 (Common Services), this project recommends that when solutions are developed by projects in SESAR during the V2 phase - that they apply the Foundation Method to identify capabilities that could be common to stakeholder groups. These capabilities can then be considered during the content integration phase as candidate Common Services for future development in the programme and validation during V3. Finally, this project also recommends candidate services identified by this project, but not developed in detail during SESAR 1 should be considered for further development in SESAR of 10

9 2 References [1] SESAR Programme Management Plan, Edition [2] European ATM Master Plan [3] Multilateral Framework Agreement ( MFA ) signed between the SJU, EUROCONTROL and its 15 selected members on August 11, 2009, amended on 14 June 2010, 19 October 2010 and 2 July 2012 [4] Options on High Level Architecture, Common Services Foundation - Definition, delivered as "Options of Common Services", D02, Edition , Date: 08/08/2014 [5] Options on High Level Architecture, Service Candidates Document, D03, , 12/04/2015 [6] Options on High Level Architecture, Common Services Foundation - Method, D04, Edition , Date: 16/07/2015 [7] Options on High Level Architecture, Business Model Services Part B - Extended AMAN, D05, Edition , Date: 27/07/2016 [8] Options on High Level Architecture, High Level Technical Architecture Service Part B - Extended AMAN, D06, Edition , Date: 12/07/2016. [9] Options on High Level Architecture, Action Plan Service Part B- Extended AMAN, D07, Edition , Date: [10] Options on High Level Architecture, Service Candidates Report, D14, Edition , Date 02/06/2016. [11] Options on High Level Architecture, Common Services Foundation Method Update, D15, Edition , Date: 13/07/2016 [12] Options on High Level Architecture, Common Service, Business Model for the Remote Tower Common Service, D16 (D05 on front cover), Date: 13/07/2015. [13] Options on High Level Architecture, High Level Technical Architecture Service, D17, Edition , Date: 12/07/2016 [14] Options on High Level Architecture, Action Plan for the Remote Tower Common Service, D18, , Date: 26/05/2016 [15] Options on High Level Architecture, Report on the Preparation for transition and hand-over 2020, D19, Edition , Date: 21/07/2016 [16] EATMA Version of 10

10 -END OF DOCUMENT- 10 of 10