Versions Compared

Version Old Version 54 New Version 55
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 describes the use cases related the eFPL usage by ANSPs.

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
absoluteUrltrue

Convention

Each ANSP Use Case (UC) is detailed in a table with the following structure.

NameName of the UC, used for mnemonic and readability purposes.
Identifier

Identifier of the UC, formed as follows:

  • For a nominal Use Case: FFICE-UC-ANSP-NOM-###
  • For a non-nominal Use Case: FFICE-UC-ANSP-NN-###
ActorsThe actor(s) involved in the UC. Can be an operational role (e.g. ATCO), an FF-ICE Service or a system (e.g. FDPS).
PreconditionsCondition(s) that must be fulfilled before the UC can happen.
TriggerThe event that causes the UC to happen.
DescriptionThe description of the UC.
Postconditions/OutcomeThe description of the results of the UC.
BenefitsA description of the value of the UC in terms of operational and/or technological enhancements.
Requirement MappingThe list of requirements that the UC relate to.
Example(s)Concrete example(s) that materialise(s) the UC.



Overview


Content of
the distributed eFPL

UC

Identifiers

Data CategoryData Item
Flight IdentificationGUFI (blue star)

Use cases (ANSPs)

Use cases (ANSPs)

Aircraft Identification
Flight Status

Operator Flight Plan Version (blue star)Use cases (ANSPs)

Use cases (ANSPs)

Revalidation Status (blue star)
Revalidation Status Explanation (blue star)
Flight Characteristics







Flight Rules
Type of Flight
Special Handling
Flight Plan Originator
Remarks
Operator
Equipment and Capabilities
Supplementary Information Source
Required Runway Visual Range
Aircraft Characteristics






Total number of aircraft
Registration
Aircraft Address
SELCAL Code
Mode A Code
Number and type of aircraft
Wake Turbulence Category
Aircraft Approach Category
Departure/Destination Data





Departure Aerodrome
Destination Aerodrome
Estimated Off-Block Time
Departure Airport Slot Identification (blue star)
Destination Airport Slot Identification (blue star)
Departure Runway (blue star)
Destination Runway (blue star)
Alternates

Alternate Destination Aerodrome(s)
Alternate Take-Off Aerodrome(s)
Alternate En-Route Aerodrome(s)
Desired Route/Trajectory (blue star)
Agreed Route/Trajectory (blue star)Use cases (ANSPs)
           Route/Traj. Group


Aircraft Take-off Mass (blue star)

Use cases (ANSPs)

Use cases (ANSPs)

Requested Cruising Speed
Requested Cruising Level
Total Estimated Elapsed Time
General Flight Constraint (blue star)
         Route/Traj. Element

















Along Route Distance (blue star)
Route Element Start PointUse cases (ANSPs)
Route to Next Element
Modified Route Indicator (blue star)
Route Truncation Indicator (blue star)
Requested Change
Route/Trajectory Constraints (blue star)
Trajectory Point (blue star)


            Geo Position (blue star)
            Time (blue star)
            Predicted Airspeed (blue star)
            Predicted Ground Speed (blue star)
            Wind Vector (blue star)
            Assumed Altimeter Setting (blue star)
            Temperature (blue star)
            Trajectory Point Property (blue star)
Planned Delay
Weight at Point (blue star)
          Route/Traj. Aircraft PerformancePerformance Profile (blue star)

Use cases (ANSPs)

Speed Schedule (blue star)Use cases (ANSPs)
Route to Revised DestinationRevised Destination
Route String to Revised Destination
Dangerous GoodsDangerous Goods Information (blue star)
AIRACAIRAC Reference (blue star)
Supplementary InformationFuel Endurance
Persons on Board
Emergency Radio
Survival Capability
Life Jacket Characteristics
Aircraft Colour and Markings
Pilot in Command
Dinghies
Remarks
Other European ItemsRoute Text
Ifps Identifier
Stay Information
AO What-If ReRoute Indicator
Replacement Flight Plan Indicator







Nominal Use Cases

