Embedded Files
The Ground module centralises the flight plan and surveillance data processing with advanced ATM features. The Ground module is able to support simulated and/or live traffic so that it can be used for both simulation and live experiment.
Description
Description
The Ground module is based on a client-server architecture, which eases function distribution across the platform and provides flexibility to integrate new components with minimal impact on the existing architecture. OASIS middleware is used in order to hide communication and distribution issues from the components and also shield the application from vendor specific implementations improving portability and interoperability.
Services Offered
Services Offered
Ground Module
Ground Module
The Ground module comprises the following components:
A flight-plan data processing component;
An airspace server (ASP) - centralises the distribution of airspace information to any Ground component. Baseline data is provided by IPAS, and updates (area activation, default runway in use) are provided by the appropriate Ground components;
A weather server (WEA) - centralises the distribution of weather information defined via a multi-layer and multi-volume model providing ISA modelisation of temperature, wind speed and direction;
An aircraft performances server (ACR) - centralises and distributes any information dealing with aircraft performance. On-line modification is not available;
A flight-plan generator (FPG) - initiates flight plans prepared by IPAS;
A flight-plan manager (FM) - manages system flight plans (using initial flight plan information provided by the FPG and trajectory updates provided by the TP). FM also collects the ATC constraints associated with the expanded route and creates the crossing boundary list. It provides the key point list composed of the 4D-profile information to the CWP;
A flight-plan manager probe (FM-PROBE) - manages the calculation of probe trajectories;
A trajectory predictor (TP) - simulates the progress of the aircraft along the 4D profile based on the current flight plan, ATC constraints, aircraft performances and predicted weather conditions. The 4D profile is updated to integrate controller orders and time deviation; and
A track deviation monitor (TDM) - checks the conformance of active flights against the correlated radar track. This includes a comparison of the predicted 4D profile with the observed actual trajectory. The track deviation is applied through a 4D-profile re-computation.
Surveillance Data Processing
Surveillance Data Processing
Surveillance data processing comprises:
An independent air surveillance (IAS) component - to manage (create, update, and delete) and distribute surveillance data (radar or satellite) tracks to any Ground component. This component is connected to the MASS sub-system in order to represent a simulated surveillance plot and resultant track; and
A DIS gateway - supports the routing of DIS messages to communicate with MASS or any DIS-compliant component.
Advanced ATM Features
Advanced ATM Features
Advanced ATM features include a safety net - to alert controllers of a potentially hazardous air situation in an effective manner and with sufficient warning time for appropriate avoiding action to be taken by the pilot. All safety net features are based on up-to-date air surveillance information. The algorithm is data driven: i.e. any parameters can be set off-line, including the inhibition area where the safety net will not be wholely or partly activated. The safety net includes:
A STCA (Short Term Conflict Alert) component - to warn the controller of any situation where the minimum separation distances between any pair of radar tracks is, or is predicted to be within a short look ahead time (usually 2 minutes), violated;
An MSAW (Minimum Safe Altitude Warning) component - warns the controller of any situation where a track is, or is predicted to be within a short look ahead time (usually 2 minutes), in collision with a ground hazard e.g. obstacles or high ground. The description of the terrain is based on French IGN data; and
An AWP (Area Proximity Warning) component - warns the controller of any situation where a track is, or is predicted to be within a short look ahead time (usually 2 minutes), flying into an area of reserved airspace.
Medium-Term Conflict Detection Features
Medium-Term Conflict Detection Features
Medium-term conflict detection features warn the controller of a predicted hazardous air situation based on extrapolated 4D aircraft profiles. The algorithm is data driven: i.e. any parameters can be set off-line, including the inhibition area where the medium-term conflict detection will not be wholely or partly activated. These include:
An MTCA (Medium-Term Conflict Alert) component; and
An MTCD (Medium-Term Conflict Detection) component - to warn the controller.
Page updated
Google Sites
Report abuse