Handbook for ANSPs
Status
WORK IN PROGRESS - content should not be used
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.
Service | Service Provider | Service Consumer |
|---|---|---|
Filing Service | NM | AUs |
Flight Data Request Service | NM | ANSPs |
Notification Service | NM | ANSPs |
Data Publication Service | NM | ANSPs |
Trial Service | NM | AUs Recommended |
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.
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 Data Publication Service.
Identifier | Title | Level of Implementation |
|---|---|---|
Requirements on the connection to NM B2B Services | ||
|
|
|
|
|
|
|
|
|
Requirements on the management of subscriptions to FF-ICE Information | ||
|
|
|
|
|
|
Requirements on the development, testing and validation of NM B2B client applications |
| |
| Development based on latest NM B2B release |
|
| Development and testing in PRE-OPS |
|
| Validation for OPS usage |
|
|
|
|
Requirements on the usage of the FF-ICE information | ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
Identifier | Title | Level of Implementation |
|---|---|---|
Requirements on the connection to NM B2B Services | ||
|
|
|
|
|
|
|
|
|
|
|
|
Requirements on the development, testing and validation of NM B2B client applications | ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements on the usage of the FF-ICE information | ||
|
|
|
|
|
|
|
|
|
|
|
|
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
Identifier | Title | Level of Implementation |
|---|---|---|
Requirements on the connection to NM B2B Services | ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements on the development, testing and validation of NM B2B client applications | ||
|
|
|
|
|
|
|
|
|
|
|
|
Requirements on the management of subscriptions to FF-ICE Information | ||
|
|
|
|
|
|
|
|
|
Requirements on the usage of the FF-ICE information | ||
|
|
|
|
|
|
|
|
|