Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 68 Next »

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

Status

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

  • Applicable implementation requirements

    CP1 requirements

    CP1 chapterCP1 extractsNotes
    TODO

    Clarifications from the SDP

    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.

    Business justification

    The eFPL content can be leveraged by the ANSPs in order to perform improved trajectory prediction for a variety of ATM functions. This would include (non exhaustive list):

    • Balancing demand against capacity more accurately
    • Providing complementary feedback in response to the distributed eFPLs, i.e. being able to fine-tune the 4DT portion applicable to their AOR;
      • See also Implementation Strategy for FPFDE NFPM, chapters 3.3 Pre-Departure Phase – Flight Planning and Filing and 4.1 Finalising the flight planning/filing phase with an Agreed Trajectory
    • Facilitating AUs’ adherence to their preferred trajectories as much as possible, leading to more efficient and sustainable flights.

    Which NM B2B R27 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 Publication Service in order to receive the eFPLs filed by the eAUs and accepted by NM.
    • Consuming the interface of the NM B2B Publication Service based on the synchronous Request/Reply MEP to manage the corresponding subscriptions.



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

    FF-ICE
    services

    FF-ICE Filing Serviceü(ü)(*)


    FF-ICE Flight Data Request Service
    ü


    FF-ICE Trial Service

    ü

    FF-ICE Data Publication Service


    ü
    FF-ICE Notification Service



    ü


    Which eFPL information will ANSPs receive?

    eAUs will file eFPL using the NM B2B Filing Service. NM will use the desired trajectory and the performance data provided by the eAU for the initial trajectory calculation. This profile will go through NM validation where some adjustment might be needed so that applicable restrictions are respected. It is the resulting eFPL with the agreed trajectory computed by the IFPS that will be distributed to ANSPs via the pub/sub.

    The eFPL distributed to ANSPs will therefore contain:

    • the agreed trajectory computed by the IFPS
    • the performance profile and take-off mass, as provided on input to NM by the eAU
    • TODO

    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.


    IdentifierTitleLevel of Implementation
    Requirements on the connection to NM B2B Services
    FFICE-REQ-001Signature of an agreement with NMMandatory
    FFICE-REQ-xxxAccess request to NM B2B Flight Management serviceMandatory
    FFICE-REQ-xxxAccess request to NM B2B Subscription Management serviceMandatory



    Requirements on the management of subscriptions to FF-ICE Information
    FFICE-REQ-xxxSubscription to relevant eFPLsMandatory



    Requirements on the development, testing and validation of NM B2B client applications
    FFICE-REQ-xxxDevelopment based on latest NM B2B releaseMandatory
    FFICE-REQ-xxxDevelopment and testing in PRE-OPSMandatory
    FFICE-REQ-xxxValidation for OPS usageMandatory



    Requirements on the usage of the FF-ICE information
    FFICE-REQ-xxxUse of GUFI for FF-ICE messages correlationMandatory
    FFICE-REQ-xxxUse of the performance profileRecommended
    FFICE-REQ-xxxUse of the take-off mass
    FFICE-REQ-xxxUse of weight information
    FFICE-REQ-xxxUse of the structured route informationMandatory
    FFICE-REQ-xxxUse of the expanded route information
    FFICE-REQ-xxxUse of selected trajectory point information







    Considerations about flight plan distribution to ANSPs in mixed-mode environment

    There will be a transition period where ANSPs will have to keep legacy and also receive eFPL, this transition period is yet to be defined but will be time limited.


    Guidance for Consuming the Flight Data Request Service, using the NM B2B services.

    Business justification

    CP1 mandates ANSPs to consume the eFPL via the Data Publication Service and to consume the Notification Service, using the NM B2B services. As a result, ANSPs will start receiving FF-ICE Messages relevant to their operations, including eFPLs filed by Airspace Users and approved by NM, and at a later stage FF-ICE Departure and Arrival Messages for the concerned flights. These messages will be pushed to ANSPs by the Publish/Subscribe interface of the NM B2B Services and will have to be correlated using the GUFI. In certain non-nominal situations, when for instance pushed messages expire before they are consumed by the client application, ANSPs might exceptionally receive FF-ICE Messages that cannot be correlated to an eFPL, or may be uncertain regarding the status of a given flight. In these situations, the ANSPs are expected to obtain the latest eFPL (& GUFI), or the latest flight status information, using of the Flight Data Request service provided by NM.

    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
    Trial
    Service

    NM B2B
    Flight Management
    Service

    NM B2B
    Notification
    Service
    NM B2B
    Subscription Management
    Service
    FF-ICE
    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.


    IdentifierTitleLevel of Implementation
    Requirements on the connection to NM B2B Services
    FFICE-REQ-001Signature of an agreement with NMMandatory
    FFICE-REQ-xxxAccess request to NM B2B Flight Data Request serviceMandatory






    Requirements on the development, testing and validation of NM B2B client applications
    FFICE-REQ-xxxDevelopment based on latest NM B2B releaseMandatory
    FFICE-REQ-xxxDevelopment and testing in PRE-OPSMandatory
    FFICE-REQ-xxxValidation for OPS usageMandatory






    Requirements on the usage of the FF-ICE information
    FFICE-REQ-xxxUse of GUFI for FF-ICE messages correlation









    Guidance on the requirements

    TODO





    Guidance for Consuming the Notification Service using the NM B2B services

    Business justification

    TODO

    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 the 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
    Trial
    Service

    NM B2B
    Flight Management
    Service

    NM B2B
    Notification
    Service
    NM B2B
    Subscription Management
    Service
    FF-ICE
    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


    IdentifierTitleLevel of Implementation
    Requirements on the connection to NM B2B Services
    FFICE-REQ-001Signature of an agreement with NMMandatory
    FFICE-REQ-xxxAccess request to NM B2B Notification serviceMandatory
    FFICE-REQ-xxxAccess request to NM B2B Flight Management serviceMandatory
    FFICE-REQ-xxxAccess request to NM B2B Subscription Management serviceMandatory



    Requirements on the development, testing and validation of NM B2B client applications
    FFICE-REQ-xxxDevelopment based on latest NM B2B releaseMandatory
    FFICE-REQ-xxxDevelopment and testing in PRE-OPSMandatory
    FFICE-REQ-xxxValidation for OPS usageMandatory



    Requirements on the management of subscriptions to FF-ICE Information
    FFICE-REQ-xxxSubscription to relevant notifications of departure and arrivalMandatory






    Requirements on the usage of the FF-ICE information
    FFICE-REQ-xxxUse of GUFI for FF-ICE messages correlationMandatory










  • No labels