11.01.03-D26 Final Project Report - sesarju.eu · enhanced FOC and WOC functions, which have been derived from the operational requirements, ... FOC-DM Functional Block FOC Data Management

Final Project Report

Document information

Project Title System Specification and Architecture

Project Number 11.01.03

Project Manager Lufthansa Systems

Deliverable Name Final Project Report

Deliverable ID D26

Edition 00.01.00

Template Version 03.00.04

Task contributors

Lufthansa Systems, Sabre Airline Solutions, Honeywell, Airbus Defence and Space, Airbus .

Abstract

Project P11.01.03 designed the technical architecture of the systems supporting the operations of the civil and state airspace users. P11.01.03 breaks down these systems in Functional Blocks, where the flight operation of the civil Airspace Users and the military airspace users were considered. Project P11.01.03 developed in addition the Step 1 and Step 2 system requirements for enhanced FOC and WOC functions, which have been derived from the operational requirements, provided by P11.01.02 in its ODED document. The elaborated requirements were defined to support the software prototypes produced in P11.01.04 that allowed the validation of the operational concepts and requirements defined by P11.01.02. The traceability between the system requirements and the operational ones is a key element of the technical specification from P11.01.03. The specification from P11.01.03 may be used by Flight Planning Service Providers for the adaptation of their FOC and WOC systems and it can also be used by Airlines for the further development of their flight planning tools.

Project Number 11.01.03 Edition 00.01.001 D26- Final Project Report

2 of 25

©SESAR JOINT UNDERTAKING, 2015. Created by Lufthansa Systems for the SESAR Joint Undertaking within the frame of the SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly acknowledged

Authoring & Approval

Prepared By - Authors of the document.

Name & Company Position & Title Date

Urban Weißhaar / Lufthansa Systems P11.01.03 / Project Leader 26/08/2016

Reviewed By - Reviewers internal to the project.


Olaf Belzer / Sabre Airline Solutions WP11.1.4 Project Manager 15/09/2016

Matej Papp / Honeywell WP11.1 Project Member 08/09/2016

Klaus-Dieter Herrmann / Airbus DS WP11.1 Project Member 15/09/2016

Daniel Chiesa, Airbus WP11.1 / Work Package Leader

16/09/2016

Marcus Hantschke / Lufthansa Systems Senior Research Engineer SESAR / WP11.1 Project Member

15/09/2016

Thomas Eschenhagen / Lufthansa Systems P11.01.03 Architect / Senior Architect SESAR

29/08/2016

Max Hoffmann / Lufthansa Systems Research Engineer SESAR / WP11.1 Project Member

29/08/2016

Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations.


Marc Brochard / Euroconrol B.04.03 Project Leader 15/09/2016

Radosveta Borisova / Euroconrol WP B.04.03 Member 15/09/2016

Juliette Engel / Euroconrol WP B.04.03 Member 15/09/2016

Mehtap Karaarslan / Euroconrol WP7.6.4/13.2.3 Expert 15/09/2016

Nadine Pilon / Euroconrol OFA05.03.07 / UDPP OFA Coordinator

09/09/2016

Marie-José Ribera/ Euroconrol P07.06.02 Project Member 15/09/2016

Gérard MAVOIAN Euroconrol P07.06.02 Project Manager 15/09/2016

Philippe LEPLAE / Euroconrol P07.06.02 Project Manager 15/09/2016

Jacqueline Coquel / Air France Airspace User Expert 15/09/2016

Russel Olivier / HOP! Airspace User Expert 15/09/2016

Jim Pettitt / British Airways Airspace User Expert 15/09/2016

Yamit Hahn / El Al Airspace User Expert 15/09/2016

Gerd Mattes / Lufthansa Airspace User Expert 15/09/2016

Mikael Diaz / Airbus B.04.03 Member 05/09/2016

Siegfried Schäfer / DFS B.04.03 Member 15/09/2016

Martina Stehlikova/ Honeywell SESAR Program Manager 08/09/2016

Michael Ebenhoch/ Airbus DS P11.1.3 Expert 30/08/2016

Approved for submission to the SJU By - Representatives of the company involved in the project.


Urban Weisshaar / Lufthansa Systems P11.01.03 / Project Leader <8/09/2016

Rejected By - Representatives of the company involved in the project.



3 of 25


<Name / Company> <Position / Title> <DD/MM/YYYY>

Rational for rejection

None.

Document History

Edition Date Status Author Justification

00.00.01 26/08/2016 Draft Urban Weißhaar Initial version

00.00.02 30/08/2016 Draft Urban Weißhaar Internal review feedback included

00.00.03 27/09/2016 Draft Urban Weißhaar External review feedback included

00.01.00 28/09/2016 Final Urban Weißhaar Version for the upload

Intellectual Property Rights (foreground)

This deliverable consists of SJU foreground.


4 of 25


Acronyms

Acronym Definition

4D Four Dimensional

A/G Air-Ground

A/C Aircraft

A-CDM Airport Collaborative Decision Making

ADD Architecture of technical systems Description Document

ATM Air Traffic Management

AFUA Advanced Flexible Use of Airspace

