Status
This handbook gives guidance to help AUs satisfy the CP1 requirements in relation to FF-ICE/R1.
Introduction
The SESAR Deployment Programme explains that Airspace Users shall:
- Consume the Filing Service using the NM B2B services in support of information Exchange of FF-ICE.
The next chapters provides AUs with guidance to achieve this goal.
Guidance for Consuming the Filing Service using the NM B2B services
Business justification
By consuming the Filing Service, AUs will be able to share more detailed trajectory information and perform negotiations based on known constraints, thus offering opportunities to optimise flight operations earlier and more accurately.
AUs consuming the Filing Service and operating entirely within the IPFS Zone will also be in position to start defining a potential sunset date for removing their ability to support the legacy FPL exchanges.
Which NM B2B services to use?
Consume the Filing Service using the NM B2B services means
- Consuming the request/reply interface of the NM B2B Filing Service to file / update / cancel eFPLs and get immediately a submission response and a filing status.
- Subscribing to the Pub/Sub interface of the NM B2B Filing Service in order to be notified of the changes in ePFL acceptance occurring any time after the filing
OR
Consuming the NM B2B Flight Data Request service in order to retrieve the changes in ePFL acceptance occurring any time after the filing
Although not strictly required, consuming the NM B2B Trial Service should be considered as well. The NM B2B Trial Service allows to test out alternative trajectories without committing to them and enables to assess the feasibility of alternative trajectories before submitting a change to an eFPL. This service works similarly to the request/reply interface of the NM B2B Filing Service, except that Trial Request data is not retained by NM system. A stakeholder understanding how the request/reply interface of the NM B2B Filing Service works to file eFPLs will de facto understand how to use the NM B2B Trial Service. Consuming the NM B2B Trial Service in addition to the NM B2B Filing Service is therefore expected to be a straightforward and low-cost development enabling AU to improve the quality of information submitted to the Filing Service.
- - - - - - - - - - - - > | Information services | ||||||
NM B2B | NM B2B Flight Data Request Service | NM B2B Trial Service | NM B2B | NM B2B Notification Service | NM B2B Subscription Management Service | ||
|---|---|---|---|---|---|---|---|
| Business services | FF-ICE Filing Service | ü | (ü)(*) | (ü)(*) | |||
| FF-ICE Flight Data Request Service | ü | ||||||
| FF-ICE Trial Service | ü | ||||||
| FF-ICE Data Publication Service | ü | ü | |||||
| FF-ICE Notification Service | ü | ü | ü | ||||
(*) at least one of the two options.
Conformity Checklist
The following table makes reference to 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 Filing service | Mandatory |
| FFICE-REQ-xxx | Access request to NM B2B Subscription Management service. | Mandatory Conditional (*) |
| FFICE-REQ-xxx | Access request to NM B2B Flight Data Request service | Mandatory Conditional (*) |
| FFICE-REQ-xxx | Access request to NM B2B Trial service | Recommended |
| (*) satisfying one of the two requirements is 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 content of the FF-ICE information | ||
| FFICE-REQ-xxx | Provision of a performance profile in the eFPL | |
| FFICE-REQ-xxx | Provision of a speed schedule in the filed eFPL | |
| FFICE-REQ-xxx | Provision of wind vectors in the filed eFPL | |
| FFICE-REQ-xxx | Provision of take-off mass in the filed eFPL | |
| FFICE-REQ-xxx | Provision of weight information in the filed eFPL | |
| FFICE-REQ-xxx | Provision of an expanded route in the filed eFPL | |
| FFICE-REQ-xxx | Provision of selected trajectory points in the filed eFPL | |