Status
This handbook gives guidance to help ANSPs satisfy the CP1 requirements in relation to FF-ICE/R1.
Introduction
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.
Which NM B2B services to use?
Consume the eFPL via the Data Publication Service using the NM B2B services means
- Subscribing to the Pub/Sub interface of the NM B2B Flight Management Service in order to receive the eFPLs filed by the eAUs and accepted by NM.
| - - - - - - - - - - - - > | makes use of | | Information services | |||||
| NM B2B Filing Service | NM B2B Flight Data Request Service | NM B2B | NM B2B Trial Service | NM B2B Notification 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 | ü | ü | ||||
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 | Request access to NM B2B Flight Management service and NM B2B Subscription Management service. | Mandatory |
| Requirements on the management of subscriptions to FF-ICE Information | ||
| FFICE-REQ-xxx | Subscription to relevant eFPLs | 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 performance profile | Recommended |
| FFICE-REQ-xxx | Use of the speed schedule | |
| FFICE-REQ-xxx | Use of the wind vectors | |
| FFICE-REQ-xxx | Use of the take-off mass | |
| FFICE-REQ-xxx | Use of weight information | |
| FFICE-REQ-xxx | Use of the structured route information | |
| FFICE-REQ-xxx | Use of the expanded route information | |
| FFICE-REQ-xxx | Use of selected trajectory point information | |
| 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 |
Guidance for Consuming the Flight Data Request Service, using the NM B2B services.
Which NM B2B services to use?
Consume the Flight Data Request Service, using the NM B2B services means
- Consuming the NM B2B Flight Data Request Service for...
| - - - - - - - - - - - - > | makes use of | | Information services | |||||
| NM B2B Filing Service | NM B2B Flight Data Request Service | NM B2B | NM B2B Trial Service | NM B2B Notification 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 | ü | ü | ||||
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 |
|---|---|---|
Guidance for Consuming the Notification Service using the NM B2B services
Which NM B2B 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.
- Subscribing to Pub/Sub interface of the NM B2B Flight Management Service in order to receive notifications of departures and arrivals of flights for which an eFPL has been filed.
| - - - - - - - - - - - - > | makes use of | | Information services | |||||
| NM B2B Filing Service | NM B2B Flight Data Request Service | NM B2B | NM B2B Trial Service | NM B2B Notification 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 | ü | ü | ||||
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 |
|---|---|---|