AIM Aeronautical Information Management

AIP Aeronautical Information Publication

AIRM Aeronautical Information Reference Model

AIS Aeronautical Information Services

AIXM Aeronautical Information Exchange Model

ANSP Air Navigation Service Provider

AO Aircraft Operator

APOC Airport Operations Centre

ATCO Air Traffic Controller

ATM Air Traffic Management

AU Airspace User

BMT Business/Mission Trajectory

B2B Business to Business (B2B)

BT Business Trajectory

CDM Collaborative Decision Making

CONOPS CONcept of OPerationS

CTA Controlled Time of Arrival

DCB Demand Capacity Balancing


5 of 25


D-NOTAM Digital NOTAM

DMA Dynamic Mobile Area

DOD Detailed Operational Description

EATMA European ATM Architecture

EFB Electronic Flight Bag

EFPL Extended Flight Plan

ENB Enabler

EPP Extended Projected Profile

ETA Estimated Time of Arrival

FAB Functional Airspace Block

FB Functional Block

FF-ICE Flight and Flow Information in a Collaborative Environment

FIXM Flight Information eXchange Model

FL Flight Level

FMS Flight Management System

FOC Flight Operations Centre

FOC-FM Functional Block FOC Flight Management

FOC-OM Functional Block FOC Operations Management

FOC-DSM Functional Block FOC Decision Support Management

FOC-DM Functional Block FOC Data Management

FOC-CM Functional Block FOC Communication Management

FOC-FDM Functional Block FOC Flight Deck Management

FPL Flight Plan

I4D Initial 4D

ICAO International Civil Aviation Organization

ICAO FIXM ICAO flight plan in FIXM format

IER Information Exchange Requirements

IFPS Initial Flight Plan Processing System


6 of 25


INTEROP Interoperability Requirements

IRS Interface Requirements Specification

IRSM Information Service Reference Model

NM Network Manager

NOP Network Operations Plan

OFA Operational Focus Area

OFP Operational Flight Plan

OR Operational Requirements

OSED Operational Service and Environment Definition

SCG Service Coordination Group

SJU SESAR Joint Undertaking (Agency of the European Commission)

SOA Service Oriented Architecture

STG SESAR System Thread Guidance document

SPR Safety and Performance Requirements

SWIM System Wide Information Management

TAD Technical Architecture Description

TR Technical Requirements

TS Technical Specification

UDPP User Driven Prioritisation Process

VALP Validation Plan

VALR Validation Report

WOC Wing Operations Centre

WP Work Package

WXXM Weather Information Exchange Model

XML Extensible Markup Language


7 of 25


1 Project Overview

P11.01.03 developed the technical architecture of the systems supporting the operations of the civil and military Airspace Users. The designed FOC and WOC architecture breaks down these systems in Functional Blocks and describes the evolution reached at the end of SESAR 1. For each system it is depicted how its Functional Blocks are related to each other. P11.01.03 contains a depiction of the context of these systems within the European ATM System. The FOC and WOC architecture is coordinated with the architecture in the European ATM Architecture (EATMA). The architecture of the FOC builds the base for the future evolvement of the relation between Airspace User systems and the systems of the other ATM stakeholders in SESAR 2020.

The purpose of project P11.01.03 was also to provide the technical specification and interface requirements (TS/IRS) for the FOC functions. Project P11.01.03 is describing the adaptation and developments of technical means supporting the 4D business trajectory management. P11.01.03 was responsible for the design of the FOC and WOC system, from business objectives to systems requirements, fully compliant with the SESAR performance target, but was also responsible to ensure that the design of FOC system meets stakeholder needs and that system elements are developed accordingly. Project P11.01.03 includes the translation of the operational and business requirements for an FOC and WOC from P11.01.02 into system requirements and specifications for the FOC and WOC.

1.1 Project progress and contribution to the Master Plan

P11.01.03 aimed from the beginning to translate the operational and business requirements for the FOC/WOC derived from P11.01.01 and P11.01.02 into system requirements and specifications for the FOC/WOC. All requirements, scenarios and use cases of the developed technical specification are therefore in accordance with the operational scenarios and requirements described in the FOC and WOC OSED and have been designed taking into account the description of the Technical Architecture in the WP11.01 FOC and WOC TAD. The TAD for the FOC itself covers not only the FOC system, but also all systems of the Civil AU Operation centre. The requirements from P11.01.03 have been developed to support the software prototypes produced in P11.01.04 that allowed the validation of the operational concepts and requirements defined by P11.01.02. For all requirements and traces, Dataset 16 has been used as the reference in the Technical specification. From the beginning, it was the objective, that the technical specification defines the reference for system requirements of the FOC and WOC as a blue print for the development of future FOC and WOC systems. Therefore the specification should be used by Flight Planning Service Providers and airlines for the development of their enhanced FOC tools.

The technical approach for P11.01.03 combined from the beginning well-known international best practices in system and software engineering in order to stepwise elaborate the operational views and the system logical and technical architecture. This included developing requirements iteratively and managing the requirements and their changes. Furthermore, the identification of system and technical actors, roles and responsibilities were examined.

