Versions Compared

Version Old Version 8 New Version Current
Changes made by

LEPORI Hubert

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


warningtitleWORK IN PROGRESS - content should not be used
Excerptpanel
borderColor
black
borderStyle
Status
dashed


Excerpt

This

handbook

section 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

Which NM B2B services to use?

Consume the Filing Service using the NM B2B servicesmeans
  • Consuming the NM B2B Filing Service to file eFPLs and get immediately a submission response and a filing status.
    • Subscribing to the Pub/Sub interface of the NM B2B Flight Management 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
      - - - - - - - - - - - - >
      |  makes use of
      |    Information servicesNM B2B
    Filing ServiceNM B2B
    Flight Data Request Service

    NM B2B
    Flight Management Service
    &
    Subscription Management Service

    NM B2B
    Trial ServiceNM B2B
    Notification ServiceBusiness
    servicesFF-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

    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


    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 Consume the eFPL via the Data Publication Service using the NM B2B servicesConsuming NM's Filing Service.


    IdentifierTitleLevel of Implementation
    Requirements on the connection to NM B2B Services

    		REQ-FFICE-
    REQ
    007 -
    001Signature of an agreement with NM
    Consumption of NM Filing Service by impacted AUsMandatory
    FFICE-

    		REQ-
    xxxAccess request to NM B2B Filing serviceMandatory
    FFICE-
    REQ-xxxAccess request to NM B2B Flight Management service and NM B2B Subscription Management service.Mandatory Conditional (*)FFICE-REQ-xxxAccess request to NM B2B Flight Data Request serviceMandatory Conditional (*)FFICE-REQ-xxxAccess request to NM B2B Trial serviceOptional(*) satisfying one of the two requirements is mandatory.Requirements on the management of subscriptions to FF-ICE Information
    FFICE-REQ-xxxSubscription to relevant eFPLsMandatoryRequirements on the content of the FF-ICE informationFFICE-REQ-xxxProvision of a performance profile in the eFPLFFICE-REQ-xxxProvision of a speed schedule in the filed eFPLFFICE-REQ-xxxProvision of wind vectors in the filed eFPLFFICE-REQ-xxxProvision of take-off mass in the filed eFPLFFICE-REQ-xxxProvision of weight information in the filed eFPLFFICE-REQ-xxxProvision of an expanded route in the filed eFPLFFICE-REQ-xxxProvision of selected trajectory points in the filed eFPLRequirements on the development, testing and validation of NM B2B client applicationsFFICE-REQ-xxxDevelopment based on latest NM B2B releaseMandatoryFFICE-REQ-xxxDevelopment and testing in PRE-OPSMandatoryFFICE-REQ-xxxValidation for OPS usage
    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