Status
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 Consume the eFPL via the Data Publication 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 Publication service | Mandatory |
| Requirements on the management of subscriptions to FF-ICE Information | ||
| FFICE-REQ-xxx | Subscription to relevant eFPLs | 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 usage of the FF-ICE information | ||
| FFICE-REQ-xxx | Use of GUFI for FF-ICE messages correlation | Mandatory |
| FFICE-REQ-xxx | Use of the take-off mass | ... |
| FFICE-REQ-xxx | Use of the performance profile | |
| ... | ||
| FFICE-REQ-xxx | Use of selected trajectory point information | Mandatory |
| FFICE-REQ-xxx | Use of the expanded route information | ... |
| ... | ||
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.
- - - - - - - - - - - - > | Information services | |||||
NM B2B | NM B2B Flight Data Request Service | NM B2B Trial Service | NM B2B | NM B2B Notification Service | ||
|---|---|---|---|---|---|---|
FF-ICE | FF-ICE Filing Service | ü | (ü)(*) | |||
| FF-ICE Flight Data Request Service | ü | |||||
| FF-ICE Trial Service | ü | |||||
| FF-ICE Data Publication Service | ü | |||||
| FF-ICE 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.
| 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 Flight Data Request 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 usage of the FF-ICE information | ||
| FFICE-REQ-xxx | Use of GUFI for FF-ICE messages correlation | |
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.
TO BE CLARIFIED - should this cover as well the subscription to the Pub/Sub interface of the NM B2B Flight Management Service or NM B2B Publication Service in order to receive notifications of departures and arrivals of flights for which an eFPL has been filed?
- - - - - - - - - - - - > | Information services | |||||
NM B2B | NM B2B Flight Data Request Service | NM B2B Trial Service | NM B2B | NM B2B Notification Service | ||
|---|---|---|---|---|---|---|
FF-ICE | FF-ICE Filing Service | ü | (ü)(*) | |||
| FF-ICE Flight Data Request Service | ü | |||||
| FF-ICE Trial Service | ü | |||||
| FF-ICE Data Publication Service | ü | |||||
| FF-ICE 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 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 |