P11.01.03 itself was supporting B04.03 over the whole project period for the System-, Service- and Information- architecture. In this role, P11.01.03 participated in many meetings and workshops with SESAR Projects and Airspace Users to align the development of content in the System, Service and Information architecture and the integrated roadmap. The main synchronisation was performed with the Architecture Description Document (ADD), the Information Service reference Model (ISRM) and the ATM Information reference Model (AIRM). Dedicated support to the ATM Masterplan was given to have consistent definition of the enablers and OI steps during the lifecycle of the corresponding Data Sets.

P11.01.03 itself was not developing any software prototype; this work was performed within project P11.01.04. Furthermore, all validation activities from WP11.01 were performed under the umbrella of P11.01.05. Therefore, in below following table only the enablers are listed, for which TS requirements


8 of 25


have been identified. The identification of the processed OI steps is under the responsibility of P11.01.02. Furthermore the maturity level of the enablers is not defined, as this was part of P11.01.04; at the same time the maturity level for OI steps is not listed, as this is part of P11.01.05.

Enablers considered within P11.01.03

Enablers used in this document are with reference to the Integrated Roadmap Dataset 16.

Code Name Project contribution Maturity at project start

Maturity at project end

AOC-ATM-11 Integration of constraints and answers

Link of TS requirement within D24:

REQ-11.01.03-TS-S1TS.1005

REQ-11.01.03-TS-S2TS.1005

REQ-11.01.03-TS-S2TS.1010

REQ-11.01.03-TS-S1NR.1010

REQ-11.01.03-TS-S1EF.1005

REQ-11.01.03-TS-S1EF.1010

REQ-11.01.03-TS-S1EF.1015

REQ-11.01.03-TS-S1EF.1020

REQ-11.01.03-TS-S1EF.1025

REQ-11.01.03-TS-S1EF.1030

REQ-11.01.03-TS-S1EF.1035

REQ-11.01.03-TS-S1EF.1040

REQ-11.01.03-TS-S1NR.1015

REQ-11.01.03-TS-S1EF.1045

REQ-11.01.03-TS-S1EF.1050

REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S1NR.3010

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1TS.4005

REQ-11.01.03-TS-S1EF.1055

REQ-11.01.03-TS-S1EF.5005

REQ-11.01.03-TS-S1EF.5010

REQ-11.01.03-TS-S1EF.1060

REQ-11.01.03-TS-S1NR.3015

V-level / TRL tbd. by

P11.01.04

P11.01.05 as these projects were developing the prototypes and performing the validation exercises.

PRO-096 Airline Operational Procedures for modifying SBT including agreed TTA to accommodate selected priorities


REQ-11.01.03-TS-S1TS.1005

REQ-11.01.03-TS-S2TS.1005

REQ-11.01.03-TS-S2TS.1010

tbd. by

P11.01.04

P11.01.05 as these projects were developing the


9 of 25


prototypes and performing the validation exercises.

AOC-ATM-10 Modification of AOC/WOC-ATM trajectory management system (or new systems) to allow quality of service requested by NOP for pre-flight trajectory with dynamic routing


REQ-11.01.03-TS-S1FR.1005

REQ-11.01.03-TS-S1NR.1005

REQ-11.01.03-TS-S1FR.1010

REQ-11.01.03-TS-S1NR.1015

REQ-11.01.03-TS-S1FR.4005

REQ-11.01.03-TS-S1FR.4010

REQ-11.01.03-TS-S1FR.4015

REQ-11.01.03-TS-S1FR.4020

REQ-11.01.03-TS-S1FR.4025

REQ-11.01.03-TS-S1FR.4030

REQ-11.01.03-TS-S1FR.1015

tbd. by

P11.01.04


AOC-ATM-13 Participating of the FOC/ WOC in the airport triggered CDM process


REQ-11.01.03-TS-S2NR.1005

REQ-11.01.03-TS-S1EF.1035

REQ-11.01.03-TS-S1TS.4005

REQ-11.01.03-TS-S1AF.4005

REQ-11.01.03-TS-S1NR.3015

tbd. by

P11.01.04


SWIM-APS-05b Provision and Consumption of Flight Object Sharing services for Step 2


REQ-11.01.03-TS-S2NR.1005

tbd. by

P11.01.04


FOC-006 FOC flight lifecycle monitoring and

Link of TS requirement within D24: tbd. by


10 of 25


situational awareness capabilities

REQ-11.01.03-TS-S2NR.1005

REQ-11.01.03-TS-S2NR.1010

REQ-11.01.03-TS-S1NR.1020

REQ-11.01.03-TS-S2BT.1005

P11.01.04


FOC-008 Processing of ADD information for flight monitoring purposes


REQ-11.01.03-TS-S2NR.1005

REQ-11.01.03-TS-S2NR.1010

REQ-11.01.03-TS-S1FR.1010

REQ-11.01.03-TS-S1AF.1005

REQ-11.01.03-TS-S1NR.1020

REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S1NR.3010

REQ-11.01.03-TS-S2BT.1005

tbd. by

P11.01.04


