Si FDPS

PDF Version

Si ATM stand-alone Flight Data Processing System

Si FDPS is a stand-alone flight plan data processing system and highly adaptable so that it can be integrated into most ATM environments. It supports Air Traffic Control flight data operations for En-route (ACC), Approach (APP) and Tower (TWR) control functions. It was first launched for operational use in 2001 and since then has been upgraded with new functionalities as defined and requested by the ATM community.

Overview functionality

The following functionality is included in the Si FDPS:

  • Reception and sending of ATS and weather messages via the AFTN, either manually or automatically.
  • Fully automatic flight plan data processing with route analysis and trajectory prediction
  • Reception and sending of data for CNS/ATM functions
  • Support for CPDLC, e.g. departure clearance delivery by means of data link
  • Support for Flexible Use of Airspace (FUA)
  • Paperless and strip less controller HMI
  • Strip printing functionality if requested
  • Presentation of CNS/ATM based surveillance data
  • Presentation of flight plan tracks
  • On Line Data Interchange (OLDI) and AIDC
  • Monitoring aids with conformance monitoring and reminder handling
  • Medium Term Conflict Detection (MTCD)
  • Data exchange with external systems; e.g. FIDS, Billing system, adjacent FIRs, Meteorological system, Tower systems etc.

Tasks and operators

Si FDPS basically supports the following tasks:

  • Flight Plan Data Management
  • Air Traffic Control

The system provides data to the following operators:

  • Flight Data Assistants who will collect, maintain and distribute correct flight plan data based upon RPLs, information from the AFTN, OLDI and other sources.
  • ATC Controllers who will receive correct flight plan information and have the ability to update it, with correct times, route, level and other data, during the progress of flights through the airspace.

Flight plan data management

Handling of RPLs: RPLs can be searched, created, modified and deleted manually, but also handled automatically based upon the operator’s airline time schedules received on data media. Temporary changes and suspensions of flights are supported.

 

Handling of FPLs: FPLs are normally created automatically from RPLs or received from the AFTN. They can also be searched, created, modified and deleted manually. Received AFTN and OLDI messages are processed and checked automatically and produce updates to relevant FPLs.

 

Billing: Billing data is automatically collected and submitted to external systems at FPL termination.

Route Analysis: For RPLs and FPLs, route details are examined against the local airspace structure for compliance with ICAO rules. The airspace structure is defined by the system using known parameters.

Data Preparation: The system is easily adaptable to any operational environment by means of system parameters.

 

Flight Data Assistants: They have an efficient HMI to support editing, browsing, queue handling and specification of complex search criteria.

ATC functions

4D Trajectory Prediction: A trajectory describing the flight’s path in airspace along the cleared route is calculated with consideration to aircraft performance characteristics and current weather data. SID and/or STAR allocation is performed automatically. The trajectory’s coverage of ATC sectors determines the distribution of flight data to the working positions. The trajectory is continuously updated to reflect given clearances and position reports. These can be given verbally or via data link.

 

Traffic surveillance: Traffic is shown in a geographical window as flight symbols i.e. position symbols with labels. The shown geographical position reflects current position according to the trajectory. The type of position symbol indicates the data source and quality.

 

ATC tools: Monitoring Aids and Medium Term Conflict Detection developed strictly in accordance with EUROCONTROL specifications are available.

 

Meteorological data: is received, processed, stored and presented to controllers.

 

CNS/ATM: These functions are performed through a gateway connecting to an ARINC or SITA network. Functions to handle AFN logon/logoff, ADS contracts and CPDLC functions are available. Departure Clearances can be performed by means of data link.

 

Strip printing: is available on request. It is highly configurable regarding the strip layout, timing and printing criteria.

 

Controller HMI: The HMI is window driven and adapts to the recommendations of EUROCONTROL concerning paperless HMI with extensive use of flight list and label interactions.

Main operational features are:

  • The functionality supports ACC, APP and TWR operations
  • Traffic situation can be shown as “tracks” in a geographical window.
  • Flight plan data is presented and operator interaction is performed in lists and labels.
  • The design of these HMI objects is to present only the required data, however, additional data is easy to retrieve, with a click of the mouse
  • Lists and labels are specially designed to support control of the air traffic in a paperless environment.
  • Each flight plan is dynamically updated based upon controller input of clearances/instructions given verbally or as part of CPDLC. Input facilities are available in any of the flight’s HMI objects.
  • Internal co-ordination is performed silently through system functions, including that co-ordination between controllers in TWR and APP.
  • Coordination with adjacent centres is performed by means of OLDI/AIDC where such connections are available.
  • The dynamic handling of the operational configuration allows a highly flexible use of the airspace. Reconfiguration of sector jurisdiction is handled in a decentralised manner. The system supports on-line reclassification of sectors.

Technical Features

Commercial hardware and software

  • COTS workstations with monitor(s), keyboard and mouse
  • Fault-tolerant servers
  • Redundant LAN
  • Unix / Linux operating system
  • X Window / Motif
  • Application software is in C, C++ and ADA

General Design aspects

  • Client/server concept
  • Open system architecture
  • Distributed processing
  • Fault-tolerant software