Anchor
FFICE-UC-ANSP-NOM-001
FFICE-UC-ANSP-NOM-001

FFICE-UC-ANSP-NOM-001 - Use of GUFI for FF-ICE Publication Messages association

Expand
Name

Use of GUFI for FF-ICE Publication Messages association

IdentifierFFICE-UC-ANSP-NOM-001
Actors

Main: ANSP System

Other: NM Publication Service, ANSP B2B client application

Preconditions
  • the NM Publication Service is consumed by the ANSP B2B client application
Trigger

An FF-ICE Publication Message is received by the ANSP B2B client application.

Description

When the trigger for the publication message is the first distribution of the eFPL agreed by NM, the GUFI is stored together with the rest of the associated flight data. Message association is irrelevant as this is the first message received about that flight.

For all the other cases, for instance when the trigger for the publication message is a flight plan update, a flight plan cancellation or a change of Filing status following a flight plan re-evaluation by NM, the GUFI is used to associate the received Ffice Publication message to the correct flight.

Postconditions/Outcome
BenefitsPerform better association of received information with a specific flight.
Requirement Mapping
Example(s)

Anchor
FFICE-UC-ANSP-NOM-002
FFICE-UC-ANSP-NOM-002

FFICE-UC-ANSP-NOM-002 - Checking the validity of the Operator Flight Plan Version

Expand
NameChecking the validity of the Operator Flight Plan Version
IdentifierFFICE-UC-ANSP-NOM-002
Actors

Main: ANSP

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Operator Flight Plan Version is provided by the AU in the filed eFPL
  • the Operator Flight Plan Version provided in the filed eFPL is shared by NM in the distributed eFPL
Trigger

A distributed eFPL is received by the ANSP.

Description

Upon receipt of the eFPL, the system checks that the value of the Operator Flight Plan Version is equal to or greater than that of the previous eFPL received for the same flight, and discards the received eFPL if this check fails.

Postconditions/Outcome
Benefits
Requirement Mapping
Example(s)

Anchor
FFICE-UC-ANSP-NOM-003
FFICE-UC-ANSP-NOM-003

FFICE-UC-ANSP-NOM-003 - Processing of the Aircraft Take-off Mass for trajectory computation

Expand
NameProcessing of the Aircraft Take-off Mass for trajectory computation
IdentifierFFICE-UC-ANSP-NOM-003
Actors

Main: ANSP FDPS

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Take-Off Mass is provided by the AU in the filed eFPL
  • the Take-Off Mass provided in the filed eFPL is shared by NM in the distributed eFPL
TriggerA distributed eFPL containing a Take-Off Mass is received by the ANSP.
Description

A take-off mass is received. It is used by the FDPS as a replacement of the current parameter (e.g. as a replacement of a static adapted BADA parameter).

Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-001, FFICE-REQ-INFO-013
Example(s)

Anchor
FFICE-UC-ANSP-NOM-004
FFICE-UC-ANSP-NOM-004

FFICE-UC-ANSP-NOM-004- Display of the Aircraft Take-off Mass to the ATCO

Expand
NameDisplay of the Aircraft Take-off Mass to the ATCO
IdentifierFFICE-UC-ANSP-NOM-004
Actors

Main: ATCO, ANSP

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Take-Off Mass and the Type of Aircraft are provided by the AU in the filed eFPL
  • the Take-Off Mass and the Type of Aircraft provided in the filed eFPL are shared by NM in the distributed eFPL
Trigger

A distributed eFPL containing a Take-Off Mass and the Type of Aircraft is received by the ANSP.

Description

A Take-Off Mass and a Type of Aircraft are received. The Take-Off Mass is displayed to the ATCO with an indication whether this is considered heavy for such an Type of Aircraft or not.

The ATCO can use this information to directly evaluate whether some rate of climb/descent can be made or not, without having to ask, thus saving frequency time.

Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-001, FFICE-REQ-INFO-013
Example(s)

Anchor
FFICE-UC-ANSP-NOM-005
FFICE-UC-ANSP-NOM-005

