ADMAR

from Wikipedia, the free encyclopedia

ADMAR ( A bgesetzte D ESCRIPTION of MA DAP R adardaten ) is a software used for emergency service is available (BOS) to coordinate and control of air traffic. It was the predecessor system to CIMACT .

ADMAR was able to record the civilian radar track data, position data and flight plans from various data sources available in European airspace , process them in an IT-based manner, combine them into an air situation image and display them with selected air traffic control functionalities.

history

ADMAR was developed and constantly updated by the European Organization for the Safety of Aviation (EUROCONTROL) on behalf of the Federal Ministry of Defense . Related to this are the previous versions ADKAR (remote display of KARLDAP radar data) and GAME ((GEADGE (German Air Defense Ground Environment) / ADKAR Message Exchange)).

ADMAR last version

With the last version, ADMAR 2000, the Luftwaffe operations command service (EinsFüDstLw) had a second air situation independent of the FüWES ARKONA at that time , which was ready for use as a backup system for the control of aircraft as part of flight safety . MADAP (Maastricht Automatic Data Processing System) and KARLDAP (Karlsruhe Automatic Data Processing System) served as ADMAR data sources.

use

ADMAR was developed exclusively for the German Air Force and was used in the stationary Control and Reporting Center (CRC) of the operational command areas. Other users were the NLFZ SiLuRa , Luftwaffeamt , PCC , AFSBw and JG 71 . The transition to CIMACT was also ordered by the IT-AmtBw . The Air Force Office, later the Air Force Material Command and finally the WaSysKdo Lw , were responsible for in-service support management.

Functionality

The civilian radar track data available at Maastricht UAC or in the area of DFS were transmitted to the ADMAR users and combined to form an aerial situation image. There, the flight plans of the aircraft were linked with the tracks of the air situation picture. ADMAR experienced increasing acceptance and ultimately became indispensable for the German Air Force.

Data transfer

The data transfer to the ADMAR applications took place directly via EUROCONTROL MAASTRICHT UAC, DFS KAARLSRUHE or direct data connection to the next DFS GmbH property . X25 data channels, ISDN or the AutoFüFmNLw were used as the transmission medium. For reasons of availability and to improve survivability, the data transfer of sensor data and flight plan data to the EinsFüDstLw took place separately via separate data connections. A data connection was usually sufficient for third-party users. Due to the comparatively low volume of air traffic, data rates of up to 64 kbit / s were also to be expected. Data connections for mobile use were NOT provided.

Model change ADMAR - CIMACT

ADMAR still had disadvantages in the last version, which required a qualitatively new approach to the overall design with particular emphasis. Examples of some disadvantages:

  • The proprietary software could not generally run on commercially available hardware ( COTS ).
  • The ADMAR Map Drawing Tool was out of date.
  • The user interface (HMI) had serious differences to civil air traffic control .
  • The user requirements for mobile use could not be met.
  • Lack of Mode S capability and limited "Radar data Recording and Replay" (RRR) functionality.

Since 2003, other countries, NATO , BMVg and BMI as well as German authorities and organizations with security mandates have been increasingly interested in the functionality of ADMAR. In addition, ADMAR was still indispensable in EinsFüDstLw. Therefore, there was no alternative to the further development, the integration of additional functionalities and finally the model change to CIMACT .

Web links