DataDistribution

The flight plan data distribution ensures that each client is provided with the latest up-to-date flight plan information detailing the fol-lowing information:
• General flight plan information
• Clearances
• 4D-Trajectory
• Airspace crossing & sector sequence information
• Entry & Exit coordination data for the current leg
• Current (under-control or first) and next sector conditions
• Basic correlation information
Note that the current implementation of the service only includes the coordination information related to the current leg . Downstream leg information may be provided at the same time by another service or by extending the definition of the current data type (see section Error! Reference source not found.), but this is considered out-of-scope of the ADaaS project. For the 4D-Trajectory, airspace crossing and sector sequence information, the complete flight within the considered system’s AoI will be covered.

The SectorSpecific data distribution ensures that each client is provided with the latest up-to-date OPS sector-specific information for a flight detailing the following information:
• Sector status (normal, skipped, bypassed, etc.)
• Entry, Internal & Exit coordination data for the OPS sector for which information is distributed.
• Intra-sector dialogue information
• Event trigger information (for display purposes) for the OPS sector t
Important: the service will emit all sector-specific data for all flights over the service. It is the clients responsibility to filter out the relevant messages for him. The rationale of using such an approach is that it allows the usage of topics (multicast) at a later stage in the project without changing the client side functionality.

This service provides all subscribed clients with all detected deviations (Lateral, Vertical and Longitudinal) between the trajectories cleared data and the track. Additionally, it provides an automatic re-routing proposal when available.
The service is implemented by means of the FpmMessage. Conformance monitoring information is only provided for SFPLs, which are under-control and not in MANUAL sub-state. Re-routing information may already be received for SFPLs, which have been coordi-nated at entry (e.g. ACT received at the server, or manual coordination performed) and are not yet-under-control of the local centre.

This service provides all subscribed clients with all detected deviations (Lateral, Vertical and Longitudinal) between the trajectories cleared data and the track. Additionally, it provides an automatic re-routing proposal when available.
The service is implemented by means of the FpmMessage. Conformance monitoring information is only provided for SFPLs, which are under-control and not in MANUAL sub-state. Re-routing information may already be received for SFPLs, which have been coordi-nated at entry (e.g. ACT received at the server, or manual coordination performed) and are not yet-under-control of the local centre.

The flight bright distribution service provides the means to highlight a flight within for the own OPS sector based on SSR Code(s) “SSR Bright” and/or ModeS callsign(s) “ModeS bright”, and within own or to other OPS sectors (internal/external) based on callsign(s) “flightplan bright”.
The service is implemented by means of the FlightBrightMessage. The message is distributed to the own OPS sector (case of bright for SSR code, ModeS code, or flightplan bright for the own OPS sector) or to another OPS sector (case of flightplan bright to another OPS sector); in other words message distribution is “OPS sector oriented”.
At initialisation, actual bright information for the OPS sector is distributed. Per OPS sector there can be a maximum of 20 requests for flight bright.

The sectorisation distribution service ensures that each client is provided with the latest up-to-date sectorisation information residing at the server. Basically, the following information is distributed:
• Sectorisation pattern: contains the sectorisation pattern (i.e. unique identifier for each sectorisation) selected for each sector group.
• Sector composition: composition contains the list of airspace volumes and basic sectors composing each flight sector (see section Error! Reference source not found. for more information on the concept).
• Sector consolidation: contains the list of flight sectors consolidated into each OPS sector (see section Error! Reference source not found. for more information on the concept).
• Sector allocation: contains the list of flight sectors allocated to each internal/external centre.

The service provides the OPS sector with the information related to reservation of a free manual-assignable SSR code sequence described in section Error! Reference source not found..
The service is implemented by means of the SsrCodeMessage. The message is distributed to the own OPS sector only.

The meteorological information distribution service aims to provide all operational sectors with the latest:
• Wind & temperature forecast information extracted from the external world for a range of different levels,
• Airport related meteorological information received from the external world from the following sources:
o METAR and METAR COR
o SPECI and SPECI COR
• QNH, transition level and transition altitude information for airports

This service is implemented by means of two messages:
• WindForecastMessage, containing the wind & temperature forecast information.
• AirportMeteoMessage, containing the airport related infor-mation.

The map distribution service aims to provide requesting clients with the latest information of map data. A distinction is made between static, semi-dynamic and dynamic maps:
• Static: It is defined offline, and their contours cannot be modified on-line. Textual elements and/or other display elements may be modified.
• Semi-dynamic: It is defined offline, and their contours can be modified on-line. Textual elements and/or other display elements may be modified.
• Dynamic: They are created on-line. All of their contents may be modified.

The system mode distribution service provides to all connected & subscribed clients the following FDPS system information:
• System: Primary or Fallback
• System mode: Operational or Test mode
• System sub-mode: Authorised or unauthorised
• Link status: ON or OFF (link between Primary and Fallback)
• MTCD Status: ON or OFF
• MTCD Time Horizon
• FDPS degradation level
• FDPS SW and adaptation data version
FDPS coordinate projection parameters