FFICE-UC-ANSP-NOM-005- Processing of the Performance Profile for trajectory computation

Expand
NameProcessing of the Performance Profile for trajectory computation
IdentifierFFICE-UC-ANSP-NOM-005
Actors

Main: ANSP FDPS

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Performance Profile is provided by the AU in the filed eFPL
  • the Performance Profile provided in the filed eFPL is shared by NM in the distributed eFPL
  • the Performance Profile provided in the distributed eFPL is received by the ANSP
Trigger

A distributed eFPL contaning a Performance Profile is received by the ANSP.

Description

A performance profile is received. It is composed of a climb profile and a descent profile, both expressed as a sequence of profile points each containing: distance, time duration, flight level or altitude, and optionally the true airspeed.

Upon receipt, the climb and descent profiles are compared with the relevant departure and arrival portions of the FDPS local trajectory assuming zero-wind, standard atmosphere and no constraint.

This comparison produces correction factors (in distance, time, level, speed...) that can be subsequently applied by the FDPS during the trajectory computation, as appropriate.

Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-002, FFICE-REQ-INFO-014
Example(s)

Anchor
FFICE-UC-ANSP-NOM-006
FFICE-UC-ANSP-NOM-006

FFICE-UC-ANSP-NOM-006- Processing of the Speed Schedule  for trajectory computation

Expand
NameProcessing of the Speed Schedule for trajectory computation
IdentifierFFICE-UC-ANSP-NOM-006
Actors

Main: ANSP FDPS

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Speed Schedule is provided by the AU in the filed eFPL
  • the Speed Schedule provided in the filed eFPL is shared by NM in the distributed eFPL
Trigger

A distributed eFPL containing a Speed Schedule is received by the ANSP.

Description
Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-003, FFICE-REQ-INFO-015
Example(s)

Anchor
FFICE-UC-ANSP-NOM-007
FFICE-UC-ANSP-NOM-007

FFICE-UC-ANSP-NOM-007- Use of the (Expanded) Route Element Start Points for trajectory computation

Expand
NameUse of the (Expanded) Route Element Start Points for trajectory computation
IdentifierFFICE-UC-ANSP-NOM-007
ActorsMain: ANSP FDPS

Other: NM Publication Service
Preconditions
  • the NM Publication Service is consumed by the ANSP
  • An Expanded Route is provided by the AU in the filed eFPL (package 2B or 2C)
  • An Expanded Route and the Route Text are provided by NM in the distributed eFPL
TriggerA distributed eFPL containing an Agreed Route/Trajectory with an Expanded Route is received by the ANSP.
Description

Upon receipt of the eFPL, the sequence of Route Element Start Points from the eFPL is used as follows by the FPDS:

  • OPTION 1: the FPDS no longer computes an expanded route from the Route Text, and uses instead the sequence of Route Element Start Points from the eFPL "as is";
  • OPTION 2: the FDPS still computes an expanded route from the Route Text, and then compares this computed expanded route with the expanded route from the distributed eFPL. The outcome of this comparison is then used by the FPDS to enhance the computed expanded route. For instance, expanded route points present in the eFPL but missing in the computed expanded route are added to the computed expanded route.
Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-004, FFICE-REQ-INFO-016
Example(s)

Non-Nominal Use Cases

FFICE-UC-ANSP-NN-001 - Display of the Operator Flight Plan Version to the ATCO

Anchor
FFICE-UC-ANSP-NN-001
FFICE-UC-ANSP-NN-001

Expand
NameDisplay of the Operator Flight Plan Version to the ATCO
IdentifierFFICE-UC-ANSP-NN-XXX
Actors

ATCO

ATC Systems, NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Operator Flight Plan Version is provided by the AU in the filed eFPL
  • the Operator Flight Plan Version provided in the filed eFPL is shared by NM in the distributed eFPL
  • the Operator Flight Plan Version is valid
Trigger

A distributed eFPL with a valid Operator Flight Plan Version is received by the ANSP

DescriptionThe Operator Flight Plan Version is displayed to the ATCO so that the ATCO is in a position to check with the pilot that the same information for the flight is used, if needed operationally.
Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-012, FFICE-REQ-INFO-022
Example(s)


