Handbook for AUs

Owned by LEPORI Hubert
Last updated: 2024 Jun 17 by WILSON Scott

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

Status

WORK IN PROGRESS - content should not be used
Full table of contents

Overview

Family 5.6.1 – Flight Information Exchange comprises five FF-ICE/R1 Services provided by NM. Two of them must be consumed by the AUs () within the geographical scope.

ServiceService Provider Service Consumer 
Filing Service NMAUs
Flight Data Request ServiceNMANSPs
Notification Service NMANSPs 
Data Publication Service NMANSPs
Trial ServiceNMAUs Recommended


Consuming NM's Filing Service

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.

Conformity Checklist

The following table makes reference to the requirements that need to be satisfied in order for an ANSP to achieve the goal Consuming NM's Filing Service.


IdentifierTitleLevel of Implementation
Requirements on the connection to NM B2B Services

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

REQ-FFICE-aaa - Obtaining NM B2B certificate enabling eFPL filing and cancellationMandatory

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

REQ-FFICE-bbb - Obtaining NM B2B certificate enabling the use of the trial service.Mandatory Conditional (*)
Information Exchange Requirements

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













Working Draft