Applicable implementation requirements

CP1 requirements

Sub-AF 5.1.6 General

Sub-AF 5.1.6 System requirements

"ATM systems operated by stakeholders referred to in point 5.3 must enable the use of the flight information exchange services."

Clarification of "ATM Systems" from EU 2018/1139

Chapter 1, Article 3 Definitions

3.1.   General

ATM/ANS systems and ATM/ANS constituents providing related information to and from the aircraft and on the ground shall be properly designed, produced, installed, maintained, protected against unauthorised interference and operated to ensure that they are fit for their intended purpose.

The systems and procedures shall include in particular those required to support the following functions and services:

(a)

Airspace management;

(b)

Air traffic flow management;

(c)

Air traffic services, in particular flight data processing systems, surveillance data processing systems and human-machine interface systems;

(d)

Communications including ground-to-ground/space, air-to-ground and air-to-air/space communications;

(e)

Navigation;

(f)

Surveillance;

(g)

Aeronautical information services; and

(h)

Meteorological services.

Clarifications from the SDP

The SESAR Deployment Programme explains that ANSP shall:

• Consume the eFPL via the Data Publication Service using the NM B2B services in support of information Exchange of FF-ICE;
• Consume the Flight Data Request Service, using the NM B2B services in support of information Exchange of FF-ICE;
• Consume the Notification Service using the NM B2B services in support of information Exchange of FF-ICE.

The next chapters provides ANSPs with guidance to achieve these goals.

Overview

Family 5.6.1 – Flight Information Exchange comprises five FF-ICE/R1 Services provided by NM. Three of them must be consumed by the ANSPs within the geographical scope.

Consuming NM's Data Publication Service

Business justification

The eFPL content can be leveraged by the ANSPs in order to perform improved trajectory prediction for a variety of ATM functions. This would include (non exhaustive list):

• Balancing demand against capacity more accurately
• Providing complementary feedback in response to the distributed eFPLs, i.e. being able to fine-tune the 4DT portion applicable to their AOR;
  
  • See also Implementation Strategy for FPFDE NFPM, chapters 3.3 Pre-Departure Phase – Flight Planning and Filing and 4.1 Finalising the flight planning/filing phase with an Agreed Trajectory
• Facilitating AUs’ adherence to their preferred trajectories as much as possible, leading to more efficient and sustainable flights

For details, go to the page Use Cases.

Which NM B2B R27 services to use?

• .

  - - - - - - - - - - - - >
  |  makes use of
  |
  |

NM B2B
Filing
Service

NM B2B
Publication
Service

FF-ICE
services

Which eFPL information will ANSPs receive?

eAUs will file eFPL using the NM B2B Filing Service. NM will use the desired trajectory and the performance data provided by the eAU for the initial trajectory calculation. This profile will go through NM validation where some adjustment might be needed so that applicable restrictions are respected. It is the resulting eFPL with the agreed trajectory computed by the IFPS that will be distributed to ANSPs via the pub/sub.

The eFPL distributed to ANSPs will therefore contain:

• the agreed trajectory computed by the IFPS
• the performance profile and take-off mass, as provided on input to NM by the eAU
• TODO

Conformity Checklist

The following table summarises the requirements that need to be satisfied in order for an ANSP to achieve the goal Consume the eFPL via the Consuming NM's Data Publication Service using the NM B2B services.

Considerations about flight plan distribution to ANSPs in mixed-mode environment

Consuming

NM's Flight Data Request Service

Business justification

CP1 mandates ANSPs to consume the eFPL via the Data Publication Service and to consume the Notification Service, using the NM B2B services. As a result, ANSPs will start receiving FF-ICE Messages relevant to their operations, including eFPLs filed by Airspace Users and approved by NM, and at a later stage FF-ICE Departure and Arrival Messages for the concerned flights. These messages will be pushed to ANSPs by the Publish/Subscribe interface of the NM B2B Services and will have to be correlated using the GUFI. In certain non-nominal situations, when for instance pushed messages expire before they are consumed by the client application, ANSPs might exceptionally receive FF-ICE Messages that cannot be correlated to an eFPL, or may be uncertain regarding the status of a given flight. In these situations, the ANSPs are expected to obtain the latest eFPL (& GUFI), or the latest flight status information, using of the Flight Data Request service provided by NM.

Conformity Checklist

The following table summarises the requirements that need to be satisfied in order for an ANSP to achieve the goal Consuming NM's Flight Data Request Service.

Consuming NM's Notification Service

Business justification

TODO

Conformity Checklist

The following table summarises the requirements that need to be satisfied in order for an ANSP to achieve the goal Consuming NM's Notification Service

Conformity Checklist

The following table summarises the requirements that need to be satisfied in order for an ANSP to achieve the goal Consume the Flight Data Request Service, using the NM B2B services.

Guidance on the requirements

Guidance for Consuming the Notification Service using the NM B2B services

Business justification

TODO

Conformity Checklist

The following table summarises the requirements that need to be satisfied in order for an ANSP to achieve the goal Consume the Notification Service using the NM B2B services