FFICE-UC-ANSP-NN-002 - Display of the Agreed Route/Trajectory to the ATCO when radar contact has been lost

Anchor
FFICE-UC-ANSP-NN-002
FFICE-UC-ANSP-NN-002

Expand
NameDisplay of the Agreed Route/Trajectory to the ATCO when radar contact has been lost
IdentifierFFICE-UC-ANSP-NN-002
Actors

Main: ATCO, ANSP

Other: NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
  • the Agreed Route/Trajectory is shared by NM in the distributed eFPL
  • The distributed eFPL containing an Agreed Route/Trajectory is received by the ANSP
TriggerRadar contact is lost with the flight
Description

The agreed route/trajectory is displayed to the ATCO when radar contact is lost. This enables the ATCO to keep performing ATC and apply the appropriate procedural separation mechanisms.

Postconditions/Outcome
Benefits
Requirement MappingFFICE-REQ-INFO-016
Examples


FFICE-UC-ANSP-NN-003 - Processing of an FF-ICE Publication Message with unknown GUFI

Anchor
FFICE-UC-ANSP-NN-003
FFICE-UC-ANSP-NN-003

Expand
Name

Processing of an FF-ICE Publication Message with unknown GUFI

IdentifierFFICE-UC-ANSP-NN-001
Actors

Main: ANSP System

Other: NM Publication Service, NM Flight Data Request Service, ANSP B2B client application

Preconditions
  • the NM Publication Service is consumed by the ANSP B2B client application
Trigger

An FF-ICE Publication Message is received by the ANSP B2B client application with a GUFI that is not known to the ANSP. 

Description

In the case of an unknown GUFI, the latest eFPL agreed by NM is obtained through the use of the Flight Data Request service.

Postconditions/Outcome
Benefits
Requirement Mapping
Example(s)







Expand
titleWork Area / Old content

Use of eFPL for Visualisation

General Description

Several items of the eFPL can be displayed to various actors in an ACC for enhancing their situational awareness and satisfying additional information needs.

  1. Use of the eFPL data as an analysis tool – for learning purposes and training
  2. Visualisation of eFPL data as a Fall back mechanism, should the system encounter failure
  3. Visualisation of eFPL data enabling to perform ATC even when radar contact has been lost (Lack of contact with AU, procedural separation mechanisms)

Relevant eFPL content

These items include:

  • Agreed 4D Trajectory
  • Unconstrained Trajectory
Note

To be clarified: is this the desired trajectory captured in the filed eFPL, or the performance profile, which a zero-wind, standard atmosphere profile reflective of the flight capabilities and desired parameters.

  • Trajectory Change Points (TCP)
  • FPL2012 Field 15

Actors

  • Flight Data Assistant
  • Flow Manager
  • Supervisor
  • Coordination Controller
  • Executive Controller

Use of eFPL for Flow Management (Traffic Complexity Tools)

General Description


The information of the eFPL can be used in Flow- and Complexity Tools in order to improve the quality of the respective forecasts and the related planning for sector configurations and staff allocation.


Info
Quote from ICAO FF-ICE Guidance Material, Section “Implementation Strategy”
By taking the first step of accepting FF-ICE flight plans through the filing service, ASPs would gain access to more detailed trajectory information. This would be useful for strategic traffic flow management purposes, at the same time allowing ASPs to explore/develop other capabilities made possible by the additional trajectory information. ASPs will be able to gain experience in using the trajectory information and hence better build up their system capabilities for information processing, ……

Relevant eFPL content

  • Take-off Mass ( Would be used in EFD)

  • Performance data: performance profile, speed schedule ( Would be used in EFD)

  • Agreed 4D Trajectory

  • Trajectory Change Points (TCP)

  • FPL2012 Field 15

Actors

  • Flow Manager

  • Supervisor

Use of eFPL data in Core ATC system (FDPS)

General Description