PRO-249 Procedures Linked to Collaborative Flight Planning in Step 2


REQ-11.01.03-TS-S2NR.1010

REQ-11.01.03-TS-S1NR.1010

REQ-11.01.03-TS-S1TS.1010

REQ-11.01.03-TS-S1TS.1015

REQ-11.01.03-TS-S1TS.1020

REQ-11.01.03-TS-S1TS.1025

REQ-11.01.03-TS-S1NR.1015

REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S1NR.3010

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1NR.3015

tbd. by

P11.01.04


FOC-002 Assessment of real time ASM data


REQ-11.01.03-TS-S1AF.1005

REQ-11.01.03-TS-S1NR.1020

tbd. by

P11.01.04

P11.01.05 as these projects were developing the prototypes and


11 of 25


performing the validation exercises.

PRO-248 Collaborative Procedures for improving Airport Operations in Adverse Conditions in Step 2


REQ-11.01.03-TS-S1NR.1010

tbd. by

P11.01.04


FOC-009 Improved trajectory planning through consideration of ground operation milestones and actual taxi time.


REQ-11.01.03-TS-S1NR.1010

REQ-11.01.03-TS-S1NR.1015

tbd. by

P11.01.04


AOC-ATM-13 Participating of the FOC/ WOC in the airport triggered CDM process


REQ-11.01.03-TS-S1TS.1010

REQ-11.01.03-TS-S1TS.1015

REQ-11.01.03-TS-S1TS.1020

REQ-11.01.03-TS-S1TS.1025

REQ-11.01.03-TS-S1TS.4010

REQ-11.01.03-TS-S1BT.1005

tbd. by

P11.01.04


AOC-ATM-20 Sharing of trajectory data between AOC/WOC and the ATM world using B2B web services


REQ-11.01.03-TS-S1EF.1005

REQ-11.01.03-TS-S1EF.1010

REQ-11.01.03-TS-S1EF.1020

tbd. by

P11.01.04

P11.01.05 as these projects were


12 of 25


REQ-11.01.03-TS-S1EF.1040

REQ-11.01.03-TS-S1BT.1005

REQ-11.01.03-TS-S1BT.1010

developing the prototypes and performing the validation exercises.

SWIM-APS-04a Consumption of ATFCM Information Services for Step 1


REQ-11.01.03-TS-S1EF.1035

REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1TS.4005

tbd. by

P11.01.04


SWIM-APS-04b Consumption of ATFCM Information Services for Step 2


REQ-11.01.03-TS-S1EF.1035

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1TS.4005

tbd. by

P11.01.04


AIMS-07 Generation of pre-flight briefing information


REQ-11.01.03-TS-S1HT.1005

REQ-11.01.03-TS-S1HT.1010

REQ-11.01.03-TS-S1TS.1030

REQ-11.01.03-TS-S1HT.4005

REQ-11.01.03-TS-S1HT.4010

REQ-11.01.03-TS-S1NR.4005

REQ-11.01.03-TS-S1HT.5010

tbd. by

P11.01.04


AIMS-07a Generation of Enhanced Pre-flight Briefing based on

Link of TS requirement within D24: tbd. by


13 of 25


digital data REQ-11.01.03-TS-S1HT.1005

REQ-11.01.03-TS-S1TS.1030

REQ-11.01.03-TS-S1HT.1010

REQ-11.01.03-TS-S1HT.4005

REQ-11.01.03-TS-S1HT.4010

REQ-11.01.03-TS-S1NR.4005

REQ-11.01.03-TS-S1HT.5010

P11.01.04


FOC-007 Improved flight crew briefing through integration of digital data


REQ-11.01.03-TS-S1HT.1005

REQ-11.01.03-TS-S1HT.1010

REQ-11.01.03-TS-S1TS.1030

REQ-11.01.03-TS-S1HT.4005

REQ-11.01.03-TS-S1HT.4010

REQ-11.01.03-TS-S1NR.4005

tbd. by

P11.01.04


SWIM-APS-02b Consumption of Aeronautical Information services for Step 2


REQ-11.01.03-TS-S1HT.1005

REQ-11.01.03-TS-S1HT.1010

REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1NR.4005

REQ-11.01.03-TS-S1HT.4020

REQ-11.01.03-TS-S1HT.5005

tbd. by

P11.01.04


AOC-ATM-17 UDPP Departure system for FOC


REQ-11.01.03-TS-S1ST.2005

REQ-11.01.03-TS-S1ST.2010

REQ-11.01.03-TS-S1ST.2015

REQ-11.01.03-TS-S1ST.2020

REQ-11.01.03-TS-S1NR.3005

REQ-11.01.03-TS-S2NR.2005

tbd. by

P11.01.04



14 of 25


AOC-ATM-18 FOC adaptation to support UDPP


REQ-11.01.03-TS-S1ST.2005

REQ-11.01.03-TS-S1ST.2010

REQ-11.01.03-TS-S1ST.2015

REQ-11.01.03-TS-S1ST.2020

REQ-11.01.03-TS-S1NR.3005

REQ-11.01.03-TS-S2NR.2005

