Applicable implementation requirements

CP1 requirements

Sub-AF 5.1.6 General

Clarifications on the CP1 wording:

1. routes generation and validation: this relates to the Expanded Route as described in the FF-ICE/R1 Implementation Guidance Manual, Appendix E3. (An expanded route contains every significant point that is in the route. While a Route has only the entry and exit point from each ATS route traversed, the expanded route contains each significant point traversed along each ATS route.)
2. 4D trajectory: this relates to the Trajectory as specified in the FF-ICE/R1 Implementation Guidance Manual, Appendix B-3 and Appendix E-3.
3. flight performance data: this relates to the Route/Trajectory Specific Performance Data as described in the FF-ICE/R1 Implementation Guidance Manual, Chapter 10.3, table 2. It comprises Climb and descent speed schedule, Take-off mass and Performance climb and descent profile.
4. flight status: this relates to the Operator Flight Plan Version and the Filing Status (ACCEPTABLE, NON-ACCEPTABLE) as described in the FF-ICE/R1 Implementation Guidance Manual, Appendix B. This also relates to NM Revalidation status (COMPLIANT, ADVISORY or SUSPENDED).
5. flights lists: the notion of "Flights Lists" is not described in the FF-ICE/R1 Implementation Guidance Manual. It is therefore considered that this particular CP1 wording relates related to flight plan identification based on GUFI/IFPLID.
6. detailed flight data: This relates to the eFPL content that is not new compared to what is currently exchanged, i.e. this relates to the flight plan data items already exchanged in FPL 2012 format.

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.

Guidance for Consuming the eFPL via the Data Publication Service using the NM B2B services.

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?

• Subscribing to the Pub/Sub interface of the NM B2B Publication Service in order to receive the eFPLs filed by the eAUs and accepted by NM.
• Consuming the interface of the NM B2B Publication Service based on the synchronous Request/Reply MEP to manage the corresponding subscriptions.

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

NM B2B
Filing
Service

NM B2B
Publication
Service

FF-ICE
services

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 Data Publication Service using the NM B2B services.

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

TODO

Guidance for Consuming the Flight Data Request Service, using the NM B2B services.

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.

Which NM B2B R27 services to use?

Consume the Flight Data Request Service, using the NM B2B services means

• Consuming the NM B2B Flight Data Request Service for retrieving the latest eFPL in order to resolve flight status uncertainties or FF-ICE message correlations problems. 

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 for Consuming the Notification Service using the NM B2B services

Business justification

TODO

Which NM B2B R27 services to use?

Consuming the Notification Service using the NM B2B services means

• Consuming the NM B2B Notification Service for submitting FF-ICE Departure and Arrival messages for flights for which an eFPL has been filed.

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

Identifier	Title	Level of Implementation
Requirements on the connection to NM B2B Services
FFICE-REQ-001	Signature of an agreement with NM	Mandatory
FFICE-REQ-xxx	Access request to NM B2B Notification service	Mandatory
FFICE-REQ-xxx	Access request to NM B2B Flight Management service	Mandatory
FFICE-REQ-xxx	Access request to NM B2B Subscription Management service	Mandatory
Requirements on the development, testing and validation of NM B2B client applications
FFICE-REQ-xxx	Development based on latest NM B2B release	Mandatory
FFICE-REQ-xxx	Development and testing in PRE-OPS	Mandatory
FFICE-REQ-xxx	Validation for OPS usage	Mandatory
Requirements on the management of subscriptions to FF-ICE Information
FFICE-REQ-xxx	Subscription to relevant notifications of departure and arrival	Mandatory
Requirements on the usage of the FF-ICE information
FFICE-REQ-xxx	Use of GUFI for FF-ICE messages correlation	Mandatory