The information of the eFPL can be used in various components of the core ATS-System, where flight plan information is used and needed. The mainly affected component would be the Flight Data Processing System (FDPS), but also other components could benefit directly or indirectly from eFPL information, e.g. Arrival Management Systems and Conflict Detection Tools

Relevant eFPL content

  • Take-off Mass:
    • Displaying the take-off mass to the ATCO with an indication whether this is considered heavy for such A/C type could give an indication on whether some ROCD can be made or not, without the ATCO having to ask, thus saving frequency time.
      • As an example, A320 is categorised as ”medium” but could be an actual ”heavy”
    • as input to the local trajectory computation
  • Performance data: 
    • Performance profile
    • Speed schedule
  • Agreed 4D Trajectory
  • Trajectory Change Points (TCP)
    • In today's operations, ANSP systems commonly ignore, or make assumptions on, level constraints and “clip them out”. This operationally leads to (1) clearances instructed by the ATCO (e.g. instructs FL350, while the clipped out level was FL300) and (2) sometimes intruders to our next partner. Especially if we know levels because of regulations, situation (2) would no longer occur. The information about the reason why a level constraint is present in the trajectory (for instance, PTR or regulation) will help avoid (2)
  • FPL2012 Field 15

Actors

  • Supervisor
  • Coordination Controller
  • Executive Controller






Use of the distributed eFPL by an ANSP

The data contained in the eFPL can be used by an ANSP in different ways:

ATC related

  • Several items of an eFPL can be displayed to various actors in an ACC (Flight Data Assistant, Flow Manager, Supervisor, Coordination Controller, Executive Controller) for enhancing their situational awareness and satisfying additional information needs. For instance:
    • Use of the eFPL data as an analysis tool – for learning purposes and training
    • Visualisation of eFPL data as a Fall back mechanism, should the system encounter failure
    • Visualisation of eFPL data enabling to perform ATC even when radar contact has been lost (Lack of contact with AU, procedural separation mechanisms)
  • The eFPL can be used in various components of the core ATS-System, where flight plan information is used and needed. The mainly affected component would be the Flight Data Processing System (FDPS), but also other components could benefit directly or indirectly from eFPL information, e.g. Arrival Management Systems and Conflict Detection Tools.

ATFM related

  • The information of the eFPL can be used in Flow- and Complexity Tools in order to improve the quality of the respective forecasts and the related planning for sector configurations and staff allocation, as acknowledged in the ICAO FF-ICE Implementation Guidance Manual, Section “Implementation Strategy”
    • By taking the first step of accepting FF-ICE flight plans through the filing service, ASPs would gain access to more detailed trajectory information. This would be useful for strategic traffic flow management purposes, at the same time allowing ASPs to explore/develop other capabilities made possible by the additional trajectory information. ASPs will be able to gain experience in using the trajectory information and hence better build up their system capabilities for information processing, …


The following table provides



Business UCs

Improve flight information presented to the ATCO

NameImprove flight information presented to the ATCO
Actors

Operational: ATCO

Systems: FDPS, NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
TriggerA distributed eFPL is received by the ANSP.
Description


related eFPL content UCs

Use of GUFI for Ffice Publication Messages correlation

Checking the validity of the Operator Flight Plan Version
Display of the Operator Flight Plan Version to the ATCO

Processing of the Aircraft Take-off Mass for trajectory computation by the FDPS
Display of the Aircraft Take-off Mass to the ATCO

Use of the (Expanded) Route Element Start Points for trajectory computation by the FDPS 

Processing of the Performance Profile for trajectory computation by the FDPS 

Processing of the Speed Schedule for trajectory computation by the FDPS 

...

Support ATCO in non-nominal situations

NameSupport ATCO in non-nominal situations
Actors

Operational: ATCO

Systems: FDPS, NM Publication Service

Preconditions
  • the NM Publication Service is consumed by the ANSP
TriggerA distributed eFPL is received by the ANSP.
Description


related eFPL content UCs

Use of GUFI for Ffice Publication Messages correlation

Display of the Agreed Route/Trajectory to the ATCO when radar contact has been lost

...