tbd. by

P11.01.04


FOC-005 FOC capabilities to participate in UDPP


REQ-11.01.03-TS-S1ST.2005

REQ-11.01.03-TS-S1ST.2010

REQ-11.01.03-TS-S1ST.2015

REQ-11.01.03-TS-S1ST.2020

REQ-11.01.03-TS-S1NR.3005

REQ-11.01.03-TS-S1NR.3015

REQ-11.01.03-TS-S2NR.2005

tbd. by

P11.01.04


SWIM-APS-02a Consumption of Aeronautical Information services for Step 1


REQ-11.01.03-TS-S1TS.2005

REQ-11.01.03-TS-S2NR.3005

REQ-11.01.03-TS-S1HT.4020

REQ-11.01.03-TS-S1HT.5005

tbd. by

P11.01.04


PRO-095 Airline Operational Procedures for modifying RBT including agreed TTA to accommodate selected priorities


REQ-11.01.03-TS-S1TS.2005

tbd. by

P11.01.04

P11.01.05 as these projects were developing the prototypes and


15 of 25


performing the validation exercises.

SWIM.INFR-05a High Criticality SWIM Services infrastructure Support and Connectivity.


REQ-11.01.03-TS-S1AF.4005

tbd. by

P11.01.04


AIMS-06 Ground-Ground AIS provision to ASM

REQ-11.01.03-TS-S1HT.4020 tbd. by

P11.01.04


AIMS-19a Aeronautical Information system is interfaced to receive and distribute aeronautical information electronically to/from ANSPS systems.

REQ-11.01.03-TS-S1HT.5005 tbd. by

P11.01.04


ENB02.01 SWIM REQ-11.01.03-TS-S2NR.1015

tbd. by

P11.01.04

P11.01.05 as these projects were


16 of 25


developing the prototypes and performing the validation exercises.

WOC enablers:

AOC-ATM -14

Upgrade of WOC system to handle improved OAT flight plans

Manifold requirements within the D16

AOC-ATM - 15 Upgrade of Wing Ops System Technical Architecture to provide Military Mission Trajectory Services


SWIM-APS-02a Consumption of Aeronautical Information services for Step 1


SWIM-APS-04a Consumption of ATFCM Information Services for Step 1


METEO-03

Provision and monitoring of real-time airport weather information, Step 1


METEO-04b Generate and provide MET information services relevant for Airport and final approach related operations, Step 1


METEO-05b Generate and provide MET information relevant for TMA and En-route related operations, Step 1


MIL-0106 Wing Operations Centre Mission Support System enhanced to support the CDM process


AOC-ATM-20 Sharing of trajectory data between AOC/WOC and the ATM world using B2B web services


MIL-0502 Upgrade of military ground systems to allow bi-directional exchanges with non-military IP networks



17 of 25


P11.01.03 contributed with its system requirements and the architecture of FOC and WOC to the following SESAR solutions:

More Direct Routes for Cross-Border operations

