Versions Compared

Version Old Version 43 New Version 44
Changes made by

LEPORI Hubert

LEPORI Hubert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColorblack
borderStyledashed
Excerpt

This section gives guidance to help AUs satisfy the CP1 requirements in relation to FF-ICE/R1.

Table of Contents
maxLevel1
absoluteUrltrue
typeflat
separatorpipe

Warning
titleStatus
WORK IN PROGRESS - content should not be used
Panel
titleFull table of contents

Table of Contents

Applicable implementation requirements

CP1 requirements

CP1 chapterCP1 ExtractsNotes
Sub-AF 4.1.3 General

“FF-ICE (1) flight plan data (FF-ICE Release 1/Filing and trial services) must be used to enhance the quality of the planned trajectory information, thus enhancing flight planning and complexity assessments.”



Sub-AF 4.1.3 System requirements

“Airspace users’ and ANSP’s systems must support the exchange of FF-ICE Release 1 filing services, once available as set out in AF 5.1.6.”

AF4 deadline is December 2023, but this requirement leads to the AUs mandate to AF5 with a deadline of 31st December 2025.
Sub-AF 5.1.6 General

"Operational stakeholders must implement services that support the exchange of flight information using the SWIM yellow profile, as specified in the deployment programme:

(a) related to FF-ICE Release 1 Services:      
  - flight plan and routes generation and validation;
  - flight plans, 4D trajectory, flight performance data, flight status;
  - flights lists and detailed flight data;

See clarifications on this CP1 wording on page Handbook for ANSPs.

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.”


Clarifications from the SDP

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 R27 services to use?

Consume the Filing Service using the NM B2B servicesmeans

  • 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.


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

Information services

NM B2B
Filing
Service

NM B2B
Flight Data Request
Service		NM B2B
Trial
Service

NM B2B
Publication
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



ü

(*) if the interface of the NM B2B Filing Service based on the Publish/Subscribe MEP is NOT used

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.


IdentifierTitleLevel of Implementation
Requirements on the connection to NM B2B Services

Signature of an agreement with NMMandatory
Access request to NM B2B Filing serviceMandatoryAccess request to NM B2B Flight Data Request service

REQ-FFICE-007 - Consumption of NM Filing Service by impacted AUsMandatory


Mandatory Conditional (*)
Access request to NM B2B Trial service

Exchange of flight information - Flight status

Exchange of flight information - Flights listsExchange of flight information - Detailed flight data.

REQ-FFICE-XXX - Consumption of NM Trial Service by impacted AUsRecommended



(*) if the interface of the NM B2B Filing Service based on the Publish/Subscribe MEP is NOT used.
Requirements on the management of subscriptions to FF-ICE Information

Subscription to relevant eFPLsMandatory



Requirements on the development, testing and validation of NM B2B client applications

Development based on latest NM B2B releaseMandatory

Development and testing in PRE-OPSMandatory

Validation for OPS usageMandatory



Information Exchange Requirements
Exchange of flight information - Route and 4D trajectoryExchange of flight information - Flight Performance Data

REQ-FFICE-008 - Satisfying the ICAO IERs for the Filing Service (consumer side)Mandatory

REQ-FFICE-009 - Provision of an expanded route if the submitted eFPL

Mandatory Conditional (*)

REQ-FFICE-010 - Provision of trajectory information in the submitted eFPLMandatory Conditional (*)

REQ-FFICE-011 - Provision of performance data in the submitted eFPLMandatory Conditional (*)

REQ-FFICE-012 - Provision of the operator flight plan version in the submitted eFPLMandatory

REQ-FFICE-013 - Provision of GUFI in the submitted eFPLMandatory

REQ-FFICE-014 - Provision of flight data mandatory in FPL 2012 format in the submitted eFPLMandatory
Requirements on the ATM systems

REQ-FFICE-015 - Upgrade of all AUs/AROs ATM systems to use NM Filing ServiceMandatory