o Free Route through the use of direct routings (SJU reference #32/Release 5)

Europe-Wide Free Routing

o Free routing for flights both in cruise and vertically-evolving above a specific flight level in low-to-medium density airspace (SJU reference #33/Release 5)

More Efficient Airspace Management

o Automated support for dynamic sectorisation (SJU reference #66/Release 2)

Advanced Flexible Use of Airspace

o Variable profile military reserved areas and enhanced civil-military collaboration (SJU reference #31/Release 5)

Airline Input improves departure output

o User-driven priorisation process (UDPP) departure (SJU reference #57/Release 4)

Improved planning thanks to enriched data

o Extended flight plan (SJU reference #37/Release 5)

The benefits of digital data

o Digital integrated briefing (SJU reference #34/Release 5)

Learning to SWIM

o Initial system-wide information management (SWIM) technology solution (SJU reference #46/Release 5)

Allowing Users to choose their route

o User Preferred Routing (SJU reference #65/Release 2)

1.2 Project achievements

In order to ensure a comprehensive and coherent development and maintenance of the FOC and WOC Architecture and the requirements for the technical systems, the work within P11.01.03 achieved following results:

TAD:

o The TAD includes the systematic description of the functionality of the systems supporting the operations of civil and state airspace users based on the experience reached at the end of SESAR 1. The TAD fits to the architecture of the other ATM systems represented in the European ATM Architecture (EATMA) and described in the Architecture Description Document (ADD). It describes the technical architecture of the FOC and WOC systems and the depiction of their context within the European ATM System and allow to understand their external relations to the other ATM systems. The TAD document contains a breakdown of all systems in Functional Blocks. The relations between the Functional Blocks of each system are depicted also mainly for the system supporting the flight operations.

EFPL:


18 of 25


o Detailed Technical Specification for the EFPL representing an extension to the ICAO 2012 flight plan. The EFPL provides the 4D trajectory as calculated by the flight planning system to generate the operational flight plan. The usage of the EFPL helps to reduce the number of flight plan rejections resulting from the very low resolution of the ICAO 2012 flight plan. Furthermore, the EFPL improves the demand and capacity calculations of the European Network Manager (NM) due to the availability of accurate trajectory data received from the airspace users. Thanks to the EFPL, ATM and flight crew can get the same profile information from the flight operations centre (FOC).

Free Route:

o Technical Specification for free route trajectories enabling airspace users with maximum of freedom for their flight operations within a free route environment. This allows much more flexible routing options, providing the base for airspace users to be substantially more cost or fuel-efficient.

AFUA

o Technical Specification for Advanced Flexible use of Airspace concepts, which allows aircraft operators as part of the flight monitoring functionality to be informed in real-time about airspace status changes. Using FOC systems, aircraft operators can carry out impact assessments from their perspective and submit new flight plans optimised for the new situation. Technical aspect for the access of the B2B information (EAUP, EUUP, SUUP) are considered. Strong involvement of state airspace users within all AFUA activities was guaranteed through intensive WOC contribution.

UDPP

o Technical Specification for UDDP concepts, providing more flexibility to airspace users in case of delays on departure, en-route and arrival in capacity constrained situations (for example due to adverse weather or industrial action). Airspace users can significantly reduce delay costs, by prioritising flights in anticipation of capacity constrained situations.

Digital Briefing

o Technical Specification for AIM/digital briefing concept using digitally enhanced pre-flight briefing services. The technical specification covers SWIM-compliant digitally enhanced flight briefing services requirements, comprising aeronautical information (based on Digital NOTAM) and selected meteorological information.

Improved OAT Flight plan

o TS for all aspects of State Airspace Users mission: Maintaining Aeronautical data for planning, airspace reservation & CDM, OAT Flight Plan generation and update as well Mission monitoring.

For all individual civil Technical Specifications the system requirements are combined in the single document / deliverable D24.

The corresponding prototypes and validation exercise contribution are described within P11.01.04 and P11.01.05.

1.3 Project Deliverables The following table presents the relevant deliverables that have been produced by the project.

Reference Title Description


19 of 25


D01 Step 1 Use Cases and System Requirements for FOC system

Technical Specification (TS) for FOC Step 1

Initial technical specification for STEP 1 including the first functional blocks of the FOC architecture.

D02 Technical Specification (TS) of the Flight Operations Centre for the Trajectory Management within SESAR Step 2

BMT (FOC) Step 2 Technical Specification

This technical specification gathers the technical requirements for the development of the Flight Operations Centre within SESAR Step 2, only focussing on the Trajectory Management throughout all ATM stakeholders. The document was produced in the context of Validation Exercise EXE-11.01.05-VP-775 addressing the trajectory negotiation between the FOC (AU) and ATC. The TS describes requirements for a negotiation process between ATC & FOC domains that is based on the provision of airspace volumes that shall be avoided by the flight (provided by ATC) and trajectories that satisfy those planning constraints (provided by the FOC). This specification is integrated into a single FOC TS document describing the complete system - D24.

D06 AFUA (FOC) Step 1 Technical Specification (TS)

This TS describes the technical requirements applicable to the FOC-related systems that have to be implemented to support validation exercise EXE07.05.04-VP-710. Exercise VP-710 aimed at demonstrating the feasibility of updating the real time airspace status automatically into the NM systems, delivering a closed CDM process between ASM support systems, NM systems, ATC systems and FOC systems. It was developed as standalone document, but it can best be used also in combination with D24 summarizing all requirements from FOC perspective as closure documents from P11.01.03.

D18 Updated WOC Step 1 TAD (BMT, AFUA, iOATFPL)

This TAD describes the Technical Architecture of the technical system WOC in the context of SESAR System Architecture (ADD) viewed from State Airspace User's perspective. The TAD contains the Step 1 system architecture for enhanced WOC functions, which have been derived from the operational processes provided by P11.01.01 in it's Step 1 sections of the DOD. This document identifies Functional Blocks and its enablers, which are relevant for WOC capabilities of this project phase. This system architecture together with the requirements of the technical specification (TS) formed the basis for development of the prototype(s) of project P11.01.04, which were used to verify the scope and functionality of the enhanced WOC system

D20 WOC Step 2 TAD (BMT, AFUA, iOATFPL) for Step 2

The TAD contains the Step 2 system architecture for enhanced WOC functions, which have been derived from the operational requirements provided by P11.01.01 in its Step 2 section of the DOD. This


20 of 25


document identifies Functional Blocks and its enablers which are relevant for WOC capabilities of this project phase. For WOC systems, the focus of Step 2 is on enhanced data exchange with the Network Manager via SWIM.

D16 Update Technical Specification Step 1 for WOC System (BMT, AFUA, iOATFPL

This technical specification includes a consolidated set of Technical Requirements including Interface Requirements for the State AU Wing Operations Centre (WOC) Technical System in Step 1. The scope of the requirements covers the functional blocks ‘Information and Communication Management’, ‘Flight Data Support Management’, ‘Flight Planning and Flight Operations Management’. This specification is based on dataset 15. From content point of view, the State AU Wing Operations Centre (WOC) Technical System provide for Step 1 a wider support of State Airspace Users’ processes by seamless digital exchange

D09 Technical Specification Step 2 as available for WOC System (BMT, AFUA, iOATFPL

D09 consists of 2 documents: 1. Technical Specification Step 1 for WOC System (BMT, AFUA, iOATFPL) 2. Technical Specification Step 2 as available for WOC System (BMT, AFUA, iOATFPL)

The purpose of this document is to provide a consolidated set of Technical Requirements including Interface Requirements for the WOC Domain System in Step 1. In accordance with the contract, the scope of the requirements is limited to the Functional Blocks ‘Information and Communication Management’, ‘Flight Data Support Management’, ‘Flight Planning and Flight Operations Management’. The requirements have been derived from the operational requirements for the WOC documented in the WOC INTEROP and WOC SPR documents considering the WOC OSED. 2. The purpose of this document is to provide a consolidated set of Technical Requirements including Interface Requirements for the WOC Domain System in Step 2. The requirements shall be derived from the operational requirements for the WOC documented in the WOC INTEROP and WOC SPR documents considering the WOC OSED.

D11 Final WOC Step 1 and Step 2, as available, Interoperability Requirements (INTEROP)

This INTEROP deliverable describes the interoperability requirements in the context of Step 1 and what is available from Step 2 V2 of the SESAR V&V Storyboard viewed from the WOC system and State Airspace user's perspective. It describes the interoperability requirements for interfacing a WOC with the NM, AMC and ATC systems, and other State Airspace Users facilities as Air Defence. The connection of the WOC with those systems enables the State Airspace User operations through all phases of the Mission Trajectory Lifecycle. It supports the State Airspace User during planning, filing and sharing of OAT Flight plan data / 4D Trajectories. It support Airspace booking and negotiation by interfacing


21 of 25


with the ASM support tool.

D21 Technical Specification Step 1 & Step 2 as available for FOC system (AIM)

This technical specification provides a set of Technical Requirements for the FOC system within AIM OFA. The specification was produced in context of Validation Exercise EXE-13.02.02-VP-461 addressing the providing of digital integrated briefing for pre-flight and in-flight use, for on-board electronic information devices for crews of Business and General Aviation. It includes requirements adressing the usability of the aeronautical and meteorological information presented to the pilots for all phases of flight, through the use of digital aeronautical and MET information.

D17 FOC System Interface Requirements Step 1 & Step 2 as available (AIM)

This technical specification describes the FOC interface requirements for the AIS data distribution by focussing on the process of the AIS data from the Data provider to the End user (AU) for the purpose of AIM OFA EXE-461prototype of AIS. In addition all interface requirements for FOC System stakeholders such as AIS Data producers (ATC, Authorities), FOC, D-NOTAM providers, EFB Applications providers, Airspace users are covered.

D22 FMS Weather Uplink Step 1 Technical Specification

This deliverables elaborated the main improvements consisting of the uplink of weather and temperature information from FOC to the FMS as an enabler for Reference Business Trajectory operations. With respect to the I4D, primary the descent phase of the flight was impacted to comply with Controlled Time of Arrival (CTA) accuracy and reliability requirements. Improved weather information improves computation of Estimated Time of Arrival (ETA) that are provided in the Extended Projected Profile (EPP). This specification provides functional requirements and the technical details of the interface between FOC and aircraft systems to enable the corresponding weather information uplink to the FMS.

D10 EFPL (FOC) Step 1 Technical Specification

This TS document includes primary aspects related to the Business Trajectory. The main part includes requirements that support the development of the FOC prototype systems that were needed to support the different trials within validation exercise EXE-07.06.02-VP-713. In summarize all requirements in reference to the EFPL and the extensive validations of 4D trajectories cooperating with the NM 4D system. This considers also the use of the FIXM format for the exchange of the business trajectory. It was developed as standalone document, but it can best be used also in combination with D24 summarizing all requirements from FOC perspective as closure documents from P11.01.03.

D13 Free Route (FOC) Technical Specification

The free route technical specification includes only aspects related to Free Route. It is dealing with requirements defined for the Free Route OSED and to support validation exercise EXE-04.03-VP797.


22 of 25


The focus of this document is on the processing of the information about the Free Routing Airspace by the FOC, the subsequent adapted trajectory planning process as well as the options to react to changes to the Free Routing Airspace environment. It was developed as standalone document, but it can best be used also in combination with D24 summarizing all requirements from FOC perspective as closure documents from P11.01.03. This deliverable focusses on defining the technical requirements necessary for the FOC to support the airspace users’ operations in a Free Route environment.

D24 Technical Specification Step 1 and Step 2 for FOC system (including IRS requirements

This key deliverable of P11.01.03 includes as single TS document all dependencies and interactions to the Functional Blocks of the FOC operation. This document can serve as a single general reference, summarizing all FOC requirements arising from SESAR1 based on the complete work experience from WP11.1. This Technical Specification facilitates in getting an overview of how the functional blocks are involved in the procedural and technical process and how they interact. The TS gives an overview of the grouping of requirements in accordance with the architecture and structure of the FOC. The structure of requirements is based on the functional block structure defined for the flight operations centre. Furthermore the TS gives an overview and description of the functional break down of the flight operations centre.

D25 Contribution to ADD Documents This document describes the contribution of P11.01.03 to the Architecture Description Documents with regard to the civil Airspace User’s aspects. Main input to the ADD includes aspects of the composition of the FOC System in Functional Blocks and the creation of the Civil AU Operations Centre Capability Configuration (separately from State AU Operations Centre CC). Furthermore, it considers the support of the modelling of the Flight Operations Centre in the EATMA repository as precondition for the creation of the diagrams for the FOC System Interfaces and the Civil AU OperationsCentre CC.

D19 Civil AU Operations Centre TAD This document is one of the key deliverables of P11.01.03. It contains a coverage of all relevant systems of the civil Airspace Users.The TAD includes a systematic description of the functionality of the FOC systems based on the experience reached at the end of SESAR 1. The TAD fits to the architecture of the other ATM systems represented in the European ATM Architecture (EATMA) and described in the Architecture Description Document (ADD). D19 describes the technical architecture of the FOC systems and their context within the European ATM System, and it allows to understand their external relations to the other ATM systems. The TAD document contains a breakdown of all


23 of 25


systems in Functional Blocks. The relations between the Functional Blocks of each system are depicted mainly for the system supporting the flight operations."

1.4 Contribution to Standardisation

The work within project P11.01.03 did not produce standards on its own, but it contributed to standardisation activities in following ways:

In SESAR, P11.01.03 worked together with projects in work package WP8 to address AIRM and ISRM needs. In particular, the new services for EFPL were coordinated together with Eurocontrol (P07.06.02) and included into ISRM 1.4

P11.01.03 contributed from FOC and WOC perspective to SWIM Systems Engineering deliverables by performing several reviews and giving the relevant input for this.

P11.01.03 contributed from FOC and WOC perspective to FF-ICE concepts in relation to the EFPL

P11.01.03 contributed from FOC and WOC perspective within SESAR to following standardisation groups:

o FIXM tech group, EATMA, Service Coordination group , 4D architecture study group.

1.5 Project Conclusion and Recommendations

Project P11.01.03 supported the prototype developments for P11.01.04 and all validation activities within P11.01.05 by providing all relevant technical requirements and the architecture environment. Especially the architecture description TAD for the Civil AU Operations Centre will be a basis input for SESAR2020 projects like PJ06, PJ07, PJ08, PJ09 and PJ18. It describes the Civil AU Operations Centre and its role within other ATM stakeholders.


24 of 25


2 References

[1] SESAR Programme Management Plan, Edition 03.00.01

[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] SESAR Solutions Catalogue, ISBN 978-92-9216-060-9, edition 2016

[5] D05 - Project Initiation Report WP 11.1.3, edition 00.01.00, 13.12.2011

[6] D01 - Step 1 Use Cases and System requirements for FOC/WOC system, edition 00.00.21, 25.02.2013

[7] D07 Technical Specification (TS) of the Flight Operations Centre for the Trajectory Management within SESAR Step 2, edition 00.01.00, 26.09.2014

[8] D09 - Technical Specification Step 1 for WOC System (BMT, AFUA, iOATFPL), edition 00.02.00, 30.07.2015

[9] D09 - Technical Specification Step 2 as available for WOC System (BMT, AFUA, iOATFPL), edition 00.01.00, 30.07.2015

[10] D10 - EFPL (FOC) Step 1 Technical Specification, edition 00.00.04, 14.09.2015

[11] D13 - Free Route (FOC) Technical Specification, edition 00.00.04, 15.09.2015

[12] D16 Update Technical Specification Step 1 & Step 2 as available for WOC system (BMT, AFUA, iOATFPL), edition 00.03.00, 25.09.2016

[13] D17 - FOC System Interface Requirements Step 1 & Step 2 as available (AIM), edition 00.00.03, 11.09.2015

[14] D18 - WOC Step 1 TAD (BMT, AFUA, iOATFPL), edition 00.01.01, 17.04.2014

[15] D18 - WOC Step 2 TAD (BMT, AFUA, iOATFPL), edition 00.01.00, 28..05.2014

[16] D18 - Updated WOC Step 1 TAD (BMT, AFUA, iOATFPL), edition 00.01.00, xx.09.2016

[17] D19 - Civil AU Operation Centre TAD, edition 00.01.00, 26.08.2016

[18] D20 - WOC Step 1 and 2 TAD (BMT, AFUA, iOATFPL), xx.09.2016

[19] D21 - Technical Specification Step 1 & Step 2 as available for FOC system (AIM), edition 00.00.05, 31.08.2015

[20] D22 - FMS Weather Uplink Step 1 Technical Specification, edition 00.01.00, 31.08.2015

[21] D24 - Technical Specification Step 1 and Step 2 for FOC systems including IRS requirements, edition 00.01.00, 02.09.2016

[22] D25 - Contribution to ADD Documents, edition 00.01.02, 01.07.2016

[23] D26 - Final Project Report, edition 1.0, 27.09.2016

https://www.atmmasterplan.eu/


25 of 25


-END OF DOCUMENT-